Connect source-ordered Advanced Ecaz new-ally Duke grant

docs/CURRENT_STATUS.md

@@ -20,6 +20,11 @@ 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.
+
 
 **Richese cache cancellation connected.** The printed Karama cancellation
 now reaches the restore-one-ordinary-lot policy selected on 7 October. First/last
@@ -77,6 +82,12 @@ paths; Advanced-only powers and deferred combinations were kept separate.
 Compact faction guides now describe connected Basic Richese/Ecaz prototypes
 and bounded Moritani effects rather than stale blanket absence. This is an
 inventory result, not comprehensive rules or complete-mode acceptance.
+**Advanced Ecaz new-ally Duke grant.** Supplied PDF physical p30 adds an available
+shared Duke automatically after Ambassador alliance consent. The accepting action
+now grants the original disc and resumes the entrant without another loan choice.
+Basic remains optional. One-battle tenure stays provisional; unavailable/captured
+scope remains guarded. One actual grant-and-battle smoke and three changed
+contract cases pass; types pass. No broad suite or deployed acceptance was run.
 
 
 

docs/DUKE_VIDAL_RULES.md

@@ -35,7 +35,7 @@ The [base Harkonnen capture rules, p. 17](https://www.gf9games.com/dunegame/wp-c
 | Moritani acquisition from captured or ghola custody | Ecaz’s Ambassador explicitly excludes both; Moritani’s acquisition excludes only Tanks and says to take Duke from any controller. Do not silently copy the Ecaz exclusions as a confirmed Moritani rule. The interaction with concealed capture and the apparent ghola restriction needs an explicit supported policy. |
 | Duke used in a lost battle against Harkonnen        | One-battle tenure and postbattle capture both apply. No retrieved Duke-specific text orders release versus selection into the capture pool. Removing him first changes the random pool; keeping him first can change custody. Gate this combination until resolved rather than choosing by handler order.              |
 | Returning a captured Duke                           | Native identity is Ecaz, but temporary prior custody may be Moritani or a loaned ally. Base capture return plus Duke’s special acquisition restrictions do not explicitly settle active-control versus set-aside destination in every combination. Preserve prior custody rather than discarding that information.     |
-| Loan to the new Ecaz ally | The printed loan lasts this turn. The 8 October Basic-first prototype now offers the loan after an accepted Ambassador alliance, with the same physical disc. One-battle tenure and unused living turn-end set-aside are explicitly provisional implementation policies. Advanced, capture and alliance-break interactions remain for refinement; no publisher clarification is claimed. |
+| Loan to the new Ecaz ally | Basic has an optional same-disc first version after accepted Ambassador alliance consent. The authorized supplied Advanced PDF, physical p30 Ecaz A, instead adds an available Duke automatically after consent and sets an unused disc aside at turn end; that path is now connected without another acknowledgement. One-battle release is still provisional. Capture and alliance-break interactions remain for refinement. |
 | Ecaz co-occupied battles                            | Ecaz’s Occupy rules distinguish participating forces from the faction chosen to fight. Duke eligibility excludes battles involving Ecaz, but no direct combined example decides every Ecaz-ally designation case. Ordinary faction-pair battle lists alone do not certify the full Occupy interaction.                 |
 | Revival alternatives                                | Ecaz’s Tleilaxu Ambassador effect and sharing an Ambassador benefit may interact with the absolute Ecaz-only restriction. No retrieved specific exception permits another faction to revive Duke. Keep that restriction unless a primary clarification establishes otherwise.                                          |
 

docs/ECAZ_DUKE_ACQUISITION.md

@@ -15,9 +15,32 @@ Private decision ownership and a minimal legal bot choice are connected.
 The first version uses one-battle tenure and sets an unused living loan aside
 at turn end. These are labelled implementation policies under the Basic-first
 instruction, not a publisher clarification of return destination or mid-loan
-alliance changes. Advanced loans and exceptional custody remain for later work.
+alliance changes. Exceptional custody and wider combinations remain for refinement.
 A direct Basic arrival → consent → legal bot loan → resumed entrant smoke passes.
 
+## Advanced accepted-alliance Duke grant — 8 October 2026
+
+The authorized supplied `UNOFFICIAL_Revised_Dune_Rulebook_v.2.3_web.pdf`,
+physical **page 30, Ecaz A**, says “Then, add Duke Vidal to the triggering
+faction’s leader pool” after alliance consent, and sets an unused disc
+aside at turn end. Advanced therefore grants an available canonical Duke
+automatically in the accepting action, with **no separate Ecaz loan choice
+or acknowledgement**. Basic keeps its existing optional prototype choice.
+
+The same disc changes controller/source, preserving identity and death
+history without appending a native leader or Traitor. Existing dead,
+captured/ghola and Advanced-Harkonnen scope guards remain; unavailable
+Duke does not veto alliance consent. One-battle release remains the
+explicit provisional tenure policy, not an additional supplied-text ruling.
+The entrant’s original arrival suffix resumes once after consent/grant.
+
+One direct Advanced smoke reproduces the missing grant, then uses Easy's
+real consent, the automatic same-disc grant, a real Duke Battle Plan and
+surviving release through native aftermath. Three changed alliance
+contract cases pass, including Basic decline and dead/shared custody.
+Actual SSR consent controls were observed in Chromium with automatic
+grant wording. Types pass; no broad suite or deployed acceptance was run.
+
 ## Rules and authoritative execution
 
 `game/ecaz-duke-acquisition.ts` quotes a detached next `DukeState` using the existing custody helper. It requires a current seated Ecaz owner and the existing canonical shared disc. It preserves identity, death history and `usedAt`; it never appends a leader to a native roster, adds a Traitor card, manufactures a replacement disc, samples randomness or grants new battle-use permissions. Starting-force initialization remains the normal disc-creation boundary.

docs/RULE_DECISIONS.md

@@ -23,6 +23,18 @@ They supersede earlier software-absence claims only within their named scope.
 No publication or faction/mode gate is opened. The exact 7 October user
 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**
+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.
+Turn-end set-aside is supplied text; one-battle loan release remains the
+explicit provisional implementation policy. Existing exceptional custody and
+Advanced Harkonnen guards remain. [Current Duke grant contract](ECAZ_DUKE_ACQUISITION.md).
+
 ## User rulings — 7 October 2026
 
 Five previously pending questions were answered directly by the user. These are