Allow Residual Poison after Cunning inspections

docs/CURRENT_STATUS.md

@@ -16,6 +16,41 @@ open mode gates.
 
 
 ## Current checkpoint and work
+**Residual Poison after Cunning — 26 October. Prototyped / Partial.**
+The printed pre-leader window now stays available after two completed nonleader
+Cunning inspections. Resolve one actual random leader death/discard, retain an
+independently possible native answer, then require the extra answer to fit the
+same legal plan. An impossible native answer reopens both original fields in
+order, retaining private observations and the spent Nexus. This ordered-pair
+policy is provisional and specific to Residual; existing Sardaukar cancellation
+retains its other feasible answer. Persistent card guidance explains the priority.
+
+Three disjoint native-source/controlled-reconciliation/control lanes and root
+integration pass **17 files,131/131**, types/lint/build and **five engine/GameTable
+SSR journeys** on unchanged source. Seven native cases, four revised controlled
+engine cases and six controlled rendering cases cover the slice. Genuine public
+Basic108/Advanced120-action sources include an actual cache Residual1 purchase,
+original Nexus draw, Richese1 shipment into Arrakeen and both actual answers;
+one death preserves both commitments and the battle completes legally. Three
+explicitly controlled Advanced resource/leader seams separately prove native
+dial/weapon priority, actual cash-in or Ghola and ordered native/extra re-answers.
+All sources retain45 physical Treachery and12 Nexus cards. The four existing
+profiles use the legal new window; strategy/calibration remain deferred.
+
+Frozen v3 report/logs:
+`/home/quintine/.local/share/dune/checkpoints/20261026-residual-cunning-proof-v3/`;
+journeys/HTML: adjacent `20261026-residual-cunning-runtime/`.
+No saved-room/D1/server, reset/restart, deployment or recovery operation occurs.
+No DOM/hydration, browser/mobile or real clicked-control acceptance is claimed.
+Complete rules/combinations, final assurance and mode gates remain open.
+[Source and selected priority](NEXUS_ATREIDES_RULES.md#residual-poison-and-two-inspected-commitments).
+
+Next concrete function gap: the Caladan High victory reinforcement is still
+decline-only when native Face Dance is pending. Scope its original victory
+army and subsequent physical replacement through
+[the reinforcement contract](HOMEWORLD_VICTORY_REINFORCEMENT_RULES.md),
+`openHomeworldVictoryReturn` and `game/homeworld-victory-reinforcement.ts`.
+
 **Box shipping-cost recovery — 26 October. Prototyped / Partial.**
 Paid Box search now permits an active purchased-shipment cost in discard.
 Exact cost recovery preserves its original price/creator/beneficiary and ends
@@ -44,13 +79,6 @@ No saved-room/D1/server, reset/restart, deployment or recovery operation occurs.
 DOM/hydration, browser/mobile, complete rules/combinations and final assurance
 remain due. [Source and provisional policy](NULLENTROPY_BOX_ENGINE_AUDIT.md#shipping-price-cost-recovery--26-october-2026).
 
-Next concrete card-function gap: Residual Poison still rejects its pre-leader
-window after two answered Cunning inspections. Scope the existing native-first
-reconciliation rather than postponing the printed card window; see
-[Nexus inspection boundary](NEXUS_ATREIDES_RULES.md#residual-poison-and-two-inspected-commitments),
-`validateResidualPoison`, `reconcileChangedBattleInspections` and
-`tests/nexus-residual-ambiguity.test.ts`.
-
 **Reactive Fremen Nexus worm prevention — 26 October. Prototyped / Partial.**
 Fremen Nexus Betrayal now responds at actual unmade ordinary/Great Maker
 rides, after the original completed effects. Uniform public Nexus-back holders

docs/IMPLEMENTATION_STATUS.md

@@ -1,5 +1,36 @@
 # Dune implementation status
 
+## 26 October 2026 — Residual Poison after completed Cunning
+
+**Prototyped / Partial.** Remove the blanket pre-leader refusal after two
+answered nonleader Cunning inspections. The actual one-death/one-discard effect
+uses selected provisional native-first reconciliation. Preserve an independently
+possible native answer; test the extra jointly. If native becomes impossible,
+reopen both original fields in order, preserving observations and the spent
+Nexus. Both normal and original discard continuations opt into this ordered
+Residual policy; Sardaukar cancellation retains its other feasible answer.
+Persistent card guidance explains the composition. No leader-commitment or
+other active-interaction restriction is removed.
+
+Frozen **17-file131/131**, types/lint/build and **five engine/GameTable SSR
+journeys** pass. Two genuine public Basic108/Advanced120-action cache/Nexus/
+shipment/battle sources preserve both answers after one real random death and
+finish the actual battle. Three clearly controlled Advanced resource/leader
+sources separately prove native dial3 cash-in, retained weapon with actual Ghola,
+and impossible-native ordered re-answers. All45 physical Treachery and12 Nexus
+cards remain. Seven native cases, four revised controlled engine cases and six
+rendering supplements cover rejection, commitments and four minimal profiles.
+Feedback repaired a base-only test initializer, omitted native outcome readiness,
+CSS-class/attribute assertions and the unrelated cancellation regression; final
+lint also removed an unnecessary test-array copy.
+
+Proof: `/home/quintine/.local/share/dune/checkpoints/20261026-residual-cunning-proof-v3/`;
+journeys/HTML: adjacent `20261026-residual-cunning-runtime/`.
+No saved-room/D1/server, reset/restart, deployment or recovery operation. No
+DOM/hydration, browser/mobile or actual clicked-control acceptance. Complete
+rules/combinations, final assurance and all mode gates remain open.
+[Source and priority](NEXUS_ATREIDES_RULES.md#residual-poison-and-two-inspected-commitments).
+
 ## 26 October 2026 — Box recovery of a purchased shipment cost
 
 **Prototyped / Partial.** Remove the blanket pending-refund search ban. Exact

docs/NEXUS_ATREIDES_RULES.md

@@ -70,42 +70,68 @@ The unresolved cases were reported to the coordinator before implementation deci
 
 ## Residual Poison and two inspected commitments
 
-The following is a reasoned counterexample from the existing preparation rules,
-not a reported executed gameplay regression. In Advanced play, CHOAM has four
-ordinary forces in the battle, no spice, one living usable leader, a projectile,
-Ghola and a real Karama, and its cash-in power is unused. Suppose native
-Prescience fixed the dial at three and Cunning fixed the projectile. Before a
-leader death, both answers are reachable: cashing Ghola supplies three spice,
-enough to support the dial, while the living leader permits the projectile.
+**Selected provisional composition — 26 October 2026.** The 14 October
+choose-recommended authority supersedes the earlier blanket product refusal.
+The printed Residual Poison window remains available after two completed
+nonleader Cunning inspections, before either combatant commits a leader.
+Active interactions and exact card commitments still resolve as required.
+This does not make leader-valued inspection commitments poisonable.
 
-If Residual Poison kills that last leader, each answer can remain feasible by
-itself. Keeping the projectile permits Ghola revival with a lower dial. Keeping
-the dial permits cash-in while omitting the weapon. Keeping both cannot spend
-the same Ghola both on revival and on funding, nor cash the committed projectile.
-There is therefore no generally valid assumption that an earlier answer, a later
-answer, or all individually feasible answers identify the uniquely correct
-surviving set. The retrieved publisher rules do not select between these sets.
+Resolve the one actual random eligible leader death and discard first. Use the
+same existing reconciliation already used after canceled Sardaukar enhancement:
 
-The coordinator has asked whether the affected player should choose the retained
-commitment, the earlier commitment should take priority, or this combination
-should await an official ruling. The answer is pending. No such priority is
-implemented by this document. Until resolved, the runtime uses an explicit
-development boundary: Residual Poison is unavailable after an answered Cunning
-inspection. This guard depends on the publicly played mode and completion stage,
-not the opponent's hidden cards, spice, or whether a private feasibility search
-happens to find a conflict. It is not a printed prohibition. The independent
-leader-commitment restriction still applies, and this boundary does not prohibit
-the single-element Secret Ally continuation.
+1. Test the original native nonleader answer without obsolete extra bindings
+   or Truthtrance. Keep it if a legal prepared plan can still honor it.
+2. Test the extra Cunning answer jointly with any retained native answer. If
+   no legal plan honors both, reopen the extra answer's original field.
+3. If the native answer itself is impossible, reopen both current bindings.
+   Answer its original field first, then the extra field through the original
+   saved protocol, so the old extra binding cannot constrain the renewed native
+   choice.
+4. Reconcile Truthtrance only after retiring the impossible inspection bindings.
+   Keep earlier private observations and the spent Nexus receipt; re-answering
+   changes neither field selection nor card cost. Never redraw the victim,
+   restore a dead leader or repeat the discard to save a commitment.
 
-Any later implementation should test complete legal continuations with the
-proposed retired bindings removed on private copies. Testing one binding while
-another impossible binding remains can falsely release a valid dial. Likewise,
-reconciling Truthtrance before retiring an impossible inspection can wrongly
-release an otherwise feasible promise. Preserve historical disclosures and the
-consumed Nexus receipt separately from active bindings; a renewed answer is to
-the original field and does not consume another card. Multiple incomparable
-maximal surviving sets must not acquire an unexplained software tie-break.
+The ordered pair reopening when native becomes impossible applies to Residual
+Poison, including its original discard continuation. Sardaukar cancellation
+retains its existing still-feasible other answer. The native-first priority is
+an explicit online interpretation, not a retrieved publisher choice among
+incomparable surviving answer sets. The earlier source
+question is not a separately answered publisher ruling. Ordinary single-element
+Secret Ally and native inspection paths continue to use their existing rules.
 
-The focused [public-guard regression](../tests/nexus-residual-ambiguity.test.ts)
-covers the declared implementation boundary and hidden-state independence. It
-does not claim to execute or resolve the counterexample above.
+A resource-exclusive example motivates the joint check: Advanced CHOAM can have
+four ordinary battle forces, no spice, one usable living leader, a projectile,
+Ghola and the one Karama needed to activate its unused cash-in power. Native
+dial3 and Cunning projectile may both be reachable before death by selling
+Ghola for support. After that last usable leader dies, Ghola cannot both be
+sold for support and revive a leader for the projectile. Keeping native dial3
+permits an unarmed plan after cash-in; keeping the projectile alone can permit
+revival with a lower dial. The special-activation Karama is not a second freely
+saleable funding card. The controlled regression must execute the real actions
+and check reachable continuations rather than treating this prose as proof.
+
+[Controlled reconciliation evidence](../tests/nexus-residual-ambiguity.test.ts)
+is separate from [the genuine acquisition/Nexus/battle source](../tests/fixture-residual-cunning.ts)
+and [its runtime cases](../tests/residual-cunning-engine.test.ts).
+Complete combinations and final assurance remain open.
+
+## Focused prototype evidence — 26 October 2026
+
+Frozen17-file131/131, types/lint/build and five engine/GameTable SSR journeys
+pass. Genuine public Basic108/Advanced120-action sources really buy Residual1,
+draw the original Atreides Nexus, ship Richese1 into Arrakeen and answer both
+fields. The actual random death preserves both feasible answers; each battle
+finishes legally. Separate controlled Advanced resource/leader seams execute
+both resource-exclusive priorities and impossible-native ordered re-answers,
+including actual cash-in, Ghola and battle. All45 physical Treachery and12 Nexus
+cards remain. Seven native cases, four controlled engine cases and six rendering
+supplements include four-profile legal participation and existing cancellation
+compatibility. Controlled setup is not original acquisition proof.
+
+Report/logs: `/home/quintine/.local/share/dune/checkpoints/20261026-residual-cunning-proof-v3/`;
+journeys/HTML: adjacent `20261026-residual-cunning-runtime/`.
+No saved-room/D1/server, deployment/restart or recovery operation. No DOM/
+hydration, browser/mobile or clicked-control acceptance; complete combinations,
+full rules and final assurance remain due.

docs/RICHESE_RESIDUAL_POISON_ENGINE_AUDIT.md

@@ -6,6 +6,19 @@ The Advanced Harkonnen exclusion below is superseded by the
 [18 October captive-death composition](#native-captive-death--18-october-2026).
 Earlier timings, test totals and unimplemented-card statements remain historical.
 
+## Answered Cunning follow-up — 26 October 2026
+
+The pre-leader window now remains available after two answered nonleader
+Cunning inspections. Under the 14 October choose-recommended authority, use
+the existing native-first reconciliation after the single actual death:
+preserve an independently possible native answer, then require the extra
+answer to permit the same legal plan. Reopen only required original fields;
+retain private observations and the original spent Nexus. No victim redraw,
+second death/discard or new card payment occurs. Leader commitments and other
+active interactions remain guarded. The priority is a provisional online
+composition, not a publisher tie-break among incompatible surviving sets.
+[Canonical inspection composition](NEXUS_ATREIDES_RULES.md#residual-poison-and-two-inspected-commitments).
+
 ## Evidence and confirmed effect
 
 The publisher card face says **“Play on your opponent before choosing leaders in a battle.”** It then randomly sends one available leader of that faction to the Tanks, specifies **“No spice is collected for it”**, and requires disposal after use. The enlarged physical face was visually read at `/tmp/dune-rules/choam-residual-reading.png`, from the [photograph of the actual components](https://cdn.anyfinder.eu/assets/QsUJtVktEC87xwK08oLlwnKyaozUWfuaLzG0LFEn67ENEEVgNrDGoITy3608Dqe7), linked by the [product gallery](https://www.tabletopfinder.eu/en/boardgame/32692/dune-choam-richese). The photographer's printing/date is unverified; the evidence is the visible publisher text, not retailer commentary. Photograph SHA256: `9c1d3e65fa33489e7675055ed1fc932fefcb79f6053ee365ddee6737ae10b81f`.

docs/RULE_DECISIONS.md

@@ -1,5 +1,18 @@
 # Rule decision index
 
+## Residual Poison after answered Cunning — 26 October 2026
+
+Under the 14 October choose-recommended authority, remove the product refusal
+for two completed nonleader inspections. Resolve the single actual random death
+and discard, then use the existing native-first reconciliation: preserve an
+independently feasible original native answer, test the extra answer jointly,
+and reopen only required original fields. An impossible native answer reopens
+first. Keep private observation history and the original spent Nexus; do not
+redraw the victim or replay its death. This software priority is provisional,
+not a publisher choice among competing surviving commitments. The printed
+pre-leader restriction and other active-interaction/card commitments still apply.
+[Current composition](NEXUS_ATREIDES_RULES.md#residual-poison-and-two-inspected-commitments).
+
 ## Box recovery of a purchased shipment cost — 26 October 2026
 
 Under the 14 October choose-recommended authority, extend the selected Semuta