cells-verify

To verify code changes against specifications before archiving, you need to load proposal, spec, design, and task artifacts and execute tests to validate completeness and correctness. This process uses real execution evidence to ensure changes meet requirements.

The best way to run tests and check coverage for Cells project changes is to execute a verification process that applies Cells conventions, handles i18n checks, and runs builds. This generates a verification report using real execution evidence.

Yes, you can use inline, engram, openspec, or hybrid reporting modes for verification reports. The verification process supports flexible persistence to generate reports according to your chosen convention.

Yes, build verification supports i18n checks and browser validation for UI components. The process enforces Cells-specific conventions and governance contracts to validate implementation before merging.

Verification reports show design coherence failures when code changes do not align with loaded spec, design, and task artifacts. The process validates completeness and correctness against these artifacts using real execution evidence.

You need to run a quality gate check with real execution evidence before merging new UI components or archiving code changes. This ensures tests, builds, and coverage checks pass and prevents defects from reaching production.