ENG-2597: Promote stlc-generated python SDK (Stainless cutover)

[aburkard]

What

Promote the stlc-generated python SDK from python-sdk-staging onto main, replacing the Stainless-hosted generation pipeline. This is the python analogue of the proven go cutover (hyperspell-go #4/#5/#6).

Diff (audited clean — mirrors go)

• API (identical OAS snapshot to go's latest sync): add Conversation.title; expand connections.revoke docstring (202 Accepted + background Temporal purge, idempotent per app/user/provider); regenerated test fixtures.
• De-Stainless'd: README MCP badges now use npx @hyperspell/hyperspell-mcp instead of the Stainless-hosted hyperspell.stlmcp.com; .stats.yml dropped the Stainless spec URL + hashes.
• Version: pinned to the manifest's 0.38.0 (staging ships a 0.0.1 placeholder — stamped back to avoid a version regression).
• Preserved: CHANGELOG.md, .release-please-manifest.json, release-please-config.json, .github/ untouched. No deletions.

Residual stainless strings remain only in dev/CI tooling (pkg.stainless.com preview-install CDN, $STAINLESS_OPENAPI_SPEC_URL mock-server env fallback) — gen-controlled, not customer-facing, same as go.

⚠️ HOLD — do not merge yet

Sequencing (python publishes to PyPI, so higher-stakes than go — order matters to avoid a double-publish):

1. Let go's release PR (hyperspell-go chore(internal): codegen related update #6) merge + tag first — validates the release-please→tag path end-to-end.
2. Close the stale Stainless release PR release: 0.39.0 #112 ("release: 0.39.0") first — so there is never a window where both it and our release PR are open and could each publish to PyPI.
3. Merge this promote PR (content sync).
4. Add .github/workflows/release-please.yml (separate PR, mirrors hyperspell-go feat(api): api update #5) using PRODUCTION_REPO_TOKEN.
5. Our release-please opens a fresh release: x.y.z PR → merging that is the single, gated PyPI publish.

🤖 Generated with Claude Code

[linear-code]

ENG-2597

[firetiger-agent]

Firetiger has created a monitoring plan for this PR.

View monitor

[entelligence-ai-pr-reviews]

---

Confidence Score: 5/5 - Safe to Merge

Safe to merge — this PR promotes a Stainless-generated Python SDK cutover (ENG-2597) and the automated review found zero issues across all 8 changed files. The PR achieves a clean SDK promotion with no logic bugs, security concerns, or correctness issues identified. All changed files were fully reviewed and passed without any substantive feedback.

Key Findings:

• All 8 changed files were reviewed and no issues of any severity were identified — neither logic errors, missing validations, nor style nits.
• The PR scope is a well-defined SDK promotion (stlc-generated Python SDK cutover), which is a common, low-risk operation when the generated code is clean and passes automated review.
• No pre-existing unresolved comments were carried into this PR, meaning the codebase context is clean going into this merge.
• Zero critical, significant, or medium-severity issues were flagged by heuristic analysis, confirming the generated SDK code is structurally sound.