Compose the deferred Terror arrival and green the mixed E3 programmes

Queue a committed Terror entry whose arrival also opened its own
interaction — Guild income, a Bene Gesserit fighter Intrusion or advisor
choice, or Fremen storm protection — in the additive
Game.pendingArrivalReaction list, and open the oldest queued entry from
settleAutomaticContinuations once nothing is pending. Payment, force
transfer and the original movement never replay; a Terror entry already in
flight and every Ambassador combination still reject.

Both withdrawn mixed E3 programme pairs are green: Moritani 9/9 and Ecaz
14/14, stable across 20 consecutive full-file runs. Their recorded resume
constraints became real fixture repairs, and the two restored consumer
omissions were corrected against the engine rather than re-pinned.

Repair pre-existing failures inherited at 45e6084 against current engine
behavior: stale Discovery and module gates in the native skills, Ix and
expansion-faction prototypes, the advanced Moritani skill boundary, the
Richese Nexus betrayal sale-credit expectation, one incidental gate
message and one flaky Collection-readiness assertion that reproduced at
HEAD.

Offline suite 7,793/7,793 with typecheck and lint clean. No game, seat,
saved-state, deployment, public-start or played-save conversion changes.

docs/MORITANI_ENTRY_TIMING.md

@@ -21,7 +21,7 @@ No targeted publisher/designer clarification establishes which of Ecaz's Ambassa
 
 Both optional trigger opportunities belong to the **same already committed entry**. Snapshot the original entrant, token identities, physical arrival amount and turn; finish the first owner's choice and its allowable continuations before offering the second. Revalidate the second effect's physical requirements without replaying the original shipment payment, movement or force transfer. Owner-private Terror identity remains concealed until revealed. If the first reaction changes an alliance, the other owner keeps the trigger earned at the original entry; it does not gain a new trigger from a later action.
 
-This bounded path excludes competing BG fighter Intrusion, Guild income/advisor and CHOAM prevention windows, Homeworlds, Nexus, Discoveries, Leader Skills and the still-unfinished Atomics effect. Fremen relocation or Guild free-shipment Ambassador effects can create nested arrivals before the second owner; they remain declineable but cannot be activated in this overlap until their child continuation is integrated. These guards are development boundaries, not physical-game prohibitions.
+This bounded path originally excluded competing BG fighter Intrusion, Guild income/advisor and CHOAM prevention windows, Homeworlds, Nexus, Discoveries, Leader Skills and the still-unfinished Atomics effect. **The competing BG fighter Intrusion, Guild income and BG advisor windows are now integrated as a deferred entry — see the 7 October 2026 section below.** Fremen relocation or Guild free-shipment Ambassador effects can create nested arrivals before the second owner; they remain declineable but cannot be activated in this overlap until their child continuation is integrated. These guards are development boundaries, not physical-game prohibitions.
 
 ## Paired native Nexus composition — 7 October 2026
 
@@ -50,6 +50,33 @@ This does not merge an advisor's separate arrival into the parent's
 reaction, make advisors eligible for Ambassadors, or claim a universal
 optional-module priority order.
 
+## Deferred arrival entry behind the arrival's own interactions — 7 October 2026
+
+The engine no longer rejects a Terror arrival that coincides with the arrival's
+own pending interaction. `openTerritoryEntry` stores the already committed
+entry in the additive `Game.pendingArrivalReaction` record — original entrant,
+destination, sector, amount, elite, cause, resume kind and turn/phase — and
+`settleAutomaticContinuations` opens it as soon as no response, decision,
+Terror entry, Ambassador entry or Ecaz/Moritani overlap is pending. Payment,
+force transfer and the original movement are never replayed; the deferred
+record only reopens the entry.
+
+**Selected order (provisional implementation interpretation, not a publisher
+ruling):** the arrival's own interaction settles first — the committed
+shipment's Guild income payment and BG advisor choice, the BG fighter
+Intrusion, or Fremen storm protection — and the Terror entry is offered
+afterwards. This reuses the bounded policy already recorded for an accompanying
+counter, whose own qualifying entry likewise follows earlier Intrusion and
+income, and it respects the November 2020 FAQ wording that Intrusion must occur
+immediately when the other faction intrudes. No source ranks the optional
+Terror reaction against those windows; this table selects one order rather than
+leaving the entry uncommitted.
+
+Still guarded after this integration: `controls.pendingTerror` (a Terror entry
+already in flight), every Ambassador combination
+(`Ambassadors combined with another arrival reaction`), Atomics, unsupported
+child effects and the CHOAM prevention windows.
+
 ## Atomics and later allies
 
 The current official indexed p. 5 still says: “From this turn forward, your hand limit is reduced by 1 (as well as your ally’s)”. It does not specify how a later alliance change affects either former or new allies. Both a continuing current-ally modifier and a detonation-time recipient remain interpretations. No targeted clarification was found. [GF9 E3, p. 5](https://www.gf9games.com/dune/wp-content/uploads/EcazMoritani-Rulebook-LOWRES.pdf#page=5)