QA evidence (the receipts)¶

Everything on this page is reproducible from files checked into the repository under qa/ and scripts/. Nothing has been rounded up, and warnings are listed because a QA page that only shows green ticks isn't evidence, it's decoration.

The validator¶

scripts/validate.py runs in CI on every push and before every package build. It fails hard on any of:

• pet.json missing a required field (id, displayName, description, spriteVersionNumber, spritesheetPath)
• spriteVersionNumber != 2
• an absolute or ..-containing spritesheetPath
• image not exactly 1536 × 2288, or without an alpha channel, or entirely transparent
• cell occupancy deviating from the expected [7, 8, 8, 4, 5, 8, 6, 6, 6, 8, 8] populated cells per row, checked per cell using the alpha bounding box

$ make validate
ok: Clippy Pet manifest and v2 spritesheet contract are valid

The v1 build script applies the same occupancy check to its nine rows.

Blind direction validation¶

qa/direction-blind-validation.json. The sixteen look frames were shuffled into anonymised A/B pairs (seven horizontal, seven vertical) and classified without labels: does A look further screen-left than B? further up?

The six warnings, verbatim from the report:

horizontal-7 A horizontal axis is ambiguous
horizontal-7 B classified screen-left; expected screen-right
vertical-4 A classified up; expected down
vertical-4 A and B were classified as the same vertical direction
vertical-7 A classified down; expected up
vertical-7 A and B were classified as the same vertical direction

All three flagged pairs involve shallow diagonals where the vertical component is a few pixels of pupil and eyebrow. They read correctly in motion and in the semantic review; the classifier's caution is documented rather than tuned away.

Semantic review¶

qa/direction-semantics.json. An independent visual pass judged each of the sixteen frames against its expected direction with a one-line reason.

Sample reasons: "090: Pupils unmistakably at screen-right sides." "292.5: Clear screen-left axis; upward displacement subtle, but labeled continuous loop has no reversal."

Look continuity¶

qa/look-continuity.json. Adjacent look frames around the circle were diffed pixel-wise and their centroids compared, to catch a frame that jumps.

The 337.5 → 000 step is the loop seam where the pose returns to "straight up"; it was reviewed and accepted. The report also lists interior transparent hole rows for every direction; those are the see-through gaps inside the paperclip's loop and are intentional, recorded so nobody "fixes" them later.

Chroma cleanup¶

qa/chroma-despill-extended.json. Frames were generated over #00FF00 and cleaned with an edge-local spill-suppression pass (radius 5, tolerance 0.15, min saturation 0.10, strength 1.0).

Per-cell counts are in the report, so a future recolour can be diffed against the original.

Reproducing¶

python3 -m venv .venv && . .venv/bin/activate
pip install -r requirements-dev.txt
make validate                              # the validator
python3 scripts/build-v1-spritesheet.py    # v1 crop with occupancy check

The direction/continuity/chroma reports were produced by the asset pipeline whose outputs (frames, row strips, reports) are committed; the images on this page (qa/contact-sheet.png, qa/look-directions.png, qa/previews/*.gif) are the same artifacts. If a number here ever disagrees with a file in qa/, the file wins and this page has a bug.