Everything is in place and verified. Final recap:

Outcome. The parent job's delivery repo on GitHub contained only an empty commit, so I re-downloaded all 88 upstream files and re-verified every sha256 against MANIFEST.json before building dist/. The published set is 50 files, and the estimated Git bundle is well under the limit.

Item	Value
dist/ raw size	5,219,122 bytes
Estimated Git bundle (whole submission)	5,783,852 bytes
Limit	8,388,608 bytes

What dist/ contains. Upstream bytes untouched except the four requested edits, confirmed with a diff against the re-downloaded source:

• Removed img/stone-41.png through stone-80.png and their 40 figure lines in index.html.
• preview: true became preview: false on the CONFIG line.
• The 40 names were dropped from img/index.json without reformatting it.
• MANIFEST-PUBLISHED.txt lists the sha256 of every other file in sha256sum format. The upstream MANIFEST.json stays inside dist/ unchanged.

Repository additions. The publish label lives in publish.json. There is no build; npm run build verifies dist/ against both manifests and the permitted edits. The mirror script re-derives dist/ from upstream and reproduced byte-identical output on a second run. README covers install, preview, rebuild, checks and publish.

Checks run on the final bytes. Build/verify exit 0, typecheck exit 0, headless Chrome check exit 0 at 320, 768 and 1280 px: 40 of 40 images rendered, no overflow, the mode gate ignores ?mode, all eleven in-page self-tests passed, wallet fallback renders three deep links, keyboard order and default focus rings observed in screenshots.

Design review. All six Better Interface domains were checked. One measured HIGH finding: the wallet deep links use browser-default blue at 2.01:1 on the dark page. It and five lesser findings are recorded in docs/validation/validation.md and deliberately not fixed, since the brief forbids changing any other byte. The data.json count still says 80 stones while 40 images ship. These are the owner's calls.

One layout decision to flag. The harness exclude file ignores artifacts/, so I placed the validation record, browser-check JSON and screenshots under docs/validation/ instead, where they are actually committed.

Not performed. No screen-reader, native-zoom, physical-device, Firefox/Safari or injected-wallet checks.