fix-wg-cleanup

Metadata

Description

## Objective
`wg cleanup nightly` and `wg cleanup orphaned` fail with "Error: WG not initialized. Run 'wg init' first." when run from the repo root of a fully initialized, actively-running graph (the daemon dispatches on it fine). So the sanctioned disk/lifecycle cleanup is unusable exactly when it's needed, forcing manual `rm`/graph surgery. (`wg cleanup orphaned --dir` exists but the default path detection is broken.)

## Work
- Fix graph detection for the `wg cleanup *` subcommands so they operate on the current project graph by default (consistent with `wg service`, `wg agents`, etc.).
- Honor `--dir` / `--graph` explicitly; default to the CWD project graph.
- Verify dry-run + --execute both work from a standard repo layout.

## Validation
- [ ] `wg cleanup nightly` and `wg cleanup orphaned` run from the repo root without "not initialized"; dry-run reports, --execute cleans.
- [ ] Graph detection matches the rest of the wg CLI.

## Reference
This session: both cleanup subcommands errored "WG not initialized" on a running graph.

Depends on

• (none)

Required by

• open .flip-fix-wg-cleanup

Log

• 2026-07-26T06:37:08.367317610+00:00 Task paused
• 2026-07-26T06:37:19.821511425+00:00 Task published
• 2026-07-26T07:16:17.917851669+00:00 Spawned by coordinator --executor pi --model zai:glm-5.2 --isolation required-worktree
• 2026-07-26T07:16:39.829210363+00:00 Task pending required evaluation gate (agent reported done; awaiting exact attempt-bound `.flip-*`/`.evaluate-*` verdicts)
• 2026-07-26T07:17:06.951213562+00:00 Pinned historical PendingEval as a required gate at evaluator threshold 0.70
• 2026-07-26T07:17:30.630310046+00:00 Pinned historical PendingEval as a required gate at evaluator threshold 0.70
• 2026-07-26T07:17:52.796240830+00:00 Pinned historical PendingEval as a required gate at evaluator threshold 0.70
• 2026-07-26T07:17:57.797972082+00:00 Pinned historical PendingEval as a required gate at evaluator threshold 0.70
• 2026-07-26T07:18:14.610393689+00:00 Pinned historical PendingEval as a required gate at evaluator threshold 0.70
• 2026-07-26T07:18:19.991521694+00:00 Pinned historical PendingEval as a required gate at evaluator threshold 0.70
• 2026-07-26T07:18:39.765502135+00:00 Pinned historical PendingEval as a required gate at evaluator threshold 0.70
• 2026-07-26T07:18:44.712262931+00:00 Pinned historical PendingEval as a required gate at evaluator threshold 0.70
• 2026-07-26T07:19:03.247450887+00:00 Pinned historical PendingEval as a required gate at evaluator threshold 0.70
• 2026-07-26T07:19:08.233954295+00:00 Pinned historical PendingEval as a required gate at evaluator threshold 0.70
• 2026-07-26T07:19:23.899469313+00:00 Pinned historical PendingEval as a required gate at evaluator threshold 0.70
• 2026-07-26T07:28:04.759807179+00:00 Pinned historical PendingEval as a required gate at evaluator threshold 0.70
• 2026-07-26T07:28:09.766931413+00:00 Repaired evaluation pipeline drift for authoritative source attempt 1 (evalp-67088563a8d6ed494c156a7c)
• 2026-07-26T07:57:06.580107167+00:00 Pinned historical PendingEval as a required gate at evaluator threshold 0.70
• 2026-07-26T08:14:36.177991176+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:36.177996316+00:00 Cleared stuck evaluation gate via `wg retry` — a fresh attempt will be minted; no graph.jsonl edit required.
• 2026-07-26T08:14:36.178021157+00:00 Minted evaluation pipeline evalp-b25050361c2e078a033539eb for source attempt 2 (resume-in-place retry)
• 2026-07-26T08:14:36.240089821+00:00 Task paused