api(coverage): reconcile typed handler routes with the refreshed Redis Cloud OpenAPI spec

[joshrotenberg]

Summary

Refreshing the bundled OpenAPI fixture and adding executable route coverage checks surfaced a concentrated set of typed-route mismatches between the current client implementation and the upstream Redis Cloud spec.

What the new coverage check found

With the refreshed fixture:

• 89 OpenAPI paths
• 137 schemas
• 151 HTTP operations

The typed handler inventory currently shows:

• 29 spec operations with no matching typed handler path
• 22 typed handler routes that do not match any current OpenAPI path

Concentrated mismatch areas

Most of the drift is in connectivity and Active-Active path shapes:

• Private Service Connect
• Transit Gateway invitations/attachments
• Active-Active peerings
• Active-Active PrivateLink deletes/disassociate flows
• subscription resource tags

Examples of missing current-spec routes

• PUT /subscriptions/{subscriptionId}/resource-tags
• GET /subscriptions/{subscriptionId}/transitGateways/invitations
• GET /subscriptions/{subscriptionId}/regions/{regionId}/transitGateways
• POST /subscriptions/{subscriptionId}/regions/peerings
• DELETE /subscriptions/{subscriptionId}/regions/{regionId}/private-link

Examples of client routes that no longer match the spec

• GET /subscriptions/{subscriptionId}/tgw/shared-invitations
• POST /subscriptions/{subscriptionId}/transitGateways/attachments
• GET /subscriptions/{subscriptionId}/private-service-connect/endpoints
• DELETE /subscriptions/{subscriptionId}/regions/private-service-connect

Relevant files

• tests/openapi_route_coverage.rs
• tests/fixtures/openapi_unsupported_routes.txt
• tests/fixtures/openapi_non_spec_routes.txt

Acceptance criteria

• reduce the allowlist by reconciling typed handler paths with the current spec
• add or fix missing typed handlers where the API is supported but not modeled yet
• remove legacy/non-spec route shapes or document compatibility handling if both must remain
• keep the route coverage allowlists as small, intentional exceptions rather than a long-term inventory of drift

[joshrotenberg]

Route-reconciliation progress landed in draft PR #71.

This pass corrected the spec-backed Active-Active VPC peering routes, Transit Gateway invitation/attachment routes, added missing PrivateLink connection-disassociate + Active-Active delete support, and added PUT /subscriptions/{subscriptionId}/resource-tags.

The executable OpenAPI coverage drift dropped from 29 unsupported-spec operations / 22 non-spec handler routes to 11 / 11.

What remains is mostly PSC-oriented path/signature cleanup plus any deeper request/response harmonization we want to do as part of the broader refresh.