Skip to content

UAT Artifact Retention

What UAT produces per release, and what is committed vs. ephemeral.

Committed (versioned in git)

  • docs/uat/v<ver>/probe_pass/{report.json,report.md} — executable probe contract result (small, authoritative record of the surface contract).
  • docs/uat/v<ver>/responsiveness.json — performance-model sample.
  • docs/uat/v<ver>/automated_run/vision_findings.{json,md} — vision pass verdicts (text, advisory).
  • docs/uat/v<ver>/manual_uat_handoff.md + verdict.md — the operator hand-off and gate record.
  • Curated **/*.webp baseline/candidate screenshot pairs (small, lossy).

Ephemeral (gitignored)

  • Raw full-resolution docs/uat/**/screenshots/**/*.png captures — large; regenerated by the Playwright capture spec on demand. Convert the few worth keeping to .webp and commit those.

Pruning

Committed .webp pairs accumulate for ~3 major releases, then prune to the last 3. The text artifacts (probe_pass, responsiveness, vision_findings, hand-off) are small and kept indefinitely as the release record.

Pipeline

FCC_UAT_RELEASE=v<ver> npx playwright test uat_pages   # capture (in frontend/)
python scripts/uat_visual_pass.py                       # advisory qwen3-vl judging

Current as of v1.10.0.