verifylisted

## Live Context Before verification, gather current state: - Working directory: !`pwd` - Git status: !`git status --short 2>/dev/null || echo "Not a git repo"` - Recent commits: !`git log --oneline -5 2>/dev/null || echo "No git history"` - Last modified files: !`find . -type f -mmin -30 -not -path './.git/*' 2>/dev/null | head -10 || echo "None"` ## Intent Execute **verify** to determine whether an artifact (code, configuration, state, output) conforms to a specification, passes tests, or satisfies declared invariants. **Success criteria:** - Clear PASS or FAIL verdict with supporting evidence - Every check is grounded to observable output or file content - Failures include actionable fix suggestions - All assumptions about expected behavior are explicit **Compatible schemas:** - `schemas/output_schema.yaml` ## Inputs | Parameter | Required | Type | Description | |-----------|----------|------|-------------| | `spec` | Yes | string\|object | The specification, test suite, or invariants to check against | | `artifact` | Yes | string\|object | The target being verified (file path, function, API endpoint, state) | | `constraints` | No | object | Verification constraints: timeout, test filter, coverage threshold | | `check_types` | No | array | Types of checks: assertion, invariant, regression, schema | ## Procedure 1) **Load specification**: Read the spec/test/invariant definition - Identify testable assertions from the spec - Parse test commands or invariant ex