Built: - Economy: raid loot capped to the room the raiders have at home (rest stays with the victim, "lootLeft" in the report); trade escrow reserves its room so refunds always fit; trade accept refuses with no_room_for_goods when the goods would not fit. Loot destroyed per 30-day run 31-61k -> ~1k, refunds clipped ~27k -> 0 (docs/BALANCE.md, 3 seeds). - End game: members of the holding alliance garrison landing sites (migration 005_site_garrison.sql), garrison counts in site defence, 72 h capture shield, withdraw route, POP view lists garrisoned units. Shipping capacity scales with world speed (3x world: winner 76-98 -> ~30-36 days after sites open). Bot runs show real contests (84-194 attacks on held sites at 1x). - Ops: deploy/update.sh (backup, stop, ff-merge, npm ci --ignore-scripts, health check, rollback), deploy/upstream-offsite (rsync only), admin end-world snapshots results, EPIPE fix, docs/workflows/ filled in. - e2e 62 -> 163 checks: units, raids/reports, alliance+messages, trade, end game, nb, PWA, reconnect, slow polling fallback (opt-in). Two app bugs found: message push ignored, "New" button stayed English. Tested: npm test 274/274, openapi check, npm run e2e 163/163 (137 s), bot runs 50x30d seeds 1-3 and 140-day/60-day speed-3 end-game runs INVARIANTS OK, adversarial review pass (findings fixed or documented). NOT tested: update.sh on a real box (systemd, real npm, runuser; stubs only, shellcheck not installed), garrison card/loot text on a phone, Node 22.13, humans. Known leaks left open and documented (BALANCE S6): loot/shipments can still overflow when stock arrives in flight, bounced backbone shipments lose overflow (reported to the sender). Garrison numbers (heldDefenceMult 2, shield 72 h) are first guesses from 2 seeds. Not claimed: balanced. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Q2MJaQ5LXAHzGnTDgceT14
12 lines
862 B
SQL
12 lines
862 B
SQL
-- Garrisons at backbone landing sites (docs/DECISIONS.md E6). Units of owner_town_id's operator standing in a landing site that the
|
|
-- operator's alliance holds. They defend the site (on top of its static defence) and draw the OWNER's power (state.unitDraw), because
|
|
-- a site has no power budget of its own. Same shape as `stationed`, whose host is a POP; a site is not a POP (E1), hence a table of its own.
|
|
-- Written only by commands/events inside their transaction; the bot ledger counts these units as alive.
|
|
CREATE TABLE site_stationed (
|
|
site_id INTEGER NOT NULL REFERENCES landing_sites(id),
|
|
owner_town_id INTEGER NOT NULL REFERENCES towns(id),
|
|
unit TEXT NOT NULL,
|
|
count INTEGER NOT NULL CHECK (count > 0),
|
|
PRIMARY KEY (site_id, owner_town_id, unit)
|
|
);
|
|
CREATE INDEX site_stationed_owner ON site_stationed(owner_town_id);
|