forge-shiplisted

# forge-ship: Release readiness ## Purpose Enforce a fail-closed release gate across project checks, findings, generated assets, packages, licenses, and installation. 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-ship`, asks about release readiness, or discovery finds an applicable boundary. Run it from the repository root after project discovery. ## When it applies - A candidate release or deployment ## When it does not apply - Exploratory work not represented as release-ready Do not silently skip it. Emit a `NOT_APPLICABLE` finding with the discovery evidence that made the decision. ## Inputs from project discovery - project profile - finding reports - detected project commands - package and license manifests 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. Assemble the gate inputs: latest audit findings, tes