Connect Advanced allied reserve transit and legal departure

docs/ALLIED_TRANSIT_RULES.md

@@ -2,6 +2,33 @@
 
 Audit: 7 September 2026. Read-only source and code audit, retained by the coordinating agent. Scope is classic GF9 base rules and the applicable November 2020 FAQ, not tournament or movie-game rules.
 
+## Advanced ordinary allied shipment follow-up — 8 October 2026
+
+Ordinary physical reserve shipment may now enter an ally's territory on the
+shipper's own unused turn before movement, under the same scoped entry
+permission as Basic. This composes the November FAQ's shipment/departure
+permission with the authorized supplied **physical p15** ending constraint.
+Stronghold capacity, storm, price, counters and movement range still apply.
+No-Fields, allied No-Field offers, Homeworld and mobile transports keep their
+separate guards; normal ground-movement endpoints are not broadened.
+
+Advanced creates no Basic visitor receipt. At ending, the existing native
+Advanced quote removes **all the ending player's shared forces**, including
+old counters, not just newcomers. Advisor, Polar Sink and native Ecaz
+coexistence exemptions remain. Basic keeps its visibly provisional excess-
+visitor policy and older co-occupation deadline. No extra move or refund
+is granted when departure is unavailable.
+
+The pre-shipment notice explains the mode-specific consequence; the
+existing ending warning names the shared territories. Minimal legal AI
+prioritizes a native departure and does not leave a city sentinel behind.
+Three direct smokes cover paid normal1/special1 arrival and Medium departure,
+ending with old5 plus new2 (only the actor's7 go to Tanks), and third-faction
+capacity rejection. Chromium observed native GameTable SSR pre-arrival and
+ending warnings with enabled finish. No broad suite, recovery campaign or
+deployed acceptance was run.
+
+
 ## Basic ordinary allied shipment prototype — 8 October 2026
 
 The content-first Basic pass connects the FAQ's ordinary physical
@@ -29,10 +56,10 @@ co-occupation deadlines still resolve separately. AI prioritizes available
 native departures and does not retain a stronghold sentinel from a
 visiting group.
 
-Concealed and allied No-Field arrivals, mobile/homeworld transports,
-optional arrival compositions and Advanced entry permission are not
-expanded by this prototype. Refinement of interrupted and mixed-cohort
-interactions remains later work.
+Concealed and allied No-Field arrivals, mobile/homeworld transports and
+optional arrival compositions are not expanded by the Basic prototype.
+Advanced ordinary physical entry is connected in the follow-up above.
+Refinement of interrupted and mixed-cohort interactions remains later work.
 
 **Brief smoke evidence:** paid Basic allied arrival followed by Medium's
 native departure and clean ending; ending without departure removes two
@@ -69,13 +96,13 @@ the existing later-player and formation-turn conditions, including its
 non-exempt advisor treatment.
 
 This resolves the **Advanced** timing/advisor and end-turn consequence
-questions below. It does not remove the current allied-entry guard, grant
-new shipments or extra moves, alter alliance formation/breaking windows,
-or settle every optional arrival composition. A forced end consequence
-does not require a new loss confirmation; the existing `endMovement`
-action remains legal even when no escape is available. The native force,
-elite and No-Field custody paths remove the ending player's group once,
-not its ally's group.
+questions below. The 8 October follow-up also connects scoped ordinary
+allied reserve entry, without granting new shipments or extra moves,
+altering alliance formation/breaking windows or settling optional arrivals.
+A forced end consequence needs no new loss confirmation; `endMovement`
+remains legal even when no escape is available. Native custody removes the
+ending player's group once, not its ally's group; concealed No-Field removal
+retains its separate custody guard.
 
 The own clean-turn warning uses the canonical engine quote via
 `GameView.advancedAllySeparation: { territories: string[] } | null`.

docs/CURRENT_STATUS.md

@@ -20,10 +20,14 @@ open mode gates.
 requests usable first versions for every faction before refinement. Administration
 is deferred. Broad suites and capture-resumption campaigns are deferred; rule
 delivery uses brief changed-path smoke only, with batched compiler feedback.
-**Active pass — Advanced first versions.** Basic standalone core-function
-inventory is closed at prototype level, with its stated provisional policies.
-This does not certify Basic timing variants, combinations or public expansion
-starts. Those remain after the Advanced function pass.
+**Active pass — rule interactions and remaining optional paths.** Basic and
+Advanced standalone core-function inventories are closed at prototype level.
+Bounded classic/expansion mapping plus the connected follow-ups below found
+no further absent standalone faction primitive in the examined paths.
+This is not complete-mode acceptance: exceptional custody, timing variants,
+optional skill bands, combinations and public expansion starts remain open.
+Rules implementation continues; comprehensive assurance and administration
+remain deferred until all rules are implemented.
 
 
 **Richese cache cancellation connected.** The printed Karama cancellation
@@ -120,6 +124,14 @@ Two native Easy smokes, two cycle regression cases, owned GameTable SSR
 Chromium choices and types/lint pass. No broad suite or deployed acceptance
 was run; prevention, price, death history and one-leader allowance remain.
 
+**Advanced ordinary allied arrival connected.** Scoped physical reserve
+shipment can enter an ally's territory before movement. Native supplied
+p15 ending removes all shared actor forces, including old counters; Basic
+keeps its separate provisional visitor policy. Medium departs typed arrivals
+without a city sentinel. Three direct scenarios, one cross-mode arrival/ending
+regression, types/lint and native GameTable SSR pre-arrival/ending controls
+pass; no broad suite or deployed proof was run.
+
 **7 October 2026 — five pending rulings resolved by the user.** The user
 answered five recorded questions; each is now recorded in
 [the decision index](RULE_DECISIONS.md#user-rulings--7-october-2026) and

docs/RULE_DECISIONS.md

@@ -25,9 +25,10 @@ rulings below remain distinct from these prototype choices.
 
 ## Advanced prototype pass — 8 October 2026
 
-The Basic standalone core-function inventory is closed at first-version
-level, not complete-mode acceptance; Advanced function delivery now precedes
-timing/combination refinement. Ecaz's supplied physical PDF **p30, A**
+Basic and Advanced standalone core-function inventories are closed at
+first-version level, not complete-mode acceptance. Exceptional custody,
+timing variants and optional combinations remain active rule work.
+Ecaz's supplied physical PDF **p30, A**
 requires an available Duke grant after accepted Ambassador alliance consent.
 The accepting action now performs that same-disc transfer automatically,
 without a new loan acknowledgement. Basic keeps its optional prototype.
@@ -57,6 +58,12 @@ The separate five-ordinary-disc cycle exclusion is a visibly provisional
 implementation policy, not a numerical user ruling or publisher answer.
 [Source, policy and runtime evidence](CHOAM_AUDITOR.md).
 
+Advanced ordinary allied reserve shipment now uses the FAQ's scoped
+shipment-then-departure permission and supplied **p15** end-turn constraint.
+Its ending removes all shared actor forces, not the Basic prototype's
+excess newcomers. Storm/capacity and advisor/Polar/Ecaz exemptions remain.
+No-Field and optional transports are separate. [Allied transit](ALLIED_TRANSIT_RULES.md).
+
 ## User rulings — 7 October 2026
 
 Five previously pending questions were answered directly by the user. These are