fix-worktree-build

Metadata

Description

## Objective
Isolated agent worktrees accumulate Rust `target/` build dirs with no retention, which exhausted the disk this session: agent-688/target=58G, agent-749/target=53G, agent-808/target=33G (144G total, from only 3 dead worktrees) pushed the volume to 100% full. There is no automatic cleanup of build artifacts in worktrees, and the disk guard only pauses new BUILDS after the damage is done.

## Work
- Add retention/cleanup for build artifacts inside worktrees: clean `target/` (and similar) for worktrees whose agent is dead/done/abandoned, on a cadence and on worktree reap.
- Make the existing disk guard proactive: estimate per-worktree target/ growth and clean/reclaim before hitting the warning floor, not only pause new builds after.
- Ensure `wg cleanup` (nightly/orphaned) sweeps dead worktrees' build artifacts.

## Validation
- [ ] Dead/done worktrees have their `target/` cleaned automatically (no manual `rm -rf` needed).
- [ ] A disk-full from accumulated worktree target/ cannot recur; the guard reclaims before the warning floor.
- [ ] `wg cleanup` removes dead-worktree build artifacts.

## Reference
This session: 144G in 3 dead worktrees' target/ -> disk 100% full (832M free).

Depends on

• (none)

Required by

• open .flip-fix-worktree-build

Log

• 2026-07-26T06:37:08.280589575+00:00 Task paused
• 2026-07-26T06:37:19.447956969+00:00 Task published
• 2026-07-26T07:16:43.809322001+00:00 Spawned by coordinator --executor pi --model zai:glm-5.2 --isolation required-worktree
• 2026-07-26T07:17:06.274049345+00:00 Task pending required evaluation gate (agent reported done; awaiting exact attempt-bound `.flip-*`/`.evaluate-*` verdicts)
• 2026-07-26T07:17:30.630178982+00:00 Pinned historical PendingEval as a required gate at evaluator threshold 0.70
• 2026-07-26T07:17:52.796291792+00:00 Pinned historical PendingEval as a required gate at evaluator threshold 0.70
• 2026-07-26T07:17:57.798031034+00:00 Pinned historical PendingEval as a required gate at evaluator threshold 0.70
• 2026-07-26T07:18:14.610317438+00:00 Pinned historical PendingEval as a required gate at evaluator threshold 0.70
• 2026-07-26T07:18:19.991508094+00:00 Pinned historical PendingEval as a required gate at evaluator threshold 0.70
• 2026-07-26T07:18:39.765637089+00:00 Pinned historical PendingEval as a required gate at evaluator threshold 0.70
• 2026-07-26T07:18:44.712105646+00:00 Pinned historical PendingEval as a required gate at evaluator threshold 0.70
• 2026-07-26T07:19:03.247503439+00:00 Pinned historical PendingEval as a required gate at evaluator threshold 0.70
• 2026-07-26T07:19:08.234111539+00:00 Pinned historical PendingEval as a required gate at evaluator threshold 0.70
• 2026-07-26T07:19:23.899693640+00:00 Pinned historical PendingEval as a required gate at evaluator threshold 0.70
• 2026-07-26T07:28:04.759640994+00:00 Pinned historical PendingEval as a required gate at evaluator threshold 0.70
• 2026-07-26T07:28:09.766793419+00:00 Repaired evaluation pipeline drift for authoritative source attempt 1 (evalp-9cc381eb5874f82d80d34445)
• 2026-07-26T07:57:06.580019545+00:00 Pinned historical PendingEval as a required gate at evaluator threshold 0.70
• 2026-07-26T08:14:35.747028121+00:00 Task reset for retry from pending-eval/failed-pending-eval (stuck evaluation gate) (attempt #1) — reason: Operator recovery: clear legacy pending-eval hold with the newly sanctioned CLI; keep paused until reliability review.
• 2026-07-26T08:14:35.747035141+00:00 Cleared stuck evaluation gate via `wg retry` — a fresh attempt will be minted; no graph.jsonl edit required.
• 2026-07-26T08:14:35.747057172+00:00 Minted evaluation pipeline evalp-992d3495b014fa022eb81694 for source attempt 2 (resume-in-place retry)
• 2026-07-26T08:14:35.811559765+00:00 Task paused