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

Target Gitea CI at develop
All checks were successful
Core validation / Linux core gate (push) Successful in 2m33s
Details

Browse Source
This commit is contained in:
gamer147
2026-08-03 13:44:26 -04:00
parent 71ec6e55ed
commit 6ae75b3ded
4 changed files with 13 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -958,7 +958,9 @@ do not mix mechanical moves with semantic changes.
The workflow moved to `.gitea/workflows/core-validation.yml` and matches the same-server baseline:
`ubuntu-latest`, checkout/setup-dotnet v4, setup-python v6, and Gitea-specific artifact upload. A standalone
source-only repository under an arbitrary name passes the complete core driver without sibling game/extracted
data. The first actual Linux runner result remains pending until the user adds and pushes the selected remote.
data. The rewritten repository is now published to the selected private Gitea remote on its default `develop`
branch; the workflow's push and pull-request filters target `develop`. The first actual Linux runner result
remains to be confirmed in the server UI.
**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
@@ -1306,9 +1308,9 @@ layer's rendering diverges from ADV; save layout.
---
## 8. Immediate next step
Continue step 5 of the **codebase consolidation** maintenance slice by adding and pushing the user-selected
private Gitea remote, then confirm the first hosted Linux core result. After that, make the user-owned project-
license and Kelebek-derived-material decisions required before wider distribution. Do not infer a license choice
or configure/publish a remote without the user's explicit direction.
Continue step 5 of the **codebase consolidation** maintenance slice by confirming the first hosted Linux core
result on the private Gitea `develop` branch. After that, make the user-owned project-license and Kelebek-derived-
material decisions required before wider distribution. Do not infer a license choice or change remote policy
without the user's explicit direction.
Concrete playthrough blockers may still preempt this bounded maintenance work; the consolidation effort does
not replace Phase B gameplay validation or the open cross-platform gates.