Enforce Atomics shipment ban across transport
Verify and publish checkpoint container / container (push) Successful in 10m7s

This commit is contained in:
Quintine committed 2026-10-29 03:03:18 +11:00
1 parent 4feb418488
commit 0f8e0b4153
17 files changed
+477 -19

No files matched your search

+16 -2
View File
@@ -17,6 +17,19 @@ open mode gates.
## Current checkpoint and work
**Aftermath shipment and Recruits Semuta — 29 October. Prototyped / Partial.**
Moritani Atomics Aftermath now blocks Spiritual accompaniment, Guild
Ambassador, cross-planet and Junction shipments, including concealed markers;
ordinary movement, reserve return and the printed Sneak Attack exception stay
available. Basic native expansion rosters can offer the independent Recruits
discard to Semuta without broadening other discard producers. Twelve related
files pass 93 cases, including actual Guild Ambassador/Atomics actions and real
Tleilaxu/Ecaz games with selected card order. Typecheck, lint and the production
build pass.
Great Maker's reserve ride classification, other Semuta producers and complete
module games remain open. [Aftermath scope](MORITANI_TERROR_RULES.md#aftermath-shipment-destinations--29-october-2026);
[Semuta scope](SEMUTA_DISCARD_CONTINUATIONS.md#recruits-with-native-expansion-factions--29-october-2026).
**Black Market knowledge and group Guild transport — 29 October. Prototyped /
Partial.** Atreides can answer the existing private auction-knowledge question
from an actual Advanced Black Market inspection. A staged group Guild ally can
@@ -643,8 +656,9 @@ published revision and checkpoint tags with digest
Run 26 was canceled before starting; run 27 for `2fe97dd` was running at the
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
canceled before starting; run 53 for `3ba9087` succeeded, including HTTP
verification and image publication. Run 54 was canceled before starting and
run 55 for `4feb418` was 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.