@bastani/atomic 0.9.14 → 0.9.15-alpha.1

package/dist/builtin/subagents/src/shared/types-results.ts

@@ -3,9 +3,8 @@
  */
 
 import type { SessionStats } from "@bastani/atomic";
+import type { Message } from "@bastani/pi-ai/compat";
 import type { AgentToolResult } from "@earendil-works/pi-agent-core";
-import type { Message } from "@earendil-works/pi-ai/compat";
-import type { NestedRunAddress, NestedRunSummary, NestedStepSummary } from "./types-nested.js";
 
 export interface MaxOutputConfig {
 	bytes?: number;
@@ -80,8 +79,6 @@ export interface ControlEvent {
 	agent: string;
 	index?: number;
 	runId: string;
-	nestedRunId?: string;
-	nestingPath?: NestedRunAddress["path"];
 	message: string;
 	reason?: "idle" | "active_long_running" | "tool_failures" | "time_threshold" | "turn_threshold" | "token_threshold";
 	turns?: number;
@@ -97,60 +94,6 @@ export interface ControlEvent {
 export type SubagentResultStatus = "completed" | "failed" | "paused" | "detached";
 export type SubagentRunMode = "single" | "parallel";
 
-export type PublicNestedStepSummary = Pick<
-	NestedStepSummary,
-	| "agent"
-	| "status"
-	| "sessionFile"
-	| "activityState"
-	| "lastActivityAt"
-	| "currentTool"
-	| "currentToolStartedAt"
-	| "currentPath"
-	| "turnCount"
-	| "toolCount"
-	| "startedAt"
-	| "endedAt"
-	| "error"
-> & {
-	children?: PublicNestedRunSummary[];
-};
-
-export type PublicNestedRunSummary = Pick<
-	NestedRunSummary,
-	| "id"
-	| "parentRunId"
-	| "parentStepIndex"
-	| "parentAgent"
-	| "depth"
-	| "path"
-	| "sessionId"
-	| "sessionFile"
-	| "intercomTarget"
-	| "ownerIntercomTarget"
-	| "leafIntercomTarget"
-	| "ownerState"
-	| "mode"
-	| "state"
-	| "agent"
-	| "agents"
-	| "activityState"
-	| "lastActivityAt"
-	| "currentTool"
-	| "currentToolStartedAt"
-	| "currentPath"
-	| "turnCount"
-	| "toolCount"
-	| "totalTokens"
-	| "startedAt"
-	| "endedAt"
-	| "lastUpdate"
-	| "error"
-> & {
-	steps?: PublicNestedStepSummary[];
-	children?: PublicNestedRunSummary[];
-};
-
 export interface SubagentResultIntercomChild {
 	agent: string;
 	status: SubagentResultStatus;
@@ -159,7 +102,6 @@ export interface SubagentResultIntercomChild {
 	artifactPath?: string;
 	sessionPath?: string;
 	intercomTarget?: string;
-	children?: PublicNestedRunSummary[];
 }
 
 export interface SubagentResultIntercomPayload {

package/dist/builtin/subagents/src/shared/types-runtime.ts

@@ -81,8 +81,6 @@ export const SLASH_SUBAGENT_STARTED_EVENT = "subagent:slash:started";
 export const SLASH_SUBAGENT_RESPONSE_EVENT = "subagent:slash:response";
 export const SLASH_SUBAGENT_UPDATE_EVENT = "subagent:slash:update";
 export const SLASH_SUBAGENT_CANCEL_EVENT = "subagent:slash:cancel";
-export const MAX_SUBAGENT_NESTING_DEPTH = 5;
-export const DEFAULT_SUBAGENT_MAX_DEPTH = MAX_SUBAGENT_NESTING_DEPTH;
 export const SUBAGENT_ACTIONS = [
 	"list",
 	"get",

package/dist/builtin/subagents/src/shared/types.ts

@@ -7,7 +7,7 @@
 
 export * from "./types-config.js";
 export * from "./types-depth.js";
-export * from "./types-nested.js";
+export * from "./types-foreground-state.js";
 export * from "./types-output.js";
 export * from "./types-results.js";
 export * from "./types-runtime.js";

package/dist/builtin/subagents/src/shared/utils.ts

@@ -4,7 +4,7 @@
 
 import * as path from "node:path";
 import { getAgentDir as getAtomicAgentDir } from "@bastani/atomic";
-import type { Message } from "@earendil-works/pi-ai/compat";
+import type { Message } from "@bastani/pi-ai/compat";
 import { formatToolCall } from "./formatters.js";
 import type { AgentProgress, Details, DisplayItem, ErrorInfo, SingleResult, ToolCallSummary } from "./types.js";
 

package/dist/builtin/subagents/src/slash/slash-live-state.ts

@@ -1,5 +1,5 @@
+import type { Message } from "@bastani/pi-ai/compat";
 import type { AgentToolResult } from "@earendil-works/pi-agent-core";
-import type { Message } from "@earendil-works/pi-ai/compat";
 import type { SubagentParamsLike } from "../runs/foreground/subagent-executor.js";
 import { type Details, type SingleResult, SLASH_RESULT_TYPE, type Usage } from "../shared/types.js";
 import type { SlashSubagentResponse, SlashSubagentUpdate } from "./slash-bridge.js";

package/dist/builtin/web-access/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bastani/web-access",
-  "version": "0.9.14",
+  "version": "0.9.15-alpha.1",
   "private": true,
   "description": "Atomic extension for web search, URL fetching, GitHub repo cloning, PDF/video extraction. Fork of: https://github.com/nicobailon/pi-web-access",
   "contributors": [
@@ -10,7 +10,7 @@
   "license": "MIT",
   "type": "module",
   "engines": {
-    "bun": ">=1.3.14"
+    "bun": ">=1.4.0"
   },
   "main": "./index.ts",
   "types": "./index.ts",

package/dist/builtin/web-access/summary-review.ts

@@ -1,5 +1,5 @@
-import type { ProviderHeaders } from "@earendil-works/pi-ai";
-import { getModel, type Message, type Model } from "@earendil-works/pi-ai/compat";
+import type { ProviderHeaders } from "@bastani/pi-ai";
+import { getModel, type Message, type Model } from "@bastani/pi-ai/compat";
 import type { ExtensionContext } from "@bastani/atomic";
 import type { QueryResultData } from "./storage.js";
 

package/dist/builtin/web-access/web-search-summary.ts

@@ -1,5 +1,5 @@
-import { getModel, type Model } from "@earendil-works/pi-ai/compat";
-import type { ProviderHeaders } from "@earendil-works/pi-ai";
+import { getModel, type Model } from "@bastani/pi-ai/compat";
+import type { ProviderHeaders } from "@bastani/pi-ai";
 import type { QueryResultData } from "./storage.js";
 import {
 	buildDeterministicSummary,

package/dist/builtin/workflows/CHANGELOG.md

@@ -6,6 +6,20 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 
 ## [Unreleased]
 
+## [0.9.15-alpha.1] - 2026-08-21
+
+### Changed
+
+- Workflow-stage orchestration context no longer carries a subagent delegation-depth constraint. Stage delegation itself is unchanged: a stage is a top-level session and still launches subagents once. What changed is that the children it launches can no longer delegate further, and nothing configures that.
+
+### Fixed
+
+- Fixed `/workflow` cards being swallowed while the agent is streaming. The dispatch, list, and status cards were sent as ordinary turn-triggering messages, so a card emitted during a live model turn — for example right after a workflow lifecycle notice started one — was queued as steering and did not reach the transcript until that turn ended. Cards are already-rendered transcript surfaces and are now sent as non-turn messages, so they appear immediately whether or not a turn is in flight. Workflow lifecycle notices are unchanged and still nudge the model.
+- Persistent workflow progress widgets now reattach after a host UI reset or remote-engine release while keeping the existing mount-once, update-in-place behavior ([#2556](https://github.com/bastani-inc/atomic/issues/2556)).
+- Fixed one stuck heartbeat send silencing every workflow heartbeat for the rest of the session. All runs in a session share a single FIFO heartbeat-delivery queue, and its in-flight head had no deadline: a `sendMessage` promise that never settled held that head forever, so later runs queued behind it and never delivered a card, with no error and no degraded mode. Terminal cleanup could not rescue it either, because it deliberately spares a send already handed to the host. Each in-flight send now carries a bounded two-minute watchdog; on expiry the attempt is abandoned as an undelivered heartbeat, its run's pending slot is released so the run re-arms at its next future boundary, and the queue advances to the next run. Settlement is guarded by a per-attempt token, so a late resolution or rejection from an abandoned attempt cannot settle twice, restart retries, or disturb the current head. An emitter that rejects directly now settles as a failed delivery through the existing retry path instead of wedging the queue. The intended one-heartbeat-per-run rule before the deadline, the existing retry backoff and attempt budget, and the deadline-free hold on a card already admitted into the parent's queue are all unchanged ([#2557](https://github.com/bastani-inc/atomic/issues/2557)).
+- Fixed a confirmed workflow pause silently reversing to a terminal failed run. Disposing a stage session while its stage was parked on an acknowledged pause rejected the parked pause waiter with `stage "<name>" session has been disposed`, which surfaced as a stage failure and emitted a terminal `workflow.run.end` with status `failed` — after `workflow pause` had already reported success and status had reported the run paused and resumable. Disposal that arrives during a confirmed pause is now deferred instead of rejecting the waiter, so the run stays paused and resumable and explicit resume continues through the normal path with intact metadata. Abort and kill still reject a parked waiter and fail visibly, a deferred disposal is still completed once that abort arrives, and disposal outside a confirmed pause is unchanged and still reported ([#2558](https://github.com/bastani-inc/atomic/issues/2558)).
+- Fixed a workflow stage session leak when a confirmed-paused stage was cleared from the live control registry, resumed through its stale handle, and then completed. Deferred controller cleanup now drains once at terminal completion, releasing the session and its listeners without double-disposal.
+
 ## [0.9.14] - 2026-08-19
 
 Cumulative release of the `0.9.14-alpha.1` – `0.9.14-alpha.6` prereleases. The summary below covers the user-visible outcome of that work; the per-change detail remains in the prerelease sections below.

package/dist/builtin/workflows/README.md

@@ -7,7 +7,7 @@
 
 Default to workflows for non-trivial work and requests with inherent structure plus a verifiable objective; reserve direct chat for tiny deterministic low-risk work. Workflow-first is not builtin-only or monolithic: Atomic can author custom TypeScript `workflow({...})` definitions inline, import reusable project/package workflows or builtins from `@bastani/workflows/builtin`, and nest them with `ctx.workflow(...)`. Imported children may nest further workflows within `maxDepth`, so compose proven research, implementation, design, verification, and approval graphs rather than copying them. Custom parents can also use runtime classification, dynamic fan-out and synthesis, adversarial verification, candidate tournaments, HIL gates, and bounded convergence.
 
-Workflow stage sessions are created in process and receive a typed stage policy rather than inheriting subagent environment flags. Resource reload never mutates `process.env`; stage options carry the subagent management/fanout policy directly, so concurrent stage creation is race-free while existing tool allowlists and orchestration depth limits remain authoritative. Legacy child environment keys are only a compatibility path for older hosts.
+Workflow stage sessions are created in process and receive a typed stage policy rather than inheriting subagent environment flags. Resource reload never mutates `process.env`; stage options carry the subagent management/fanout policy directly, so concurrent stage creation is race-free while existing tool allowlists and the one-level delegation rule remain authoritative. Legacy child environment keys are only a compatibility path for older hosts.
 
 <p align="center">
   <a href="#authoring-api">Authoring API</a>
@@ -441,7 +441,7 @@ Atomic registers the canonical `structured_output` tool only for schema-enabled
 
 When an item configures both `schema` and `output`, its successful `structured_output` turn has two separate channels: all ordinary assistant text blocks from that exact message, in order, form the human-readable artifact written to `output`, while the successful tool arguments remain the typed machine-readable workflow result. Atomic never serializes those arguments into the artifact. The runner snapshots the result together with the exact successful tool-call id, so corrective attempts, another call with the same tool name, and later admitted turns cannot replace either side of the pairing. When the successful message has no ordinary text — including after a model-fallback session recreation that leaves the live session without that message — Atomic falls back to the most recent earlier assistant text that made no `structured_output` call; only when no such text exists is the artifact written empty, with the standard empty-artifact warning in the receipt. Items with `schema` but no `output` keep their existing result-text behavior.
 
-`subagent` is available as a default workflow-stage tool with the same five-level nesting budget as main chat: a stage can launch recursively delegated subagents until the shared depth guard reaches five delegated levels, then deeper calls are blocked. `tools` allowlists apply to bundled extension tools as well as built-ins; if a stage sets `tools`, list every tool it should see. Workflow stages can explicitly list `subagent`, `web_search`, `fetch_content`, `intercom`, and other loaded extension tools, while `excludedTools` and `noTools: "all"` still win. Bundled `@bastani/subagents` agent definitions are available to the `subagent` tool in workflow stages, including workflows launched from a subagent child process.
+`subagent` is available as a default workflow-stage tool on the same terms as main chat: a stage is a top-level session, so it can delegate once, and the children it launches cannot delegate further. Delegation is one level deep and nothing configures it. `tools` allowlists apply to bundled extension tools as well as built-ins; if a stage sets `tools`, list every tool it should see. Workflow stages can explicitly list `subagent`, `web_search`, `fetch_content`, `intercom`, and other loaded extension tools, while `excludedTools` and `noTools: "all"` still win. Bundled `@bastani/subagents` agent definitions are available to the `subagent` tool in workflow stages, including workflows launched from a subagent child process.
 
 ### Model fallbacks
 

package/dist/builtin/workflows/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bastani/workflows",
-  "version": "0.9.14",
+  "version": "0.9.15-alpha.1",
   "private": true,
   "description": "Atomic extension for multi-stage workflow authoring and execution.",
   "contributors": [
@@ -10,7 +10,7 @@
   "license": "MIT",
   "type": "module",
   "engines": {
-    "bun": ">=1.3.14"
+    "bun": ">=1.4.0"
   },
   "main": "./src/index.ts",
   "types": "./src/authoring.ts",