audit-schema

To audit PocketBase collection rules, compare live rule strings fetched from your test instance against corresponding spec definitions in web/src/lib/schema. This process enumerates collections from pocketbase-types.ts and checks all five rule slots (list, view, create, update, delete) to surface inconsistencies.

PocketBase rule drift occurs when live rule strings in your database diverge from their intended spec coverage, creating lockdown inconsistencies. You detect this drift by applying an audit schema that compares each collection's five rule slots against corresponding specifications to produce a structured findings report with severity rankings.

You can validate PocketBase schema lockdowns automatically by enumerating all collections defined in pocketbase-types.ts. The audit fetches live rules from the test PocketBase instance and compares every rule slot against corresponding specs to generate a coverage matrix with severity-ranked findings guiding remediation.

Generating a coverage matrix for PocketBase collection rules requires fetching live rules from your test instance and comparing them against specs in web/src/lib/schema. The output is a structured findings report with a severity-ranked matrix that guides remediation of lockdown inconsistencies.

Running a PocketBase schema audit requires spec files located in web/src/lib/schema and collection type definitions in pocketbase-types.ts. You also need access to a live test PocketBase instance to fetch current rule strings for comparison against those corresponding specifications across all five rule slots.

PocketBase collection rules become inconsistent with schema specs due to drift between live rule strings and their spec coverage. An audit-schema process identifies this drift by enumerating collections from pocketbase-types.ts, fetching live rules, and comparing each rule slot against corresponding specs to produce severity-ranked findings.