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
@@ -1,5 +1,27 @@
|
||||
# Dune implementation status
|
||||
|
||||
## 13 September 2026 — Smuggler with owned Richese No-Field
|
||||
|
||||
The [officially permitted combination](SMUGGLER_NO_FIELD.md) now ships one
|
||||
separate free physical force alongside a concealed marker at its unchanged price.
|
||||
The private panel, shared AI quote, both cancellation/interception stages and saved
|
||||
continuation are connected. Revealing zero/three/five tokens preserves all physical
|
||||
forces; bots can reveal a zero marker accompanied by a real force before movement.
|
||||
Genuine CHOAM & Richese Leader Skills setup uses the sourced two-card deck addition
|
||||
or replacement without duplicate Ix cards. Public starts remain gated.
|
||||
|
||||
After the outage report, the healthy existing server was reused. All 529 opening
|
||||
games and their seat/recovery records matched the private backup. Focused tests,
|
||||
independent recovery review, browser evidence, required broad checks and final
|
||||
preservation/Git results are recorded in the checkpoint commit and private report.
|
||||
Allied No-Field and remaining combined modes are unfinished.
|
||||
|
||||
The first broad check exposed two deck/gate expectations and a randomized
|
||||
recovery test incorrectly asking an unautomated human seat for an AI action.
|
||||
The deck assertions now match the sourced inventory while other audit starts
|
||||
retain their gate. The recovery test now submits an explicit legal human choice.
|
||||
The failed report is retained separately from final verification.
|
||||
|
||||
## 13 September 2026 — Sandmaster movement collection prototype
|
||||
|
||||
[Sandmaster](SANDMASTER_MOVEMENT.md) now collects optional spice from distinct
|
||||
|
||||
Reference in new issue
Block a user