Compose same-plan Harass and Reinforcements with original reserve costs

This commit is contained in:
Quintine committed 2026-10-16 06:48:04 +11:00
1 parent feb2b03251
commit be0644c0e9
15 files changed
+288 -30

No files matched your search

+20 -1
View File
@@ -29,6 +29,25 @@ optional skill bands, combinations and public expansion starts remain open.
Rules implementation continues; comprehensive assurance and administration
remain deferred until all rules are implemented.
**Same-plan Harass / Reinforcements — 16 October.** Both slot orders now follow
the existing original-reserve-cost-before-return order under explicit
choose-recommended interpretation. Future returns cannot fund deficient reserves
or replace the original normal/elite quote. Original score-only +2, fixed Ecaz
commitment, variable ally losses, all-outcome reserve cost and Traitor-canceled
Harass remain separate; both physical cards discard once.
Affected eleven-file134/134, types/lint and build pass. Six new behavioral
regressions, eight fresh Node policy programs/all four profiles with16 accepted
continuation actions and a real390px typed-cost journey pass. Original2-normal/
1-elite reserve payment survives the later4-normal return; owner finishes
reserves4/Tanks16/elite Tanks5/spice29, both cards discarded and collection open.
No root overflow or browser/application error. Current parse/policy anchor and38
topic evidence paths resolve; all ten facets remain Partial.
[Policy and scoped proof](REINFORCEMENTS_RUNTIME.md#combined-utility-plan--16-october-2026).
Stone/Reinforcements, other profile/module limits and final assurance remain
separate. No human server, saved room, D1, deployment or public gate changed.
**Harass / Stone Burner interaction — 16 October.** Richese-family Harass now
uses visibly provisional post-withdrawal physical comparison under the standing
choose-recommended priority; the earlier source question remains unanswered.
@@ -47,7 +66,7 @@ Original Richese lot and shared-preparation fixture drivers were corrected;
incidental collection-wallet expectations were removed. Current guide parse,
policy anchor and33 evidence paths resolve; both topics' five facets stay
Partial. [Policy and scoped proof](HARASS_WITHDRAW_RUNTIME.md#provisional-stone-burner-timing--16-october-2026).
Ix/Poison Tooth, same-plan Harass/Reinforcements, Reinforcements/Stone, own
Ix/Poison Tooth, Reinforcements/Stone and own
concealed No-Field Harass and other module gates remain. No human server,
saved room, D1, deployment or public gate changed; final assurance stays due.
+5 -3
View File
@@ -249,9 +249,11 @@ Reinforcements uses the card user's own three normal-first reserve counters
and existing +2 score-only modifier, not ally reserves, extra physical dial
losses or support. Existing provisional all-revealed-outcome cost/disposal
is unchanged and remains explicitly not a publisher ruling. Both slots and
opposing holders work; own same-plan Harass/Reinforcements and Reinforcements
with Stone/optional modules remain guarded. Basic/unprofiled co-side card
battles remain rejected.
opposing holders work. Same-plan Harass/Reinforcements now follows the
[provisional original-reserve-cost-first policy](REINFORCEMENTS_RUNTIME.md#combined-utility-plan--16-october-2026),
preserving actual card-user ownership and original fixed losses.
Reinforcements with Stone/optional modules and Basic/unprofiled co-side
card battles remain guarded.
Native/pure67 cases, relevant284-case batch and27 actual native-program
cases pass, including all four legal policies. Two natural captured games
+6 -5
View File
@@ -110,11 +110,12 @@ This is a legal strategy path, not strength calibration.
returns only actual card-user forces: original fixed Ecaz commitment or the
selected ally's native variable commitment. It never returns the other ally
or recomputes mandatory fixed losses from the diminished board.
- [Bounded Reinforcements](REINFORCEMENTS_RUNTIME.md) can appear in the
opposing Battle Plan in classic-faction Basic/Advanced games. The two cards
cannot share one player's plan; their relative same-plan timing remains
unresolved. Both prototypes retain their separate provisional cost and
outcome interpretations.
- [Bounded Reinforcements](REINFORCEMENTS_RUNTIME.md) may appear in the opposing
or the same supported Battle Plan. Same-plan use provisionally pays the
original reserve quote before returning undialed counters; a future return
cannot fund or change that cost. Both prototypes retain their separate
provisional outcome interpretations. See the
[combined policy](REINFORCEMENTS_RUNTIME.md#combined-utility-plan--16-october-2026).
## Scoped interaction proof — 16 October 2026
+26
View File
@@ -1,5 +1,31 @@
# Dune implementation status
## 16 October 2026 — Same-plan Harass and Reinforcements
Connected both physical slot orders without adding a new settlement mechanism
or state field. Existing native order pays the original three-reserve quote
before Harass returns undialed fighters. Future returns cannot fund deficient
reserves or change quoted elite cost. This is explicitly provisional under
choose-recommended, not a new source ruling; original all-outcome fee and
score-only +2 remain. Own fixed/variable Occupy pools and Traitor cancellation
stay separate. Both physical cards discard once.
Eleven-file134/134, types/lint and production build pass with the existing
module-register/large-chunk/Unknown-route warnings. Six new behavioral cases
cover original typed reserve cost, eligibility, both slots, Traitor/explosion
and fixed/variable Occupy. Eight fresh Node programs exercise all four legal
policies/both modes and16 accepted continuation actions.
Actual390px controls seal original2-normal/1-elite payment and dial1/support1.
The +2 decisively beats opposing leader4; four ordinary forces return, but
the original elite cost still pays. Final reserves4/Tanks16/elite Tanks5,
spice29, both cards discarded and collection open. No root overflow or
browser/application error. Current parse/anchor and38 topic paths resolve;
all ten facets stay Partial. Obsolete pair rejection and absent-card pin
removed. Other gates remain; no human server, D1, saved room, deployment or
broad/HTTP/recovery assurance campaign changed.
[Combined policy and proof](REINFORCEMENTS_RUNTIME.md#combined-utility-plan--16-october-2026).
## 16 October 2026 — Provisional post-Harass Stone comparison
Removed only the public Richese-family Harass guard. Under standing
+53 -2
View File
@@ -9,8 +9,9 @@ families; Basic/unprofiled co-side use stays guarded. The
holder may commit it in either Battle Plan card slot. It is neither a weapon
nor a defense: Prescience of a category receives **None**, while the physical
slot stays occupied and hidden until reveal. A named-card inspection still
fixes the exact card. Harass & Withdraw and Stone Burner cannot share this
plan; Homeworld and other optional-module combinations remain gated.
fixes the exact card. Harass & Withdraw may share the plan under the
[provisional original-cost-first policy](#combined-utility-plan--16-october-2026).
Stone Burner, Homeworld and other optional-module combinations remain gated.
The [combined-army follow-up](ECAZ_OCCUPY_RULES.md#independent-cards-with-combined-armies--2-october-2026)
retains own-holder reserve cost and selected lead card/payment ownership.
@@ -23,3 +24,53 @@ The holder must have three own reserve counters when sealing the plan. The owner
The owner receives a card-slot explanation and disabled reason when fewer than three reserve counters remain or the bounded mode is unsupported. All four AI profiles generate legal candidates in the classic and Ecaz/Moritani profiles and can select either slot, including an Advanced plan. The current scoring is a minimal legal participation heuristic, not difficulty calibration. The prototype does not certify the whole three-card variant, other expansion combinations, optional modules, historical-save compatibility or public mode starts.
Focused rule, engine, controls and in-memory SQLite tests cover both slots, Basic/Advanced payment, elite subpool conservation, traitor/explosion disposal, private sealed views, JSON restoration, rejected-action immutability and competing final room commits, now including a paired Ecaz/Moritani saved battle. The test results and actual browser/UI evidence for the current checkpoint are recorded in [Implementation status](IMPLEMENTATION_STATUS.md); test coverage is not a publisher ruling.
## Combined utility plan — 16 October 2026
The standing choose-recommended priority selects the existing native settlement
order for the two physical specials in one plan: quote and debit three
**original own reserve** counters before Harass returns any undialed counters.
This is an implementation interpretation, not a newly retrieved publisher FAQ
or an answer to the earlier reserve-payment question. The source audit's printed
effects and original provisional all-outcome/normal-first cost are unchanged.
Three reserves must exist at commitment. A future return cannot fund a deficient
plan or change its quoted normal/elite mix. For example, two original ordinary
and one elite reserve are spent even when Harass subsequently returns four
ordinary counters. Both cards discard once. The +2 remains normal-score-only,
not extra physical dial, support or winner casualties. Opposing successful
Traitor cancels only Harass; Reinforcements still pays under its existing
provisional all-outcome policy.
Both slot orders compose in the existing Basic/Advanced and selected Advanced
Occupy envelopes. Only the card user's reserves and undialed forces change;
original fixed Ecaz commitment and the other ally's pool stay separate.
Stone/Reinforcements, Basic/unprofiled co-side and other module gates stay.
No persisted state or fresh/public profile is added.
### Scoped proof
The affected eleven-file offline union passes **134/134**, with types/lint and
production build passing (module-register, large-chunk and Unknown-route
warnings). Six new behavioral regressions cover both slots, original typed
costs, deficient original reserves, all Traitor outcomes, explosion and both
active Occupy card-user roles. The test battle uses rock so automatic
collection income cannot obscure support accounting.
Fresh Node programs exercise eight Basic/Advanced cases across all four
profiles, both slot orders and16 accepted continuation actions. A real styled
390px journey starts at three reserves (two normal, one elite), selects both
cards and shows the explicit provisional order. Original dial1/support1 with
leader2 plus bonus2 beats opposing leader4. Four ordinary fighters return;
the original elite reserve is spent, leaving reserves4/Tanks16/elite Tanks5,
spice29 and no army, battle or decision. Both cards discard once; native
collection opens. No root overflow or browser/application error occurred.
Current guide parse, combined-policy anchor and38 evidence paths across the
two topics resolve; all ten checklist facets remain Partial. Removed the
obsolete pair rejection and an incidental absent-card candidate pin. No
human server, saved room, D1, deployment or public gate changed; no new broad,
HTTP, recovery/privacy/custody assurance campaign ran. Private proof artifacts
remain outside Git; the owned source host and throwaway scripts were removed.
+1 -1
View File
@@ -758,7 +758,7 @@ These are unresolved in the cited records. Do not infer an answer from elapsed t
| Boundary | Still unresolved | Existing record |
| --- | --- | --- |
| Reinforcements cost | The user question still asks whether to keep the card disabled, always transfer three reserve forces on every outcome, or waive only a sole traitor-call winner's cost; no answer is assumed. The bounded classic and Ecaz/Moritani prototype provisionally charges on all revealed outcomes, chooses normal reserves before elite and counts the transfer as battle losses. Those are product interpretations, not a ruling. Same-plan Harass/Stone Burner remain gated; opposing Harass is supported. Eligibility never depends on concealed matching Traitors. | [Source cost review](ECAZ_TREACHERY_RULES.md#14-september-reinforcements-cost-review) · [Bounded runtime](REINFORCEMENTS_RUNTIME.md) |
| Reinforcements cost | The earlier all-outcome versus sole-Traitor-winner question remains unanswered. The bounded prototype provisionally charges on every revealed outcome, chooses normal reserves first and counts the transfer as battle losses. Under standing choose-recommended, same-plan Harass composes by paying that original reserve quote before returns; future returns cannot fund or change it. Those are product interpretations, not publisher rulings or a numerical user answer. Stone/Reinforcements and other module gates remain. Eligibility never depends on concealed matching Traitors. | [Source review](ECAZ_TREACHERY_RULES.md#14-september-reinforcements-cost-review) · [Combined policy](REINFORCEMENTS_RUNTIME.md#combined-utility-plan--16-october-2026) |
| Harass / Stone Burner | The earlier question (keep gated or compare after withdrawal) remains unanswered. Under the standing 14 October choose-recommended instruction, the development prototype now provisionally compares undialed counters remaining after successful withdrawal. Opposing Traitor cancels the return; original fixed Occupy commitment stays. Public preflight considers possible fixed Ecaz withdrawal without reading hidden custody. Allocation ambiguity, Ix/Poison Tooth and other module boundaries remain. This is an implementation interpretation, not a publisher ruling or a user answer. | [Provisional timing](HARASS_WITHDRAW_RUNTIME.md#provisional-stone-burner-timing--16-october-2026) |
| Recruits late accounting and rates | The earlier one/two-further-free question remains unanswered. The content-first prototype now preserves paid spice, deducts recorded actual free usage from the doubled rate and all returns from the total cap: two-free/one-paid Atreides can take two more free. This is visibly provisional, not a numerical user ruling. Unknown ledgers, pending repricing, late rate changes and same-turn replay remain guarded. | [Source alternatives](RECRUITS_RULES.md), [provisional runtime](RECRUITS_RUNTIME.md) |
| Sapho remaining timing | First versus unspent Advanced Guild priority, partly completed combined turns, cyclic auction duration and later battle timing stay guarded. The existing pre-plan opportunity supports [early aggressor](SAPHO_AGGRESSOR.md). Prior questions remain unanswered. | [Source audit](JUICE_OF_SAPHO_SOURCE_UPDATE.md), [battle review](JUICE_OF_SAPHO_BATTLE_REVIEW.md) |