Draft a nation's infrastructure once per set of theatres #103

Manually merged
vinny merged 0 commits from vinny/infra-regions into master 2026-10-16 03:17:47 -04:00 AGit
Owner

Closes #46. A nation's order of battle is shared by every plan with that nation and year. Its infrastructure, though, was one request, marked CIV:infrastructure for the whole entry, naming the theatres of the plan that asked first. Russia's was drafted for the Sea of Japan, and the Norwegian Sea plan's Kola Peninsula got no port, airport or power plant. - Infrastructure is now asked once for each set of theatres (region:CIV:infrastructure:<key>), the same way #38 asks for units near the theatres. The request lists the sites the entry already has, the new sites are added beside them, and a site given again is dropped. - A Redraft (clear) and a restart now remove the service's region: marks along with its rows. Before, the marks stayed behind, so the units near a plan's theatres were never asked for again. - A row that copies an order-of-battle task's example (a real unit of one nation: 4 FS, VMFA-314, 689 GvIAP, Ras Tanura) is left out of every other nation's entry, with a note. - Tests: infrastructure drafted per region with the sites listed and no duplicate, then not asked again for the same region; region marks cleared; the example copy left out for Finland and kept for Russia. All three fail on the old code. Builder suite green. 🤖 Generated with Claude Code

Closes #46. A nation's order of battle is shared by every plan with that nation and year. Its infrastructure, though, was one request, marked `CIV:infrastructure` for the whole entry, naming the theatres of the plan that asked first. Russia's was drafted for the Sea of Japan, and the Norwegian Sea plan's Kola Peninsula got no port, airport or power plant. - Infrastructure is now asked once for each set of theatres (`region:CIV:infrastructure:<key>`), the same way #38 asks for units near the theatres. The request lists the sites the entry already has, the new sites are added beside them, and a site given again is dropped. - A Redraft (`clear`) and a restart now remove the service's `region:` marks along with its rows. Before, the marks stayed behind, so the units near a plan's theatres were never asked for again. - A row that copies an order-of-battle task's example (a real unit of one nation: 4 FS, VMFA-314, 689 GvIAP, Ras Tanura) is left out of every other nation's entry, with a note. - Tests: infrastructure drafted per region with the sites listed and no duplicate, then not asked again for the same region; region marks cleared; the example copy left out for Finland and kept for Russia. All three fail on the old code. Builder suite green. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
A nation's order of battle is shared by every plan with it that year, but its
infrastructure was one request marked covered for the whole entry, naming the
theatres of the plan that first asked: Russia's was drafted for the Sea of
Japan, and the Norwegian Sea plan's Kola Peninsula got no port, airport or power
plant. Infrastructure is now asked once per set of theatres
(region:CIV:infrastructure:<key>), the request lists the sites the entry has,
and new ones are added beside them; a site named again is dropped.

Also:
- A Redraft (clear) and a restart take the service's region marks with its
  rows; left behind, the units near a plan's theatres were never asked again.
- A row copying an order-of-battle task's example, a real unit of one nation,
  is left out of every other nation's entry, with a note (Russia's 689 GvIAP
  was copied into Finland's rows).

Closes #46.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Version 0.7.66 (infra-regions)
Some checks failed
check / check (ubuntu-latest) (push) Has been cancelled
check / check (windows-latest) (push) Has been cancelled
check / check (windows-latest) (pull_request) Has been cancelled
check / check (ubuntu-latest) (pull_request) Has been cancelled
42fea57a16
vinny manually merged commit 42fea57a16 into master 2026-10-16 03:17:47 -04:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
vinny/CMOnet!103
No description provided.