twining-verifylisted

# Twining Verify — Pre-Completion Verification For complex tasks (multi-file changes, architectural decisions, long sessions), verify your work against Twining's coordination state. For simple tasks, posting a `status` entry via `twining_post` is sufficient. > **Note:** `twining_verify` requires `tools.full_surface: true` in config. If not available, post a `status` entry via `twining_post` summarizing what you did. ## When to Invoke - Complex multi-file changes with architectural decisions - Before handing off work to another agent on a large task - Before creating a pull request with significant changes - When you want to check for decision drift or unresolved warnings ## Workflow ### 1. Run Verification Call `twining_verify` with: - `scope`: The area you worked on (e.g., `"src/auth/"`) - `checks`: Array of checks to run. Include all relevant ones: - `"test_coverage"` — Are decisions backed by `tested_by` relations? - `"warnings"` — Are all warnings acknowledged or resolved? - `"assembly"` — Were decisions made after assembling context (not "blind")? - `"drift"` — Has code drifted from decision intent? - `"constraints"` — Do checkable constraints still pass? ### 2. Interpret Results Each check returns a status: **`pass`** — No issues found. Proceed. **`warn`** — Issues exist but aren't blocking: - Uncovered decisions (no `tested_by` relation) — consider adding test links - Blind decisions (made without `twining_assemble`) — acknowledge or re-verify - Mi