Skip to content

[v6-p4p5] Recursive planner (refuses unsafe, proposes one, stops) + soak operations (889 tests green)#50

Merged
CTlanston merged 7 commits into
mainfrom
claude/v6-p4-recursive-planner
Jun 11, 2026
Merged

[v6-p4p5] Recursive planner (refuses unsafe, proposes one, stops) + soak operations (889 tests green)#50
CTlanston merged 7 commits into
mainfrom
claude/v6-p4-recursive-planner

Conversation

@CTlanston

Copy link
Copy Markdown
Owner

V6-P4 (recursive planner) + V6-P5 (soak operations)

Recursive planner (packages/daemon/src/recursive-planner.ts, 20 tests): pure planNextCycle with 8 refusal paths (dirty tree / red tests / blocked budget / ambiguous SoT / open holds / unmerged prev PR / unparseable §0 / empty registry — each with human recovery); strict single-pick priority safety_evidence > user_ux > automation > fleet > polish; cycle ledger to evidence/loop-cycles/ AND event-sourced (planner.cycle_planned, rebuildable — GR#5). pnpm loop:plan shell gathers real inputs (actually runs the test suite, scans SoT claimants, checks the real budget db) and stops at the proposal — never implements, never pushes (GR#10).

First real run committed as evidence: a smoke run honestly REFUSED on a dirty tree; the official clean run proposed cycle 1 = v6-p3-real-proof-closeout (safety_evidence) — exactly the operator-gated top gap. evidence/loop-cycles/cycle-1.json.

Soak ops (docs/operations/SOAK_OPERATIONS.md + pnpm soak:status, 5 tests): one-week command, launchd plist, evidence contract, resume/failure recovery, ntfy wiring, soak-pending.json status artifact (overdue detection, sticky terminal states).

WORKBOOK_v6 §0 → V6-P6; V6-P3 stays honestly operator-gated. Gates: typecheck ✅ lint ✅ test 889 passed / 0 failed / 6 skipped (+25).

https://claude.ai/code/session_01AgdV9SKZZP6JbyTBo2gAWZ


Generated by Claude Code

@CTlanston CTlanston marked this pull request as ready for review June 11, 2026 02:23
@CTlanston CTlanston merged commit 4ff0806 into main Jun 11, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants