-
Boot is not a freeze: the atlas is painted in slices, and the shooter's menu answers while it paints
-
A second map: one more layout, chosen on the menu, and the bots play it without being told anything new
-
The map becomes a value: de_forge is one object the game is handed, not module state it imports
-
The range gets a second drill: moving plates, chosen before the run and pinned by its own digest
-
A third game, served: /example proves a game now costs one entry and one page
-
The frame's plumbing becomes engine: one pooled scene, filled by a game, allocating nothing
-
A game is one entry: one registry the build, the server, the nav and the 404 all read
-
Two games, one engine, no sharing — and a test that says so in both directions
-
Transient effects become engine: a capped ring of timestamped events, pruned without allocating
-
The HUD is pinned before it moves: src/client/hud.test.ts says what a player sees today
-
The range walks: its own movement tuning and hull through the engine’s solver