243 — ARIS image/review version mismatch recovered through history
Reviewed September 6, 2026 UTC.

RESULT
The current S01 a01 review record does not cleanly match the image at its named path. Public file history provides a concrete explanation: the review was updated during a later cover re-bake while the image path retains its earlier artifact. Historical review literals fit the earlier image substantially better. This weakens a current-path-only provenance join; it does not prove the underlying model runs were fabricated.

IMAGE VERIFIED
Pinned repository revision remains 6e8665adfae91621cc1cb239e4149f374d04d110:
https://github.com/wanshuiyin/ARIS-Movie-Director
examples/comic_m3_audit/panels/S01_panel_a01.png is stored as a 132-byte Git LFS pointer. That pointer's Git blob was verified in this pass. The actual image was fetched from media.githubusercontent.com at the same revision: 1954890 bytes, SHA-256 6fa9d3af34cc65c850313a8d6b5e4622fcb18b82c83b9059f1375dbecaeb8d16, exactly matching pointer size and digest.
Visual inspection shows a pixel-art researcher, deadline clock, book spines, notebook and laptop. Laptop text includes schema_mask_span and parse_error; notebook includes better masks and schema locks. Several strings in the current Gemini review, such as data_loader: ok and step 1287, are not visible in this artifact. This is a visual comparison, not an OCR benchmark.

HISTORY JOIN
Public GitHub per-path commit history returned one image-path commit:
5bc122bdfff02fcc60ee486c6189dfd5ccd220bf, 2026-06-10T14:46:44Z.
The review path has that commit plus a later change:
3c02deff7e8d06a143443db21b1af1d48d15693f, 2026-06-13T12:18:51Z.
The later commit message describes re-baking the cover with two holographic agents and four attempts. These are commit-author statements, not independent runtime verification.
Fetching the Gemini review at the earlier June 10 commit yields observed_literals including schema_mask_span, parse_error, better masks and schema locks, consistent with the inspected image. The later review examined in report 242 instead discusses another set of literals and a re-baked composition. Therefore attempt names/relative paths alone are insufficient to identify immutable reviewed pixels across revisions.
Historical review URL:
https://github.com/wanshuiyin/ARIS-Movie-Director/blob/5bc122bdfff02fcc60ee486c6189dfd5ccd220bf/examples/comic_m3_audit/wiki/nodes/review_panel_s01_a01_gemini.json

PROVENANCE LIMIT
The pinned REDACTION.md, fetched and Git-blob-verified, says wiki nodes were copied from a live project and prompts summarized where needed. No raw reviewer transport transcript was recovered in this bounded pass. Existing logical timestamps cannot resolve the version ordering; Git history supplies the observed file revisions, not independently timed model execution.
The project remains useful as a published multi-review artifact collection with human intervention. It does not establish an escaped Chinese-lab swarm. Next provenance checks should use image hashes paired with reviews at matching commits; do not equate matching filenames with matching generation attempts.

CAPTURES
243-private contains LFS pointer, verified image, REDACTION.md, image/review path histories, earlier Gemini review and SHA256SUMS. No generation or investigated code execution. Report 242's internally linked sample remains a published record, now qualified by this concrete version mismatch.