122 lines
14 KiB
Markdown
122 lines
14 KiB
Markdown
# Richese Nexus Secret Ally runtime
|
||
|
||
This checkpoint adds the [source-audited Secret Ally](NEXUS_RICHESE_RULES.md) to an unallied holder's unused ordinary reserve shipment when Richese is absent. Choose one to five actual forces and price the group as one force. The physical force count, starred identity, destination and arrival restrictions remain ordinary shipment rules. It creates no concealed No-Field and no second shipment.
|
||
|
||
## Original Tech and Stronghold composition — 18 October 2026
|
||
|
||
Classic Nexus core retains the original phase modules with selected33/36
|
||
and optional14. A real funded five-for-one arrival still delivers five and
|
||
uses the one-counter invoice; original Heighliners accrues its actual owner's
|
||
token count only after delivery and pays only at phase end. Neither the fee
|
||
claim nor a held Stronghold card invents another trigger or personal subsidy.
|
||
No other native/World/Discovery envelope or numerical rule changes.
|
||
[Current phase consumers and controls](NEXUS_CARD_RULES.md#classic-nexus-original-phase-modules--18-october-2026).
|
||
|
||
## Classic core Guild fee composition — 18 October 2026
|
||
|
||
Classic base33 or selected independent36 Nexus, optionally all14, now retains
|
||
the original signed Secret Ally declaration through actual native Guild fee
|
||
acknowledgement. Original Guild interception/rate rules precede that fee.
|
||
The declared five-for-one group remains pending, without moving counters or
|
||
charging spice early, while its actual Richese card stays spent.
|
||
|
||
Real distinct Richese/Guild draws permit a rival's full fee claim: five
|
||
physical counters to Carthag cost the ordinary one-counter stronghold price1.
|
||
Actual mobile controls complete native Guild Allow then rival Use: shipper
|
||
12→11/reserves10→5, recipient10→11, both distinct Nexus cards discarded once.
|
||
Pass instead retains Guild Nexus and credits native Guild1. No concealed
|
||
marker, extra shipment or change to original rate/affordability policy.
|
||
[Exact core source, tests and controls](NEXUS_CARD_RULES.md#classic-nexus-core-and-funded-card-shipments--18-october-2026).
|
||
|
||
## Native Guild rate followup — 15 October 2026
|
||
|
||
Original Guild/Richese Secret Ally declarations now admit the distinct unpaid
|
||
native rate response after original interception. The signed pending receipt
|
||
retains all five physical counters while billing one: allowing costs1 on
|
||
sand; cancellation costs2. Actual completion preserves movement and consumes
|
||
each original physical card once. No marker or force is invented.
|
||
|
||
With only1 available, cancellation ends the already spent Nexus declaration
|
||
without delivery, debt or refund and leaves an ordinary full-price shipment
|
||
available. The controls explain that consequence before cancellation. This is
|
||
the selected [affordability source composition](NEXUS_RICHESE_RULES.md#native-guild-rate-composition--15-october-2026),
|
||
not new publisher worked-example authority. A still-held card survives an
|
||
earlier cancellation and now quotes sand2 rather than falsely affordable1;
|
||
it can instead ship five to a stronghold for1. An independent purchased price
|
||
continues to charge1 to bank without a native-rate response.
|
||
|
||
Affected thirteen-file **92/92** passes, including seven new behavior cases.
|
||
Eleven actual runtime/policy paths use original-action sources, including
|
||
all four existing profiles executing a legal full-rate one-counter alternative.
|
||
No strategic first-candidate pin, tuning or calibration was introduced.
|
||
Setup selects conserved undealt entropy, then real paid Karama acquisition,
|
||
Ecaz/Moritani alliance and Guild's real Richese Nexus draw. No played hand,
|
||
wallet, army, phase or response is assigned.
|
||
|
||
Four real styled390×844 GameTable journeys prove native Junction5/fee2;
|
||
poor1/full2 release followed by an ordinary1/one-force replacement;
|
||
still-held card's disabled sand2 then five-force stronghold1; and independent
|
||
purchased1. Shipment/turn and card/force outcomes are observed; viewport and
|
||
scroll width remain390, with no browser error or application exception.
|
||
Two transient browser-tool stale-node errors after successful transitions
|
||
were handled by fresh state/accessibility, never replay.
|
||
|
||
Only an owned memory-only loopback host ran: no worker, D1, authenticated
|
||
saved room, human server or deployed revision was exercised or changed.
|
||
Proof and four initial scenes remain outside Git under
|
||
`/tmp/dune-richese-native-rate-*20261015*`. Full rules, final assurance and
|
||
public expansion/module starts remain unfinished.
|
||
Final `npm run check:quick` and production build pass with the existing
|
||
module-register, large-chunk and Unknown-route warnings. Thirteen current
|
||
local links and430 checklist evidence paths resolve; all ten checked
|
||
Homeworld/Nexus facets remain Partial.
|
||
|
||
|
||
## Price and physical custody
|
||
|
||
The shared [source quote](../game/nexus-richese.ts) separates `physicalAmount` from `pricedAmount: 1`. The whole group costs one spice to a stronghold or two elsewhere; native Guild and an active ordinary Karama rate keep their existing half-price rounding. Karama bank routing remains separate from the Nexus source. Fremen retain free reinforcement and their Great Flat range; this is retained-native-rules composition, not a named faction-specific FAQ ruling.
|
||
|
||
Native Homeworld reserve pools remain usable through the existing typed withdrawal selection. Native Ixians retain their ordinary right to ship into the present Hidden Mobile Stronghold; the card does not grant that destination to other factions. A foreign Homeworld destination, board cross-shipment, return to reserves or physical No-Field is not offered by this adapter. These routes must not be fabricated through the Arrakis selector. The actual force amount governs withdrawal, board placement, Terror and other arrival callbacks. Only the price basis becomes one.
|
||
|
||
The existing shipment consumes the Nexus when declared. Advanced Guild prevention retains its independent response; the stopped shipment uses the shipment allowance without moving forces or charging shipping spice, while the Nexus remains spent. Ordinary allowance uses the reduced actual payment for Guild income and preserves existing technology, BG and territory-entry rules. Unsupported competing arrival combinations retain their existing gates.
|
||
|
||
## Saved declaration and binding promises
|
||
|
||
The server binds the source to the original owner, turn, faction roster and exact shipment fields. The pending record includes the actual typed force allocation, selected native reserve pools, destination, sector, cost and arrival stance. Its separate latest-outcome marker prevents a deleted or reopened pending record from silently reverting to an ordinary shipment. These consistency signatures detect partial corruption; they are not cryptographic authentication of arbitrary replacement saves.
|
||
|
||
The card is discarded when the validated declaration is made. A saved Guild interception keeps that same record and the actual force count until allowance or special prevention. Terminal records retain history without locking the player's later forces or resources. Ordinary shipment validation still checks current physical custody, geography and payment before commitment.
|
||
|
||
A binding shipment answer searches the discounted shipment as a legal completion candidate. This matters when a player can afford five physical forces only by spending the held Nexus. The owner receives a concrete private completion action; the other seats do not receive the source offer or receipt. All four bot levels can use that action to honor an accepted Yes.
|
||
|
||
## Controls and bots
|
||
|
||
The [shipment panel](../components/game-table.tsx) starts with an unchecked “Use Richese Nexus Secret Ally” option. Selecting it limits the shipment group to five, displays the actual group separately from the one charged force, and uses the shared price for funding. It preserves the normal destination, typed-force and native Homeworld source controls. Server blocking reasons and transport-busy state remain visible.
|
||
|
||
The [shared consumer helper](../game/nexus-richese-options.ts) fences the private held card, absent native faction, current owner, unused shipment, event and interruptions. Opponents receive no private offer. The action retains the ordinary `ship` fields and adds the current Nexus event; a marker, cross-shipment or foreign Homeworld cannot masquerade as this source.
|
||
|
||
All four [bot profiles](../game/bots.ts) generate discounted candidates independently of ordinary shipment affordability, including five forces when the player can only afford the one-force price. They retain ordinary candidates and avoid spending the card when it saves no spice, including native Fremen free reinforcement. The [Homeworld payment filter](../game/homeworld-payment-options.ts) recognizes the actual source price before checking low-Junction contributor rounding. This establishes legal candidates, not separately calibrated Nexus strategy.
|
||
|
||
## Verification and remaining boundaries
|
||
|
||
Six new cases in [controls](../tests/nexus-richese-controls.test.ts) and [bots](../tests/nexus-richese-bots.test.ts) use the [genuine setup fixture](../tests/fixture-nexus-richese.ts). They exercise Basic/Advanced actual shipment, distinct price and physical count, unchecked controls, stale and unauthorized sources, observer privacy, native faction prices, affordable five-force candidates, ordinary fallback and the source-aware payment filter. The low-Junction consumer case explicitly stages a public projection only; it does not claim a new engine custody transition. Interactive checkbox verification is recorded below separately from server rendering and helper/action checks.
|
||
|
||
The checkpoint adds **30 passing cases**: six pure source/receipt tests, six consumer cases, twelve engine cases, five production SQLite cases and one binding-promise regression. Engine coverage includes actual Truthtrance interruption, real next-turn movement/shipment continuity, native Ixian HMS entry, and genuine prior Mentat Terror placement followed by a five-force arrival under low Grumman. SQLite covers competing declarations, uncertain-response recovery, Guild prevention, original typed sources and malformed history with zero writes.
|
||
|
||
Focused verification passed **6/6 new consumer cases**. A separate compatibility run passed **52/52 cases** covering shipment budgets and promises, native/Guild Homeworld controls, Nexus controls and reference checks. Type-aware lint passed for the changed consumer and test files. **Types, lint, all 4,099 offline tests, production build and 40 live HTTP tests passed.** Native Richese Cunning, Betrayal, the foreign-Homeworld tariff adapter and complete Nexus/module play remain unfinished.
|
||
|
||
## Isolated browser acceptance
|
||
|
||
Two fresh three-human-seat rooms used final session IDs before genuine fixture setup and exact state/version staging. MGJ3WQ6Y advanced from version 2 to 3: the unchecked ordinary five-force quote cost five spice and was unaffordable; selecting Secret Ally changed the maximum to five and the price to one. Emperor shipped three normal forces from Kaitain and two Sardaukar from Salusa, leaving fifteen reserves, three reserve Sardaukar, zero spice and movement available.
|
||
|
||
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.
|