chore(main): release 1.261.1

[coreplane-infra]

🤖 I have created a release beep boop

1.261.1 (2026-09-23)

Bug fixes

• coding: show the requester and thread above every PR description (#2326) (c873c50)
• deploy: fence bot rollbacks with application state (#2323) (37007ea)
• deploy: install package root dependencies (#2315) (fc66ac6)
• dispatcher: resume ended pipelines from their threads (#2324) (438f898)
• isolate ingress thread identities (#2313) (54d6d6f)
• providers: shape direct Responses tools (#2322) (d7e5464)
• review: preserve typed verdicts in oversized posts (#2314) (6c0d389)
• runs: preserve state during reservation promotion (#2308) (cc4eb54)
• ship: reconcile findings against the exact PR head (#2310) (9e6abc7)

---

This PR was generated with Release Please. See documentation.

[github-actions]

What merging this release deploys

Deploy targets for 1e003ef: 2 of 4 Workers — memory, bot

Worker	Decision	Judged against	Why
memory	deploy	live 903ae28	deploy/cloudflare-memory/worker.ts src/core/pipelineStanding.ts (imported by deploy/cloudflare-memory/worker.ts) src/core/plane/decide.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/runLedger/types.ts (imported by deploy/cloudflare-memory/worker.ts) src/core/runLiveState.ts (imported by deploy/cloudflare-memory/worker.ts) … +3 more
bot	deploy	live 903ae28	src/channels/adminCoordinator.ts src/channels/http.ts src/channels/mcp.ts src/channels/modelProxy.ts src/core/codingPrPostStep.ts src/core/coordinator/driver.ts src/core/dispatch/operator.ts src/core/dispatch/provision.ts … +46 more
resident	skip	live 903ae28	no input changed
sandbox	skip	live 903ae28	no input changed

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-switchboard]

LGTM: Release 1.261.1 contains the exact merged continuation fix and changes only consistent release metadata afterward.

Note

Approved · head 1e003ef · no findings

Full review

No findings. The exact release head contains continuation fix 438f8985, and all subsequent changes are consistent 1.261.1 release metadata.

[github-actions]

Auto-approved: coreplane-switchboard[bot] reviewed this PR and posted an LGTM verdict (see its review). This repository opted in through its REVIEW_BOT_LOGIN and REVIEW_BOT_ID variables.

[coreplane-infra]

🤖 Created releases:

• v1.261.1

🌻

[justinhelmer]

Production shipment verified September 23, 2026 at 3:00:30 PM PDT: release workflow and deployment job succeeded. Bot container application targets 1.261.1 at version 2; its live gate observed exact commit 3746a1c5fa2d30bebd66baec1fb3534a1f927e3a. Independent post-deploy public health reads confirm bot and memory both report ok and that exact commit; bot reports draining=false, Slack connected, inFlight=0. Resident and sandbox were skipped because their inputs did not change. CLI work admitted during the rollout has a durable pushed result in cli#111, head cddb40f05e1fd78055a2e23852692477b8fadf5d; hosted pipeline terminal/handoff state remains unverified. The reported transient MCP 1101 was not retried, so MCP recovery and feature-level acceptance remain separate outstanding proofs. Narrow CLI→website rollout hold released to its existing owners; no expansion of deployment or fixture authority.

[justinhelmer]

Work-preservation follow-up: the already-admitted CLI pipeline now has a terminal Slack outcome, independently read from its original thread: ship completed as “merge-ready” after one review round, with four green checks at approved head cddb40f05e1fd78055a2e23852692477b8fadf5d. The coding child reports 17/17 focused tests and pushed that same head; CLI #111 merged as 4175743da2c6791e35bfb07518f2fdf7bc8a9f61 and 0.2.42 distribution/install smoke passed. This proves preservation and successful completion of this accepted pipeline during the release window. It does not establish that the coding child crossed a bot generation or prove arbitrary interrupted-run handoff. No stop or duplicate recovery was needed for this pipeline.