jds-verify

Test verification requires running exact commands and displaying complete outputs to back task completion. This structured workflow executes tests, plan checks, and regression verification to ensure claims are provably correct.

Auditable completion criteria require a repeatable verification workflow that enforces running tests and command-based checks. This provides traceable results across the software development lifecycle to eliminate unverified claims.

Regression checks and plan verification are executed by running specific verification commands for the current task. The complete command output is displayed to provide end-to-end evidence and structured validation.

Completion claims fail when concrete verification outputs are missing because unverified claims cannot be proven correct. Enforcing test execution and command-based checks eliminates this gap and routes failures for diagnosis.

Test failures and verification errors are routed to jds-debug for diagnosis. This ensures that command outputs showing failures during regression checks or plan verification are systematically analyzed rather than ignored.

Command-based verification supports end-to-end evidence across the software development lifecycle by enforcing test runs and plan checks. It applies to any software task requiring provably correct results and structured validation.