Connect independent-card battle and arrival reactions
Verify and publish checkpoint container / container (push) Canceled after 0s
Verify and publish checkpoint container / container (push) Canceled after 0s
This commit is contained in:
1 parent
4d769af8c7
commit
6719245f40
10 files changed
+464
-9
No files matched your search
+20
-1
@@ -16,6 +16,23 @@ open mode gates.
|
||||
|
||||
|
||||
## Current checkpoint and work
|
||||
**Basic mixed-family independent-card arrival overlap — 28 October.
|
||||
Prototyped / Partial.** Selected native families with Ecaz and Moritani can
|
||||
retain the original Ambassador/Terror queue when independent Ecaz cards are
|
||||
enabled. Paid entry and both owners' actual token decisions follow the existing
|
||||
provisional storm order; other optional-module combinations remain separate.
|
||||
[Scope](MORITANI_ENTRY_TIMING.md#basic-mixed-family-independent-cards--28-october-2026).
|
||||
The mixed arrival and Semuta related union passes 93 cases, including both
|
||||
child arrivals and compatibility with an already pending discard.
|
||||
|
||||
**Semuta after battle cleanup in Basic independent cards — 28 October.
|
||||
Prototyped / Partial.** The supported Richese/classic profile now offers each
|
||||
actual losing, mandatory winning and selected winning discard batch, including
|
||||
the independent battle cards, while retaining native combat and card custody.
|
||||
Earlier pending receipts without a reaction continue automatically. The focused
|
||||
tests cover real battles, claim/pass, legal AI and compatibility; other discard
|
||||
producers and roster/module combinations remain separate.
|
||||
|
||||
**Fresh No-Field with reserves to a foreign Homeworld — 28 October.
|
||||
Prototyped / Partial.** In the native Basic/Advanced Homeworld preview,
|
||||
Richese can send selected physical reserves with its fresh concealed marker;
|
||||
@@ -168,7 +185,9 @@ published its revision tag and `checkpoint` with digest
|
||||
`sha256:74340835931011be1d0be907c8db688719f05a1a1b949ba0633eff4c5fb55248`.
|
||||
Run 7 was canceled before starting; run 8 for `e529cc2` succeeded and
|
||||
published digest `sha256:9a188718e46adec7ec9e4edc29fe03126c1afe2a349bb426052339a5ee4dce55`.
|
||||
Run 9 was canceled before starting; run 10 for `1ba9421` is running.
|
||||
Run 9 was canceled before starting; run 10 for `1ba9421` succeeded and
|
||||
published digest `sha256:2c403b71b24de97188804c874f621af5b72bc6dd807bbcdcca9cbe7ab420029c`.
|
||||
Run 11 for `4d769af` is running.
|
||||
Deployment remains unverified.
|
||||
Existing NAS deployment and its persistent storage remain untouched.
|
||||
|
||||
|
||||
Reference in new issue
Block a user