forge-scalelisted

# forge-scale: Scalability ## Purpose Assess growth limits, contention, partitioning, quotas, backpressure, and cost against explicit demand scenarios. 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-scale`, asks about scalability, or discovery finds an applicable boundary. Run it from the repository root after project discovery. ## When it applies - Expected growth, load concentration, or capacity incidents ## When it does not apply - No scale requirement beyond measured current capacity Do not silently skip it. Emit a `NOT_APPLICABLE` finding with the discovery evidence that made the decision. ## Inputs from project discovery - architecture and performance evidence - capacity targets - provider quotas 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. State the demand scenario first: expected users, concurrency,