Enable native Fremen Cunning with original Nexus components

docs/CURRENT_STATUS.md

@@ -29,6 +29,20 @@ optional skill bands, combinations and public expansion starts remain open.
 Rules implementation continues; comprehensive assurance and administration
 remain deferred until all rules are implemented.
 
+**Fremen Cunning / original components — 11 October.** Classic Nexus games
+with original Tech Tokens and/or Advanced Stronghold Cards now receive the same
+empty-worm native Cunning offer as Nexus alone. The isolated software guard is
+removed; physical card/occurrence, provisional Karama response and one post-Nexus
+remote ride remain original. Dynamic destinations, Great Maker, Skills,
+Homeworlds, Discovery and expansion factions/decks stay separate.
+Types/lint and 41 affected cases pass. Nine runtime scenarios cover the four
+legal component configurations, four legal bots and printed Karama cancellation.
+Real GameTable at 390px spends Cunning and moves two Wind Pass14 counters to
+Polar Sink0; reserves8/spice3 and original component custody remain unchanged.
+A labelled QA control advances the original post-Nexus suffix between real
+spend and ride controls. No saved store or deployed game was targeted. See
+[the native contract](NEXUS_FREMEN_RULES.md#original-tech-and-strongholds--11-october-2026).
+
 **Semuta / native Intrusion — 11 October.** Final Ornithopter movement now
 offers the retired card before the original Bene Gesserit Intrusion choice.
 Forces and move counters stay committed; claim or decline cannot move twice or

docs/IMPLEMENTATION_STATUS.md

@@ -1,5 +1,36 @@
 # Dune implementation status
 
+## 11 October 2026 — native Fremen Cunning with original Tech/Strongholds
+
+The classic original-component Nexus envelope already permits Tech Tokens3+
+and Advanced Stronghold Cards2+, independently or together. `beginWorm` still
+suppressed native Cunning whenever either component was present. Removing that
+software guard preserves all existing occurrence/card/source/arrival processing
+and leaves other module/faction gates unchanged. No new dynamic destination,
+Great Maker or Tleilaxu revival ruling is inferred.
+
+The regression fails before and passes after the guard removal. Its genuine
+setup and first-turn progression establish original Tech and Stronghold owners;
+only conserved deck/card order and two reserve counters are staged at the actual
+turn-two Spice Blow. It checks the public opportunity in a paired no-card state,
+one physical card spend, exact remote movement, original wallet/reserves and
+component custody, and rejection of a retired ride event.
+
+TypeScript/lint and 41/41 affected cases pass. Nine isolated runtime scenarios
+cover Basic Tech, Advanced Tech, Advanced Strongholds and both, all four legal
+AI profiles, and printed Karama cancellation retaining the remote source.
+At 390px, real GameTable shows Spend Fremen Cunning, then the original typed
+desert/destination controls. Two Wind Pass14 counters reach Polar Sink0 while
+reserves8/spice3 and original component custody remain unchanged; no horizontal
+overflow. A labelled QA button runs the existing post-Nexus continuation policy
+between the production spend and ride controls. Completed local notices were
+dismissed explicitly; no production save, room or credential was used.
+
+Temporary scripts/server/tab were removed or closed. This is local changed-path
+proof, not full games, all optional combinations, recovery or deployed acceptance.
+Contracts: [native Cunning](NEXUS_FREMEN_RULES.md),
+[original component composition](NEXUS_CARD_RULES.md#classic-tech-and-stronghold-composition--4-october-2026).
+
 ## 11 October 2026 — Semuta before original Bene Gesserit Intrusion
 
 Final Ornithopter movement already commits forces, counters and a typed

docs/NEXUS_CARD_RULES.md

@@ -1067,6 +1067,15 @@ CHOAM winner inspection then excludes all actually played opposing cards,
 including a retained one. Card spend, casualties, income and cleanup remain
 single original events. Ordinary city Collection is separate from battle costs.
 
+**11 October — native Fremen Cunning.** The original classic Tech/Stronghold
+envelope now offers the same empty-worm native Cunning as Nexus alone.
+Original card/occurrence and post-Nexus riding remain; a completed remote ride
+does not spend normal movement or alter Tech/Stronghold ownership or income.
+Nine bounded runtime scenarios and real 390px spend/typed-ride controls prove
+the changed path. Great Maker, dynamic destinations, Skills/Homeworld/Discovery
+and unresolved protection remain separate. See
+[the current native contract](NEXUS_FREMEN_RULES.md#original-tech-and-strongholds--11-october-2026).
+
 Borrowed Voice, Fremen worm-protection reaction policy, Tleilaxu revival
 accounting and other unresolved interpretations remain guarded. This is
 bounded composition, not complete Nexus/faction/module or release acceptance.

docs/NEXUS_FREMEN_RULES.md

@@ -81,14 +81,36 @@ Two interactions need a concrete decision before treating this as a complete fea
 
 `game/nexus-fremen-cunning.ts` captures `{event, turn, territory, origin, pile?, parent?, initiallyEmpty}` at the accepted appearance before destruction, using public `presenceAt` across players. Advisers and public No-Field markers count without revealing marker denomination. `beginWorm` offers the same Fremen decision for an initially empty appearance whether or not that seat holds its own card; the owner-only card view controls the spend button. The server, not the client, issues the event and later `{event, turn, owner}` ride authorization. The actual Fremen card moves to the Nexus discard on acceptance.
 
-The current runtime path covers natural and accepted additional worms in Basic/Advanced, plus Fremen special-Karama summoned worms in Advanced, with seated classic factions, Nexus alone and no other optional modules. The summon mints a separate server-side parent event when its physical Karama is spent; a new empty appearance binds the Cunning occurrence to that parent before devouring. A saved offer or pending ride must still belong to the active summon. A summon occurring inside another unresolved Cunning offer or ride retains its ordinary worm path without a second Cunning offer. Great Maker is not enabled for this Cunning path; Sandtrout-suppressed and first-turn ignored *drawn* worms never call the appearance hook, while a real special summon still does. `quoteFremenCunning` checks native unallied entitlement and lists typed forces in each occupied sand territory. After spending, `quoteFremenCunningRide` requires the saved event authorization and spent physical card; `validateFremenCunningSelection` requotes one source and a subset of normal/Fedaykin counters immediately before moving. The destination uses Arrakis entry, storm and occupation rules, not the desert-only source restriction. Ordinary worm destruction and the applicable Nexus happen first; `nextWormRide` schedules native rides before the remote ride afterward, without consuming normal movement. BG intrusion and territory-entry continuations use the native worm-ride path. JSON normalization and rejected-action checks cover a live offer, a spent response and the post-Nexus selection.
+The current runtime path covers natural and accepted additional worms in Basic/Advanced, plus Fremen special-Karama summoned worms in Advanced, with seated classic factions and Nexus, optionally retaining original Tech Tokens3+ and/or Advanced Stronghold Cards2+. Skills, Homeworlds, Discovery and expansion factions/decks stay outside this Cunning boundary. The summon mints a separate server-side parent event when its physical Karama is spent; a new empty appearance binds the Cunning occurrence to that parent before devouring. A saved offer or pending ride must still belong to the active summon. A summon occurring inside another unresolved Cunning offer or ride retains its ordinary worm path without a second Cunning offer. Great Maker is not enabled for this Cunning path; Sandtrout-suppressed and first-turn ignored *drawn* worms never call the appearance hook, while a real special summon still does. `quoteFremenCunning` checks native unallied entitlement and lists typed forces in each occupied sand territory. After spending, `quoteFremenCunningRide` requires the saved event authorization and spent physical card; `validateFremenCunningSelection` requotes one source and a subset of normal/Fedaykin counters immediately before moving. The destination uses Arrakis entry, storm and occupation rules, not the desert-only source restriction. Ordinary worm destruction and the applicable Nexus happen first; `nextWormRide` schedules native rides before the remote ride afterward, without consuming normal movement. BG intrusion and territory-entry continuations use the native worm-ride path. JSON normalization and rejected-action checks cover a live offer, a spent response and the post-Nexus selection.
 
 A special summon during an existing Cunning offer or Karama response saves and
 restores that original control. When it interrupts a selected remote ride, the
 unfinished ride returns to its queue so the new Nexus and ordinary worm rides
 resolve first; no second Cunning offer is opened for that nested appearance.
 
-One Karama response may cancel only this additional remote ride after the Nexus card is spent. The originally empty appearance still destroys/places spice as usual; the remote source is not destroyed, and unrelated native rides continue. This is a **provisional enhanced-native cancellation composition**, not an explicit publisher ruling about Nexus/Karama classification. Games requiring other modules, a second Cunning offer inside an already pending Cunning control, Great Maker reserve replacement or Sandmaster collection stay gated until their own adapters/rulings are verified. The accepted receipt is server-issued but not cryptographically signed; this path does not claim malicious-save authentication.
+One Karama response may cancel only this additional remote ride after the Nexus card is spent. The originally empty appearance still destroys/places spice as usual; the remote source is not destroyed, and unrelated native rides continue. This is a **provisional enhanced-native cancellation composition**, not an explicit publisher ruling about Nexus/Karama classification. Games requiring modules beyond original Tech/Advanced Strongholds, a second Cunning offer inside an already pending Cunning control, Great Maker reserve replacement or Sandmaster collection stay gated until their own adapters/rulings are verified. The accepted receipt is server-issued but not cryptographically signed; this path does not claim malicious-save authentication.
+
+### Original Tech and Strongholds — 11 October 2026
+
+The existing classic Nexus component envelope now receives the same public
+empty-worm offer as Nexus alone. Private card entitlement, original occurrence,
+card cost, provisional Karama response and post-Nexus remote ride are unchanged.
+No new dynamic destination or Great Maker adapter is inferred.
+
+The reusable fixture completes genuine setup, first-Storm Tech assignment,
+first-Mentat Stronghold claims and the actual turn-two Spice Blow. Only
+conserved physical card/deck order and two reserve counters are staged.
+Nine isolated runtime scenarios cover Basic Tech, Advanced Tech, Advanced
+Strongholds and both; four legal AI profiles and printed Karama cancellation.
+Each completed ride moves the original two counters once, preserves wallet,
+reserves and original component custody, and spends one physical Nexus card.
+At 390px, real GameTable spends Cunning and selects Wind Pass14→Polar Sink0:
+two counters arrive, reserves stay8 and spice stays3, with no horizontal
+overflow. A labelled QA control advances the original post-Nexus suffix;
+the spend and final typed ride use production controls. No saved store or
+deployed game was targeted; complete module/public acceptance remains open.
+TypeScript/lint and the final 41-case affected union pass. The permanent regression
+fails before the software guard removal and passes afterward.
 
 ## Secret Ally protection