forge-tenancylisted

# forge-tenancy: Multi-tenancy ## Purpose Verify tenant context propagation and isolation across data, cache, files, jobs, search, analytics, and administration. 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-tenancy`, asks about multi-tenancy, or discovery finds an applicable boundary. Run it from the repository root after project discovery. ## When it applies - Shared applications serving distinct organizations or customer partitions ## When it does not apply - Single-tenant deployments with no shared data plane Do not silently skip it. Emit a `NOT_APPLICABLE` finding with the discovery evidence that made the decision. ## Inputs from project discovery - tenant model - authorization policies - queries, cache keys, storage paths, and jobs 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. Locate the tenant identif