4 Commits

Include renames

Author	SHA1	Message	Date
kamilkrzywda	c77e81c45b	feat: #65 sea control — 11th ability (v0.43.0) ... Adds the sea ability: a fixed set of 12 named sea zones with sole-control semantics, contest-by-higher-military, and a deterministic per-turn +1 military/+1 economy bonus for each claimed zone. Durable (owns GameState.seaZones), additive migration, stub-inert (e2e unaffected). Fixes #65 Design note: Gitea #65 sketched a free-form 'naval' layer; the implemented approved design is this richer 'sea' layer with a fixed zone set.	2026-10-16 12:50:22 +00:00
kamilkrzywda	7e4faa73d3	feat(abilities): add migration & refugees lever (v0.42.0, #64) ... Add the 10th modular LLM ability: a turn-transient TurnResult.migration lever declaring population flows between nations (migration / refugees / diaspora / exodus). The source loses a little population + economy, the destination gains a little (a large influx also strains its stability), and the from<->to relation is nudged one step toward the positive end of the ally/neutral/rival/hostile ladder (capped by kind; a war is never touched). Deterministic per-scale tables, no hidden randomness, clamped 0-100, mirrored to owned regions, re-derived aggregates; never moves territory. Registered last in ABILITIES; user prompt unchanged (user.txt golden byte-identical), system goldens re-baselined. Fixes #64.	2026-10-16 10:15:45 +00:00
kamilkrzywda	c90e9ae753	feat(abilities): add disasters & pandemics lever (v0.41.0, #63) ... Add the 9th modular LLM ability: a turn-transient `TurnResult.disasters` lever letting the LLM declare natural/man-made disasters (earthquake / flood / volcanic / wildfire / famine / plague / epidemic) on a nation or a region, applying a DETERMINISTIC (type, severity) stat dip (no hidden randomness). Like the hybrid layer it owns no GameState field, needs no db.ts change, and leaves no durable list — an ongoing plague/epidemic is simply re-declared each turn it persists. - shared/protocol.ts: DisasterType / DisasterSeverity / DisasterEvent / DisastersOps, and `TurnResult.disasters` (between `ideology` and `markers`; required, default `{ events: [] }`). - server/abilities/disasters.ts: the ability module (validate / apply / schemaLine / constraint / isMeaningful / inert stub / empty payload; no stateFields). `DISASTER_EFFECTS` is the deterministic (type, severity) dip table (population never touched). Target resolution mirrors hybrid (a region key hits its SOLE owner; 0/2+ owners dropped) but has NO `from` field, so there is no self-target drop. Dips clamp to 0-100, mirror to the target's regions (regionStats), and re-derive the target nation's stats (same 0-region / no-entry guards). - Registered last in ABILITIES (after ideology). System-prompt goldens regenerated (one schema line + one constraint bullet each); the user.txt golden stays byte-identical (payload() is {}). - New server/abilities/disasters.test.ts (33 tests); registry.test.ts updated to the 9-ability contract. - Secondary cleanups from the v0.40 refactor: AGENTS.md (abilities/ in the Layout tree + a "how to add a new ability" bullet + a disasters bullet), delete the orphaned validateTakeovers JSDoc, fold both inline `as unknown` casts into the top-level ./abilities import, and de-dup `str` (now imported from ./abilities/shared). Version bumped 0.40.0 -> 0.41.0.	2026-10-16 09:15:55 +00:00
kamilkrzywda	2d17c743f6	refactor(#74) P3: add the 8 ability modules + ABILITIES registry ... Each per-feature LLM ability is now a self-contained module in server/abilities/ with its own Ability<K> const (schema line, constraint bullet, validator, applier, isMeaningful, stub default, user-payload field). The ordered ABILITIES registry (index.ts) assembles them in the canonical order: takeovers → wars → hybrid → economy → industry → nuclear → leaders → ideology. All function bodies are moved VERBATIM from engine.ts. The engine is untouched in this commit — P4 will rewire it to use the registry.	2026-10-16 07:23:11 +00:00