railiance-bootstrap to railiance-cluster rename cleanup

workplans/CUST-WP-0004-ep-td-tracking.md

@@ -92,7 +92,7 @@ status: done
 priority: medium
 ```
 
-Assess railiance-bootstrap and related repos for technical debt.
+Assess railiance-cluster and related repos for technical debt.
 Register findings as `TD-RAIL-xxx` items via the `/technical-debt/` API.
 
 ### P2.3 — Catalogue extension points in custodian repo

workplans/CUST-WP-0008-consistency-engine.md

@@ -82,4 +82,4 @@ state_hub_task_id: "ad2a697e-6eb4-4ccf-8c76-82984e354571"
 1. Run `check-consistency-all` to verify findings match expected issues
 2. Run `fix-consistency-all` to apply C-09 repo remaps and C-04 status drift fix
 3. Verify `activity-core-foundation` and `activity-core-triggers-ops` repo_id updated
-4. Verify railiance-bootstrap `phase-0-operational-baseline` status updated
+4. Verify railiance-cluster `phase-0-operational-baseline` status updated

workplans/CUST-WP-0010-domain-and-repo-goals.md

@@ -52,7 +52,7 @@ planning and reviewing progress.
 > phoenix server setup to provide for the coulomb infrastructure with proper
 > IT-Security, Backup and Update management in a fully automated way."
 
-**railiance-bootstrap repo goal** (active, priority 10):
+**railiance-cluster repo goal** (active, priority 10):
 > "Bootstrap a new server securely at hosteurope that can function as the
 > second kubernetes host for the railiance setup. Focus on security and single
 > server; defer automated provisioning (railiance-hosts) for now."

workplans/CUST-WP-0011-state-hub-threephoenix-migration.md

@@ -194,8 +194,14 @@ local image `state-hub:local` successfully:
 current database when run locally with host networking. Verified Alembic is
 available in-image and reports current revision `r5m6n7o8p9q0 (head)`.
 
-Remaining: choose and authenticate a registry target so the image can be
-tagged, pushed, and pulled from railiance01.
+Progress 2026-05-03: registry target decision resolved to the self-hosted
+Gitea registry. A local SSH tunnel to the NodePort can reach Gitea, but Docker
+login/push still receives HTTP 404 from `/v2/`. Runtime inspection shows the
+live Gitea `app.ini` has no `[packages]` section, so package registry
+enablement/routing must be applied before publishing `state-hub:local`.
+
+Remaining: enable the Gitea package/container registry, then tag, push, and
+pull the image from railiance01.
 
 ---
 

workplans/CUST-WP-0021-multi-host-repo-paths.md

@@ -80,7 +80,6 @@ Also register bnt-lap001 paths for all repos currently using only `local_path`
 | markitect-project | /home/worsch/markitect_project |
 | railiance-apps | /home/worsch/railiance-apps |
 | railiance-cluster | /home/worsch/railiance-cluster |
-| railiance-bootstrap | /home/worsch/railiance-cluster |
 | railiance-enablement | /home/worsch/railiance-enablement |
 | railiance-hosts | /home/worsch/railiance-infra |
 | railiance-infra | /home/worsch/railiance-infra |

workplans/CUST-WP-0031-capability-registry.md

@@ -173,7 +173,7 @@ description: >
   - kaizen-agentic (custodian domain)
   - llm-connect (custodian domain) — already has description, skip
   - markitect-project (markitect domain)
-  - railiance-bootstrap (railiance domain)
+  - railiance-cluster (railiance domain)
   - railiance-hosts (railiance domain)
   - ops-bridge (custodian domain) — already has description, skip