chore(none): decommission dead Speakeasy generator scaffolding
Summary
SDK generation has been blocked at the Speakeasy account level for months — .speakeasy/gen.lock hasn't moved since #324 (2026-01-18). Removes the generator input, output, and tooling that can no longer run.
No changes under src/ — the shipped SDK is byte-identical.
What's deleted
| File | Why |
|---|---|
.speakeasy/gen.lock (1,581) | Generator state; recreated by any future run |
RELEASES.md (1,253) | Speakeasy release ledger. CHANGELOG.md is the human changelog, untouched |
codeSamples.yaml (185) | Generator output |
_jupyter/README_example.ipynb (112) | Last touched 2024-01-31; no longer runs |
tests/helpers.py (61) | Speakeasy scaffolding; real tests are in _test_unstructured_client/ and _test_contract/ |
USAGE.md (42) | Duplicate of the ## SDK Example Usage section in README.md |
files.gen (29) | Stale ownership manifest, last updated 2023-12-06 |
.github/workflows/speakeasy_sdk_generation.yml (25) | Nightly cron calling speakeasy-api/sdk-generation-action |
Plus the 7 speakeasy/jupyter Makefile targets and the 28 generator marker comments in README.md.
Docs
CONTRIBUTING.md and the README Contributions section tell contributors to install the Speakeasy CLI and run make client-generate, a target that no longer exists. Reworded to drop the generator mechanics.
Regeneration
overlay_client.yaml is left in place — it's hand-written input, not generator output, and the sole source of the split_pdf_* parameter descriptions. .genignore, gen.yaml and .speakeasy/workflow.yaml also stay.
If access is restored, regeneration is messier but not blocked: gen.lock carries the target UUID, and without the README markers a regen appends sections rather than replacing them in place.
Test plan
-
make test-unit— 249 passed, 1 xfailed (baseline) -
make test-contract— 64 passed -
make lint— mypy clean, pylint 10.00/10 - CI green