feat(api)!: sync generated SDK from staging (removes google_calendar + slack list endpoints)

[aburkard]

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

• Source: hyperspell/python-sdk-staging@ca1f56f6d237bb6dca45205a5ebe0a82f96ac4fb (ref ca1f56f6d237bb6dca45205a5ebe0a82f96ac4fb)
• Promoted by: https://github.com/hyperspell/hyperspell/actions/runs/33684943954
• 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.

[firetiger-agent]

Firetiger has created a monitoring plan for this PR.

View monitor

[entelligence-ai-pr-reviews]

---

Confidence Score: 4/5 - Mostly Safe

Safe to merge — this PR syncs a generated SDK from staging and removes the google_calendar endpoints, which appears to be an intentional breaking change reflected in the ! in the commit prefix. The change is well-scoped as a generated artifact sync, meaning the logic correctness is delegated to the upstream staging environment rather than manual authoring. No review comments were raised, and no critical or significant issues were identified by static analysis across the reviewed files.

Key Findings:

• The PR is a generated SDK sync, meaning the diff reflects upstream source-of-truth changes rather than hand-written logic — reducing the risk of human authoring errors in the changed files.
• The removal of google_calendar endpoints is a breaking API change (correctly flagged with ! in the commit message), but since this is intentional and originates from staging, the risk is that consumers of these endpoints will break if they haven't been notified — this is a coordination concern, not a code correctness issue.
• Only 10 of 35 changed files were reviewed by automated analysis, leaving some files unexamined, though the generated nature of the SDK mitigates the risk of undiscovered logic bugs.
• No null-safety, security, or logic issues were identified in the reviewed portions of the generated SDK changes.

Files requiring special attention

• Any file previously exposing google_calendar endpoint types or route handlers
• SDK index/barrel files that re-export removed endpoints (may cause import errors for consumers)

[entelligence-ai-pr-reviews]

EntelligenceAI PR Summary

Promotes the generated Python SDK from staging, adding the new context_documents resource with document generation/listing, tree generation and progress tracking, digest generation, and configurable generation settings across sync, async, raw-response, and streaming clients. The update also expands memory and integration schemas, adds chunk retrieval and richer status models, standardizes user_id header handling, and introduces dedicated SDK test CI coverage. This is a breaking change: the Google Calendar and Slack list resources and their types/tests are removed, while generated API documentation and examples are refreshed.

flowchart TD
    classDef newBehavior fill:#dcfce7,stroke:#16a34a,color:#14532d;
    Client["Hyperspell client"] --> ContextDocuments["context_documents resource"]
    ContextDocuments --> Generate["Generate context document or tree"]
    Generate --> Processing["Asynchronous processing"]
    Processing --> Progress["Poll tree progress"]
    Processing --> Latest["Fetch latest or completed tree"]
    ContextDocuments --> Digests["Generate or list digests"]
    ContextDocuments --> Config["Read, update, or reset config"]
    Client --> Removed["Google Calendar and Slack list endpoints removed"]
    class Client,ContextDocuments,Generate,Processing,Progress,Latest,Digests,Config,Removed newBehavior;

Loading

🟢 Green = new or changed in this PR

---

Review Scorecard

Dimension	Rating	Basis
Code Quality	●●●●● 5/5 — Excellent	no critical/significant findings — rated Excellent
Blast Radius	High	touches auth/access-control, infra / deploy / config, 111 file(s) / ~5394 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 from a code-quality perspective despite the High blast radius — the reviewed generated SDK changes are clean and no correctness, security, robustness, or data-integrity defects were identified. The sync, async, raw-response, and streaming client variants appear consistently updated for the new context_documents functionality, and there are no unresolved prior issues to distinguish from this change.

Key Findings:

• The new context_documents resource support is represented consistently across the SDK client variants, including document generation, listing, tree generation, progress tracking, and digest operations.
• Expanded memory, integration, chunk, and status models follow the generated SDK structure without identified validation or runtime-handling defects.
• Standardized user_id header handling and dedicated SDK CI coverage improve consistency and regression detection without introducing observed security or access-control issues.

Evaluated against

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