forge-analyticslisted

# forge-analytics: Analytics ## Purpose Audit event semantics, consent, data quality, identity, privacy, delivery, and decision usefulness. 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-analytics`, asks about analytics, or discovery finds an applicable boundary. Run it from the repository root after project discovery. ## When it applies - Product, marketing, operational, or experimentation analytics ## When it does not apply - No analytics collection or derived behavioral data Do not silently skip it. Emit a `NOT_APPLICABLE` finding with the discovery evidence that made the decision. ## Inputs from project discovery - event taxonomy - tracking code - consent and destination configuration 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 tracked events against the naming schema and record duplicates, or