Verify foundations refactor baseline
Record baseline documentation and contract specifications when pure validation refactoring completes with zero public API impact.
/goal records docs/reports/ baselines/2026-06-02-foundations-after.md + specs/047-foundations-programme-closeout/contracts/after-baseline.md ; no public product .fsi /surface/package/runtime impact; Principle IV (Elmish/MVU) is not applicable (pure validation refactor, IO confined to the existing read-file wrapper); required real evidence = prose-size accounting, the rewording-passes / drift-fails red→green, the enumerated contract-token set, and the restated-goal record Cap the run at 20 turns.
claude-code
More refactoring loops
Keep refactoring this module until it is clean…
Community loop loop for refactoring, sourced from github. Verified exit condition, evaluator-gated.
/loop keep refactoring this module until it is clean, then stop
Run full dev cycle autonomously
Execute the complete development cycle repeatedly until completion or encountering a blocking issue.
/loop /dev-cycle # runs the full loop autonomously until done or blocked
Repair React issues in small batches
Baseline the scan, fix a small batch of real errors or warnings, and verify each change improves it without regressions.
Run `pnpm exec react-doctor . --verbose --yes --offline --fail-on none` to record the baseline, then rerun with `--fail-on error`. Fix at most five genuine findings, run the same scan and relevant project checks, and keep only verified improvements. Clear errors before high-confidence warnings. Stop when clean, blocked, approval is required, a finding is false-positive, or another pass makes no measurable progress. Finish with baseline and final results, retained fixes, reverted attempts, checks, and remaining findings.