UI-Test Checkpoint Schema
Purpose
This skill packages the stage 2.2 checkpoint schema contract. It validates checkpoint artifacts, builds checkpoint bundles, and decides whether a UI flow segment can be reused without repeating earlier Midscene exploration.
Operating Rules
- Checkpoint granularity is business-subchain level, not individual click/input level.
- Use CP0-CP6 as the default stage set: governance baseline, login state, project switch, module entry, page/modal open, form fill, submit/result verification.
- Preserve dependencies between checkpoints.
- A checkpoint is reusable only when validation, evidence, governance, promotion gate, and staleness policy are satisfied.
- Write checkpoints require cleanup policy and explicit safety approval.
- Failed, degraded, or blocked checkpoints require failure attribution.
Workflow
- Read references/schema.md.
- Validate checkpoint JSON against
schema/checkpoint_schema.json.
- Build a checkpoint bundle when all required fields pass.
- Return invalid fields and missing governance evidence when validation fails.
- Output downstream views for
ui_test_packet, handoff_packet, artifact_refs, and rag_packet when available.
Scripts
Use the bundled checkpoint schema script for deterministic validation:
python .\scripts\checkpoint_schema.py validate --input .\fixtures\checkpoint_samples_valid.json
python .\scripts\checkpoint_schema.py bundle --input .\fixtures\checkpoint_samples_valid.json --output checkpoint_bundle.json
python -m unittest discover -s tests
Validation
- Schema validation passes for valid fixtures.
- Invalid fixtures fail with specific error messages.
- Bundles preserve source checkpoint ID, schema version, dependencies, evidence references, and promotion status.
Safety
Schema validation grants no execution permission. Block write-capable checkpoint reuse, credential or browser-state persistence, and promotion without the owning ui-test review and approval gates.
1---2name: ui-test-checkpoint-schema3description: Validate, bundle, and review UI-test checkpoint schema artifacts for staged exploration and reusable regression promotion. Use for stage 2.2 checkpoint packets, CP0-CP6 granularity, checkpoint evidence readiness, staleness policy, promotion gates, and checkpoint bundle validation.4---56# UI-Test Checkpoint Schema78## Purpose910This skill packages the stage 2.2 checkpoint schema contract. It validates checkpoint artifacts, builds checkpoint bundles, and decides whether a UI flow segment can be reused without repeating earlier Midscene exploration.1112## Operating Rules1314- Checkpoint granularity is business-subchain level, not individual click/input level.15- Use CP0-CP6 as the default stage set: governance baseline, login state, project switch, module entry, page/modal open, form fill, submit/result verification.16- Preserve dependencies between checkpoints.17- A checkpoint is reusable only when validation, evidence, governance, promotion gate, and staleness policy are satisfied.18- Write checkpoints require cleanup policy and explicit safety approval.19- Failed, degraded, or blocked checkpoints require failure attribution.2021## Workflow22231. Read [references/schema.md](references/schema.md).242. Validate checkpoint JSON against `schema/checkpoint_schema.json`.253. Build a checkpoint bundle when all required fields pass.264. Return invalid fields and missing governance evidence when validation fails.275. Output downstream views for `ui_test_packet`, `handoff_packet`, `artifact_refs`, and `rag_packet` when available.2829## Scripts3031Use the bundled [checkpoint schema script](scripts/checkpoint_schema.py) for deterministic validation:3233```powershell34python .\scripts\checkpoint_schema.py validate --input .\fixtures\checkpoint_samples_valid.json35python .\scripts\checkpoint_schema.py bundle --input .\fixtures\checkpoint_samples_valid.json --output checkpoint_bundle.json36python -m unittest discover -s tests37```3839## Validation4041- Schema validation passes for valid fixtures.42- Invalid fixtures fail with specific error messages.43- Bundles preserve source checkpoint ID, schema version, dependencies, evidence references, and promotion status.4445## Safety4647Schema validation grants no execution permission. Block write-capable checkpoint reuse, credential or browser-state persistence, and promotion without the owning `ui-test` review and approval gates.