Apply ruled Grumman return and Cunning placement

docs/CURRENT_STATUS.md

@@ -1,6 +1,6 @@
 # Current development status
 
-Updated 13 October 2026. **The full twelve-faction goal is unfinished. Basic
+Updated 14 October 2026. **The full twelve-faction goal is unfinished. Basic
 is playable and the six classic factions have a user-authorized Advanced preview.
 Expansion starts and full rules/publication acceptance remain gated.**
 
@@ -29,6 +29,27 @@ optional skill bands, combinations and public expansion starts remain open.
 Rules implementation continues; comprehensive assurance and administration
 remain deferred until all rules are implemented.
 
+**Ruled Grumman removal and Cunning addition — 14 October.**
+The user selected supply-only Cunning, HMS exclusion, preserved Grumman
+addition prerequisite and unrevealed return to hidden supply. Native removal
+now rotates supply IDs and pays4 once without revealing the face or spending
+Mentat placement. High-Grumman Cunning consumes one actual Nexus, binds its
+phase7 source/prerequisite and permits a static Arrakis destination only when
+an ordinary stacked addition was already eligible. No new cancellation window.
+Genuine Basic/Advanced before/after programs preserve all original stock;
+later real Guild entry at Polar Sink recognizes the Cunning placement, and its
+later Grumman removal retires only that live location. No prerequisite means
+no Cunning spend or reward. All four existing policies apply legal choices.
+Actual390px return and Red Chasm Cunning addition each pay12→16, preserve
+Mentat usage1 and close the original choice. Browser errors empty, no root
+overflow; `/tmp/dune-ruled-grumman-ui-proof.json` records local proof.
+[Cunning rulings](NEXUS_MORITANI_RULES.md#user-rulings--14-october-2026)
+and [removal ruling](GRUMMAN_STACKED_TERROR_RULES.md#user-ruling--14-october-2026)
+are interpretations selected by the user, not new publisher answers.
+No complete-mode, broad-assurance or deployed acceptance claim follows.
+Final affected14-file union92/92, types/lint and app build pass with the
+existing module-registration, chunk-size and route-classification warnings.
+
 **Documented Skills CLI validation corrected — 13 October.**
 The actual CLI still rejected `guild-betrayal --leader-skills` with
 `--leader-skills requires --profile semuta`, despite the already-connected

docs/GRUMMAN_STACKED_TERROR_RULES.md

@@ -1,6 +1,39 @@
 # Grumman Collection and stacked Terror
 
-Source audit, 10 September 2026. This supplements [HOMEWORLD_COLLECTION_RULES.md](HOMEWORLD_COLLECTION_RULES.md). It does not certify runtime integration or change release gates. The existing user question about unrevealed removal custody remains pending; this audit asks no duplicate question.
+Source audit, 10 September 2026. This supplements [HOMEWORLD_COLLECTION_RULES.md](HOMEWORLD_COLLECTION_RULES.md). It does not certify runtime integration or change release gates. The formerly pending removal-custody question is resolved by the user ruling below, not a new publisher clarification.
+
+## User ruling — 14 October 2026
+
+An unrevealed Grumman removal returns the selected placed Terror token to
+hidden supply without revealing its face. Reuse original hidden-supply ID
+rotation so its former public ID cannot track the returned face. Other placed
+tokens and all six physical faces remain intact.
+
+One completed add-or-remove operation earns four spice, once per Collection;
+declining earns none. Native Mentat placement usage remains independent.
+Available, spent, revealed Extortion and Atomics Aftermath are not placed
+Terror tokens eligible for this removal.
+The user separately selected the
+[Cunning underlying-addition prerequisite](NEXUS_MORITANI_RULES.md#user-rulings--14-october-2026).
+These are selected interpretations, not publisher rulings or mode certification.
+
+## Runtime follow-through — 14 October 2026
+
+The live Grumman quote now separately offers placed-token return even when no
+available supply token exists for addition. The original hidden return rotates
+only available-supply identities, preserves other placements/spent faces and
+leaves native Mentat use unchanged. Historical completion retains the former
+placed ID/location without treating that ID as live supply.
+
+The event-bound add/return selector, owner-only faces and shared legal policy
+connect to the original Collection frame. Current high population, target
+custody and one-use checks precede random supply rotation and four-spice credit.
+Actual390px return pays12→16, clears the placement and keeps the returned face
+hidden/reusable; new native regressions prove its later ordinary Mentat reuse.
+[Native return evidence](../tests/grumman-supply-return.test.ts) and
+[Cunning source/entry/return](../tests/grumman-cunning-runtime.test.ts)
+cover the ruled paths. No complete-mode or deployed acceptance is claimed.
+
 
 ## Evidence and its limits
 
@@ -27,13 +60,18 @@ The chosen token must remain bound to the original entry through Enemy of My Ene
 
 Do not describe that serializer as printed priority. Revalidate current native population when the Grumman action is accepted. An allowed intervening effect that changes population, token custody or the phase must use the same continuation checks; a future noncommuting interaction would require review. Ecaz settlement cannot consume Grumman’s opportunity, and Grumman cannot overwrite an unresolved allocation. Its award is not desert collection and must not create a shared Ecaz allocation or Giedi collection trigger.
 
-## Unresolved removal custody
+## Source ambiguity and selected removal custody
 
 Removal from the board is not revelation. The revelation disposal rule does not establish that an unrevealed Grumman removal is permanently spent. Conversely, other effects’ express return-to-supply instructions do not prove this removal returns to hidden supply. Neither result was authenticated by this audit.
 
-Keep that operation guarded pending the existing question. Do not reveal its face, call the revelation handler, rotate it into reusable supply, or credit four spice before its destination is resolved. Addition can be implemented independently using an actual available token and a stronghold already containing Terror. It does not authorize Homeworlds, the Hidden Mobile Stronghold, an invented token or movement from another stack.
+The original guard was required while custody was unresolved. The selected
+user interpretation above replaces it with a hidden-supply return and four-
+spice award after current population, placed custody and unused Collection
+opportunity are checked. Do not reveal the face or invoke the revelation
+handler. Addition remains an independent supply placement, with its original
+prerequisite unless modified through the selected Cunning composition.
 
-## Concrete code review findings
+## Original code review findings (historical)
 
 At the inspected checkpoint, `openTerrorEntry` in [engine.ts](../game/engine.ts) selects the first placed token at the destination. Stacking requires an owner-visible candidate choice, with hidden faces excluded from other seats, and a durable selected identity afterward.
 

docs/HOMEWORLD_COLLECTION_RULES.md

@@ -34,9 +34,23 @@ The singular phase-scoped opportunity supports one selected operation and one aw
 
 For addition, select one available physical Terror token and a permitted stronghold already holding a placed token. The card supplies an exception to ordinary Terrorize's empty-destination requirement; it does not authorize a new token, a second ordinary Mentat placement, relocation from another stronghold, Homeworld placement or use of the Hidden Mobile Stronghold. Storm alone does not prevent ordinary Terror placement. [GF9 E3, pp.5,16](https://www.gf9games.com/dune/wp-content/uploads/EcazMoritani-Rulebook-LOWRES.pdf#page=5).
 
-For removal, select one actual placed token. A spent token, the separate Atomics Aftermath marker, an available supply token or a revealed Extortion record is not a Terror token on the board. The face says removal from the board; it does not expressly name its next custody zone. Returning it to hidden supply is a plausible composition, while ordinary **revelation** expressly removes tokens from the game. Do not claim the latter as authority to permanently spend an unrevealed removal, or call `revealTerror` merely to clear its location. The removal destination remains a source boundary for the coordinator; no new question was sent by this audit.
+The [selected Cunning composition](NEXUS_MORITANI_RULES.md#user-rulings--14-october-2026)
+preserves that ordinary addition prerequisite: an eligible stacked addition
+must already exist before Cunning broadens its selected destination to static
+Arrakis. It never grants relocation, a Homeworld or HMS destination.
 
-Token change and four-spice credit must be one accepted transaction after checking current high population, valid custody, phase and unused opportunity. Reject before mutation or randomness if any check fails. Preserve the six physical identities and every other placed token. If returning a token to hidden supply is adopted from sufficient authority, use the established identity-rotation contract so a previously known face cannot be followed through a persistent public ID.
+For removal, select one actual placed token. A spent token, Atomics Aftermath,
+an available supply token or a revealed Extortion record is not eligible.
+The physical face does not name the next custody zone; the
+[14 October user ruling](GRUMMAN_STACKED_TERROR_RULES.md#user-ruling--14-october-2026)
+selects hidden supply without revelation. Do not call `revealTerror` or
+permanently retire the token to implement this removal.
+
+Token change and four-spice credit are one accepted transaction after current
+high population, placed custody, phase and unused Collection opportunity are
+checked. Reject before mutation or randomness. Preserve all six physical faces,
+other placed tokens and native Mentat usage. Rotate hidden-supply IDs using the
+original return contract so a former public ID cannot track the returned face.
 
 Stacking is a genuine new registry condition. Remove only the global one-token-per-location assumption; retain unique physical identity, exactly one location/status per token and valid stronghold locations. Ordinary Mentat placement still requires an empty destination. Never overwrite an existing token merely because both share a location.
 

docs/IMPLEMENTATION_STATUS.md

@@ -1,5 +1,56 @@
 # Dune implementation status
 
+## 14 October 2026 — ruled Grumman hidden return and Cunning addition
+
+Four user decisions resolve the earlier Moritani boundaries: Cunning enhances
+supply placement only; HMS stays excluded; Grumman Cunning preserves an actual
+ordinary stacked-addition prerequisite; an unrevealed removal returns to
+rotated hidden supply. All remain user interpretations, not publisher rulings.
+
+BEFORE genuine Basic setups without/with Nexus reached turn2 Collection
+after63/69 original actions, native population14 and a real first-Mentat
+Robbery placement in Arrakeen. Removal rejected the custody-zone guard without
+mutation. Native Grumman Cunning to Red Chasm likewise rejected the ordinary
+stronghold-only destination while holding the actual Moritani card.
+
+AFTER removal uses original `returnTerror` and hidden ID rotation, pays4 once,
+preserves the six faces/other placements and leaves `placementTurn` independent.
+The old public ID/source location stays historical, not live supply identity.
+High-Grumman Cunning reuses physical supply validation and adds a source-
+discriminated phase7 receipt with original Grumman event and ordinary
+prerequisite. Its atomic completion consumes the actual Nexus and pays4;
+Mentat receipts/events and original cancellation remain unchanged.
+The source bridge validates the real completed current Collection frame and
+its historical location authority after later turns. No extra Karama window.
+
+Native Basic/Advanced addition, failed selection/replay, prerequisite loss,
+four existing legal policies, a later real one-force Guild Polar shipment/
+Terror entry, and subsequent unrevealed Cunning-token return are exercised.
+The original other board token remains, and only the selected live Cunning
+authorization retires on return. Native removal permits later genuine Mentat
+redeployment of the same physical face under a new hidden supply ID.
+Initial new behavior tests14/14 pass. A child receipt-mutation test used an
+unnarrowed type-query union; explicit Grumman discriminant types repair it
+without production change. One old persisted removal-veto assertion is removed;
+its independent SQL decline behavior remains.
+
+Actual390px `GameTable` returns Robbery from Arrakeen, pays12→16, rotates
+all six available IDs and leaves Mentat usage1. Separate actual Cunning
+checkbox/destination controls place an available Sneak Attack at Red Chasm,
+spend the Moritani card, pay12→16 and close the original choice with a phase7
+Grumman source/prerequisite receipt. Browser errors empty, no root overflow.
+`/tmp/dune-ruled-grumman-ui-proof.json` records local source/action results.
+Owned tab/host/scaffold removed. No saved room, production server or mode
+gate changed; comprehensive assurance remains deferred.
+
+Final frozen14-file union92/92 and `npm run check:quick` pass. App build
+passes with existing module-registration, large-chunk and unknown-route
+classification warnings. The first union used a nonexistent `terror-location`
+filename fragment and ran no tests; its corrected selection first had62/63
+pass with the obsolete persisted removal-veto failure, then passes after that
+guard assertion is deleted. Independent persisted decline coverage remains.
+No complete-mode, broad-suite or deployed acceptance claim follows.
+
 ## 13 October 2026 — documented Skills CLI admission repaired
 
 Actual `tools/start-prototype.ts --profile guild-betrayal --leader-skills`

docs/NEXUS_CARD_RULES.md

@@ -2,6 +2,20 @@
 
 Original source audit, 10 September 2026, with dated bounded runtime follow-ups below. This document establishes the printed component inventory, source protocol and implementation boundaries; none lifts expansion release gates. The ordinary worm-triggered alliance Nexus already in the engine is distinct from this optional card module.
 
+## Moritani Cunning and Grumman user cutover — 14 October 2026
+
+The user selected supply-only Cunning, continued HMS exclusion, an ordinary
+eligible Grumman addition prerequisite, and unrevealed Grumman removal to
+rotated hidden supply. The connected Collection controls now apply that
+separate source without consuming the native Mentat opportunity.
+The phase7 receipt binds the actual Grumman event and original ordinary
+prerequisite; no eligible stacked-addition source means no Cunning spend.
+Physical Nexus disposal, one four-spice award, later static-territory Terror
+entry and hidden return use their original contracts.
+[Selected interpretations and runtime](NEXUS_MORITANI_RULES.md#user-rulings--14-october-2026);
+[removal custody](GRUMMAN_STACKED_TERROR_RULES.md#user-ruling--14-october-2026).
+No publisher ruling, new cancellation window or complete-mode gate is claimed.
+
 ## Classic Nexus with normal Banker income — 13 October 2026
 
 Fresh `banker-income --nexus-cards` now composes the existing deferred normal
@@ -572,10 +586,11 @@ Advanced Harkonnen remains excluded.
 Moritani preserves original Advanced skill-first assassination, normal-Traitor
 forfeiture for the rest of the game, original post-loss printed bounty and one
 actual private Mentat replacement. Basic does not gain that Advanced power.
-Cunning remains an earned Mentat supply placement into a static Arrakis
-territory/stack, not enhanced relocation/HMS/Grumman; the earlier material
-question remains unanswered. Native cancellation and later ordinary relocation
-retain their original timing and physical custody.
+Cunning remains supply-only and excludes HMS/Homeworld destinations under the
+14 October user choices. Native Mentat placement retains its original timing
+and cancellation; the separate high-Grumman source now admits Cunning only
+after an ordinary stacked addition is eligible. It creates no opportunity and
+does not consume Mentat placement. Ordinary relocation remains unchanged.
 
 Ordinary skill support/rescue, bank-held subsidy/defenses/income, card cleanup
 and mandatory original-winner Tech reuse existing handlers. Mandatory Advanced

docs/NEXUS_MORITANI_RULES.md

@@ -10,6 +10,51 @@ The [GF9 Ecaz & Moritani rulebook](https://www.gf9games.com/dune/wp-content/uplo
 
 The [Grumman component photograph](https://boardgamegeek.com/image/7767034/dune-ecaz-and-moritani) supplies its separate high-population Collection addition/removal and four-spice award. Its wording and unresolved removal custody are recorded in the linked Grumman audit. Bounded fresh publisher/designer searches found no additional authenticated clarification of Cunning relocation, Hidden Mobile Stronghold placement, or Cunning combined with Grumman. Search results from community discussions were not adopted as rulings.
 
+## User rulings — 14 October 2026
+
+The user selected **supply placement only**, not enhanced relocation, and
+**keep the Hidden Mobile Stronghold excluded**. Ordinary relocation retains
+its native destinations; Homeworlds remain excluded from Terror placement.
+
+For high-Grumman Collection addition, **preserve the prerequisite**: there
+must already be an eligible ordinary supply addition to a stronghold holding
+Terror. Cunning may then broaden the actual selected destination to static
+Arrakis. It does not create an underlying opportunity when none exists.
+The selected physical supply token, current high population, one Collection
+operation/four-spice award and separate Mentat allowance remain required.
+The native Grumman operation is immediate; no new Karama window is introduced.
+
+These are recorded user interpretations, not publisher clarifications.
+Unrevealed Grumman removal independently
+[returns to hidden supply](GRUMMAN_STACKED_TERROR_RULES.md#user-ruling--14-october-2026).
+Current runtime evidence remains in the dashboard; no complete-mode claim
+follows from resolving these source questions.
+
+## Runtime follow-through — 14 October 2026
+
+The Collection controls use the actual high-Grumman frame and current ordinary
+addition quote before offering Cunning. An accepted static-destination supply
+placement spends the singleton Nexus, pays four spice and completes that one
+Grumman frame atomically. It does not open a new Karama window or consume the
+separate native Mentat allowance.
+
+The source-discriminated receipt records `grumman`, phase7, the original
+Collection event and an eligible ordinary prerequisite. Original Mentat
+receipts/events remain unchanged. Existing live/historical location authority
+permits a later real entry at the Cunning territory and retires when that
+selected token returns, while retaining its historical receipt.
+
+Genuine native fixtures provide prior ordinary placement and an actual worm/
+Nexus draw without assigned runtime forces, wallets or hands. New evidence:
+[native Cunning source/entry/return](../tests/grumman-cunning-runtime.test.ts),
+[pure receipt/placement boundaries](../tests/nexus-moritani-grumman.test.ts),
+[hidden return and later Mentat reuse](../tests/grumman-supply-return.test.ts).
+Actual390px Collection controls separately prove return and Red Chasm
+Cunning addition for12→16, with native Mentat usage1 unchanged.
+Local proof is `/tmp/dune-ruled-grumman-ui-proof.json`; no saved room or
+production acceptance is claimed.
+
+
 ## Resolved effect and ordinary composition
 
 1. **One earned placement.** A native unallied Moritani holder can spend this card when making an otherwise earned placement. Ordinary Mentat supply placement is a concrete supported source in Basic and Advanced. The selected physical token must actually be available; no removed or front-of-shield Extortion token becomes supply. Spending the card neither creates a seventh token nor creates another Mentat action.
@@ -21,7 +66,7 @@ The [Grumman component photograph](https://boardgamegeek.com/image/7767034/dune-
 
 Ordinary later relocation can move a Cunning-placed token out to a native-legal destination. Its unusual original location does not change its placed custody status or grant an enlarged destination for the later move. Returning a token to hidden supply ends that placement's custody interval; redeployment requires its own authorization and the existing supply-ID rotation.
 
-## Material boundaries
+## Source ambiguities resolved by the selected interpretations
 
 **Relocation is not expressly placement.** The native rule deliberately offers placing a token or moving one, whereas Cunning names placement. Treating the card as a blanket modifier on the current combined place/move UI would silently include a second source category. No inspected primary clarification establishes that extension. Preserve ordinary relocation; do not present enhanced relocation as a settled printed right.
 
@@ -29,15 +74,18 @@ Ordinary later relocation can move a Cunning-placed token out to a native-legal
 
 **Grumman is a separate earned placement source.** Cunning has no Mentat-only wording, so a reusable source contract should represent Collection addition as well. A high-Grumman addition from supply is naturally a placement. The unresolved interaction is its destination condition: does Cunning replace Grumman's requirement for a stronghold already containing Terror, allowing an empty territory, or does that requirement establish an eligible addition before Cunning modifies the destination? The former follows a broad destination override; the latter follows an underlying-opportunity prerequisite. No inspected source explicitly chooses between them. Do not silently gate all Grumman use by inventing a Mentat restriction, or describe either destination composition as a publisher ruling. An enhanced Collection integration also needs to preserve its own once-only outcome and four-spice transaction, separate from Mentat usage and its cancellation source.
 
-The coordinator has now asked one combined question about enhanced relocation, the mobile stronghold and Grumman; its answer is pending. The already pending question about unrevealed Grumman removal custody remains unchanged. Cunning places a token; it does not answer removal custody. Other incomplete Terror effects and combined reaction boundaries remain independent release limitations.
+The combined interpretation question is resolved by the user rulings above.
+The separate unrevealed Grumman removal question is also resolved: return to
+hidden supply without revelation. These decisions do not establish a publisher
+answer to the original ambiguities or certify other Terror combinations.
 
-## Smallest complete integration for the resolved source
+## Original source-audit integration plan (historical)
 
 Implement a full ordinary Mentat supply-placement path over static Arrakis territories, with saved cancellation and all supported later entry effects. Keep the unresolved source/destination combinations explicit; a destination-only UI patch is insufficient.
 
 Use a separate Cunning placement quote and receipt instead of widening ordinary [placeTerror](../game/moritani-terror.ts). Suggested original evidence: version, event, owner, turn, phase, source kind and source event, physical token, original custody, destination, roster, and original Terror-state commitment. Keep pending/completed/canceled stage evidence outside mutable current token custody. A completed placement authorizes the corresponding non-stronghold custody interval; a historical receipt alone must not authorize arbitrary later relocation, a returned token's new ID, or another token.
 
-Current adapters requiring coordinated review:
+Adapters identified at the original source-audit checkpoint (not current absence claims):
 
 - [grumman-collection.ts](../game/grumman-collection.ts) validates every placed token against the five ordinary strongholds even when merely quoting unrelated Collection choices. That registry validation must accept independently authorized Cunning custody without widening Grumman's ordinary addition quote.
 - [terror-entry-receipt.ts](../game/terror-entry-receipt.ts) and [moritani-alliance-cancellation.ts](../game/moritani-alliance-cancellation.ts) restrict entry territories to those same five locations. Broaden intrinsic territory validity and separately prove the live token's authorized location. Preserve candidate and selected-token signatures through all children.

docs/RULE_DECISIONS.md

@@ -1,6 +1,27 @@
 # Rule decision index
 
-Updated 13 October 2026. This is the authoritative navigation index for existing decisions, not a replacement rulebook or a new ruling. Detailed linked contracts retain their source citations and exact supported boundaries. Runtime follow-ups supersede historical absence claims; passing tests establish software behavior, not publisher authority.
+Updated 14 October 2026. This is the authoritative navigation index for existing decisions, not a replacement rulebook or a new ruling. Detailed linked contracts retain their source citations and exact supported boundaries. Runtime follow-ups supersede historical absence claims; passing tests establish software behavior, not publisher authority.
+
+## User decisions — 14 October 2026
+
+- **Moritani Cunning / relocation:** supply placement only. Ordinary relocation
+  remains available, but Cunning does not broaden its destinations.
+- **Moritani Cunning / HMS:** keep the Hidden Mobile Stronghold itself excluded.
+  Printed static Arrakis territories remain within the destination grant;
+  Homeworlds remain excluded.
+- **Moritani Cunning / Grumman addition:** preserve the ordinary prerequisite.
+  An actual high-Grumman supply addition must first be available at an eligible
+  ordinary stronghold already containing Terror; Cunning may then broaden the
+  selected destination. It creates no underlying placement opportunity.
+  [Selected Cunning contract](NEXUS_MORITANI_RULES.md#user-rulings--14-october-2026).
+- **Unrevealed Grumman removal:** return the selected placed token to hidden
+  supply without revealing its face, using original hidden-supply ID rotation.
+  Keep one operation and one four-spice award per Collection, separate from
+  native Mentat placement usage.
+  [Removal ruling](GRUMMAN_STACKED_TERROR_RULES.md#user-ruling--14-october-2026).
+
+These are user-selected interpretations, not newly found publisher rulings.
+No public module/faction or complete-mode gate is opened.
 
 ## User decisions — 13 October 2026