feat(api)!: sync generated SDK from staging

[aburkard]

Promotes the generated SDK from the staging buffer to this production repo.

• Source: hyperspell/python-sdk-staging@cafa7d065818039fba629a81ec2e43c3a97c79e8 (ref main)
• Promoted by: https://github.com/hyperspell/hyperspell/actions/runs/33723173859
• Excluded (production-owned): CHANGELOG.md, release-please manifest/config, the release-please/publish/release-doctor workflows, and version stamps (kept at 0.39.0; release-please bumps them on release).

Merging hands off to release-please: it will open a release PR computing the next version from this PR's conventional-commit message — that release PR is the human gate for the actual publish. Amend the commit type (fix: / feat!:) before merging if the change warrants a different bump.

A re-dispatch of the promote workflow force-pushes this branch, superseding this PR's content in place.

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}

[aburkard]

Compatibility note: this removes the generated Context Documents client surface and adds read-only Entities (list/get/search) plus normalized Live source operations. The Context Documents HTTP routes are not being removed or changed; Hyperspell-owned clients continue to use them directly, and existing installed SDK versions continue to work. The breaking marker is for consumers that upgrade and compiled against those generated methods.

[entelligence-ai-pr-reviews]

EntelligenceAI PR Summary

This PR promotes a generated SDK from staging and substantially changes the public API surface. It removes the existing context-document, tree, digest, and configuration resources and replaces them with entity and live-source APIs, including synchronous, asynchronous, raw-response, streaming, pagination, and model support. Documentation and embedded OpenAPI fixtures are updated accordingly, while generated API tests are replaced with entity and live endpoint coverage. Because this is a breaking SDK change with extensive model and resource additions/removals, compatibility and generated-schema correctness warrant broad review.

---

Review Scorecard

Dimension	Rating	Basis
Code Quality	●●●●● 5/5 — Excellent	no critical/significant findings — rated Excellent
Blast Radius	High	live is referenced in 3 other file(s), touches persisted data / migrations, infra / deploy / config, 47 file(s) / ~4819 line(s) changed (size only — not a blast signal)
Merge Confidence	●●●●○ 4/5 — Mostly Safe	code quality 5/5 × High blast radius

Safe to merge despite the High blast radius — the generated SDK replacement is internally consistent and no correctness, security, robustness, or data-integrity defects were identified. The new entity and live-source APIs, including synchronous, asynchronous, raw-response, streaming, pagination, and model support, are accompanied by aligned documentation, OpenAPI fixtures, and generated coverage; there are no pre-existing unresolved issues or PR-introduced findings requiring remediation.

Key Findings:

• The replacement of context-document, tree, digest, and configuration resources with entity and live-source APIs is consistently reflected across generated API surfaces, models, fixtures, and tests.
• Synchronous, asynchronous, raw-response, streaming, and pagination variants are included without identified contract, error-handling, or concurrency defects.
• No security, access-control, persistence-integrity, or migration-related issue was found in the reviewed changes.

Evaluated against

• 54/54 changed files reviewed
• criteria: correctness, security & access control, robustness & error handling, concurrency & data integrity, repo conventions / steering docs
• steering docs: none found in repo