five-phase-pass

To keep monorepo changes coherent, use a five-phase pass that propagates edits through the web app, generator template, test artifacts, docs, and cross-skill audits. This prevents drift across the stack by enforcing deterministic CI gating and template diff parity checks.

Playwright and Storybook CI gates fail with port or process races when stale Vite processes conflict. A deterministic five-phase pass pre-kills Storybook and Vite processes before running validation checks, ensuring the CI gate runs reliably without port collisions.

The best way to sync generator template changes with test artifacts is running a phased propagation that applies {{name}} substitution diffs, regenerates the test-project, and validates the output against a deterministic CI gate to ensure template parity.

Yes, you can audit cumulative stack drift without all five phases by executing a P5-only baseline run. This performs a cross-skill coherence sweep across skill files and AGENTS/README to identify narrative inconsistencies without applying new code changes.

To update owning documentation during monorepo code propagation, the five-phase pass executes a mechanical and narrative consistency sweep across skill files and AGENTS/README during phase four, ensuring all documentation reflects the applied template and web app changes.

The five-phase pass requires strict phase ordering to validate template changes correctly. It sequentially processes the web app, generator template, regenerated artifacts, owning documentation, and cross-skill audits, ensuring deterministic gating via bun run check completes without process conflicts.