fix(#2196): declare the debug session-manager spawn foreground + no-TaskOutput + recovery (#2227)

This commit is contained in:
Tom Boucher
2026-07-12 19:47:42 -04:00
committed by GitHub
parent a65ba8a02a
commit f8c5c1590f
22 changed files with 78 additions and 19 deletions

View File

@@ -190,6 +190,8 @@ Create `.planning/debug/{slug}.md` with initial state using the Write tool (neve
After initial context setup, spawn the session manager to handle the full checkpoint/continuation loop. The session manager handles specialist_hint dispatch internally: when gsd-debugger returns ROOT CAUSE FOUND it extracts the specialist_hint field and invokes the matching skill (e.g. typescript-expert, swift-concurrency) before offering fix options.
> **Foreground, blocking spawn — #2196.** The `Agent(subagent_type="gsd-debug-session-manager", …)` call below is FOREGROUND and BLOCKING — it returns the compact session summary directly. Wait for it; do not background it, and do not poll for it. Never pass an agent or session identifier to `TaskOutput` — an agent ID is NOT a task ID, so `TaskOutput <agent-id>` always returns `No task found with ID`. If the spawn returns no usable result (the handoff is lost), do NOT claim the session is still running: preserve the checkpoint at `.planning/debug/{slug}.md`, report the failed handoff plainly, and resume by re-spawning the session manager or via `/gsd:debug continue {slug}`.
Print before spawning (runs in a subagent — no output until it returns, ~1–5 min; expected, not a freeze):
```
[debug] Delegating loop to session manager...