forge-offlinelisted

# forge-offline: Offline behavior ## Purpose Audit local persistence, queued actions, synchronization, conflicts, revocation, privacy, and recovery under intermittent connectivity. 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-offline`, asks about offline behavior, or discovery finds an applicable boundary. Run it from the repository root after project discovery. ## When it applies - Offline-capable web, mobile, or desktop applications - Clients that queue writes or cache private state ## When it does not apply - Online-only clients that store no durable application data locally Do not silently skip it. Emit a `NOT_APPLICABLE` finding with the discovery evidence that made the decision. ## Inputs from project discovery - service workers and local stores - sync protocol - authorization and conflict rules 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 decisio