forge-observabilitylisted

# forge-observability: Observability ## Purpose Verify that logs, metrics, traces, events, alerts, and dashboards answer concrete operational questions safely. 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-observability`, asks about observability, or discovery finds an applicable boundary. Run it from the repository root after project discovery. ## When it applies - Long-running or production services - Critical client workflows ## When it does not apply - Pure build-time artifacts with no runtime behavior Do not silently skip it. Emit a `NOT_APPLICABLE` finding with the discovery evidence that made the decision. ## Inputs from project discovery - telemetry instrumentation - dashboards and alerts as code - incident runbooks 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. Pick three real operational questions (