goal-batch/goalify/GOAL_COMMAND: resource hygiene for autonomous fan-out

[Brian Krabach (bkrabach)]

Why

Postmortem (2026-08-29) of a runaway autonomous fan-out: parallel work created 126 containers over 3 days with no teardown, no cumulative ledger, and no cap — the host hit 100% disk and stalled.

The gap is a pattern, not a one-off:

• Parallel-work guidance cleans up its own orchestration artifacts (worktrees, branches, tmux sessions) but is blind to resources the work units create — containers, VMs, background servers, environments.
• Per-unit bounds (turns, wall-clock) bound an agent's activity, not the cumulative resources that activity accumulates. A run can exit cleanly having stood up a hundred resources nothing ever reclaims.

This PR closes that gap across the three surfaces that shape autonomous runs.

What changed

amplifier_app_cli/data/skills/goal-batch/SKILL.md

• Phase 1 — clarify the "no lane cap" rule governs lanes, not the resources lanes create. Those need a cumulative batch-wide ceiling tracked in an orchestrator-owned resource ledger, because each lane sees only its own usage, never the total.
• Phase 3 — each lane's goal must enumerate any non-git resources it provisions (containers, VMs, background servers, environments) and include their teardown (or explicit handoff) in the lane's own DONE criteria; resources[] added to the DONE.json field list.
• Phase 7 — lanes report what they created via resources[]; the orchestrator verifies teardown as part of landing, and the orphan sweep extends beyond tmux (docker ps / incus list / process list) for survivors tied to the batch.

amplifier_app_cli/data/skills/goalify/SKILL.md

• New lint check L7: if a goal provisions infrastructure or long-lived resources, the stop condition must include teardown-complete (or explicit handoff) as part of DONE. A goal that ends with resources running and unowned is abandoned, not finished. Added to the lint table.

docs/GOAL_COMMAND.md

• In "What the cap does NOT bound": turn and wall-clock caps do not bound the resources spawned by the work. Unattended runs that provision anything need an external resource ledger and cumulative ceiling, with teardown as part of the run.

Notes

• Resource types are described generically; third-party command examples (docker, incus, tmux) are used for illustration only.
• Docs/skill-only change — no code paths touched.

🤖 Generated with Amplifier