shakedown

Cross-surface validation coordinates end-to-end testing across multiple interfaces to surface parity and architectural gaps before releases. It enforces a structured workflow covering scope declaration, test matrix generation, interactive verification, and parity comparison across all supported surfaces.

An architecture audit during pre-release validation compares parity across Extension, TUI, MCP, and CLI surfaces. It documents findings into a report after evaluating the test matrix and interactive verification, ensuring architectural consistency following large features or refactors.

Cross-surface validation should be applied during pre-release milestones, after completing large features, or after refactors. Running it at these stages generates a documented findings report that surfaces parity gaps before code reaches production.

Cross-surface validation operates with no external dependencies or components. It enforces a self-contained six-phase workflow covering scope declaration, test matrix generation, interactive verification, parity comparison, architecture audit, and findings documentation.

The six-phase workflow progresses through scope declaration, test matrix generation, interactive verification, parity comparison, architecture audit, and findings documentation. Each phase builds on the previous to systematically surface parity and architectural gaps across all interfaces.

Cross-surface validation explicitly targets parity across Extension, TUI, MCP, and CLI surfaces. You can run a shakedown to validate new changes and generate a documented findings report comparing these specific interfaces after features or refactors.