forge-requirementslisted

# forge-requirements: Requirements and domain logic ## Purpose Trace business rules and acceptance criteria to executable behavior, including adverse and recovery 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-requirements`, asks about requirements and domain logic, or discovery finds an applicable boundary. Run it from the repository root after project discovery. ## When it applies - Feature work - Domain-rule changes - Release readiness ## When it does not apply - Pure formatting changes with no behavior impact Do not silently skip it. Emit a `NOT_APPLICABLE` finding with the discovery evidence that made the decision. ## Inputs from project discovery - project profile - product documentation - tests and route handlers 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. Collect the requirement sources that