No man's land: TurnResult.unowned + release/re-claim in applyTurnResult + distinct grey map rendering (#16 P3)

- shared/protocol.ts: TurnResult.unowned (keys released this turn) + the map
  presentation contract (regionFillStyle / unownedTooltipLabel, hue-less grey)
- shared/types.ts: required GameState.unowned (cumulative mid-game releases;
  [] at init, distinct from preset-unassigned regions)
- server/engine.ts: applyTurnResult applies releases first (sole-owner only,
  never fabricating no man's land from unassigned keys), then claims against
  the post-release snapshot (gain on an ownerless key = re-claim); lone
  release is isMeaningful; prompts + user payload carry the unowned field
- server/stub.ts: unchanged behavior (never releases; e2e stays stable)
- server/db.ts: legacy rows load with unowned defaulted to []
- server/index.ts: create-game sets []; jump reference table includes
  released keys so the model can name them for re-claim
- WorldMap/App: unowned prop -> visible grey + 'No man's land' tooltip
- unit tests: 105 -> 127 (release/re-claim suites, presentation contract,
  legacy-row normalization)

This commit is contained in:

kamilkrzywda

2026-10-14 12:04:03 +00:00

parent cb426273a9

commit 764f24fc55

13 changed files with 567 additions and 53 deletions

									
										server/regions.test.ts
									
		+1
		
												View File
												
				@@ -86,6 +86,7 @@ describe('regions (region-key loader, v0.19 #16 P1)', () => {

				      events: [],

				      pending: [],

				      version: 1,

				      unowned: [],

				    };

				    // 16 GBR sub-regions + 42 FRA sub-regions, no overlap between the two.

				    expect(allTerritoryKeys(state).size).toBe(58);