forge-authorizationlisted

# forge-authorization: Authorization ## Purpose Verify deny-by-default function, object, role, tenant, and administrative authorization on every path. 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-authorization`, asks about authorization, or discovery finds an applicable boundary. Run it from the repository root after project discovery. ## When it applies - Any private, role-gated, owned, tenant, or administrative resource ## When it does not apply - Public read-only content with no hidden data or action Do not silently skip it. Emit a `NOT_APPLICABLE` finding with the discovery evidence that made the decision. ## Inputs from project discovery - role inventory - private and admin routes - policy code and tests 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. Build the access-control matrix: subjects, roles, res