[lavaman131]

Upgrades the Atomic harness from the 0.9.41-alpha.1 pre-release to the stable 0.9.42 release.

What changed

• catalog:harness pins @bastani/atomic 0.9.42. bun.lock now resolves @bastani/atomic, @bastani/atomic-natives (and all eight platform packages), and @bastani/pi-ai at 0.9.42, with no older @bastani/* entries left. Atomic's own @earendil-works/pi-* packages move from 1.3.0 to 1.4.0 with it, and pi-tui adds marked-cjk-friendly.

• No adapter code change. Nothing from 0.9.41-alpha.2 through 0.9.42 breaks apps/server/src/harness/atomic/*. The steer()/followUp() breaking change and waitForSettled() were already handled in Upgrade Atomic to the 0.9.41-alpha.1 pre-release #720, and that coverage still passes.

• Shared provider rate limits (new in 0.9.42): after one request gets a 429, every Atomic session in the Chopin server waits for that provider's cooldown before its next request. That includes Planner turns, summary workers, and research workers. Before 0.9.42, each session hit the limit on its own. I checked this with real Atomic sessions against a stub provider that returns 429 with Retry-After: 3:

  • On 0.9.42, a second session's request waited until the cooldown ended.
  • On 0.9.41-alpha.1, the second session's request went out immediately.
  • Aborting a turn while it waits ends it without sending the request.

  docs/self-hosting.md now lists this as an Atomic caveat. Chopin sets no configureProviderRequestBudget() and passes no resourceAdmission, because both are optional.

• Storage adapters by package name (new in 0.9.42): the shared top-level storage setting can now name an adapter package, which is what atomic storage join writes for libSQL. A Planner session's explicit journal still takes precedence, so its workflow runs stay in Chopin's journal. A new test in atomic/full.test.ts runs a real workflow with that setting pointing at an adapter that isn't installed. It passes. With the adapter's journal option removed, it fails with Could not load storage adapter. The same setting does reach the Planner's Intercom broker: a real run wrote the broker's tables to the operator's selected database. docs/hosted-agent.md now says so.

• No effect on Chopin:

  • Device-code /login: Chopin never runs /login. auto copies the host login. The connector's "sign in with /login" guidance is still accurate.
  • Trimming a trailing newline from { "file": … } secrets: Chopin configures no storage secrets.
  • Interactive Ctrl+C and queue fixes: Chopin drives sessions through the SDK.
  • Workflow failure containment: no change needed.
  • Operator workflows.localWorkers and workflows.admission settings: I tried both against a real Planner workflow, and its question still reached Decisions.

• docs/self-hosting.md now names 0.9.42.

The connector is unchanged. It installs @bastani/atomic without pinning a version.

No UI changes, so there is no visual preview.

Verification

• bun test: 6734 pass, 22 skip, 0 fail. This includes harness/atomic/*, atomic.contract.test.ts, and atomic/full.test.ts.
• bun run types and bun run ci both pass.
• The server Docker image builds. The container imports Atomic 0.9.42 and starts healthy with HARNESS=atomic.
• Targeted bun run e2e (run-card, setup-agents, machines, harness-children, chat-mentions): 24 passed.