meta: refresh redis-cloud-rs for consistency, coverage, and release health

[joshrotenberg]

Goal

Give redis-cloud-rs a thorough refresh so the crate is clean, internally consistent, release-healthy, and defensible in its claim to cover the Redis Cloud REST API.

Existing open issues to fold into the refresh

• docs: OpenAPI spec deltas - fields missing from official spec #40 docs: OpenAPI spec deltas - fields missing from official spec
• Python package publish failing #48 Python package publish failing
• docs(python): align from_env secret error with supported env vars #58 docs(python): align from_env secret error with supported env vars
• fix(request): send request body when deleting AA subscription regions #59 fix(request): send request body when deleting AA subscription regions
• docs(readme): update stale crate version in install example #60 docs(readme): update stale crate version in install example

New refresh issues

• refactor(types): consolidate shared task/tag/link models and normalize task status typing #64 refactor(types): consolidate shared task/tag/link models and normalize task status typing
• api(consistency): finish harmonized handler surface across remaining domains #65 api(consistency): finish harmonized handler surface across remaining domains
• python(parity): define and close the gap between Rust client and Python bindings #66 python(parity): define and close the gap between Rust client and Python bindings
• test(openapi): add executable coverage checks between client handlers and bundled spec #67 test(openapi): add executable coverage checks between client handlers and bundled spec
• packaging(python): sync python crate version and lockfile with the Rust crate #68 packaging(python): sync python crate version and lockfile with the Rust crate
• spec(fixtures): refresh bundled cloud_openapi.json from the live Redis Cloud spec #69 spec(fixtures): refresh bundled cloud_openapi.json from the live Redis Cloud spec

Suggested execution order

1. Land the straightforward correctness/doc fixes first (docs(python): align from_env secret error with supported env vars #58, fix(request): send request body when deleting AA subscription regions #59, docs(readme): update stale crate version in install example #60)
2. Refresh packaging/versioning state for Python (Python package publish failing #48, packaging(python): sync python crate version and lockfile with the Rust crate #68)
3. Refresh the vendored spec and tighten coverage checks (spec(fixtures): refresh bundled cloud_openapi.json from the live Redis Cloud spec #69, test(openapi): add executable coverage checks between client handlers and bundled spec #67, docs: OpenAPI spec deltas - fields missing from official spec #40)
4. Finish API and type harmonization in the Rust crate (refactor(types): consolidate shared task/tag/link models and normalize task status typing #64, api(consistency): finish harmonized handler surface across remaining domains #65)
5. Expand or explicitly scope Python parity (python(parity): define and close the gap between Rust client and Python bindings #66)

Definition of done for the refresh

• no known request-shape correctness gaps remain in the shared client layer
• the vendored OpenAPI fixture is current enough to drive coverage checks
• coverage claims are backed by executable validation, not just docs
• shared types and handler naming are consistent across the crate
• Python packaging/versioning is release-stable
• README / rustdoc / Python docs reflect the actual supported surface

[joshrotenberg]

Deep review — 2026-05

Completed a four-axis review (API coverage / type correctness / mock test coverage / rustdoc coverage). Headlines:

• Path coverage is genuinely 100% (151/151 spec ops, allowlists really are empty). Existing tests/openapi_route_coverage.rs machinery is what test(openapi): add executable coverage checks between client handlers and bundled spec #67 asked for — it's effectively done; suggest closing test(openapi): add executable coverage checks between client handlers and bundled spec #67 once we add a couple of follow-ups (assert path-parameter names, lint that typed handlers exist where spec promises non-Value).
• Type fidelity is the dominant defect. Spec enums in types.rs are dead code; almost every handler uses Option<String>. Date-times are String. Spec oneOf unions collapsed to flat all-Optional structs. The TaskStateUpdate dedup work in refactor(types): consolidate shared task/tag/link models and normalize task status typing #64 is correctly scoped — extending below.
• Several real bugs not covered by existing issues — filed individually:
  • FixedDatabaseHandler::list() returns broken wrapper (missing subscription field)
  • GET /tasks deserialization is inverted; silently returns Vec::new() for the API's actual {tasks: [...]} shape
  • VPC peering create body sends awsRegion/gcpProjectId/networkName vs spec's region/vpcProjectUid/vpcNetworkName
  • Database.activated should be activatedOn; silent data drop
  • PaymentMethod.credit_card_ends_with typed i32, real responses are String
  • private_link 14 methods + VPC/TGW deletes return Value instead of TaskStateUpdate
• Tests: 288 pass, 0 fail — but 4 are dead-letter (mount mocks, never call handler). cost_report (exported, on-spec) has zero tests. ~25% of public methods untested. No malformed-response test exists. No task-polling round-trip test.
• Rustdoc: cargo doc --no-deps -- -D missing_docs aborts with 378 errors. 1/205 methods has # Errors. ~13% have # Examples. ConnectivityHandler's 14 delegation methods have zero docstrings despite being recommended in lib.rs's VPC peering example.

Stale lib.rs

• Quick Start uses legacy get_subscription_databases(123, None, None) rather than the harmonized list(123) alias added later in the file
• "API Keys (Typed)" section calls get_current_account() (wrong method)
• "Prefer typed handlers" advice contradicted by lib.rs's own VPC peering example using post_raw

What's getting filed

New child issues for items not covered by #40 / #59 / #64 / #65 / #67 / #69. Higher-tier work (full doc pass, full test backfill, stringly-typed enum migrations) gets filed as we reach those tiers.

Backing per-axis reports stored locally; happy to land them as docs/audit-2026-05/ if useful.