Compose concealed No-Field battle cards before reserve costs

docs/RICHESE_NO_FIELD_RULES.md

@@ -2,6 +2,30 @@
 
 Audit date: 2026-09-06. This document distinguishes the printed token lifecycle from engine integration and unresolved combinations. It does not certify Richese, Homeworlds, or any other gated game mode.
 
+## Concealed battle-card composition — 16 October 2026
+
+Harass now composes with own concealed No-Fields in supported Basic/Advanced
+and existing Advanced Occupy card profiles. Standing choose-recommended keeps
+the native order: seal both plans, materialize the reserve-limited token at
+its actual sector, then resolve original reserve cost and successful Harass
+return before ordinary losses. This priority composition remains explicitly
+provisional, not a new dedicated publisher FAQ.
+
+Private planning forecasts actual ordinary counters and their marker-sector
+location without moving them early. Zero remains a real marker with leader/
+card legality; shortage caps by actual reserves. Mixed sectors select all
+undialed physical counters only after reveal. Harass neither returns a virtual
+marker nor clears its last-use/history fence. Opposing successful Traitor
+cancels only the return, never the original component revelation.
+
+Reinforcements requires three original own reserves **after projected native
+materialization**, before any later return. A proven token3/reserves3 plan
+previously sealed, materialized to0 and stalled on Traitor resolution; the
+new first-plan guard rejects that commitment and retains a legal Harass-only
+alternative. Other owners' reserves/markers are not shared. Owner-only preview
+facts are view data, not new saved Game fields or a historical-save migration.
+Existing mode, mixed-co-side, full-plan and optional-module gates remain.
+
 ## Advanced first versions — 8 October 2026
 
 Advanced ordinary mixed battles and discounted allied shipments now reuse
@@ -124,7 +148,7 @@ This table records the original adapter contract. The implemented subset and cur
 ## Unresolved or compositional boundaries
 
 1. **Reserve shortage when destroyed.** Voluntary/battle text explicitly caps by reserves; the destruction sentence says to lose the indicated quantity without repeating the shortage clause. The pure model caps materialization to avoid creating physical units, but that is conservation-based composition for storm/worm losses, not an independently answered FAQ. It does not select substitute losses from unrelated board forces.
-2. **Mixed forces and battle dials.** The FAQ forbids dialing more than reserves in a No-Field battle. A territory can also contain ordinary forces (the Smuggler answer demonstrates mixed presence), but no retrieved answer expressly defines that limit with existing forces, multiple sectors, typed units or independently committed reserve uses. Basic and Advanced prototypes use an explicitly provisional additive pool; this does not settle the source question. Combined Occupy remains guarded.
+2. **Mixed forces and battle dials.** The FAQ forbids dialing more than reserves in a No-Field battle. A territory can also contain ordinary forces (the Smuggler answer demonstrates mixed presence), but no retrieved answer expressly defines that limit with existing forces, multiple sectors, typed units or independently committed reserve uses. Basic and Advanced prototypes use an explicitly provisional additive pool; this does not settle the source question. Same-owner mixed ordinary/marker Occupy remains guarded; the existing marker-only Advanced Occupy profile supports the owner-specific card composition above.
 3. **Full-plan special Karama and structured Truthtrance.** The ordinary Atreides dial prohibition is explicit. Whether a broader entire-plan power or a particular promise question overrides it was not resolved by a retrieved specific answer. Do not leak the value through private legal-plan previews, public maximum dials, error strings or bot reasoning.
 4. **Homeworld use.** R3 recommends Richese in a Homeworld combination but supplies no retrieved No-Field-specific rule defining off-planet hidden custody, one-on-planet versus off-planet coexistence, or homeworld threshold disclosure. General module availability is not an answer to those lifecycle questions. The isolated model represents a single Arrakis marker and does not authorize Homeworld placement.
 5. **Capturing, transferring or returning a concealed marker as a force.** Movement-as-a-force and Gamont's explicit forced reveal do not establish a general conversion for every card or Guild transport-to-reserves. A generic return helper must not erase a hidden token without a source-backed reveal/custody cause. This module exposes no such automatic escape from last-use history.