bts-auditlisted

# Completeness Audit Audit the specified document for missing items. ## Settings Audit requires finding what's missing — it uses the main session model by default. If `agents.auditor` is explicitly set in `.bts/config/settings.yaml`, use that model instead. Bash in this fork is ONLY for the read-only command in step 1. Never run state-mutating bts commands or write files from this fork. ## Steps Do NOT read the target document in this fork — the auditor 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. 2. Spawn Agent(auditor) with the following prompt, appending GRAPH_ANALYSIS verbatim at the end: ``` You are a completeness audit specialist. Read the document at $ARGUMENTS. Your goal: find everything the document fails to address that could cause problems at runtime, during deployment, or under adversarial conditions. **Content completeness:** Think about failure modes, boundary conditions, unstated assumptions, missing integrations, security gaps, and operational concerns. Do not limit yourself to a fixed checklist — reason about what this specific system needs and what the document leaves unanswered. **Flow completeness (mermaid diagrams):** A deterministic "Mermaid Graph Analysis" block is appended to this prompt — its path/cycle/dead-end/orphan enumeration