update-reverie-inventory

To sync a JSON schema inventory, compare code-based schema definitions against the inventory file to identify and rectify mismatches in schema counts, field counts, and atmosphere entries. This ensures documentation accurately reflects implementation.

CI fails when the documented schema inventory drifts from the codebase because schema registry integrity checks detect mismatches between the JSON inventory file and the actual code-based schema definitions, requiring synchronization to pass.

The best way to detect modified domain schemas is to run an automated auditing process that compares code-based schema definitions with the JSON inventory file, identifying discrepancies in schema counts and field counts before pushing changes.

Yes, you can use this schema auditing process to fix discrepancies in atmosphere entries. The skill specifically identifies and rectifies mismatches in atmosphere entries alongside schema counts and field counts during the inventory update.

No, you do not need any external dependencies to update the Reverie schema inventory. The skill operates independently using scripts and references to compare the JSON inventory file with the codebase schemas.

You should run a schema inventory synchronization check after adding a new domain schema to update the inventory file and ensure CI checks pass, or periodically to catch any drift between documentation and implementation.