forge-storagelisted

# forge-storage: Object and file storage ## Purpose Inspect object naming, access control, encryption, lifecycle, consistency, integrity, and recovery. 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-storage`, asks about object and file storage, or discovery finds an applicable boundary. Run it from the repository root after project discovery. ## When it applies - Object stores, file systems, blob databases, and CDN-backed assets ## When it does not apply - No persistent files or objects Do not silently skip it. Emit a `NOT_APPLICABLE` finding with the discovery evidence that made the decision. ## Inputs from project discovery - storage clients - bucket and CDN configuration - object references 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 storage destinations (buckets, filesystems, database blobs) w