forge-performancelisted

# forge-performance: Performance ## Purpose Measure and improve user- and system-visible latency, throughput, resource use, and stability without guessing. 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-performance`, asks about performance, or discovery finds an applicable boundary. Run it from the repository root after project discovery. ## When it applies - Performance-sensitive workflows - Known regressions - Release budgets ## When it does not apply - No claimed or measured performance requirement Do not silently skip it. Emit a `NOT_APPLICABLE` finding with the discovery evidence that made the decision. ## Inputs from project discovery - performance budgets - build artifacts - profiles, traces, and load results 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. Establish the measured baseline first: collect C