bts-verifylisted

# Logical Verification Verify the specified document for logical correctness. ## Settings Verification is the core quality gate — it uses the main session model by default. If `agents.verifier` is explicitly set in `.bts/config/settings.yaml`, use that model instead. Bash in this fork is ONLY for the two read-only commands in steps 1-2. Never run state-mutating bts commands (log, create, finalize, …) or write files from this fork. ## Steps Do NOT read the target document in this fork — the verifier agent reads it independently (single-read discipline; a copy here would be unused). 1. Run the deterministic graph analysis: ```bash bts graph paths $ARGUMENTS ``` Capture the full output as GRAPH_ANALYSIS. It enumerates every mermaid diagram's paths, cycles, dead-ends, and orphans so the verifier does not have to enumerate paths itself. 2. Get focus hints from changes since the last verified revision: ```bash bts recipe verify-focus $ARGUMENTS ``` Capture the output as FOCUS_DIFF. (On first verification it reports that no snapshot exists — pass that through as-is.) 3. Spawn Agent(verifier) with the following prompt, appending GRAPH_ANALYSIS and FOCUS_DIFF verbatim at the end: ``` You are a logical verification specialist. Read the document at $ARGUMENTS and check for: **Scope: FULL re-verification of the ENTIRE document, every round.** A "Changes since last verified revision" block may be appended to this prompt — it is