baldart 5.11.0 → 5.11.1

package/CHANGELOG.md

@@ -5,6 +5,17 @@ All notable changes to BALDART will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [5.11.1] - 2026-07-07
+
+**`/new` now tears down its idle background subagents at end of run — closes the "Background work is running" leak on terminal exit.**
+A user reported that after every interactive `/new` run, closing the terminal warns `Background work is running` and lists the batch's teammates (`## AUTONOMOUS CARD IMPLEMENTATION — FEAT-00NN`, the `i18n-translator` fill, the doc closer) as if they were still executing. They are not — they **finished**. Root cause: `/new` spawns its coder + closer subagents with `run_in_background: true`, and a background subagent that completes its work does **NOT** terminate — it goes idle ("rests") so the orchestrator could `SendMessage`/resume it (deliberate: the empty-result gate reads their transcripts from disk, and the framework explicitly forbids messaging a rested teammate). Phase 6c's teardown ended the **Codex broker** (a Bash process) + reaped orphan MCP servers, but there was **no `TaskStop` anywhere in the framework** — so the idle teammates stayed alive until Claude Code's `SessionEnd` (whenever the user closes the terminal). Harmless to the committed work (already merged), but noisy and wasteful of session resources.
+
+- **New Phase 6c step 5c** (`framework/.claude/skills/new/references/merge-cleanup.md`) — after the merge and after every teammate's transcript has been consumed, `TaskList` → `TaskStop` the batch's idle teammates, scoped to THIS run only: matched by the `coder-<CARD-ID>` name prefix OR any card ID in the tracker `## Card Queue` (so the match survives a compaction). NEVER stops a task outside the batch signature (the user's unrelated background work in the same session). Best-effort + non-blocking + one log line (`Background subagents teardown: <stopped N | none alive | N/A (Codex) | skipped>`).
+- **Mirror on early exit** (`framework/.claude/skills/new/SKILL.md` § "Terminal hygiene") — the same `TaskList`→`TaskStop` runs when the batch ends before Phase 6c (unrecoverable HALT / killed final-review workflow), exactly as the Codex-broker early teardown already did.
+- **Pointer** in `references/team-mode.md` — the parallel `coder-<CARD-ID>` fan-out is the widest source of the leak; noted that Phase 6c 5c tears them down after merge.
+- **`/new2` is unaffected** — its agents run inside the dynamic-workflow runtime and die with the workflow; only the classic `/new` (Task-tool background subagents) leaked.
+- **Codex parity: N/A** — no observable Agent/Task tool on Codex, team-mode is forced sequential there, and Codex named-agent spawns do not persist as idle background tasks (`framework/agents/runtime-portability-protocol.md`). **No new `baldart.config.yml` key** → the schema-change propagation rule does NOT apply. `/new` skill version → 2.4.1.
+
 ## [5.11.0] - 2026-07-06
 
 **Seamless framework-drift reconciliation in `baldart update` — a trivially-drifted shared framework file no longer dead-ends the whole update.**

package/VERSION

@@ -1 +1 @@
-5.11.0
+5.11.1

package/framework/.claude/skills/new/CHANGELOG.md

@@ -2,6 +2,22 @@
 
 Formato: [Keep a Changelog](https://keepachangelog.com/) · [SemVer](https://semver.org/).
 
+## 2.4.1 — 2026-07-07
+
+- **Teardown dei subagent in background a fine run (chiude il leak "Background work is running").**
+  I coder + closer di `/new` sono spawnati con `run_in_background: true`; un subagent che finisce il
+  lavoro **non termina** — va in idle ("rests") così l'orchestratore *potrebbe* farne resume. Il
+  teardown di Phase 6c fermava solo il **broker Codex** (processo Bash), mai i subagent → restavano
+  vivi in idle fino al `SessionEnd`, comparendo come "Background work is running" alla chiusura del
+  terminale. Nuovo step **6c.5c** (`references/merge-cleanup.md`): dopo il merge, `TaskList` →
+  `TaskStop` sui soli teammate di QUESTO batch — matchati per `coder-<CARD-ID>` o per card-ID dal
+  tracker `## Card Queue` (sopravvive alla compaction); mai un task fuori dalla firma del batch
+  (lavoro background non correlato dell'utente). Best-effort + non-bloccante + riga di log. Mirror
+  dello stesso teardown nel path di uscita anticipata (`SKILL.md` § "Terminal hygiene"); pointer in
+  `references/team-mode.md` (i coder paralleli sono la fonte principale del leak). `/new2` non è
+  affetto (agent nel runtime del workflow → muoiono col workflow). Codex parity: N/A (nessun
+  Agent/Task tool osservabile; team-mode forzato sequenziale). Nessuna nuova chiave `baldart.config.yml`.
+
 ## 2.4.0 — 2026-07-06
 
 - **Prossime wave per NOME nel messaggio finale.** Il Step F.6 "Prossimi Passi"

package/framework/.claude/skills/new/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: new
 effort: medium
-version: 2.4.0
+version: 2.4.1
 requires_feature: has_backlog
 description: >
   Orchestrate a team of specialized agents to implement one or more backlog cards
@@ -472,6 +472,14 @@ printf '%s' "$TD" | grep -qi "unknown command" \
 This NEVER touches a broker for another worktree or the user's interactive session (different cwd). If the
 orchestrator is hard-killed and never resumed, the `baldart doctor` reaper is the final safety net.
 
+**Also stop THIS batch's idle background subagents on that early exit** (Claude-only, best-effort) — the
+same teardown Phase 6c step 5c runs on the normal close. `/new`'s coder + closer teammates (`run_in_background`)
+go idle rather than terminate, so an early exit leaves them alive and they surface as "Background work is
+running" when the user closes the terminal. `TaskList` → `TaskStop` each task named `coder-<CARD-ID>` or whose
+name/prompt references a card ID from the tracker `## Card Queue`; NEVER stop a task that does not match the
+batch signature (the user's unrelated background work). Any `TaskStop` error / absent tool is fine — never
+gate the exit on it. (Codex: N/A — no observable Task tool.)
+
 ---
 
 

package/framework/.claude/skills/new/references/merge-cleanup.md

@@ -263,6 +263,28 @@ The most common failure mode is leaving cards IN_PROGRESS after merge. This crea
    Never gate the close on these — any error or a "nothing to do" result is fine; capture each one-line
    summary for the log.
 
+5c. **Background subagent teardown — stop THIS batch's idle teammates (Claude-only, NON-BLOCKING)**.
+   `/new` spawns coder + closer subagents with `run_in_background: true` (team-mode coders
+   `coder-<CARD-ID>`, the step-7c `i18n-translator` fill, the doc closer). A background subagent that
+   finishes its work does **NOT** terminate — it goes idle ("rests") so the orchestrator *could*
+   resume it (and the empty-result gate reads its transcript from disk, never via `SendMessage`). By
+   Phase 6c every card is merged and every teammate's transcript has already been consumed, so these
+   idle teammates are pure dead weight — but the broker teardown above only ends the **Codex broker**
+   (a Bash process); it does NOT touch the subagents. Left alone they stay alive until Claude Code's
+   `SessionEnd` (hours away) and surface as **"Background work is running"** the moment the user tries
+   to close the terminal — noise + held session resources, though the committed work is already safe.
+   Stop ONLY the teammates belonging to THIS batch — matched by the batch's card IDs (read from the
+   tracker `## Card Queue`, so the match survives a compaction) or the `coder-` name prefix:
+   - `TaskList` → for each task still `running`/idle whose `name` is `coder-<CARD-ID>` OR whose
+     `name`/prompt references any card ID in `## Card Queue` (e.g. `FEAT-00NN`) → `TaskStop` it.
+   - **NEVER** `TaskStop` a task that does not match the batch signature — the user may have unrelated
+     background work in the same session. When a task's ownership is ambiguous, LEAVE it (a stray idle
+     `/new` teammate is harmless; killing the user's unrelated work is not).
+   Best-effort: a `TaskStop` error / "already stopped" / an absent `TaskList` tool is all fine —
+   capture a one-line count for the log, never gate the close on it. **(Codex path — N/A:** no
+   observable Agent/Task tool, team-mode is forced sequential, and Codex named-agent spawns do not
+   persist as idle background tasks — see `framework/agents/runtime-portability-protocol.md`.)
+
 6. **Log and exit**:
    ```
    ## Phase 6c — Workspace Hygiene Post-merge
@@ -273,6 +295,7 @@ The most common failure mode is leaving cards IN_PROGRESS after merge. This crea
    Phase 0 snapshot restore: <n/a | popped clean | conflict-deferred-to-user>
    Codex broker teardown: <graceful (pid) | signalled N | none | skipped (error)>
    Codex MCP hygiene (reap): <reaped N/M | nothing to reap | skipped (error)>
+   Background subagents teardown: <stopped N | none alive | N/A (Codex) | skipped (error)>
    Completed: <timestamp>
    ```
    If any step ended in HALT, set `Status: HALT` and report — Phase 7 must NOT start with an unclean main repo unless the user explicitly chose `[Lascia così]`.

package/framework/.claude/skills/new/references/team-mode.md

@@ -348,4 +348,6 @@ Before starting group N, verify ALL cards in groups 0..N-1 are status: done. If
 
 After all groups are complete, run the same Final Review, Phase 6 (merge), and Phase 7 (production readiness) as documented above. Since v3.37.0 the Final Review runs a **single FULL `/codexreview` over the entire batch diff** (per the Final-review FULL gate) — no scope reduction — so every team-mode card, including any reviewed at `light` in D.4b, receives a guaranteed full review before merge.
 
+> **The parallel `coder-<CARD-ID>` teammates are torn down at Phase 6c step 5c** (`references/merge-cleanup.md`) — a `run_in_background` coder goes idle rather than terminating, so team mode (the widest fan-out) is the main source of the "Background work is running" idle-teammate leak. The Phase 6c teardown `TaskStop`s them after merge; nothing to do here.
+
 ---

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "baldart",
-  "version": "5.11.0",
+  "version": "5.11.1",
   "description": "Claude Agent Framework - Reusable framework for coordinating AI agents and humans in software projects",
   "bin": {
     "baldart": "./bin/baldart.js"