Track repeated Ecaz revival cohorts by native disc identity

docs/CURRENT_STATUS.md

@@ -29,6 +29,23 @@ optional skill bands, combinations and public expansion starts remain open.
 Rules implementation continues; comprehensive assurance and administration
 remain deferred until all rules are implemented.
 
+**Ecaz identity-tracked repeated cohorts — 14 October.** The repeated-history
+fence is replaced by provisional native-disc accounting: five Tanks including
+Duke or the existing unavailable-roster exception opens ordinary returns;
+completed native IDs preserve the remainder and later first deaths do not
+need to match a global death number. Duke stays physically separate and
+independently revivable. Actual paid, Ghola/Ambassador/foreign returns record
+completion, not requests; the absent-Tleilaxu waiver remains local.
+Affected19-file union230/230 and types/lint/build pass. Two original native
+chronologies, both four-profile paths and actual styled390px controls prove
+first-cohort11→8 and second-cohort12→10, one normal slot and original death
+history. The fifth native can remain alive at deaths0; Duke stays dead1
+without holding the native cohort. Actual bribes fund QA, not wallet staging.
+No overflow/browser errors or saved/deployed room touched.
+[Current policy/source and proof](ECAZ_REVIVAL_RULES.md#identity-tracked-repeated-cohorts--14-october-2026).
+Full combinations, assurance, calibration and publication remain open.
+Existing build deprecation/chunk/route warnings remain.
+
 **Original quiet-phase Ecaz Cunning — 14 October.** Printed current-turn
 tenure no longer has an artificial Battle-only fence. Existing quiet
 boundaries preserve committed decisions, native chooser/phase, costs and

docs/DUKE_VIDAL_RULES.md

@@ -105,3 +105,15 @@ use; separate Cunning can then acquire him. Only Ecaz revives him: no
 Tleilaxu-owned foreign Ghola is manufactured. Native identity, strength6,
 five-disc faction rosters, absent Traitor card and death history remain.
 [Current controls, verification and remaining gates](NEXUS_ECAZ_RULES.md#original-captured-duke-and-ecaz-ghola-composition--14-october-2026).
+
+## Native repeated revival cohorts — 14 October 2026
+
+Ecaz's normal native returns no longer stop merely because any shared or
+native disc has died more than once. A provisional identity-tracked cohort
+preserves five-Tanks opening, native unavailable-roster exceptions and
+remaining ordinary returns without equating Duke's independent death history
+to the native cohort number. Duke remains separate, costs5 normally and
+returns set aside; he neither becomes a sixth native leader nor a foreign
+Ghola. Actual ordinary/Ghola returns, native controls and four legal profiles
+are connected. The old repeated-cycle guard above is historical.
+[Current policy, original native proof and remaining gates](ECAZ_REVIVAL_RULES.md#identity-tracked-repeated-cohorts--14-october-2026).

docs/ECAZ_REVIVAL_RULES.md

@@ -24,6 +24,69 @@ available, without making a repeated six-disc algorithm up. Captured, Ghola
 or concealed shared-disc custody and Advanced Harkonnen combinations retain
 their existing uniform boundary.
 
+## Identity-tracked repeated cohorts — 14 October 2026
+
+The blanket repeated-history gate is replaced by an explicit **provisional
+product composition**, chosen under the recommendation-first instruction:
+
+- Five actual leaders in Tanks, including Duke, open ordinary Ecaz returns.
+  The existing no-available-native-leader captured/foreign-custody exception
+  remains distinct from counting a living captive as physically dead.
+- Each opened cohort records completed **native disc identities**, not equality
+  between every disc's death count and one global counter. Unreturned native
+  deaths remain eligible after another native is revived and killed again.
+  A late first death can join a later open cohort without being misclassified
+  as a repeat. An already returned identity waits for the remaining native
+  cohort and another legal opening.
+- Duke remains outside the five ordinary discs. His actual presence in Tanks
+  can open a cohort, but his independent death counter does not number or hold
+  the native cohort. An independent Duke resurrection preserves an already
+  satisfied opening before removing that fifth Tanked disc.
+- Actual normal, Ghola, first-death Ambassador and foreign-ghola native returns
+  record the identity only when the physical return commits. A first capture
+  execution retains the original face-down first-cohort exclusion; it does
+  not create a permanent native-disc ban.
+- One ordinary leader allowance, printed native price, Duke5/discount3,
+  prevention, payment/income and original return custody remain unchanged.
+  Ghola and Nexus Cunning keep their own physical-card costs and allowances.
+  The absent-Tleilaxu waiver explicitly quotes the unopened first cohort
+  without opening ordinary permission or reusing a consumed identity.
+
+The optional server-only `Player.ecazRevivalCohort` stores the current cohort
+and native returned IDs. Valid older first-cohort states seed their existing
+face-down/revived identities lazily; no disc is recreated, no death history
+is rewritten, and no database migration/reset is needed. Its new state is
+included conditionally in the related ordinary-discard signature; absence
+preserves the old grammar. This is not historical-save certification.
+
+The original mixed-death rejection fails before and passes after. The affected
+nineteen-file union passes **230/230**, with types/lint/build. Actual native setup
+and weapon battles produce two consumer boundaries: five native deaths plus
+a paid return/repeat, and four native returns (three paid, one real Ghola)
+followed by four real repeat deaths while the never-killed fifth native lives
+and the original dead Duke remains at deaths1. The second cohort is used
+inside the original ten-turn game. Funding is an actual private15/25-spice
+bribe held until Mentat, not assigned wallet credit.
+
+Actual API paths pay11→8 for an unreturned first-cohort disc and12→10 for a
+second-cohort return. All four legal profiles in both positions perform
+original Cunning, ordinary forces and a paid native return, preserving cohort
+permission even when Cunning resurrects Duke. Actual canonical-styled390px
+GameTable selectors and revival buttons reach the same prices, one ordinary
+slot and retained death history; the repeat stays dead in the first path,
+and Whitmore remains alive at deaths0 in the second. No overflow/browser
+errors or saved/deployed room mutation. The native smoke chooses its next
+battlefield after the real Storm rather than silently skipping past turn ten.
+The final build retains existing module-deprecation, large-chunk and route
+classification warnings; no complete-mode or publication gate is opened.
+
+See [cohort rules](../game/ecaz-revival-cohort.ts),
+[boundary regressions](../tests/ecaz-revival-cohort.test.ts) and
+[original native runtime](../tests/ecaz-revival-cohort-runtime.test.ts).
+This supersedes the repeated-cohort guard above and historical algorithm
+boundary below, not the binding Ecaz-only revival rule, broader profile
+guards or complete-mode/deployed acceptance.
+
 ## Captured return and legal Ghola composition — 14 October 2026
 
 The original standalone Ecaz/classic no-Skills Nexus envelope now admits

docs/IMPLEMENTATION_STATUS.md

@@ -1,5 +1,51 @@
 # Dune implementation status
 
+## 14 October 2026 — Ecaz identity-tracked repeated native cohorts
+
+Replaced the blanket repeated-six-disc guard with explicit provisional native
+identity accounting. Actual five-Tanks opening includes Duke; the original
+unavailable-native-roster exception stays separate. Completed native returns
+preserve the remaining cohort, a late first death need not equal its global
+generation, and a returned identity waits for completion plus another opening.
+Duke's independent death counter neither indexes nor holds native cohorts.
+
+Paid completion, own/foreign Ghola and first-death Ambassador returns record
+actual native use; a first capture execution retains its face-down exclusion.
+Independent Duke normal/Ghola/Nexus resurrection preserves a satisfied opening.
+Pending normal requests do not commit the new cohort. The absent-Tleilaxu
+waiver is explicit and local rather than a fabricated copied cycle. Removed
+obsolete cycleBlock producer/UI/caller and its guard test, not re-pinned.
+Ordinary slot, printed prices, prevention/payment/income, separate card costs,
+native five-disc identity, Duke history and Ecaz-only set-aside return remain.
+
+The optional server-only cohort field preserves exact old ordinary-discard
+signature grammar when absent. No schema migration, saved-room reset or
+historical assurance campaign is introduced. Provisional accounting is labelled,
+not presented as a publisher's missing six-disc example or user numeric ruling.
+
+The mixed-death rejection fails before/passes after. Affected19-file union
+230/230 and types/lint/build pass. Original native setup, physical shipments and
+poison battles create five native deaths, a paid return and its repeat, then
+an independently completed four-native cohort with original Ghola, four repeat
+deaths and the same Tanked Duke. The never-killed fifth native survives and
+the second cohort is used inside turn ten. Original private15/25-spice bribes
+become spendable at Mentat; no wallet/death/history assignment funds this proof.
+The fixture selects its next battlefield after the actual Storm to avoid
+running a skipped-battle chronology past the original game end.
+
+Actual API and canonical-styled390px production controls pay11→8 for the
+unreturned native while the repeat stays dead, and12→10 in the second cohort
+while Whitmore stays alive/deaths0 and Duke stays Tanked/deaths1. One ordinary
+leader slot is spent. All four policies in both original positions use
+actual Cunning, ordinary force revival and a paid native return; Cunning's
+independent Duke resurrection retains the open native permission.
+No overflow/browser errors or saved/deployed room mutation. Proof JSON stays
+outside Git; broader combination/recovery review, calibration and deployed/
+publication acceptance remain open.
+Final build retains the existing module-deprecation, chunk-size and route
+classification warnings.
+[Canonical policy, source and current evidence](ECAZ_REVIVAL_RULES.md#identity-tracked-repeated-cohorts--14-october-2026).
+
 ## 14 October 2026 — Original quiet-phase Ecaz Cunning
 
 Removed the artificial Battle-only availability fence from printed

docs/RULE_DECISIONS.md

@@ -66,6 +66,24 @@ These decisions do not open public module/faction or complete-mode gates.
 
 These decisions do not open public module/faction or complete-mode gates.
 
+## Recommended Ecaz repeated native cohorts — 14 October 2026
+
+Choose explicit native-disc cohort accounting instead of the unresolved
+blanket repeated-history gate or equality with a global death count.
+Five physical Tanks including Duke, or the existing unavailable-native-roster
+exception, opens ordinary permission. Completed native identities determine
+the remainder; another legal opening follows completion. A late first death
+may join the current cohort. Duke's independent deaths do not index or hold
+the native cohort, while his actual presence can satisfy its opening.
+
+This is **provisional product composition**, not a publisher-specific
+six-disc example or a new numerical user ruling. Preserve native five-disc
+identity, ordinary one-leader use, native prices and Duke5/discount3,
+Ecaz-only revival/set-aside custody, printed first-execution exclusion and
+separate Ghola/Nexus allowances. Record actual returns rather than pending
+requests. Broader rule/privacy/persistence review remains deferred.
+[Source, exact policy and current runtime proof](ECAZ_REVIVAL_RULES.md#identity-tracked-repeated-cohorts--14-october-2026).
+
 ## Recommended quiet-phase Duke Cunning — 14 October 2026
 
 Remove the prototype's Battle-only fence: the printed face specifies
@@ -630,7 +648,7 @@ dedicated retrieved worked FAQs. [Contract and remaining limits](HOMEWORLD_OCCUP
 | Guild Secret Ally | One explicit Guild-priced ordinary shipment; borrowed prices/routes preserve native identity. Free Fremen reinforcement remains a separate choice. | [Route contract](NEXUS_GUILD_SECRET_ALLY_RULES.md), [verified runtime](NEXUS_GUILD_SECRET_ALLY_RUNTIME.md) |
 | Homeworld custody and mobility | Physical home/visitor groups, population thresholds, tariffs and transport permissions retain distinct sources; Homeworld immunity is not universal immunity. | [Homeworld rules](HOMEWORLD_RULES.md), [benefits](HOMEWORLD_BENEFITS_RULES.md), [mobility](HOMEWORLD_MOBILITY_RULES.md), [invasion](HOMEWORLD_INVASION_RULES.md), [Guild transport](GUILD_HOMEWORLD_TRANSPORT_RULES.md) |
 | Homeworld effects | Keep original payment/revival/placement identities and qualification observations; observations alone do not choose an occupied-benefit owner. | [Payments](HOMEWORLD_PAYMENT_INCOME_RULES.md), [card economy](HOMEWORLD_CARD_ECONOMY_RULES.md), [Collection](HOMEWORLD_COLLECTION_RULES.md), [revival deployment](HOMEWORLD_REVIVAL_DEPLOYMENT_RULES.md), [victory reinforcement](HOMEWORLD_VICTORY_REINFORCEMENT_RULES.md), [replacement](HOMEWORLD_REPLACEMENT_RULES.md), [Tupile](HOMEWORLD_TUPILE_INTELLIGENCE_RULES.md) |
-| Duke Vidal revival custody | The user selected set-aside custody after Ecaz revives the shared disc: revival clears the Tanks but does not itself grant battle control. Ecaz still needs a separate Ambassador or Nexus acquisition; only Ecaz may revive Duke, including by Ghola. This resolves one post-revival product interpretation, **not** the separate six-disc repeated-cycle, exceptional capture or battle-used Ghola questions. No publisher clarification assigning a post-revival controller was located. | [Publisher Ecaz/Moritani pp. 7–9](https://gamers-hq.de/media/pdf/0f/7a/86/Dune_EcazMoritani_Rulebook_EN.pdf#page=9), [revival readiness](ECAZ_DUKE_REVIVAL_READINESS.md) |
+| Duke Vidal revival custody | The user selected living set-aside custody after Ecaz revives Duke; a separate Ambassador/Nexus acquisition grants battle control. Only Ecaz may revive him, including Ghola. Native repeated returns now use the separately labelled provisional identity-cohort policy, not a new publisher example or user number. Captured scope and broad combinations remain separately bounded. | [Selected custody](ECAZ_REVIVAL_RULES.md#selected-product-interpretation-28-september-2026), [current cohort policy](ECAZ_REVIVAL_RULES.md#identity-tracked-repeated-cohorts--14-october-2026) |
 | Mirror Weapon copied-card cleanup | The user selected ordinary winner retention for the physical Mirror even if its effective copy activates Tooth or Artillery. The original Tooth/Artillery cards retain their named mandatory-discard exceptions. This is a product interpretation, **not** a located publisher ruling. Independent copy-first Tooth/Stone choices and physical cleanup now have a bounded CHOAM/Richese-deck battle runtime; combined modules and full Richese games remain gated. | [Printed Mirror face and source audit](MIRROR_WEAPON_ENGINE_AUDIT.md#user-selected-cleanup-interpretation-28-september-2026) |
 | Kull Wahad preview timing | User selected a **distinct eligible counter** while the interrupted physical card stays reserved, and BG Worthless interception **before conversion/discard**. Pending declaration is not a ban; only success stamps turn/phase and retains original/special once-use. Decline or prevention resumes the original once. Old `kull` stays printed-only; fresh `nexus-kull` admits native CHOAM plus classic Basic/Advanced seats, CHOAM/Ix Treachery and Nexus alone, without physical Sandtrout. Nexus Use needs actual unallied CHOAM Nexus and canonical eligible own fuel: accepted declaration spends Nexus even if prevented, fuel stays held until success. Use requires source/event/card, with no old-source action shim or proactive Kull. Verified prior printed counter saves migrate only their selection binding; no new-choice retrofit. Reservations, promises and remaining winning-payment coverage constrain fuel/counters; ordinary retained Karama payment is not a canceled Cunning effect. Priority/custody/overbid are user policy; neutral timing/spend conventions are application policy. Bounded checks/CLI/runtime/phone cases pass; broader verification is Partial and no full/public/deployed gate opens. | [Selected preview policy](CHOAM_KULL_SOURCE_UPDATE.md#user-selected-preview-timing--30-september-2026), [source/cost boundary](NEXUS_CHOAM_RULES.md#kull-source-cost-and-action-boundary), [runtime and remaining limits](CHOAM_KULL_DESIGN.md), [new evidence](NEXUS_CHOAM_RUNTIME.md#five-part-status-for-the-new-interaction) |
 | Semuta full-hand exchange | User selected **Allow exchange**: acquisition followed by Semuta disposal is an atomic net-zero hand exchange at the faction limit. Existing incoming reservations still consume capacity; this does not permit an already overfull hand or settle Box/Richese purchase timing. | [Selected capacity policy](SEMUTA_SOURCE_UPDATE_20260907.md#user-selected-full-hand-exchange--30-september-2026) |