Route Advanced Emperor allied auction funding
Verify and publish checkpoint container / container (push) Canceled after 0s

This commit is contained in:
Quintine committed 2026-10-29 02:48:11 +11:00
1 parent 3ba9087405
commit 599af2475d
19 files changed
+883 -35

No files matched your search

+22 -1
View File
@@ -17,6 +17,23 @@ open mode gates.
## Current checkpoint and work
**Advanced Emperor auction funding — 29 October. Prototyped / Partial.**
New ordinary and Richese auction invoices route the Emperor's direct allied
contribution to the bank under the supplied Advanced source, while direct gifts
remain buyer-owned and Basic keeps its existing payment rule. Pair and staged
classic group bids, Richese lots and selected payment effects have focused
coverage: nine changed-path files pass 69 cases, and the two related paired
Bureaucrat files pass 102 cases after updating their expectations. Typecheck,
lint and build pass.
An additional five-file legacy payment run exposed 56 failures at the previous
commit and 58 here: 55 failure names overlap, one Charity fixture failure varied
between runs, and the two new outdated expectations were corrected afterward.
Homeworld fixture repair and a clean broader run remain open. Current-turn negative bribe answers also permit group funding without
releasing the answer, and group members are excluded from bribe recipient
controls. Full group games and broader module interactions remain open.
[Payment scope](NEXUS_EMPEROR_RULES.md#advanced-emperor-contribution-recipient--29-october-2026);
[group scope](OPTIONAL_ALLIANCE_VICTORY.md#group-funding-with-negative-bribe-answers--29-october-2026).
**Advanced classic group foundation — 29 October. Prototyped / Partial.**
Staged group alliances now connect genuine Advanced Nexus consent, ordinary
multi-donor bid/shipment funding, the ending player's immediate allied
@@ -612,7 +629,11 @@ Run 24 was canceled before starting; run 25 for `83ccd71` succeeded and
published revision and checkpoint tags with digest
`sha256:4548e1501826946b3edb20ef73cf1d1be53ac15f22b472f0ef1d8b9124d7b836`.
Run 26 was canceled before starting; run 27 for `2fe97dd` was running at the
last check.
last earlier check. Run 51 for `cdc47ed` subsequently succeeded, including
isolated HTTP verification, registry login and image publication. Run 52 was
canceled before starting; run 53 for `3ba9087` was still running at the latest
check. The already-approved runner network adjustment and registry secret
remain in use; neither needed to be recreated.
Deployment remains unverified.
Existing NAS deployment and its persistent storage remain untouched.