forge-querieslisted

# forge-queries: Query behavior ## Purpose Find correctness, injection, overfetching, N+1, pagination, locking, and index-use risks in data access. 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-queries`, asks about query behavior, or discovery finds an applicable boundary. Run it from the repository root after project discovery. ## When it applies - Database, search, analytics, and remote query code ## When it does not apply - Systems with no queryable data source Do not silently skip it. Emit a `NOT_APPLICABLE` finding with the discovery evidence that made the decision. ## Inputs from project discovery - query call sites - schema and indexes - representative query plans when available 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 query call sites from ORM and driver evidence and identify the hot pat