Cooperative lantern restoration print-and-play game

Create an original cooperative print-and-play game for two players, intended to take about 15 minutes, using a printed board, exactly twelve cards and ordinary counters. Restore lanterns on a fictional seven-island archipelago before eight rounds pass. Give the players different abilities. All information is public and rules deterministic so sessions can be replayed. Deliver printable SVG components, a complete concise rulebook, a dependency-free rules checker, one legal winning transcript and one legal losing transcript. Include illegal-move checks. Make an actual playable game, with meaningful resource choices and explicit setup, turn order, transitions, win/loss conditions. Do not claim human playtesting or proven balance. Deliver English materials, original content and offline reproducible checks. The artifact is the product; no web application or external service. Make reasonable reversible design choices independently.

Repair the existing Lanterns of the Seven Tides offline kit with bounded changes. Independent replay found the original rules and both transcripts legal: A wins after action 15 in round 8 with wood 7/oil 0; sixteen passes correctly lose when round 9 begins. Preserve those legal examples and their rules unless a clearly documented minimal correction is necessary. This is not a request for a game redesign. Make the printable cards match their stated dimensions. The current A4 SVG has 230x250-unit rectangles in a 794x1123 viewBox, physically about 60.83x66.12mm rather than 63x88mm, and the last three outlines extend below the page. Twelve 63x88mm cards cannot fit one A4 even without margins. Deliver the twelve distinct 63x88mm cards on two coherent A4 SVG sheets, with complete cut outlines and readable labels inside each viewport. Update the rulebook, component index, source print metadata, verifier and inventory for the actual page count and measured geometry. Inspect actual coordinates, physical units, text bounds and stroke bounds; counting rectangles is insufficient. Make source/game.json genuinely authoritative for declared numerical and setup rules. Currently abilities.B.gatherAmount is ignored: changing it and both associated source descriptions from 2 to 3 still gives 2, while verify-kit accepts the altered source after its checksum is refreshed. Use machine-readable source values for abilities, restore costs, card resource effects, resource caps, setup, turn order and round limit; ordinary action-transition algorithms may remain in code. Prove source authority with a disposable parameter-change test that changes the resulting state, rather than checking for a readFileSync string. Keep printed rules, card effects and machine rules consistent. Explicitly explain the four face-up reserve cards: timber-2, timber-3, oil-1 and oil-2 currently cannot enter a hand under any listed action. An intentional unused reserve/reference role is acceptable if plainly stated; do not imply an undocumented draw action. Keep exactly twelve physical card identities and distinguish the full card catalogue from the four-card public reserve in state/accounting. Preserve deterministic public-state replay and card/resource conservation. Retain and extend meaningful offline checks: original win/loss, immediate seventh-lantern victory on B's last action of round 8 before loss, exact resource 12 accepted and 13 rejected, A/B gather and restoration costs, wraparound versus nonadjacent move, unavailable/reused card, repeated restoration, and any action after terminal. Negative cases must actually reject and cannot catch their own failure-to-reject assertion. Update honest verification and hashes; no claim of human playtesting, proven balance, fifteen-minute duration or physical print testing.