Integrate Smuggler companion with owned Richese No-Field
Connect the GF9 FAQ combination: one free physical reserve force accompanies an owned concealed No-Field at its unchanged one-marker price. Preserve zero/three/five token values, actual supply at later reveal, optional human choice and all four legal AI paths. Genuine CHOAM & Richese Leader Skills development setup adds the two sourced battle cards without duplicating their Ix identities. Public mode and publication gates stay closed; allied and remaining combined routes are unfinished. Bind the private declaration across initial No-Field cancellation and later Advanced Guild interception, including saved interruptions. Validate before projection/actions/normalization, hide the internal proof, reject altered declarations immutably, and withdraw the companion once only on successful commitment. Independent rules/privacy/persistence review found no blocker. Preserve other audit setup gates despite expanded deck assembly. Repair the existing randomized recovery test with a genuine seeded Rihani offer and explicit human choice, replacing an inappropriate AI-policy call on a human seat. Initial Karama and later Guild stop retain their distinct existing opportunity outcomes. Validation: 72 focused regressions plus 10 deck tests; typecheck, lint, 4520 offline tests, production build and 43 HTTP tests passed. SQLite restart, concurrent allowance/cancellation and exact physical custody passed. Browser genuine assignment, private token selection, opt-in, one-spice shipment, refresh, five-force reveal and final refresh preserved six physical Arrakeen forces, 14 reserves, zero Tanks, four spice, Crysknife and Soo-Soo Sook. Genuine four-profile Basic/Advanced games completed in 77/116 actions with 3/4 JSON restores and no rejected candidates; Advanced exercised one companion shipment and later reveal. After the outage the existing server was healthy. Preserved all 529 opening rooms and original seat/recovery records (563 after QA/HTTP). SQLite integrity and foreign keys passed. No restart, database reset or automation. Verified source tree: c2aee4138bcb46a05814a340d62eadace3470247ca620844eb0375e78ea4d6c4
This commit is contained in:
1 parent
bf8036dfc1
commit
788453e07e
20 files changed
+1213
-51
No files matched your search
@@ -23,8 +23,9 @@ Flat reinforcements retain their existing rule. See the
|
||||
pages 9–11 and 13, and [November 2020 FAQ](https://www.gf9games.com/dune/wp-content/uploads/2020/11/Dune-FAQ-Nov-2020.pdf), page 5.
|
||||
|
||||
The CHOAM & Richese FAQ explicitly permits a Richese No-Field with a separate
|
||||
free Smuggler force into empty territory. That valid combination still needs
|
||||
concealed-counter integration here; its current guard is an implementation gap.
|
||||
free Smuggler force into empty territory. The [No-Field follow-up](SMUGGLER_NO_FIELD.md)
|
||||
now connects that owned-marker combination with one separate actual reserve force
|
||||
and the unchanged marker price.
|
||||
No new material user ruling was required for the ordinary reserve route.
|
||||
|
||||
## Connected behavior
|
||||
@@ -72,7 +73,7 @@ exercise the new effect. Required broad check/build/HTTP results and final
|
||||
preservation totals are recorded in the checkpoint commit and private report.
|
||||
|
||||
Smuggler battle collection still needs its reveal/survival settlement. Combined
|
||||
No-Field, Homeworld, Nexus, Discovery, Stronghold and technology routes remain
|
||||
allied No-Field, Homeworld, Nexus, Discovery, Stronghold and technology routes remain
|
||||
outside this prototype. Mentat questioning, Bureaucrat payments, Sandmaster
|
||||
movement collection, Spice Banker and Diplomat also remain incomplete. Reuse
|
||||
this ordinary route when integrating those dependencies.
|
||||
Reference in new issue
Block a user