Enable future battle questions in Basic expansions
Verify and publish checkpoint container / container (push) Successful in 10m55s

This commit is contained in:
Quintine committed 2026-10-29 02:16:15 +11:00
1 parent 7fc6f1cd43
commit 0e52c25355
7 files changed
+151 -14

No files matched your search

+10
View File
@@ -17,6 +17,16 @@ open mode gates.
## Current checkpoint and work
**Basic expansion future-battle Truthtrance — 29 October. Prototyped / Partial.**
The conditional native-leader question is available in quiet Basic games with
expansion factions and decks, except Ecaz and optional modules. CHOAM Yes/No
answers bind actual battles; a Richese answer survives the physical discard
and Semuta pass, then expires if no battle occurs. Ecaz's late combined-battle
lead, Semuta exchange, other expansion interactions and Advanced remain open.
Seven focused files pass 33 cases, including four minimal bot answers and a
staged Ecaz guard probe; typecheck, lint and build pass.
[Scope](TRUTHTRANCE_TURN_ACTIONS.md#conditional-next-battle-leader-question--28-october-2026).
**Sequential Richese bidding clock — 29 October. Prototyped / Partial.**
Fresh Once Around and normal Black Market lots use the trusted ten-second
countdown and native pass, with supported binding Truthtrance bids honored.
+12 -3
View File
@@ -3,7 +3,7 @@
## Conditional next-battle leader question — 28 October 2026
**Prototyped / Partial.** In a quiet Basic Storm, Spice Blow, Charity, Bidding, Revival or Shipment and Movement window with
classic factions and no optional modules, a player can ask whether another
classic or expansion factions, no Ecaz and no optional modules, a player can ask whether another
player will use a named native leader in that player's first later battle this
turn, if one occurs. A definite answer creates a waiting receipt; it does not
require a shipment, movement or battle. At the first actual battle involving
@@ -12,7 +12,9 @@ validator and guidance. If no battle occurs, the receipt expires when Battle
ends. An independently impossible answer is released by the existing battle
promise reconciliation. Another structured action answer for that respondent
is guarded while the conditional answer is active; broader promise composition,
expansion factions, optional modules and Advanced are not supported here.
Ecaz, optional modules and Advanced are not supported here. Ecaz's combined
battle may select a different lead after scheduling, so it needs its own binding
and expiry treatment before this question can be enabled in those games.
Storm requires its original post-dial, pre-movement window; Spice Blow requires
the original pre-draw window with no Nexus or worm continuation. During these
windows, Charity, Bidding and Revival, definite answers use currently available native leaders or
@@ -24,9 +26,16 @@ answer while possible. The first-battle binding and no-opportunity expiry are
provisional online interpretations, not specific publisher rulings. The
[native runtime tests](../tests/truth-future-battle-leader-runtime.test.ts) and
[Bidding continuation tests](../tests/truth-future-battle-bidding.test.ts) and
[Storm/Spice continuation tests](../tests/truth-future-battle-early.test.ts)
[Storm/Spice continuation tests](../tests/truth-future-battle-early.test.ts),
plus [Basic expansion tests](../tests/truth-future-battle-leader-expansions.test.ts),
exercise both answers and expiry without inventing a battle.
The Basic expansion widening has focused coverage of CHOAM's Yes and No in
actual battles and a Richese physical discard, Semuta pass and no-battle
expiry, plus all four minimal answer profiles. The Ecaz guard uses a staged
seat; it is not an Ecaz game journey. Semuta exchange, other expansion-faction
battle interactions, Advanced and optional modules remain unverified.
## Printed flight and pre-leader cards — 27 October 2026
**Prototyped / Partial.** `cardPlay/ornithopter` counts the first accepted