forge-docslisted

# forge-docs: Documentation ## Purpose Verify that user, contributor, architecture, operations, security, and release documentation is accurate and executable. Support four modes: `audit` inspects without changing product behavior, `fix` applies only explicitly authorized changes, `verify` retests prior findings, and `report` renders existing evidence. If no mode is supplied, use `audit`. ## Trigger conditions Use this module when a request names `forge-docs`, asks about documentation, or discovery finds an applicable boundary. Run it from the repository root after project discovery. ## When it applies - Every maintained or distributed project ## When it does not apply - No exemption; scope follows the artifact's audience Do not silently skip it. Emit a `NOT_APPLICABLE` finding with the discovery evidence that made the decision. ## Inputs from project discovery - documentation tree - CLI help - configuration and workflows Prefer `.forge/project-profile.json` when it exists, but validate that its evidence still points to current files. Read `../fullstack-forge/references/PROTOCOL.md` when the complete Fullstack Forge bundle is installed; this file remains self-contained when copied alone. ## Inspection procedure 1. Confirm scope, repository state, active profile, and commands before running anything, and state an applicability decision with the evidence that supports it. 2. Execute the README setup path in a clean environment and record where it breaks or diverg