forge-deploymentlisted

# forge-deployment: Deployment ## Purpose Inspect build promotion, configuration, migrations, rollout, rollback, health, and environment parity. 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-deployment`, asks about deployment, or discovery finds an applicable boundary. Run it from the repository root after project discovery. ## When it applies - Deployable applications and services ## When it does not apply - Source-only examples never deployed or distributed Do not silently skip it. Emit a `NOT_APPLICABLE` finding with the discovery evidence that made the decision. ## Inputs from project discovery - CI workflow - deployment configuration - build and migration 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. Trace the path from commit to production: CI gates, build reproducibility, artifact promotion,