Allow battle cards while Sandtrout waits
Verify and publish checkpoint container / container (push) Successful in 10m47s

This commit is contained in:
Quintine committed 2026-11-16 17:02:50 +11:00
1 parent 2cea251afd
commit 338f2d8980
13 files changed
+471 -19

No files matched your search

+13
View File
@@ -4,6 +4,19 @@ The [24 October Basic native follow-up](#basic-native-e3-admission--24-october-2
**28 September ruling and runtime:** the user selected ordinary winner retention for the physical Mirror even when its copy activates Tooth or Artillery. This is an explicit product interpretation, not a located GF9 clarification. `game/effective-weapons.ts` keeps physical identity apart from copied attacks; the engine now connects copied Tooth/Stone choices, Stone comparison, custody, battle controls and legal AI in the bounded configuration.
## Waiting Sandtrout — 16 November 2026
**Prototyped / Partial.** Waiting Sandtrout no longer disables Mirror Weapon or
Stone Burner in otherwise supported games. The ordinary Ix Spice effect stays
active until its native worm resolution; it has no printed battle-card effect.
This supersedes the earlier Sandtrout guard below. Other module and allocation
guards remain unchanged.
Focused Basic public-start cases draw the actual Sandtrout, then exercise both
weapons through selection, plans and settlement. Board forces and physical
card locations are staged. All four bot profiles submit legal candidate plans;
full combinations, complete games and deployed acceptance remain open.
## Basic native E3 admission — 24 October 2026
**Prototyped / Partial.** Bare Basic CHOAM/Richese plus Ecaz/Moritani now uses