Connect Sapho first and last to Extortion payer choices
Apply the printed ordered-action alternative provisionally to the unanswered native Extortion suffix. Preserve collected bank5, completed declines, payer membership, one payment3 and placement-first policy. Replay a public local-order receipt and retain it through ledger answers; expire the old payer event even when the same player remains next. Permit only the exact current Extortion decision as a clean Sapho window. Add persistent remaining-order/card controls and existing minimal policy participation. The typed Semuta suffix parks one updated payer decision and restores it without paying, advancing or recollecting. Validation:9-file115/115, types/lint/build and six original public Basic/Advanced host/setup/paid-cache1/placed-Terror/paid-entry1/reveal/Mentat-placement-before-bank5 programmes. An actual earlier decline stays finished; first/payment3 and last/payment3 or all-decline preserve native retirement/recovery. Four profiles make eight legal holder/payer proposals and complete. Public order and private payer affordability render in actual GameTable plus enabled/busy controls. Pure replay/no-op/recovered reuse cases are separate. Bounded source/continuation review found no concrete defect. Extortion/Sapho boundary is provisional. Direct combined Semuta claim/capture, broader combinations, complete modes, final assurance and browser/deployed acceptance remain open. No saved-room/database/reset/restart/deployment operation.
This commit is contained in:
1 parent
2d89ddb6e1
commit
6c83148ead
14 files changed
+855
-16
No files matched your search
@@ -16,6 +16,33 @@ open mode gates.
|
||||
|
||||
|
||||
## Current checkpoint and work
|
||||
**Sapho Extortion payer order — 18 October. Prototyped / Partial.** The general
|
||||
ordered-action alternative now provisionally reorders only native Extortion's
|
||||
unanswered payer suffix. Public replay preserves original membership and prior
|
||||
declines; ledger answers retain the receipt. Every use expires the native payer
|
||||
event, even if the same player remains next. Collected bank5, one payment3,
|
||||
physical storm order and the user's placement-first policy remain. Persistent
|
||||
controls display remaining names; existing minimal policies use real options.
|
||||
A typed Semuta suffix parks one updated payer decision without paying/advancing.
|
||||
|
||||
Two disjoint helper/fixture lanes, bounded source/continuation review and owner
|
||||
integration pass **9 files115/115**, types/lint/build and six original-action/
|
||||
rendered-table programmes. Public Basic/Advanced cache1, real Extortion placement,
|
||||
paid foreign1 entry/reveal, later actual Mentat placement-before-bank5 and one
|
||||
Atreides decline use120/139 source actions. First/payment3 and last/payment3 or
|
||||
all-decline use2–4 continuations: Moritani gains8 or5, the token retires or rotates
|
||||
into hidden supply, and no earlier payer repeats. Four profiles make eight legal
|
||||
holder/payer proposals and finish. Pure replay/no-op/recovered-reuse cases remain
|
||||
separate. No dealt piece, wallet, clock, payer queue or receipt is installed.
|
||||
|
||||
Frozen feedback corrected only a deliberate-invalid-mode test cast; the whole
|
||||
batch then passed together. Actual GameTable and enabled/busy card/payer controls
|
||||
render public order and payer-only affordability. No browser clicks or visual/
|
||||
deployed acceptance. Direct combined Semuta claim/capture, broader combinations,
|
||||
complete modes and final assurance remain open. No saved-room/database/reset/
|
||||
restart/deployment operation.
|
||||
[Canonical source, protocol and exact proof](MORITANI_EXTORTION_RULES.md#sapho-payer-ordering--18-october-2026).
|
||||
|
||||
**Sapho first with an unspent Advanced Guild — 18 October. Prototyped / Partial.**
|
||||
At a clean unstarted non-Guild boundary, first now reorders the remaining queue
|
||||
and retains the Guild's native next-boundary take/wait choice. A granted current
|
||||
|
||||
Reference in new issue
Block a user