post-engine-completion-checklist

To prevent documentation drift, perform a post-completion audit that validates CLAUDE.md status markers, gallery codes, and preset counts against XOmnibus master specifications to ensure project file consistency.

The best way to synchronize engine documentation with a central index is to perform an automated audit that verifies and corrects factual claims in CLAUDE.md against canonical sources like the XOmnibus master spec.

You audit CLAUDE.md status markers and Seance verdicts by validating them against XOmnibus master specifications and local knowledge compendium standards during a comprehensive post-completion documentation check.

Yes, you need a completed synth engine build because the audit validates and corrects finalized details like preset counts, accent colors, and build commands against canonical sources to prevent future errors.

To populate knowledge compendium files and prevent stubs, run a post-completion checklist that checks and enriches essential files like preset_design_patterns.md and architecture_patterns.md with accurate engine data.

MEMORY.md drifts out of sync when critical project details are updated locally without validating associated satellite files against canonical sources during the final project tracking phase.