forge-integrationslisted

# forge-integrations: External integrations ## Purpose Audit outbound and inbound integrations for authentication, validation, failure isolation, drift, and replay safety. 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-integrations`, asks about external integrations, or discovery finds an applicable boundary. Run it from the repository root after project discovery. ## When it applies - Third-party APIs, webhooks, SDKs, and service-to-service calls ## When it does not apply - Self-contained applications with no external dependency Do not silently skip it. Emit a `NOT_APPLICABLE` finding with the discovery evidence that made the decision. ## Inputs from project discovery - integration inventory - SDK manifests - webhook routes and secrets 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. Inventory outbound calls an