Prototype conditional future battle Truthtrance

docs/CURRENT_STATUS.md

@@ -16,6 +16,16 @@ open mode gates.
 
 
 ## Current checkpoint and work
+**Conditional future-battle Truthtrance — 28 October. Prototyped / Partial.**
+A quiet Basic classic game can ask whether a named native leader will be used
+in the respondent's first later battle this turn, if there is one. The answer
+waits for the actual battle, constrains its plan and expires without forcing a
+fight. Controls include a persistent own reminder; all four AI profiles can
+answer and follow the native plan. Six related offline files pass 49 cases and
+the application builds. The conditional timing is provisional; combinations,
+expansion factions, Advanced and deployed acceptance remain open.
+[Scope](TRUTHTRANCE_TURN_ACTIONS.md#conditional-next-battle-leader-question--28-october-2026).
+
 **Kull during Basic Guild shipment and Revival responses — 28 October.
 Prototyped / Partial.** Native CHOAM/Richese Kull interruptions can suspend
 eligible Karama responses while their original shipment or Revival remains
@@ -46,12 +56,16 @@ parents, optional modules and deployed acceptance remain open.
 
 **In progress: Gitea migration — 28 October.** The local `origin` now tracks
 `https://git.juiced.computer/admin/Dune`. A repository-scoped deploy key pushes
-over verified SSH on the local network; `main` reached `91ce096`. A dedicated
+over verified SSH on the local network; `main` reached `71009d7`. A dedicated
 repository-scoped TrueNAS runner is active with its own Docker daemon and a
 package-write Actions secret is configured for Gitea's registry. The first
-Gitea-native build and image publication are in progress and require observed
-success before the migration is certified. Existing NAS deployment and its
-persistent storage remain untouched.
+Gitea-native job built the application but its isolated HTTP check failed:
+job and test-container loopback addresses are in separate nested Docker
+network namespaces. With user approval the dedicated runner now shares its
+own network namespace with its jobs, while retaining its separate Docker
+daemon; the runner reconnected. A fresh end-to-end build and registry
+publication remain unverified. Existing NAS deployment and its persistent
+storage remain untouched.
 
 **Semuta before Basic Moritani ally retention — 28 October. Prototyped /
 Partial.** In the bare Basic Semuta preview, mandatory loser cards form an

docs/RULE_DECISIONS.md

@@ -1,5 +1,13 @@
 # Rule decision index
 
+## Conditional future-battle leader question — 28 October 2026
+
+The printed current-turn question can provisionally refer to a named native
+leader in the respondent's first later battle, conditional on one occurring.
+An actual battle binds the existing plan rules; no battle ends the opportunity
+without forcing one. This digital timing interpretation and its limited Basic
+scope are described in [the feature contract](TRUTHTRANCE_TURN_ACTIONS.md#conditional-next-battle-leader-question--28-october-2026).
+
 ## Kull and Semuta in Basic battle preparation — 28 October 2026
 
 The printed Kull power interrupts another player's Karama activation. In the

docs/TRUTHTRANCE_TURN_ACTIONS.md

@@ -1,5 +1,26 @@
 # Truthtrance combined current-turn actions
 
+## Conditional next-battle leader question — 28 October 2026
+
+**Prototyped / Partial.** In a quiet Basic Shipment and Movement window with
+classic factions 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
+that player the receipt binds its real battle event and uses the native plan
+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.
+
+The publisher's [November 2020 FAQ](https://www.gf9games.com/dune/wp-content/uploads/2020/11/Dune-FAQ-Nov-2020.pdf)
+permits game-related current-turn action questions and requires honoring an
+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)
+exercise both answers and expiry without inventing a battle.
+
 ## Printed flight and pre-leader cards — 27 October 2026
 
 **Prototyped / Partial.** `cardPlay/ornithopter` counts the first accepted