forge-codelisted

# forge-code: Code quality ## Purpose Find correctness, maintainability, type-safety, error-handling, and dead-code risks in changed and critical paths. 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-code`, asks about code quality, or discovery finds an applicable boundary. Run it from the repository root after project discovery. ## When it applies - Source changes - Release readiness - Refactoring ## When it does not apply - Repositories containing only non-executable documentation Do not silently skip it. Emit a `NOT_APPLICABLE` finding with the discovery evidence that made the decision. ## Inputs from project discovery - project profile - changed-file set - formatter, linter, and typecheck commands 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. Run the project's own formatter, linter, and type checker in ch