Connect Semuta with native allied retention
Verify and publish checkpoint container / container (push) Canceled after 0s

This commit is contained in:
Quintine committed 2026-10-29 03:17:07 +11:00
1 parent 4ee4d9fa10
commit 59579486a4
7 files changed
+297 -6

No files matched your search

+13 -1
View File
@@ -17,6 +17,17 @@ open mode gates.
## Current checkpoint and work
**Semuta with Moritani retention and Ixian substitution — 29 October.
Prototyped / Partial.** Supported Basic independent-card battles now retain
Moritani's allied card choice through the initial loser discard and separately
offer unkept cards afterward. The existing Ixian path offers the loser discard
before substitution and the winner's mandatory discard afterward. Six related
files pass 56 cases; their native setup fixtures stage conserved battle forces
and cards. An older Ixian fixture was repaired to complete the real battle
outcome window; the same failures reproduced at the previous commit. Typecheck,
lint and the production build pass. Advanced and other optional modules remain separate.
[Scope](SEMUTA_DISCARD_CONTINUATIONS.md#native-moritani-retention-and-ixian-substitution--29-october-2026).
**Semuta battle and special cards with native factions — 29 October.
Prototyped / Partial.** Fresh Basic Richese games with independent cards now
offer supported battle-discard batches and completed Box, Distrans, simple
@@ -684,7 +695,8 @@ isolated HTTP verification, registry login and image publication. Run 52 was
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` succeeded and published its verified image. Run 56 for
`0f8e0b4` was running at the latest check. The already-approved runner network adjustment and registry secret
`0f8e0b4` succeeded and published its verified image. Run 57 was canceled
before starting; run 58 for `4ee4d9f` 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.