Star Harvest opens the arcade

The journal grows a small arcade. Star Harvest is a 90-second canvas run: pilot a little ship, gather drifting star sparks, dodge polygon rocks, and chain quick pickups into a combo multiplier. The games index lists it first with a note that more games are coming.

Motivation

The arcade did not exist: the games path returned a missing page and no game template, metadata or asset was in the tree. The parent proposal verified a full playable spec for the first ship, and the design clearance fixed the visual language for the index and the game page. This change builds exactly that scope and nothing beyond it.

What changed

The games index now lists Star Harvest as an archive-family card with a more-games note, and the game page renders the canvas with a five-item status row, four native buttons, a touch hint, a coarse-pointer steering pad, how-to-play copy and a devlog paragraph. A single vanilla script runs the loop on animation frames with a capped delta and a fixed pool of particles, while a small additive stylesheet carries the stage, status row, controls and pad under the existing tokens. The builder reads one metadata file per game, hashes the game script and stylesheet like the other assets, and publishes the index and game routes with the sitemap extended.

How it was done

After the hosting preflight and a fresh feature branch from the main line, development added the game metadata, the index and game templates, the vanilla script and stylesheet, and the builder routes with hashed same-origin assets. The canvas palette is read from the computed tokens at boot, startling motion stays behind the reduced-motion setting, and the best score lives in a namespaced integer-only browser key rendered as text. The full unit suite, the deterministic rebuild and the presence gate run green before review, with a secret scan of the diff clean.

Verification evidence

The full unit suite runs green including the new arcade contract, which pins both routes, the zero-network script and stylesheet, the weight budgets, the pause and restart and score hooks, the reduced-motion branch, the single live region, the target sizes and the sampled contrast pairs. Rebuilt game pages carry the hashed script and stylesheet with no external requests and zero console errors, while pages outside the arcade stay byte-identical apart from the aggregated indexes and related-entry links. Frame pacing measured on the running game page: 360 animation frames sampled in headless Chromium at 1280 by 800 averaged 16.6 milliseconds per frame (60.1 frames per second; 95th percentile 16.7 milliseconds) with zero console errors. Both themes, narrow viewports, keyboard-only and touch-only loops and the reduced-motion pass were checked against the design clearance. Security and quality reviews attach to the exact pushed head after this pull request opens.