verify-discipline

To stop running the full test suite repeatedly during iterative debugging, use scoped verification to run the narrowest reliable check for your specific change, reserving the full ticket verify command for a single final gate run immediately before submission.

Focused test selection for ticket-driven debugging is the process of deriving the closest documented check for the changed code path, preventing wasted time and transcript noise from repeatedly executing broad verification suites after every minor edit.

To execute final verification gating before submitting code changes, read the recorded verify command for the ticket and run the full suite once immediately before submission, ensuring all edits are validated without generating iterative transcript noise.

Yes, you can redirect full-suite output to a temporary log during verification gating, surfacing only the exit status and relevant failure lines to maintain transcript hygiene and reduce noise during debugging sessions.

Yes, verification discipline works for Sidequest executor changes by applying scoped test selection during iteration and preserving a single full gate run of the recorded verify command immediately before task submission.