Finish first repo-family materialization wave

workplans/RAILIANCE-WP-0017-rail-rapp-reef-repo-separation.md

@@ -218,7 +218,7 @@ Apply the new reef model to the current Railiance substrate reality and decide
 whether the first rollout should be:
 
 - `reef-coulombcore`
-- `reef-railiance01`
+- `reef-railiance`
 - `reef-workstation`
 - or a grouped substrate such as `reef-ops-workstations`
 
@@ -239,7 +239,7 @@ Acceptance:
 
 2026-07-25: Added `docs/reef-first-wave-rollout.md` and
 `docs/adr/ADR-0004-first-wave-reef-rollout.md`. The first rollout is now
-`reef-railiance01`, `reef-coulombcore`, and `reef-ops-workstations`, with
+`reef-railiance`, `reef-coulombcore`, and `reef-ops-workstations`, with
 `railiance-infra` chosen as the canonical S1 ownership repo and transitional
 substrate nicknames intentionally left provisional.
 

workplans/RAILIANCE-WP-0018-first-wave-repo-family-materialization.md

@@ -4,13 +4,13 @@ type: workplan
 title: "First-Wave Repo Family Materialization"
 domain: financials
 repo: railiance-master
-status: active
+status: finished
 owner: codex
 topic_slug: railiance
 planning_priority: high
 planning_order: 18
 created: "2026-07-25"
-updated: "2026-07-25"
+updated: "2026-07-26"
 related_repos:
   - railiance-master
   - railiance-cluster
@@ -76,7 +76,7 @@ When this workplan is complete:
    `rapp-*`, and `reef-*` repos.
 2. The first concrete `rail-kubernetes` repo exists and is registered.
 3. The first concrete `rapp-openbao` repo exists and is registered.
-4. The first concrete `reef-railiance01` repo exists and is registered.
+4. The first concrete `reef-railiance` repo exists and is registered.
 5. Fabric can project the minimum rail/rapp/reef relation topology needed to
    answer placement questions.
 
@@ -120,7 +120,7 @@ Acceptance:
 
 ```task
 id: RAILIANCE-WP-0018-T02
-status: progress
+status: done
 priority: high
 state_hub_task_id: "726a0c5c-2fa5-4bb9-a730-3200abc40ac8"
 ```
@@ -151,6 +151,13 @@ but the registry endpoint at `http://127.0.0.1:8765` refused the connection.
 The repo is now remote-backed and source-registered, while live registry
 ingestion remains blocked on the local Fabric registry service being up.
 
+2026-07-25: Started the local Fabric registry service and completed the
+targeted live sync for `rail-kubernetes`. The repo is now State Hub
+registered, source-registered in the Fabric onboarding manifest, remote-backed
+in Forgejo, and live-ingested into the Fabric registry. Remaining wave-1
+`rail-kubernetes` work is now about helper scripts and command
+implementations rather than registration.
+
 2026-07-25: Imported the first core generic contract artifacts into
 `rail-kubernetes`: the canonical deployment lifecycle doc, the canonical
 `railiance/app.toml` contract doc, the machine-readable schema, and the example
@@ -163,11 +170,15 @@ deploy/observe contract, promotion/rollback guide, and Stage 1 run-command
 contract. Remaining wave-1 import debt is now mainly helper scripts and command
 implementations rather than core contract documentation.
 
+2026-07-25: Closed T02 after confirming the first-class repo baseline, source
+declaration, compatibility path, remote registration, State Hub registration,
+and live Fabric ingestion are all in place for `rail-kubernetes`.
+
 ## T03 - Launch the first `rapp-openbao` repo materialization
 
 ```task
 id: RAILIANCE-WP-0018-T03
-status: wait
+status: done
 priority: high
 state_hub_task_id: "3e46e1bd-c730-4e41-a00a-6aa7a4645023"
 ```
@@ -182,17 +193,27 @@ Acceptance:
 - the repo declares supported rails and rollout/smoke/rollback contract
 - the remaining ownership boundary with `railiance-platform` stays explicit
 
-## T04 - Launch the first `reef-railiance01` repo materialization
+2026-07-25: Confirmed that `/home/worsch/rapp-openbao` does not yet exist.
+Bootstrap will start from the boundary and first move set already recorded in
+`railiance-platform/docs/rapp-openbao-boundary.md`.
+
+2026-07-25: Bootstrapped `/home/worsch/rapp-openbao` with the first-wave repo
+baseline, `declarations/rapp.yaml`, a package-local Makefile, repo-local docs,
+the first imported OpenBao package assets from `railiance-platform`, and
+`RAPP-OPENBAO-WP-0001`. The repo is now registered in State Hub; Fabric
+registry onboarding remains open as repo-local follow-up work.
+
+## T04 - Launch the first `reef-railiance` repo materialization
 
 ```task
 id: RAILIANCE-WP-0018-T04
-status: wait
+status: done
 priority: medium
 state_hub_task_id: "f6f2ea73-0ff3-4cfa-b7a7-7b71db3afb4a"
 ```
 
 Create the concrete repo bootstrap and substrate declaration for
-`reef-railiance01` as the first durable reef repo.
+`reef-railiance` as the first grouped home reef repo.
 
 Acceptance:
 
@@ -202,11 +223,21 @@ Acceptance:
 - the repo stays compatible with the canonical S1 ownership role of
   `railiance-infra`
 
+2026-07-26: Corrected the first-wave home reef target from singleton
+`reef-railiance01` to grouped `reef-railiance`, updated the framework and S1
+source docs accordingly, and bootstrapped `/home/worsch/reef-railiance` with
+the baseline repo files, grouped reef declaration, substrate/topology files,
+repo-local docs, and `REEF-RAILIANCE-WP-0001`. The repo is now remote-backed in
+Forgejo, registered in State Hub, added to
+`railiance-fabric/registry/railiance-repos.yaml`, and live-ingested into the
+Fabric registry as `repo_family: reef` with `primary_rail: rail-kubernetes`
+and `substrate_kind: server-group`.
+
 ## T05 - Add relation projection for rails, `rapp`s, and reefs in Fabric
 
 ```task
 id: RAILIANCE-WP-0018-T05
-status: wait
+status: done
 priority: medium
 state_hub_task_id: "ef999db5-e75e-467a-a72a-d45fda2b6fa7"
 ```
@@ -223,11 +254,18 @@ Acceptance:
 - the projection path is grounded in repo-local declarations rather than
   registry-only guesses
 
+2026-07-26: Completed the Fabric relation-projection slice in
+`railiance-fabric`. Repository records now retain local checkout paths, the
+registry combined graph reopens repo-local `rail`, `rapp`, and `reef` files to
+project `governed_by`, `supports_rail`, `hosts_rail`, and `binds_rapp`, and
+the graph explorer preserves the declaration evidence on projected repository
+nodes. Focused Fabric tests passed after the projection update.
+
 ## T06 - Verify first-wave registration and coordination end to end
 
 ```task
 id: RAILIANCE-WP-0018-T06
-status: wait
+status: done
 priority: medium
 state_hub_task_id: "5834f122-b9e9-41c1-93e9-d5525cd720bf"
 ```
@@ -245,14 +283,22 @@ Acceptance:
 - cross-repo ownership and runtime relations are queryable
 - the wave can continue to second candidates without redefining the bootstrap model
 
+2026-07-26: Verified the first-wave coordination path end to end. The live
+Fabric registry at `http://127.0.0.1:8765` now stores the local paths and
+repo-family metadata for `rail-kubernetes`, `rapp-openbao`, and
+`reef-railiance`, and its graph-explorer export emits live `governed_by`,
+`supports_rail`, and `hosts_rail` edges from repo-local declarations. State
+Hub consistency sync remains clean for the framework and repo-local workplans,
+so the first wave can continue without reopening the bootstrap model.
+
 ## Exit Criteria
 
 - [x] The first-wave bootstrap contract is published
-- [ ] `rail-kubernetes` exists as a first-class repo baseline
-- [ ] `rapp-openbao` exists as a first-class repo baseline
-- [ ] `reef-railiance01` exists as a first-class repo baseline
-- [ ] Fabric projects the minimum rail/rapp/reef relation topology
-- [ ] State Hub and Fabric can coordinate the first concrete repo-family wave end to end
+- [x] `rail-kubernetes` exists as a first-class repo baseline
+- [x] `rapp-openbao` exists as a first-class repo baseline
+- [x] `reef-railiance` exists as a first-class repo baseline
+- [x] Fabric projects the minimum rail/rapp/reef relation topology
+- [x] State Hub and Fabric can coordinate the first concrete repo-family wave end to end
 
 ## Notes