Spaces:
Paused
Paused
Commit History
-
Odyssey: bound the living galaxy to 3 seed-drawn background worlds
Claude +1: Claude Opus 5Unverified signaturecreateGalaxy instantiated and simulated all 11 worlds from turn one. It now brings up the start seat plus a pseudo-random draw of BACKGROUND_WORLDS (3) others — backgroundWorldIds, keyed on the galaxy seed and the start world from its own distinctly-seeded stream, returned in fixed roster order so the background scheduler and every galaxy-wide scan read exactly as before. Which neighbours are alive is now part of what a seed means; same seed still replays the same galaxy. The rest of the roster stays DORMANT: still on the starmap, still jumpable, still a full skirmish map — built in on arrival (jumpCapital already did this for a never-visited destination) and simulating from then on like any world you leave behind. addPlanet now honours a standing claim when it builds a world in, so a dormant world the faction-spread sweep claimed flies those colours when the player finally lands on it. Three paths assumed every world's state existed, and are fixed here: - initiateJump treated a mis…b88cc9c
-
Tier 3e: a golden lock on the selection panel, before touching it
Claude +1: Claude Opus 5Unverified signaturerebuildSelectionPanel is 845 lines and ~28 independent "is one of THESE selected?" blocks appended to panelEl in a fixed order. test/hudSelection.test.js covers a lot of what those blocks decide — a disabled button stays inert, the live-patch path reuses nodes, the lane rows read the right commodity — but nothing covered the panel's SHAPE: which rows exist, in what order, with which classes and text. That is exactly the property a decomposition has to preserve and exactly the one those tests cannot see, because each looks up the single row it cares about by class or text prefix and is blind to a row that moved, vanished, or grew a sibling. So 25 fixtures spanning the branches, each serialized to a reviewable tree and compared against a recorded snapshot. The snapshot is data, not a claim about what is right; when a UI change is intended it is regenerated with UPDATE_PANEL_GOLDEN=1 and the diff IS the review artifact. Two guards on the snapshot itself, because a snapshot suite's class…a8fb083