Quality Gates

This document defines measurable release gates for Schemeta.

Release Stages

Functional correctness
- npm test passes.
- npm run test:ui passes.
Visual regression
- No unexpected screenshot diffs in tests/baselines/ui.
- UI budget thresholds (defaults in tests/ui-regression-runner.js) are met:
  - sample: crossings <= 1, overlaps <= 1, detour <= 3.6
  - drag: crossings <= 3, overlaps <= 3, detour <= 3.5
  - drag+tidy: crossings <= 2, overlaps <= 2, detour <= 4.5
  - dense fixture: crossings <= 2, overlaps <= 2, detour <= 4.2
- Machine-readable report generated:
  - output/playwright/ui-metrics-report.json
Interaction reliability
- Selection/deselection/isolate/reset flow verified.
- Undo/redo parity verified for component, pin, net, and symbol edits.
API/MCP compatibility
- api_version/schema_version values present and documented.
- Compile/analyze envelopes remain backward compatible (additive policy).

Accessibility
- Core workflows keyboard-operable.
- WCAG AA contrast on primary controls/text.
Responsive UX
- Usable at 1280x720 and 1440x900 without clipping critical controls.
Schematic readability
- No component-wire overlaps from auto layout/routing.
- Label overlap count near-zero on benchmark fixtures.
Operational readiness
- Rate limiting + auth + health checks validated.
- Error telemetry includes structured codes and context.
Data durability
- Save/load/restore and JSON roundtrip validated.
- MCP UI bundle + tool endpoints verified end-to-end.

Always required:
- syntax checks
- npm test
- npm run test:ui
- verify output/playwright/ui-metrics-report.json was produced
Release candidate required:
- checklist completion in docs/release-checklist.md
- intentional baseline updates reviewed and approved