docs-claim-auditlisted

# Docs Claim Audit ## Purpose Keep public documentation factual, bounded, and backed by repo evidence. ## Preserves Source-based reasoning and documentation honesty. ## Required Evidence - Changed docs or claim text. - Files, tests, scripts, examples, or commands that support each claim. - Known limitations or unsupported surfaces. - Target audience if relevant. ## Failure Signs - Docs claim a feature exists without a backing file or command. - Limitations are hidden behind polished wording. - Examples imply behavior that tests or scripts do not support. ## When To Use - README, docs, comments, examples, or public copy change. - A claim describes support, readiness, security, compatibility, or behavior. - Docs mention tests, checks, integrations, or runtime support. - A reviewer suspects marketing filler or unsupported scope. ## When Not To Use - Typo-only edits with no factual claim change. - Private local notes that are not public docs. - The task is to check external docs before coding; use read-the-docs-first. ## Inputs Expected - Changed documentation or claim list. - Relevant source files, validators, tests, scripts, examples, and command output. - Known limitations or out-of-scope behavior. - Diff if available. ## Output Expected ```md Claim: Evidence found: Unsupported part: Required edit: Verification: Decision: ``` ## Process 1. Extract each factual claim from the changed text. 2. Trace each claim to a repo artifact or command output. 3. Mark claim