Prototype charity Truthtrance and coalition rule foundations

docs/CURRENT_STATUS.md

@@ -16,6 +16,26 @@ open mode gates.
 
 
 ## Current checkpoint and work
+**In progress: printed three-member alliance options.** Establish a canonical
+group and unanimous admission/voluntary leaving model for the printed
+three- and four-stronghold variants. The tested, unexposed foundation handles
+membership, admission, per-edge formation age, board quotes and victory quotes;
+the existing shorter two-member target does not apply to three-member groups.
+A usable preview must connect every group member to native
+alliance consent, movement and battle restrictions, funding, faction ally
+benefits, victory and minimal legal AI. Consent, leaving behavior and shared
+benefit allocation are provisional online conventions. No group option is
+enabled or claimed complete by the standalone foundation. Allied shipment
+receipts and separation still assume a single ally, as do other engine paths.
+The combined related batch passes 189 cases, with types and lint passing.
+
+**Conditional future-battle Truthtrance in Basic Charity — 28 October.
+Prototyped / Partial.** The named-leader question also works in a quiet
+Charity window, retaining its current-leader witness, first actual battle and
+no-battle expiry. Six related offline files pass 34 cases including native
+Charity continuation and both answers. Other phase windows, factions and
+promise combinations remain separately guarded.
+
 **Optional three-stronghold two-member alliance — 28 October. Prototyped /
 Partial.** The host can select the printed shorter target; changes clear human
 readiness and the normal target remains the default. Public progress and the
@@ -74,22 +94,25 @@ 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 `71009d7`. A dedicated
+over verified SSH on the local network. 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 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. Build `02695ae` passed container startup and
+daemon; the runner reconnected. Build `02695ae` passed container startup and
 25 administrator checks, then failed one of 69 HTTP cases: the mixed Richese
 Homeworld fixture allowed an unrelated earlier automated shipment before its
 scripted two-force move. The fixture now suppresses those unrelated turns and
 asserts the zero-to-two transition; its focused HTTP case passes locally. The
 CI log did not preserve the precise earlier action, so the exact cause of its
-extra visitor remains unproven. Existing NAS deployment and its persistent
-storage remain untouched.
+extra visitor remains unproven. Gitea run 4 subsequently passed all 69 HTTP
+cases and published verified image `sha-8fb9f591060ba501ff9def8e32f8aa6e1786fc7d`.
+Run 5 for `e896570` also passed its 25 administrator checks, all 69 HTTP
+cases, restart/replacement and origin verification, and published both its
+revision-specific image and `checkpoint`. Deployment remains 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/TRUTHTRANCE_TURN_ACTIONS.md

@@ -2,7 +2,7 @@
 
 ## Conditional next-battle leader question — 28 October 2026
 
-**Prototyped / Partial.** In a quiet Basic Revival or Shipment and Movement window with
+**Prototyped / Partial.** In a quiet Basic Charity, Revival or 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
@@ -13,7 +13,7 @@ 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.
-During Revival, definite answers use currently available native leaders or
+During Charity and Revival, definite answers use currently available native leaders or
 Cheap Heroes; they do not forecast a future revival or spend its resources.
 
 The publisher's [November 2020 FAQ](https://www.gf9games.com/dune/wp-content/uploads/2020/11/Dune-FAQ-Nov-2020.pdf)