coulomb/railiance-forge
2
0
Fork 0
generated from coulomb/repo-seed
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Prepare Gitea move review

Browse Source
This commit is contained in:
Bernd Worsch
2026-06-05 12:17:07 +02:00
parent 549544531f
commit 13cd856249
2 changed files with 131 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

21
workplans/FORGE-WP-0002-registry-docs-and-readonly-ops.md
View File

@@ -63,7 +63,7 @@ deploy-capable Helm or Kubernetes apply commands.
```task
id: FORGE-WP-0002-T03
status: todo
status: done
priority: high
state_hub_task_id: "58a8073d-4665-4cf6-a1f8-e4810c7d392d"
```
@@ -80,6 +80,8 @@ Review the next candidate move from `railiance-apps`:
Done when the move plan is specific enough to preserve secret boundaries,
operator compatibility, and live Gitea stability.
Completed in `docs/deploy-capable-gitea-move-review.md`.
---
## T04 - Re-home parent workplan references
@@ -96,3 +98,20 @@ Update `railiance-apps` docs and workplans so registry operation points to
Done when the old app-side registry docs are compatibility pointers instead of
competing canonical sources.
---
## T05 - Execute reviewed deploy-capable move
```task
id: FORGE-WP-0002-T05
status: todo
priority: high
state_hub_task_id: "6f6fc3a4-a883-4803-84e7-2700629d397a"
```
After operator review, move deploy-capable Gitea files and commands into
`railiance-forge` with app-side compatibility targets.
Done when `railiance-forge` owns Gitea deploy/status/ingress commands and
`railiance-apps` no longer carries live forge deployment files as S5 scope.