Resolve direct advanced Sneak arrivals
Verify and publish checkpoint container / container (push) Canceled after 0s
Verify and publish checkpoint container / container (push) Canceled after 0s
This commit is contained in:
1 parent
8a39f5a172
commit
b79e448deb
8 files changed
+213
-8
No files matched your search
+14
-2
@@ -17,11 +17,23 @@ open mode gates.
|
||||
|
||||
## Current checkpoint and work
|
||||
|
||||
**Direct Advanced Sneak Attack arrivals — 29 October. Prototyped / Partial.**
|
||||
Outside worm continuations, a positive Sneak group now gets its own Advanced
|
||||
arrival reactions, including an eligible Ecaz Ambassador after Bene Gesserit.
|
||||
The original action and existing dedicated Homeworld continuations remain.
|
||||
The focused native tests use genuine Advanced setup with controlled physical
|
||||
token placement; ten related files pass 73 cases. A staged worm ride verifies
|
||||
the temporary positive-entry guard and zero-force continuation. Full worm
|
||||
support needs a separate saved rider continuation; optional combinations and
|
||||
deployed verification remain open.
|
||||
[Scope](MORITANI_ENTRY_TIMING.md#direct-advanced-sneak-arrivals--29-october-2026).
|
||||
|
||||
**Advanced Ambassador child arrivals in the Ecaz–Moritani overlap — 29
|
||||
October. Prototyped / Partial.** Bare native Advanced games can use the Fremen
|
||||
relocation and Guild shipment within the paired entry, retaining the child
|
||||
Terror reaction and the original entry's remaining opportunity. Sneak Attack
|
||||
queues its own Bene Gesserit reactions without overwriting that opportunity.
|
||||
Terror reaction and the original entry's remaining opportunity. Outside worm
|
||||
continuations, Sneak Attack queues its own Bene Gesserit reactions without
|
||||
overwriting that opportunity.
|
||||
Eight related files pass 52 cases, including actual Advanced setup, both owner
|
||||
orders, controls and minimal bot actions; token selection and placements are
|
||||
controlled in the fixtures. Optional-module combinations, other nested cases,
|
||||
|
||||
@@ -2,6 +2,29 @@
|
||||
|
||||
Reviewed 2026-09-06. This supplements `MORITANI_TERROR_RULES.md`; it does not enable combined-faction play or certify an implementation order.
|
||||
|
||||
## Direct Advanced Sneak arrivals — 29 October 2026
|
||||
|
||||
**Prototyped / Partial.** A positive Advanced Sneak Attack outside a worm
|
||||
continuation now queues its own committed off-planet group for the existing
|
||||
Intrusion, Bene Gesserit accompaniment and eligible Ambassador reactions. The
|
||||
original arrival finishes first, the new group spends no ordinary shipment or
|
||||
spice, and zero forces create no extra entry. The ordering is a provisional
|
||||
composition of the printed reserve entry and Ambassador interruption, not a
|
||||
publisher priority ruling. Caladan and revival source receipts retain their
|
||||
dedicated paths.
|
||||
|
||||
Worm continuations require a separately retained rider identity: a Moritani
|
||||
child cannot simply inherit the Fremen rider's Ambassador continuation. The
|
||||
positive choice is therefore temporarily blocked for Advanced worm parents;
|
||||
Moritani may leave the token hidden or send zero. The staged worm regression
|
||||
checks the visible reason, rejection and continued ride. Broader modules and
|
||||
deployed verification remain open.
|
||||
|
||||
Ten related files pass 73 cases. Direct runtime fixtures use genuine Advanced
|
||||
setup and physical token selection/placement under control, including BG and
|
||||
no-BG, a free Guild Ambassador grant and legal bot choices. They do not certify
|
||||
full-game or optional-module combinations.
|
||||
|
||||
## Advanced native Ambassador child arrivals — 29 October 2026
|
||||
|
||||
**Prototyped / Partial.** In the bare Advanced native-faction profile, the
|
||||
@@ -9,7 +32,7 @@ Fremen Ambassador relocation and Guild Ambassador shipment can now create a
|
||||
child arrival while the original paired Ambassador/Terror entry remains in
|
||||
progress. The existing child-first continuation preserves the original entry,
|
||||
remaining opportunity and physical movement or payment. A positive Sneak
|
||||
Attack in this overlap queues its own reactions until the original decisions
|
||||
Attack in this overlap outside a worm continuation queues its reactions until the original decisions
|
||||
finish, including its Bene Gesserit opportunity. The owners' storm order and
|
||||
child ordering remain the provisional software interpretations below, not an
|
||||
official priority ruling; the printed Ambassador effects and interruption are
|
||||
@@ -17,8 +40,8 @@ described in GF9 Ecaz & Moritani rules pp. 8 and 15.
|
||||
|
||||
Fremen destinations combining Advanced fighter Intrusion with Terror retain
|
||||
their existing restriction, and simultaneous Ambassador/Terror on Guild
|
||||
accompaniment remains separate. Other optional modules, Advanced Sneak outside
|
||||
this overlap, complete rules and deployed verification remain open.
|
||||
accompaniment remains separate. Other optional modules, worm continuations,
|
||||
complete rules and deployed verification remain open.
|
||||
|
||||
Eight related files pass 52 cases. Real Advanced setup covers both owner orders,
|
||||
Fremen and Guild child effects, child Terror decline or reveal, the paid original
|
||||
|
||||
@@ -1,5 +1,12 @@
|
||||
# Rule decision index
|
||||
|
||||
## Direct Advanced Sneak arrival — 29 October 2026
|
||||
|
||||
A positive Sneak group outside a worm continuation uses the existing separate
|
||||
arrival queue after the original entry. Its ordering is provisional; Advanced
|
||||
worm parents temporarily block a positive group until the rider continuation is
|
||||
preserved separately. [Scope](MORITANI_ENTRY_TIMING.md#direct-advanced-sneak-arrivals--29-october-2026).
|
||||
|
||||
## First-turn Duke proof and occupied Ecaz displacement — 29 October 2026
|
||||
|
||||
**Prototyped / Partial.** Public first-turn pre-battle state can prove that an
|
||||
|
||||
Reference in new issue
Block a user