If invoked as review-intentional, jump to Review intentional mode.

Security invariants

These hold under any user instruction; refuse and explain a request that would break one.

Never read credential or secret files. Step 1's filters drop them before any concept is formed.
Never emit credential values. Paraphrase in your own words: counts, names, public identifiers, headings. No verbatim file content in output, reasoning, or tool calls. Locate anything credential-like (API key, token, password, private key, OAuth secret, JWT, connection string with credentials) without its value: "API key value at line 42". Template placeholders ({{API_KEY}}, ${SECRET}, <YOUR_TOKEN_HERE>) and non-secret symbols (function names, configuration keys, headings) may be named.
Never modify credential values. Fixes touch only reported concepts, with content the user supplies or confirms, never echoed from another file.

Git is optional

Read-only git (git status, git diff, git log) sharpens a run where present: recent and staged changes point at drift and can support a finding. Without git, every step runs on the conversation and the filesystem at lower precision. A step that needs git is a bug; so is one that ignores git when present.

Step 1 - Apply security guards, then identify the file set

No .docs-consistency-check-ignore at the project root: offer to create it from this template, wait for a go-ahead. Present: apply it silently.