Upgrade Atomic to the stable 0.9.44 release

docs/hosted-agent.md

@@ -628,7 +628,9 @@ launched it, and its runs belong to that session, so Chopin keeps the session
 and its owner binding, and keeps the document loaded, until every run has
 finished. The next turn reuses that session, so the Planner can still see and
 steer its runs over Intercom; people steer through Chat and Decisions, never a
-stage directly. **Stop Planner** also pauses the session's live runs, resumably,
+stage directly. Since Atomic 0.9.44 such a message reaches a busy stage after
+its current tool calls finish rather than cancelling them, unless the Planner
+sends it as an `interrupt`. **Stop Planner** also pauses the session's live runs, resumably,
 through Atomic's session run control, and **Resume Planner** resumes the runs it
 paused. A run waiting on a question pauses too: Atomic withdraws the question
 from Decisions while the run is paused and presents it again on Resume, and an

docs/self-hosting.md

@@ -75,7 +75,7 @@ each owner's GitHub App user token and does not consume `HARNESS_AUTH`;
 setting `auto` on loopback passes the startup guard but does not enable host
 login in that adapter.
 
-`HARNESS=atomic` runs Atomic 0.9.43 in the Chopin server process through its
+`HARNESS=atomic` runs Atomic 0.9.44 in the Chopin server process through its
 headless SDK (`createAgentSession()`). It does not spawn the `atomic` CLI or use
 RPC mode.
 
@@ -166,8 +166,11 @@ Atomic caveats:
   sets `XDG_STATE_HOME=/var/lib/chopin`; mount a volume there to keep runs
   and those directories when the container is replaced.
 - Local workflow worker pools stay off unless the operator's Atomic settings
-  set `workflows.localWorkers`. With a pool, Atomic 0.9.43 keeps each worker's
-  standard error in `worker-logs/` beside the journal, so under
+  set `workflows.localWorkers`. Since Atomic 0.9.44 a pool runs as one
+  coordinator process per root run, started by the Chopin server process, with
+  the worker processes under it; it uses the same journal, and if the server
+  exits, the coordinator and its workers exit with it. Atomic keeps each
+  worker's standard error in `worker-logs/` beside the journal, so under
   `$XDG_STATE_HOME/chopin/atomic/worker-logs/<run id>/`, inside the directory
   Chopin creates for the journal with access for the server's user only. It
   deletes a log when its worker shuts down normally but keeps the logs of
@@ -176,6 +179,16 @@ Atomic caveats:
   its card in Chat says so. The settings `workflows.localWorkers.startupTimeoutMs`
   and `leaseMs` set how long a worker may take to start and how long an
   unresponsive one keeps its child.
+- Since Atomic 0.9.44 a workflow runs up to 1000 of its stages at once unless
+  it says otherwise (`defaultConcurrency`, 3 before), nests child workflows at
+  most three levels deep (`maxDepth`, 4 before), and a stage's `subagent` tool
+  runs up to 1000 children at once (`parallel.concurrency` and
+  `parallel.runningCapacity`, 3 and 4 before). Without a pool, all of them run
+  in the Chopin server process and share its memory and the provider rate
+  limit above. To throttle a server, lower `defaultConcurrency` in
+  `extensions/workflow/config.json` and the `parallel` limits in
+  `extensions/subagent/config.json` under the Atomic agent directory, which
+  Planner sessions read; Chopin sets none of these itself.
 - Atomic depends on `typebox` 1.3.27 while Chopin pins 1.3.7. Host tool schemas
   pass to Atomic as plain JSON Schema, so the two versions never meet.
 

package.json

@@ -69,7 +69,7 @@
 				"@ai-sdk/harness": "1.0.146",
 				"@ai-sdk/mcp": "2.0.72",
 				"@ai-sdk/sandbox-just-bash": "1.0.146",
-				"@bastani/atomic": "0.9.43",
+				"@bastani/atomic": "0.9.44",
 				"ai": "7.0.135",
 				"typebox": "1.3.7",
 				"zod": "4.4.3"