chore(main): release 1.208.0

[coreplane-infra]

🤖 I have created a release beep boop

1.208.0 (2026-09-14)

Features

• http: a per-run model-credential proxy — a run's bearer buys model calls through the bot, pinned to its preset's model and metered as its own turns, and no container ever holds a key (#1012) (524118d)
• ship: one ship implementation — every agent:ship request runs on the plan runner, the in-process round loop is deleted and ship.coordinator is gone (#1011) (f79e88b)
• ship: the child contract names the title gate among its guards (#1004) (505561c)

Bug fixes

• ship: the runner trusts the review child's own record of its post — a review posted a second ago no longer reads as unposted, and GitHub is asked patiently only when the record is silent (#1013) (2d26e08)

Documentation

• agents: the program plan absorbs record 0032 — five units retire the native loop behind pi, one preset at a time (#1005) (52576d1)
• load: the load-harness spec states how a refusal's token is recovered from a client error (#1002) (69e6477)

---

This PR was generated with Release Please. See documentation.

[github-actions]

What merging this release deploys

Deploy targets for 39b6983: 4 of 4 Workers — memory, bot, resident, sandbox

Worker	Decision	Judged against	Why
memory	deploy	live 262ef07	src/core/coordinator/contract.ts (imported by deploy/cloudflare-memory/worker.ts) src/core/reviewVerdict.ts (imported by deploy/cloudflare-memory/worker.ts) src/core/runEvents.ts (imported by deploy/cloudflare-memory/worker.ts) src/core/runFriction.ts (imported by deploy/cloudflare-memory/worker.ts) src/core/runRecord.ts (imported by deploy/cloudflare-memory/worker.ts) src/core/ship/contract.ts (imported by deploy/cloudflare-memory/worker.ts) src/core/trace/streamSpans.ts (imported by deploy/cloudflare-memory/worker.ts) src/core/trace/workerTrace.ts (imported by deploy/cloudflare-memory/worker.ts)
bot	deploy	live a5e85d6	src/channels/adminCoordinator.ts src/channels/adminModelProxy.ts src/channels/modelProxy.ts src/config/validate.ts src/core/coordinator/briefs.ts src/core/coordinator/contract.ts src/core/coordinator/driver.ts src/core/coordinator/handOff.ts … +27 more
resident	deploy	live c460669	src/core/trace/workerTrace.ts (imported by deploy/cloudflare-resident/worker.ts)
sandbox	deploy	live c460669	src/core/trace/workerTrace.ts (imported by deploy/cloudflare-sandbox/worker.ts)

Unclassified paths: none.

Judged per Worker against the commit it is serving right now. Re-rendered by the release-please workflow on every merge to main; merging this PR runs deploy all --affected and deploys exactly the Workers marked deploy.

[coreplane-infra]

🤖 Created releases:

• v1.208.0

🌻

[justinhelmer]

Deployed: 1.208.0, production — in two steps.

surface	receipt
config	document base v47 pushed before the bot step (the retired ship.coordinator key already gone from infrastructure main by infrastructure#85)
state Worker	switchboard-memory on 348d6f6e, deployed 03:43Z
bot	generation 20260914T034433Z-77069d8b, build 348d6f6e, live 03:44:33Z after the old container drained six runs
release run	https://github.com/coreplanelabs/switchboard/actions/runs/34803210518 — the deploy job failed at 03:53:59Z: The self-hosted runner lost communication with the server; the step log was never uploaded (the check-run annotation carries the cause). Bot and state Worker were already live; the resident and sandbox steps did not run.
resident + sandbox	redeployed from main by https://github.com/coreplanelabs/switchboard/actions/runs/34805591801 (targets=resident,sandbox, 04:19–04:23Z, green); resident Worker /healthz build 973522a8 (main's head at the time, one commit past the release); all four residents warm through the roll
what it carried	one ship implementation (#1011), the review post recorded before finish (#1013), the plan absorbing record 0032 (#1005); live receipt: plan 2026-09-14-001… ran on the runner with no loop and merged its unit (#835)