Add optional short alliance victory
Verify and publish checkpoint container / container (push) Successful in 11m2s

This commit is contained in:
Quintine committed 2026-10-28 21:40:24 +11:00
1 parent 8fb9f59106
commit e896570f07
25 files changed
+632 -27

No files matched your search

+18
View File
@@ -16,6 +16,24 @@ open mode gates.
## Current checkpoint and work
**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
actual Mentat outcome use the same calculation. A genuine Nexus alliance with
a staged three-stronghold board tests both selected and default outcomes;
the existing four-stronghold target remains for two physical controllers as a
provisional precedence choice. The combined batch passes 96 focused cases and
three administrator boundary HTTP cases. The administrator's existing audited
lobby controls can also show and change the setting. Larger alliances, wider interactions and deployed
acceptance remain open. [Scope](OPTIONAL_ALLIANCE_VICTORY.md).
**Conditional future-battle Truthtrance in Basic Revival — 28 October.
Prototyped / Partial.** The existing phase-five question also works in a quiet
phase-four window, using leaders available at answer time without predicting a
revival. Native Revival, subsequent real battles and no-battle expiry are
covered in the 96-case combined batch. Pending transactions and broader
promise compositions remain separately guarded.
**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