Compose Harass withdrawal with provisional Stone Burner timing

docs/CURRENT_STATUS.md

@@ -29,6 +29,28 @@ optional skill bands, combinations and public expansion starts remain open.
 Rules implementation continues; comprehensive assurance and administration
 remain deferred until all rules are implemented.
 
+**Harass / Stone Burner interaction — 16 October.** Richese-family Harass now
+uses visibly provisional post-withdrawal physical comparison under the standing
+choose-recommended priority; the earlier source question remains unanswered.
+Same-plan, opposing and Mirror-resolved Stone preserve Traitor precedence,
+original support and mandatory disposal. Active Occupy removes only its
+actual card user's fixed or variable undialed pool, preserving the original
+mandatory Ecaz commitment. Public preflight considers possible fixed withdrawal
+without reading hidden cards. No persisted game field is added.
+
+Affected thirteen-file161/161, types/lint and build pass. Eight same-plan
+policy programs/all four profiles accept24 continuation actions. Two actual
+390px native-control journeys prove Basic winner reversal and Advanced typed
+return/support/leader-death/bounty through retention and collection. No root
+overflow or application/browser error in the corrected host's journeys.
+Original Richese lot and shared-preparation fixture drivers were corrected;
+incidental collection-wallet expectations were removed. Current guide parse,
+policy anchor and33 evidence paths resolve; both topics' five facets stay
+Partial. [Policy and scoped proof](HARASS_WITHDRAW_RUNTIME.md#provisional-stone-burner-timing--16-october-2026).
+Ix/Poison Tooth, same-plan Harass/Reinforcements, Reinforcements/Stone, own
+concealed No-Field Harass and other module gates remain. No human server,
+saved room, D1, deployment or public gate changed; final assurance stays due.
+
 **Ixian Nexus purchased-card interaction wave — 16 October.**
 Purchased-card replacement now composes:
 - successful native BG Karama conversion, after its original counter;

docs/ECAZ_OCCUPY_RULES.md

@@ -249,8 +249,9 @@ Reinforcements uses the card user's own three normal-first reserve counters
 and existing +2 score-only modifier, not ally reserves, extra physical dial
 losses or support. Existing provisional all-revealed-outcome cost/disposal
 is unchanged and remains explicitly not a publisher ruling. Both slots and
-opposing holders work; own same-plan Harass/Reinforcements and Stone/optional
-module guards stay. Basic/unprofiled co-side card battles remain rejected.
+opposing holders work; own same-plan Harass/Reinforcements and Reinforcements
+with Stone/optional modules remain guarded. Basic/unprofiled co-side card
+battles remain rejected.
 
 Native/pure67 cases, relevant284-case batch and27 actual native-program
 cases pass, including all four legal policies. Two natural captured games
@@ -297,8 +298,12 @@ active Occupy, or the **selected lead's own pool only** after prevention.
 Its total dial offset is removed before native typed casualty enumeration.
 Mirror copies use the same comparison and original physical-card retention.
 Public opposing No-Field preflight enumerates possible native pools, never the
-actual secret denomination. Ix Stone/Poison Tooth timing, Harass/Stone and
-genuinely winner-changing typed allocations retain their existing guards.
+actual secret denomination. Ix Stone/Poison Tooth timing and genuinely
+winner-changing typed allocations retain their existing guards.
+Harass/Stone now uses the explicitly
+[provisional post-withdrawal policy](HARASS_WITHDRAW_RUNTIME.md#provisional-stone-burner-timing--16-october-2026):
+remove only the actual card user's undialed pool, never recompute original
+fixed commitment and never inspect concealed opposing cards for preflight.
 Native Ecaz/Moritani Mirror admission is Advanced only; Basic is unchanged.
 
 The affected rule batch passes **363/363**, with types/lint and build passing.

docs/HARASS_WITHDRAW_RUNTIME.md

@@ -1,6 +1,6 @@
 # Harass & Withdraw development prototype
 
-Updated 14 September 2026. This connects the physical card to battle plans,
+Updated 16 October 2026. This connects the physical card to battle plans,
 private inspections, force returns, controls, AI and saved continuation. It does
 not complete the independent three-card variant or open public mode gates.
 
@@ -31,6 +31,34 @@ Planetologist's existing inspection answers remain unchanged. Ecaz's explicit
 instruction to report no weapon/defense is not silently extended to other
 slot substitutions.
 
+## Provisional Stone Burner timing — 16 October 2026
+
+The standing 14 October choose-recommended instruction selects the
+post-withdrawal comparison for the development prototype. The earlier question
+remains unanswered; this is an implementation interpretation, not a new
+publisher ruling or a user answer. The Harass face/designer reveal timing above
+and [Stone's physical undialed-token instruction](STONE_BURNER_ENGINE_AUDIT.md#primary-evidence-and-exact-effect)
+support treating returned reserves as no longer in the battle. A fresh text
+lookup in the supplied Advanced PDF found no named Harass/Stone combined rule.
+
+Normal Stone resolution compares counters left after successful Harass,
+including same-plan and opposing holders and Mirror-copied Stone. A successful
+opposing Traitor cancels the withdrawal; its validated outcome still wins before
+Stone scoring. Allocation choices and original dial/support legality remain
+mandatory. No return, fee, casualty or card disposal executes twice.
+
+Active Occupy returns only the actual card user's pool. Ecaz Harass removes
+the original fixed undialed `floor(E/2)`, leaving the ally variable remainder;
+ally Harass removes variable undialed counters, leaving fixed Ecaz undialed
+forces. Original mandatory `ceil(E/2)` commitment and native ally support stay.
+Canceled Occupy uses its lead's ordinary own pool.
+
+Precommit checks use public configuration and selected lead, never a hidden
+opponent Harass/Stone card. If an opposing Ecaz lead may withdraw its fixed
+remainder, each revealed alternative must have an allocation-invariant winner;
+different alternatives may legitimately have different winners. Actual controls
+label post-withdrawal counts as conditional on no opposing successful Traitor.
+
 ## Connected behavior
 
 Use the existing independent Ecaz card development setup. All three cards enter
@@ -71,11 +99,12 @@ This is a legal strategy path, not strength calibration.
   Leader Skills, Tech Tokens, Stronghold Cards and Discoveries. This includes
   the printed own-Homeworld prohibition without claiming other Homeworld
   battles are already implemented for this card.
-- Richese card-family configurations remain gated because Stone Burner may
-  compare original or post-withdrawal undialed forces, which can reverse the
-  winner. A user question has been sent; no answer is assumed. The guard uses
-  public configuration, never Stone Burner's hidden custody. CHOAM without
-  Richese remains eligible. This is a development boundary, not a printed ban.
+- Richese card-family configurations now admit Harass under the
+  [provisional post-withdrawal policy](#provisional-stone-burner-timing--16-october-2026).
+  The ordinary invariant-allocation guard and separate Ix/Poison Tooth timing
+  boundary remain. No public expansion start or played-game retrofit is added.
+  A card user's own still-concealed No-Field remains guarded until its original
+  reveal; this wave does not certify Harass on a concealed native marker.
 - Co-present armies remain guarded in Basic or without the supported Advanced
   Occupy profile. The [combined-army follow-up](ECAZ_OCCUPY_RULES.md#independent-cards-with-combined-armies--2-october-2026)
   returns only actual card-user forces: original fixed Ecaz commitment or the
@@ -87,7 +116,36 @@ This is a legal strategy path, not strength calibration.
   unresolved. Both prototypes retain their separate provisional cost and
   outcome interpretations.
 
-## Verification and preservation
+## Scoped interaction proof — 16 October 2026
+
+- The affected thirteen-file offline union passes **161/161**, including
+  Stone/Harass pure and native battle cases, original fixed/variable Occupy,
+  typed/sector returns, Mirror retention and Traitor cancellation. Types/lint
+  and production build pass; build retains module-register, large-chunk and
+  Unknown-route warnings.
+- Eight genuine Richese/classic Basic/Advanced same-plan policy programs
+  exercised all four profiles and24 accepted continuation actions. This is
+  minimal legal participation, not strategic calibration.
+- Two actual styled390px table journeys used original native controls from
+  before plan commitment through winner retention and collection. Basic
+  Harass dial2 returns3, leaving0 versus Stone dial4's1: defender wins, the
+  two committed attackers reach Tanks, and Harass discards once. Advanced
+  dial2/support1 exposes the actual typed choice; selecting one elite
+  commitment returns three ordinary counters, charges support once30→29,
+  kills both original leaders and awards bounty11. Stone winner keeps its
+  physical card and the original battle/decision clears. Conditional revealed
+  counts and the provisional warning are visible; no root overflow or
+  application/browser error occurred in the corrected host's journeys.
+- Native fixtures exposed two driver assumptions: a Richese Bidding lot can
+  exist without an ordinary row, and shared preparation still needs its actual
+  ready actions. Both now follow native controls. Bounty is compared between
+  paired modes rather than pinning a wallet before automatic collection.
+- Current reference parses;33 evidence paths across both topics resolve and
+  all ten checklist facets remain Partial. Runtime artifacts stay outside Git.
+  No human server, saved room, D1, deployment or public start changed. No new
+  broad, HTTP, recovery/privacy/custody assurance campaign ran.
+
+## Historical verification and preservation — 14 September 2026
 
 Focused rules, controls, AI and authenticated recovery suites record the exact
 supported paths. Fixtures explicitly distinguish genuine variant setup from

docs/IMPLEMENTATION_STATUS.md

@@ -1,5 +1,33 @@
 # Dune implementation status
 
+## 16 October 2026 — Provisional post-Harass Stone comparison
+
+Removed only the public Richese-family Harass guard. Under standing
+choose-recommended, Stone provisionally compares undialed counters remaining
+after successful withdrawal; the earlier question is still unanswered, not
+a new publisher ruling. Same-plan/opposing/Mirror Stone and active fixed or
+variable Occupy preserve original commitments, support, Traitor cancellation,
+mandatory Harass disposal and native winner retention. Public precommit checks
+possible fixed Ecaz withdrawal without hidden-card reads; no game field added.
+
+Affected thirteen-file **161/161**, types/lint and build pass (module-register,
+large-chunk/Unknown-route warnings). Eight original same-plan policy programs
+exercise all four profiles and24 accepted continuation actions. Two styled390px
+actual native-control journeys pass: Basic0-vs1 winner reversal with3 returned/
+2 Tanks; Advanced typed one-elite commitment returns3 ordinary, costs one
+support, kills both leaders and awards11 bounty. Winner retention clears the
+original battle/decision and reaches collection. Conditional counts and warning
+are visible, without root overflow or journey application/browser errors.
+
+Repaired two real fixture driver assumptions, rather than suppressing native
+windows: Richese Bidding without a normal row, and shared preparation ready
+actions. Bounty assertions compare paired modes instead of incidental
+pre-collection wallet values. Current reference parse/policy anchor and33
+topic evidence paths resolve; all ten facets stay Partial. Other module and
+concealed-marker/relative-timing gates remain. No human server, D1, saved room,
+deployment/public start or broad/HTTP/recovery assurance campaign changed.
+[Interpretation and bounded proof](HARASS_WITHDRAW_RUNTIME.md#provisional-stone-burner-timing--16-october-2026).
+
 ## 16 October 2026 — Direct Richese special purchase and paid-bid funding
 
 Connected actual Advanced special-Karama cache acquisition during Bidding

docs/RULE_DECISIONS.md

@@ -759,7 +759,7 @@ These are unresolved in the cited records. Do not infer an answer from elapsed t
 | Boundary | Still unresolved | Existing record |
 | --- | --- | --- |
 | Reinforcements cost | The user question still asks whether to keep the card disabled, always transfer three reserve forces on every outcome, or waive only a sole traitor-call winner's cost; no answer is assumed. The bounded classic and Ecaz/Moritani prototype provisionally charges on all revealed outcomes, chooses normal reserves before elite and counts the transfer as battle losses. Those are product interpretations, not a ruling. Same-plan Harass/Stone Burner remain gated; opposing Harass is supported. Eligibility never depends on concealed matching Traitors. | [Source cost review](ECAZ_TREACHERY_RULES.md#14-september-reinforcements-cost-review) · [Bounded runtime](REINFORCEMENTS_RUNTIME.md) |
-| Harass / Stone Burner | A user question has been sent: keep the combination gated or compare forces remaining after withdrawal. No answer is assumed. The Richese card-family configuration is guarded publicly; hidden Stone Burner custody never controls eligibility. Ambiguous physical allocations and other optional modules remain unfinished. | [Current boundaries](HARASS_WITHDRAW_RUNTIME.md#current-boundaries) |
+| Harass / Stone Burner | The earlier question (keep gated or compare after withdrawal) remains unanswered. Under the standing 14 October choose-recommended instruction, the development prototype now provisionally compares undialed counters remaining after successful withdrawal. Opposing Traitor cancels the return; original fixed Occupy commitment stays. Public preflight considers possible fixed Ecaz withdrawal without reading hidden custody. Allocation ambiguity, Ix/Poison Tooth and other module boundaries remain. This is an implementation interpretation, not a publisher ruling or a user answer. | [Provisional timing](HARASS_WITHDRAW_RUNTIME.md#provisional-stone-burner-timing--16-october-2026) |
 | Recruits late accounting and rates | The earlier one/two-further-free question remains unanswered. The content-first prototype now preserves paid spice, deducts recorded actual free usage from the doubled rate and all returns from the total cap: two-free/one-paid Atreides can take two more free. This is visibly provisional, not a numerical user ruling. Unknown ledgers, pending repricing, late rate changes and same-turn replay remain guarded. | [Source alternatives](RECRUITS_RULES.md), [provisional runtime](RECRUITS_RUNTIME.md) |
 | Sapho remaining timing | First versus unspent Advanced Guild priority, partly completed combined turns, cyclic auction duration and later battle timing stay guarded. The existing pre-plan opportunity supports [early aggressor](SAPHO_AGGRESSOR.md). Prior questions remain unanswered. | [Source audit](JUICE_OF_SAPHO_SOURCE_UPDATE.md), [battle review](JUICE_OF_SAPHO_BATTLE_REVIEW.md) |
 | Semuta Drug | Full-hand exchange is user-approved; neutral all-seat acknowledgements remain the explicit application policy. Other discard producers, nested continuation coverage and full-game acceptance remain unfinished. | [Source update and selected exchange](SEMUTA_SOURCE_UPDATE_20260907.md), [privacy review](SEMUTA_PRIVACY_REVIEW.md) |

docs/STONE_BURNER_ENGINE_AUDIT.md

@@ -16,6 +16,24 @@ Audit: 2026-09-06. Scope: the canonical weapon, its revealed-plan choice and phy
 
 The complete integrated validation checkpoint is recorded in [IMPLEMENTATION_STATUS.md](IMPLEMENTATION_STATUS.md).
 
+## Harass timing follow-up — 16 October 2026
+
+The independent Ecaz-card variant now uses the explicitly
+[provisional post-withdrawal comparison](HARASS_WITHDRAW_RUNTIME.md#provisional-stone-burner-timing--16-october-2026).
+Returned reserves are outside Stone's undialed pool; same-plan, opposing and
+Mirror-resolved Stone share that rule. Opposing successful Traitor cancels the
+return before comparison, with normal Traitor outcome precedence intact.
+Active Occupy removes only the actual card user's fixed or variable undialed
+contribution and preserves the original mandatory Ecaz dial. Public preflight
+checks possible fixed Ecaz withdrawal without inspecting hidden cards.
+
+The earlier question remains unanswered. This is an interpretation selected
+under the standing choose-recommended priority, not newly retrieved publisher
+authority. Ix/Poison Tooth, Reinforcements/Stone, own concealed No-Field Harass
+and other module boundaries remain separate. The 6 September evidence above
+is historical; the current checkpoint has its own bounded proof.
+
+
 ## Primary evidence and exact effect
 
 The physical publisher face was visually read at `/tmp/dune-rules/choam-stone-reading.png`, enlarged from the [component photograph](https://cdn.anyfinder.eu/assets/QsUJtVktEC87xwK08oLlwnKyaozUWfuaLzG0LFEn67ENEEVgNrDGoITy3608Dqe7) linked by the [product gallery](https://www.tabletopfinder.eu/en/boardgame/32692/dune-choam-richese). Photograph provenance/hash are recorded in `RICHESE_ACQUISITION_RULES.md`. The visible publisher wording is the evidence; uploader printing/date remains unverified.