chore(main): release 1.260.6

[coreplane-infra]

🤖 I have created a release beep boop

1.260.6 (2026-09-23)

Bug fixes

• core: keep provider recovery and admission failures typed (#2232) (e2e99f1)
• core: size background turns for hidden reasoning (#2276) (44df09d)
• review: recover workspaces at pull request heads (#2263) (648751a)
• ship: recover read-record races and reissues (#2264) (4bbbfad)

---

This PR was generated with Release Please. See documentation.

[github-actions]

What merging this release deploys

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

Worker	Decision	Judged against	Why
memory	deploy	live 3b665eb	deploy/cloudflare-memory/worker.ts src/core/budgets.ts (imported by deploy/cloudflare-memory/worker.ts) src/core/runLedger/decisions.ts (imported by deploy/cloudflare-memory/worker.ts) src/core/runLedger/types.ts (imported by deploy/cloudflare-memory/worker.ts) src/core/ship/coordinator.ts (imported by deploy/cloudflare-memory/worker.ts)
bot	deploy	live 3b665eb	src/channels/adminCoordinator.ts src/core/budgets.ts src/core/coordinator/driver.ts src/core/decisionRecordReservation.ts src/core/dispatch/authorize.ts src/core/dispatch/provision.ts src/core/dispatch/reply.ts src/core/harness/pi/harness.ts … +16 more
resident	deploy	live 3b665eb	src/core/budgets.ts (imported by deploy/cloudflare-resident/worker.ts) src/core/refusal.ts (imported by deploy/cloudflare-resident/worker.ts)
sandbox	deploy	live 3b665eb	src/core/budgets.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.260.6

🌻

[justinhelmer]

1.260.6 — full production fleet receipt (2026-09-23)

Tag v1.260.6 resolves to full commit 903ae2855833637fbcc0c0a22d54e7268be75965. Release-please run 35820363983 and its deploy job both concluded success; the release plan selected all four Workers.

Worker	Production evidence
bot	curl -A switchboard-session https://switchboard.coreplanelabs.dev/healthz → ok: true, build.commit: 903ae2855833637fbcc0c0a22d54e7268be75965, generation 20260923T050739Z-e196c70c, Slack connected, draining: false; deploy gate reported live 110 s after upload.
memory	curl -A switchboard-session https://switchboard-memory.coreplanelabs.dev/healthz → ok: true, build.commit: 903ae2855833637fbcc0c0a22d54e7268be75965; deploy version 37a74366-6c37-44af-b381-411296df34a0.
resident	curl -A switchboard-session https://switchboard-resident.coreplanelabs.dev/healthz → ok: true, build.commit: 903ae2855833637fbcc0c0a22d54e7268be75965; deploy version ec5e7cd1-2379-4bde-a1ce-06c59fca30d6. The preflight refused while four runs were active, waited without forcing them down, then passed at 05:30:02Z with five residents and no work/provision in flight.
sandbox	Authenticated deploy log at 05:33:34Z: Worker serves 903ae28; container application advanced from version 62 to 63; one running instance was on 63; probe echo ok exited 0 from deploy-gate:903ae2855833637fbcc0c0a22d54e7268be75965; deploy version ff3a4f9e-a515-4c99-b1a8-a380ace9fc60.

The sandbox receipt comes from the final deploy log because its health endpoint requires authority not used for this verification. This receipt proves release deployment and liveness gates only; it does not claim any feature-specific failure/race was reproduced live.