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@1432f190a8e02eb2023dd140170bbeac0bc6a3b2 (ref main)
• Promoted by: https://github.com/hyperspell/hyperspell/actions/runs/29068363046
• 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)