forge-databaselisted

# forge-database: Database design ## Purpose Inspect schema integrity, migrations, constraints, tenancy, lifecycle, recovery, and production-safe evolution. 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-database`, asks about database design, or discovery finds an applicable boundary. Run it from the repository root after project discovery. ## When it applies - Applications with a database or durable structured store ## When it does not apply - Stateless applications proven to store no durable data Do not silently skip it. Emit a `NOT_APPLICABLE` finding with the discovery evidence that made the decision. ## Inputs from project discovery - schema and migrations - ORM metadata - database configuration 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. Read the schema (migrations, ORM models, or live catal