agent-afk 5.226.2 → 5.226.4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -74,7 +74,7 @@ This phase validates each spec item independently before any writes begin. The g
74
74
 
75
75
  **Fast-path:** if the numbered spec contains exactly 1 item, skip this phase entirely -- dispatch directly to Phase 3 with the raw spec item. The parallel wave's value is proportional to item count; for a single item the overhead exceeds the benefit.
76
76
 
77
- **For 2+ spec items:** dispatch N read-only sub-agents in parallel via the `agent` tool (one call per spec item in the same tool-use turn -- pure fan-out). Do NOT use `compose` for this wave: compose nodes accept only `{ id, prompt, model }` and cannot carry `agent_type` or per-node `cwd`, so the read-only and worktree-scoping guarantees would be silently lost. Each probe:
77
+ **For 2+ spec items:** dispatch N read-only sub-agents in parallel via the `agent` tool (one call per spec item in the same tool-use turn -- pure fan-out). Do NOT use `compose` for this wave: compose passes `agent_type` as a display label only -- it does NOT resolve named agents through the agent registry, so tool-surface restrictions (e.g. research-agent's read-only enforcement) are silently lost. Until compose wires registry resolution (see #2000), only the `agent` tool enforces named-agent permissions. Each probe:
78
78
 
79
79
  - **agent_type:** `research-agent` (mechanically read-only -- cannot write files, run bash, or commit).
80
80
  - **cwd:** `<worktree path>` (so file reads target the PR branch, not the main working tree).