[lavaman131]

Moves the Atomic harness to the 0.9.41-alpha.1 pre-release (npm next) and adapts it to what that release changes.

Versions

catalog:harness pins @bastani/atomic 0.9.41-alpha.1. The lockfile resolves these at 0.9.41-alpha.1, with no older @bastani package left:

• @bastani/atomic
• @bastani/atomic-natives and all eight of its platform packages
• @bastani/pi-ai

No other dependency moves with them.

What in the release reaches Chopin

• steer() and followUp() now start a turn on an idle session that already has messages (breaking). A Planner session between Chopin's turns is exactly that kind of session. So a message an extension or workflow queues there now starts a turn of its own. The adapter already stops any turn it did not start before the turn reaches the model. I checked this against real Atomic sessions:

  • triggered notices, queued steer and followUp custom messages, and queued user messages were each stopped;
  • the Planner's next turn still ran normally after each one.

  The existing guard test now also covers a queued follow-up. Both cases fail when the guard is disabled.

• session.workflows.waitForSettled(runId) (fix for a run left running in the journal). Chopin lets a Planner session go as soon as its last run ends. That is the case Atomic fixed. Before disposing the session, the adapter now waits, for at most 10 seconds, until each run that finished, failed or was stopped has its ending journaled.

  • Live, paused and blocked runs are not waited on; disposing stops them.
  • A run whose ending could not be recorded is logged by its ID, and the session still goes.
  • The new unit test failed before the change. A real Atomic run showed that the call returns once the run's final status is in the journal.

• Structured output now names failing paths, and decisions have a total timeoutMs. This does not reach Chopin. Chopin uses its own result tool, not Atomic's structured_output.

The OAuth refresh, model routing and default-Copilot-model changes do not reach Chopin either. Its Atomic sessions keep credentials in memory and always name their model.

Docs

• docs/self-hosting.md names the new version.
• docs/hosted-agent.md describes both adapter behaviours.

Verification

• bun test: 6713 pass, 22 skip, 0 fail.
• bun run types and bun run ci pass.
• The server Docker image builds. A container with HARNESS=atomic started healthy and imports Atomic 0.9.41-alpha.1. It holds only 0.9.41-alpha.1 @bastani packages.
• Targeted bun run e2e (run cards, Planner attachment, harness, smoke): 34 passed, no retries.

The connector (apps/connector) does not change.