Skip to content

Upgrade the Atomic harness to 0.9.32 - #445

Merged
lavaman131 merged 1 commit into
mainfrom
atomic-0.9.32
Oct 10, 2026
Merged

lavaman131 merged 1 commit into
mainfrom
atomic-0.9.32

Conversation

@lavaman131

Copy link
Copy Markdown
Collaborator

Upgrade the Atomic harness to 0.9.32

Moves the Atomic harness to 0.9.32, which fixes workflow stages in
SDK-hosted sessions losing the session's extensions and running in the
server's directory instead of the Planner's checkout
(bastani-inc/atomic#3551). Planner stages now load operator extensions
such as pdd-kit and run in the document's checkout.

0.9.32 also gives stages the session's inline extension factories, so
Chopin's own two now stay out of stage sessions:

  • atomicTurnExtension no longer appends the Planner turn's instructions
    to a stage's system prompt, hides chopin_submit_atomic_result from the
    stage, and blocks any call to it there.
  • workflowRuns no longer observes activity, folds lifecycle events, or
    replaces planner.rootOf from a stage, so a stage cannot overwrite the
    Planner's run cards. rootOf is now set at session start rather than at
    factory construction.

bun.lock moves @bastani/atomic, @bastani/atomic-natives (all eight
platform packages) and @bastani/pi-ai to 0.9.32. Atomic's
@earendil-works packages stay at 1.1.0. docs/self-hosting.md now says
0.9.32.

Assistant-model: Claude Opus 5.5 (fast)
Assistant-workflow: inline
Assistant-verification: bun test red/green passed: full.test.ts workflow-stage test fails on 0.9.32 without the guard (stage offered chopin_submit_atomic_result) and passes with it
Assistant-verification: bun test passed: 4426 pass, 4 skip, 0 fail (GIT_CONFIG_GLOBAL=/dev/null)
Assistant-verification: bun run types passed: all workspace checks
Assistant-verification: bun run ci passed: dprint, oxlint (31 warnings, same as main), tokens, design contract, Impeccable
User-preference: Keep pdd-kit and Chopin on the same Atomic release, with transitive deps upgraded together
User-preference: Merge the Atomic upgrade PRs, update the dev/integration pin, and merge those too

Moves the Atomic harness to 0.9.32, which fixes workflow stages in
SDK-hosted sessions losing the session's extensions and running in the
server's directory instead of the Planner's checkout
(bastani-inc/atomic#3551). Planner stages now load operator extensions
such as pdd-kit and run in the document's checkout.

0.9.32 also gives stages the session's inline extension factories, so
Chopin's own two now stay out of stage sessions:

- atomicTurnExtension no longer appends the Planner turn's instructions
  to a stage's system prompt, hides chopin_submit_atomic_result from the
  stage, and blocks any call to it there.
- workflowRuns no longer observes activity, folds lifecycle events, or
  replaces planner.rootOf from a stage, so a stage cannot overwrite the
  Planner's run cards. rootOf is now set at session start rather than at
  factory construction.

bun.lock moves @bastani/atomic, @bastani/atomic-natives (all eight
platform packages) and @bastani/pi-ai to 0.9.32. Atomic's
@earendil-works packages stay at 1.1.0. docs/self-hosting.md now says
0.9.32.

Assistant-model: Claude Opus 5.5 (fast)
Assistant-workflow: inline
Assistant-verification: bun test red/green passed: full.test.ts workflow-stage test fails on 0.9.32 without the guard (stage offered chopin_submit_atomic_result) and passes with it
Assistant-verification: bun test passed: 4426 pass, 4 skip, 0 fail (GIT_CONFIG_GLOBAL=/dev/null)
Assistant-verification: bun run types passed: all workspace checks
Assistant-verification: bun run ci passed: dprint, oxlint (31 warnings, same as main), tokens, design contract, Impeccable
User-preference: Keep pdd-kit and Chopin on the same Atomic release, with transitive deps upgraded together
User-preference: Merge the Atomic upgrade PRs, update the dev/integration pin, and merge those too
@lavaman131
lavaman131 merged commit 943aacc into main Oct 10, 2026
3 checks passed
@lavaman131
lavaman131 deleted the atomic-0.9.32 branch October 10, 2026 06:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant