conco/OpenMaidEngine
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 3 Wiki Activity

Record hosted Linux artifact acceptance

Browse Source
This commit is contained in:
gamer147
2026-08-03 19:07:02 -04:00
parent 400f431652
commit 51ce6cfca9
2 changed files with 9 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
docs/platform-portability.md
View File

@@ -64,9 +64,11 @@ publish peaks at 223,764 KiB, so nesting the latter under the former can cross a
The build now serializes those peaks: it creates the exact self-contained publish first with compiler/build
servers disabled, lets the real Godot export consume a strictly validated one-assembly proxy publish, and stages
the complete external managed payload only after Godot exits. The complete revised path passes locally, including
payload verification and the packaged opcode/FFmpeg smoke gate. The hosted retry remains the acceptance gate for
the mitigation plus cache/artifact action behavior; release publication is intentionally deferred until it
succeeds. The workflow reports both host memory and cgroup limits to make any further runner constraint explicit.
payload verification and the packaged opcode/FFmpeg smoke gate. The hosted retry at `400f431` then completed
successfully on 2026-08-03, accepting the mitigation and the complete build/smoke/artifact-upload path on the
target runner. The workflow reports both host memory and cgroup limits for future diagnostics. Release
publication remains a separate tag-only promotion step; it should consume this already-verified artifact rather
than rebuilding it.
## Dependency inventory

7
docs/remake-architecture-and-roadmap.md
View File

@@ -1010,9 +1010,10 @@ do not mix mechanical moves with semantic changes.
isolated publish peak, explaining why the nested processes can exceed a roughly 1 GiB cgroup. The build now
runs the exact self-contained publish first, substitutes a tightly validated one-assembly publish while Godot
creates the real PCK/executable, and stages the full external managed payload after the editor exits. The
revised complete build, payload verification, and packaged smoke gate pass locally; a hosted retry is the
immediate acceptance gate. Once that succeeds, the next bounded slice can promote an already-verified tag
artifact to a Gitea release without rebuilding it.
revised complete build, payload verification, and packaged smoke gate pass locally. The hosted retry at
`400f431` completed successfully on 2026-08-03, accepting the mitigation and full artifact-upload path on the
target Gitea runner. The next bounded slice can promote an already-verified tag artifact to a Gitea release
without rebuilding it.
**Not cleanup targets:** generated `build/` output, the two intentional solution files, historical
`docs/superpowers/` plans/specifications, and fidelity-specific complexity that is directly covered by the