Canonicalize registry docs and read-only ops

workplans/FORGE-WP-0001-repository-foundation.md

@@ -4,7 +4,7 @@ type: workplan
 title: "railiance-forge repository foundation"
 domain: railiance
 repo: railiance-forge
-status: active
+status: finished
 owner: codex
 topic_slug: railiance
 planning_priority: high
@@ -115,7 +115,7 @@ file move.
 
 ```task
 id: FORGE-WP-0001-T05
-status: todo
+status: done
 priority: medium
 state_hub_task_id: "a5924b97-ccf7-4da0-acea-4f6017fef278"
 ```
@@ -129,3 +129,6 @@ Create first draft contracts for:
 - basic forge observability.
 
 Done when follow-on implementation work can be split into focused workplans.
+
+Completed in `docs/initial-operating-contracts.md`, with read-only operator
+entry points in `Makefile` and follow-on migration tracked in `FORGE-WP-0002`.

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

@@ -0,0 +1,98 @@
+---
+id: FORGE-WP-0002
+type: workplan
+title: "Canonical registry docs and read-only forge operations"
+domain: railiance
+repo: railiance-forge
+status: active
+owner: codex
+topic_slug: railiance
+planning_priority: high
+created: "2026-06-05"
+updated: "2026-06-05"
+state_hub_workstream_id: "00c57adc-b8e6-46d6-a963-d6847646a6b0"
+---
+
+# Canonical registry docs and read-only forge operations
+
+## Context
+
+The `railiance-forge` remote now exists and the repository is synced with
+State Hub. The first safe extraction step is to move registry operating
+knowledge and read-only inspection targets before moving deploy-capable Gitea
+configuration from `railiance-apps`.
+
+## T01 - Adopt canonical Gitea registry docs
+
+```task
+id: FORGE-WP-0002-T01
+status: done
+priority: high
+state_hub_task_id: "16fa09f4-f8fe-4d73-a9b1-7611bbf13dc9"
+```
+
+Move canonical container and Python package registry operation notes into
+`railiance-forge/docs/`, leaving compatibility pointers in `railiance-apps`.
+
+Done when operators can find registry endpoints, credential handling, package
+publish/install recipes, and current storage notes in this repo.
+
+---
+
+## T02 - Add read-only operator targets
+
+```task
+id: FORGE-WP-0002-T02
+status: done
+priority: high
+state_hub_task_id: "977af707-e455-4669-aeb5-62ccf31a8d55"
+```
+
+Add a forge-side `Makefile` with:
+
+- `make registry-docs`;
+- `make check-tools`;
+- `make gitea-status`.
+
+Done when the new repo can inspect current Gitea state without owning
+deploy-capable Helm or Kubernetes apply commands.
+
+---
+
+## T03 - Prepare deploy-capable Gitea move review
+
+```task
+id: FORGE-WP-0002-T03
+status: todo
+priority: high
+state_hub_task_id: "58a8073d-4665-4cf6-a1f8-e4810c7d392d"
+```
+
+Review the next candidate move from `railiance-apps`:
+
+- `helm/gitea-values.sops.yaml`;
+- `helm/gitea-registry-values.yaml`;
+- `manifests/gitea-ingress.yaml`;
+- `releases/gitea/values.yaml`;
+- `make gitea-deploy`;
+- `make gitea-ingress-deploy`.
+
+Done when the move plan is specific enough to preserve secret boundaries,
+operator compatibility, and live Gitea stability.
+
+---
+
+## T04 - Re-home parent workplan references
+
+```task
+id: FORGE-WP-0002-T04
+status: done
+priority: medium
+state_hub_task_id: "bc0daafa-0b01-479b-9f46-79c6d8fe1c0e"
+```
+
+Update `railiance-apps` docs and workplans so registry operation points to
+`railiance-forge`, while app release runbooks stay in S5.
+
+Done when the old app-side registry docs are compatibility pointers instead of
+competing canonical sources.

workplans/archived/260605-RAILIANCE-WP-0001-statehub-bootstrap.md

@@ -4,7 +4,7 @@ type: workplan
 title: "Bootstrap State Hub integration"
 domain: railiance
 repo: railiance-forge
-status: ready
+status: archived
 owner: codex
 topic_slug: railiance
 created: "2026-06-05"
@@ -14,13 +14,18 @@ state_hub_workstream_id: "96ff8f40-fc3d-4f48-94e4-c862f2eb866b"
 
 # Bootstrap State Hub integration
 
-This file defines what `railiance-forge` owns, when to use it, and where its boundaries stop.
+This generated bootstrap plan records the initial State Hub onboarding for
+`railiance-forge`.
+
+It is archived because the generated files have been reviewed, repo-specific
+instructions are present, and `FORGE-WP-0001` now carries the real repository
+foundation work.
 
 ## Review Generated Integration Files
 
 ```task
 id: RAILIANCE-WP-0001-T01
-status: todo
+status: done
 priority: high
 state_hub_task_id: "695cbdcc-ff69-4b83-9611-1080ae5a46ef"
 ```
@@ -32,7 +37,7 @@ Replace generated placeholders with repo-specific facts where needed.
 
 ```task
 id: RAILIANCE-WP-0001-T02
-status: todo
+status: done
 priority: high
 state_hub_task_id: "60d01b85-1b82-49d0-9a19-f4147f12348f"
 ```
@@ -45,7 +50,7 @@ changes confidently.
 
 ```task
 id: RAILIANCE-WP-0001-T03
-status: todo
+status: done
 priority: medium
 state_hub_task_id: "41d82631-86fb-4c2f-813d-305e0e18eab6"
 ```