T-Y6L4-reconcile-ensure-ready-pass-path-flags

Status: closed/done · Impact: low · Complexity: small

Goal

task-work Step 5a’s documented invocation of the readiness gate and ensure_ready_mutate.ts’s own pass-path argument validation disagree about --cleanup-on-fail: the skill prose shows the gate invoked with both --commit-on main --cleanup-on-fail, but the script rejects --cleanup-on-fail on the --mode pass path with exit 2. An operator (or automation) shelling the mutator directly on the PASS path therefore hits a hard validation error against guidance the skill itself documents. This task reconciles the two so the documented happy path actually runs. Surfaced by a downstream markdown-contract post-mortem.

task-work Step 5a documents invoking the readiness gate with both --commit-on main --cleanup-on-fail, but ensure_ready_mutate.ts --mode pass rejects --cleanup-on-fail (exit 2); an operator shelling the mutator directly on the PASS path hits the validation. Reconcile the disagreement — either the script’s pass-path arg validation should accept-and-ignore --cleanup-on-fail, or Step 5a’s flag guidance should stop documenting it on the pass path.

— from T-0P0U-web-ui-live-status-sse in git@github.com:sksizer/markdown-contract.git