Connect bounded Richese Nexus Cunning No-Field pair

docs/NEXUS_RICHESE_RUNTIME.md

@@ -41,3 +41,11 @@ Two fresh three-human-seat rooms used final session IDs before genuine fixture s
 In 3C2N43XF, the five-force declaration reached the Guild at version 3. The Guild used its actual special Karama control; version 4 retained all twenty shipper reserves and its one spice, consumed the shipment, and left the Nexus spent. No phantom physical marker appeared.
 
 Desktop 1440-pixel and phone 390-pixel screenshots were captured and visually inspected, including the typed source selection, price breakdown and Guild stop controls. Phone checks found no horizontal overflow. All six private sessions refreshed successfully with no page errors; opponents lacked the shipper's private hand, traitors and spice, and no internal shipment/history record was projected. The read-only restoration script is `/tmp/dune-richese-nexus-restore.cjs`. Staging the first room preserved all 3,548 other room states and versions; staging the second preserved all 3,549 other rooms. Final comparison after both browser rooms and thirty isolated HTTP rooms retained every version/hash of all 3,548 opening rooms; 3,580 rooms now persist. The 02:48 UTC controlled restart used a database backup, preserved all opening games and restored twelve earlier Moritani/CHOAM private sessions. Six new Richese private sessions subsequently restored. No publication or full module gate opened; the maintenance automation remains removed.
+
+## 27 September 2026 — bounded native Cunning shipment
+
+In a genuine paired Richese/CHOAM Nexus game with classic factions and no other optional modules, an unallied Richese holder can spend the native Richese Nexus card on one shipment of two distinct available No-Field tokens. One is immediately revealed into up to its printed value of actual normal forces from current reserves; the other remains the sole concealed marker. The pair costs one ordinary marker shipment. Neither token can match the prior shipped marker, and the concealed token becomes the next `lastShipped`. This same-shipment history choice is a documented product interpretation, not a retrieved publisher answer. A previously deployed marker blocks another shipment until its ordinary native resolution.
+
+The declaration binds both token IDs, the native event, destination, sector and price to a saved receipt. Native Karama cancellation spends the card but leaves tokens, spice, reserves and the ordinary shipment available; Advanced Guild special prevention spends the card and shipping allowance without moving either token or charging spice. Accepted arrival publicly logs the revealed denomination, reserve-capped actual force count and concealed one-force marker without revealing the other denomination. Owner-only selectors and all four minimal bot profiles share the supported route. The owner/rival read-only browser fixture showed the separate two-token selector and no rival private panel; no room was written. A concurrent in-memory SQLite CAS case restored the pending native/Guild continuation, settled one pair and rejected replay. Focused No-Field/Cunning/recovery verification passed 60 cases after the continuation-integrity and allocation-only validation fixes; the final frozen complete suite passed 5,581/5,581 cases across 700 files.
+
+Persistent faceup-component artwork, high-Richese extra ordinary forces, allied No-Field combinations, Homeworld/Leader Skills/Discovery/Sandtrout/Ecaz interactions, Richese Betrayal and complete Nexus acceptance remain separate. The earlier Secret Ally checkpoint above is historical evidence; it is not a claim that the native Cunning or live production image was deployed at that time.