Iron Litany v0.3.0 — published revision and verification

Published 5 October 2026 local time / 6 October UTC. This is a playable systems revision in review, not creator approval of the demo or final art.

• Browser game
• Game page
• Cassette XVI
• Windows x64
• Linux x64
• Public release, checksum files and manifests

Frozen game and native verification

Game source is frozen at 9f2d334975313e44b86bd0b2c900084e81cd27a5. The source version tag identifies that exact runtime; later source commits may add release evidence without changing its bundled files.

The native workflow succeeded on both Linux and Windows. Both packages contain exactly the frozen raw bytes of all 126 dist files and the desktop entry, including canonical LF text. Both ZIPs passed CRC and manifest/hash checks; executable headers establish x64. The pinned official runtime is Electron 44.5.1.

The release receipt and metadata contain the complete hashes. Both native runners passed startup, first-person/overhead transition, offline cassette and manual pages, and saved-origin reload. Their real WebGL tests admitted a physical slit when aligned, rejected closed/behind/obstructed cases, and moved its centre to black when the body moved. Overhead admitted 1,709 / 4,096 pixels of real ground in the controlled probe, retained exactly that count while facing away, and returned zero with closed shutters or beyond the finite cones.

All six public assets, including both complete ZIPs and four checksum/manifest sidecars, were streamed anonymously and matched local SHA-256 and sizes. No redundant downloaded archive copies were retained. Machine-readable evidence is under docs/native-v030/, with direct-download metadata in docs/native-downloads-v030.json.

Website and preserved delivery

Kadabra source was pushed at 2a7f4933b32d17599e1dd638ee8838cffb33bd0d. The game, page, cassette and current native metadata were updated inside the existing complete production package. Other game channels, the literal metadata override tail, trailers, access-denial routing, edge functions and hosting configuration were retained.

The website source check passed for 1,825 files; all 11 native/channel checks passed. Production routing checks established 68 denials without fallback and 11 allowed requests, retaining the upstream fallback on its intended surface. Deployment 6ac48ce1f7a8bb1b52b75109 succeeded, with the immutable origin recorded in publication.json.

Actual public page and cassette navigation exposed the current v0.3.0 Linux/Windows links and version labels. Six canonical game entry/runtime files matched frozen bytes exactly. The hosting response rewrote the front page's field-manual hrefs to its clean URL; parsed tags, text and other attributes remained equivalent and the manual destination returned 200. This bounded check is not a complete remote file inventory. The two prepared complete game trees were separately compared against all frozen files.

The original owner-private Sites mirror also published the same frozen game successfully. Its audience was preserved. Exact native and public deployment identities are recorded in docs/native-v030/publication.json.

Post-publication real controls

A fresh watch on the new immutable origin completed the three protected tool holds, walked the revised engine/loading/coolant routes and formally corrected the loader. It entered first person, fired aimed shots, destroyed a small body, and left its source open long enough for another body to appear. A visible reload replenished the magazine from three to six and reduced reserve from 30 to 27. After the returned body was killed, a continuous cautery contact sealed the entry and spent exactly one seal, six to five.

The watch was paused after returning overhead. Read-only state recorded two kills, one sealed entry, ammo four/reserve 27, and a separate unsealed source and creature still present. Purifying one wound did not silently clear the whole tank. Runtime diagnostics reported eight active slit cones, zero offscreen targets/captures, and full current-room light with adjoining/distant rooms dimmed. The bounded console check captured no error or warning.

Evidence: docs/screenshots/published-v030-intruder.png, published-v030-overhead.png, published-v030-state.json, published-v030-game-page.png, published-v030-cassette.png and published-v030-download-chooser.png. Browser interactions used ordinary player controls; the canonical origin was only opened to its welcome menu, with its existing saved watch left intact.

Acceptance still open

The earlier actual recovery run reached the first repair halt and performed all three crew replacements with save/reload. The eight synthetic campaigns all reached victory. These do not establish a full v0.3.0 human-control campaign victory or final pacing acceptance. Authored crew anatomy/contact, creature/environment fidelity, touch journey and sustained human listening remain in review. Cinematic and narrated gameplay production still waits for creator approval of the demo.