Canonicalize registry docs and read-only ops

SCOPE.md

@@ -29,8 +29,9 @@ The practical contract is:
    paths;
 4. `railiance-apps` consumes forge artifacts and deploys user-facing workloads.
 
-No live Gitea files have been migrated here yet. This repo is being founded as
-the future home for that operational surface.
+Canonical registry operation docs and read-only forge checks now live here.
+Deploy-capable Gitea Helm/SOPS/manifests remain in `railiance-apps` until the
+explicit migration gate for live-affecting files is reviewed.
 
 ---
 
@@ -104,16 +105,20 @@ the future home for that operational surface.
 
 ## Current State
 
-- Status: founding.
-- Implementation: repository contract and first workplan are being created.
-- Stability: emerging.
-- Usage: intended as the new home for forge responsibilities currently
-  visible in `railiance-apps`.
+- Status: early extraction.
+- Implementation: repository contract, registry docs, initial operating
+  contracts, and read-only operator targets are present.
+- Stability: emerging but non-disruptive; no deploy-capable Gitea state has
+  moved yet.
+- Usage: canonical reference point for forge and registry responsibilities
+  currently transitioning out of `railiance-apps`.
 
 Known starting point:
 
 - `railiance-apps` currently owns Gitea Helm values, registry overlays, ingress,
-  Gitea Makefile targets, and registry docs.
+  and deploy-capable Gitea Makefile targets.
+- `railiance-forge` owns registry operation docs, operating contracts, and
+  read-only status entry points.
 - `railiance-enablement` owns the intent for delivery templates and developer
   paved paths, but not forge runtime operation.
 - `railiance-forge` should absorb forge runtime and artifact infrastructure
@@ -167,7 +172,9 @@ Known starting point:
 2. Read `INTENT.md` for stable purpose.
 3. Read this file for scope and boundaries.
 4. Read active files in `workplans/`.
-5. For migration context, read
+5. For registry operations, read `docs/gitea-container-registry.md` and
+   `docs/gitea-package-registry.md`.
+6. For migration context, read
    `/home/worsch/railiance-apps/workplans/RAILIANCE-WP-0006-railiance-forge-extraction.md`.
 
 ---