Fix marker transfer CI fixture funding
Verify and publish checkpoint container / container (push) Failing after 6m26s
Verify and publish checkpoint container / container (push) Failing after 6m26s
This commit is contained in:
1 parent
e457478f7d
commit
68643925e7
3 files changed
+27
-5
No files matched your search
@@ -17,6 +17,16 @@ open mode gates.
|
||||
|
||||
## Current checkpoint and work
|
||||
|
||||
**Gitea marker-transfer failure — 29 October. Partial.** Run #82 failed
|
||||
because its marker-transfer fixture attempted a second all-reserve Caladan
|
||||
evacuation after the marker had arrived: eight forces cost more than the
|
||||
remaining three spice. The fixture now performs that evacuation only before
|
||||
placement and declines optional native revival/Ghola through legal actions.
|
||||
Both related HTTP scenarios, quick type/lint checks and the production build
|
||||
pass locally. CI must still verify the pushed revision. CHOAM's faction guide
|
||||
also now reflects the existing Basic Kull/Tech configuration and its question
|
||||
limits. [Fixture](../tests/richese-homeworld-marker-transfer-http.test.ts).
|
||||
|
||||
**Sapho at a shared arrival — 29 October. Prototyped / Partial.**
|
||||
Supported Basic Ecaz/Moritani entries now give both reaction owners a public
|
||||
ordering opportunity before either acts. An eligible Sapho can reorder its
|
||||
|
||||
Reference in new issue
Block a user