Adopt repo-owned workplan prefix per ADR-007

Retires the shared prefix. Live plans move to the new prefix keeping their
running number; finished and archived files keep the old prefix as
historical record, per the ADR-007 option 2 migration ruling.

Hub UUIDs are unchanged, so reconciliation matches on
state_hub_workstream_id rather than filename and will update the slug in
place instead of registering duplicates.

Assigned in RMGR-WP-0004-T09.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

.claude/rules/workplan-convention.md

@@ -1,7 +1,7 @@
 ## Workplan Convention (ADR-001)
 
-File location: `workplans/RAIL-BS-WP-NNNN-<slug>.md`
+File location: `workplans/RCLUSTER-WP-NNNN-<slug>.md`
-ID prefix: `RAIL-BS-WP-`
+ID prefix: `RCLUSTER-WP-`
 
 Work items originate as files in this repo **before** being registered in the hub.
 
@@ -12,7 +12,7 @@ repo state, and `finished` when implementation is complete. `stalled` and
 `needs_review` are derived health labels, not stored statuses.
 
 Closed workplans may be moved to `workplans/archived/` with a completion-date
-prefix: `YYMMDD-RAIL-BS-WP-NNNN-<slug>.md`. The frontmatter id remains
+prefix: `YYMMDD-RCLUSTER-WP-NNNN-<slug>.md`. The frontmatter id remains
 unchanged; the prefix is only for quick visual reference.
 
 Small opportunistic tasks discovered during another session use **Ad Hoc Tasks**:
@@ -29,7 +29,7 @@ Never register by hand with `create_workplan` (legacy MCP alias: `create_workstr
 Task blocks use this shape:
 
 ```task
-id: RAIL-BS-WP-NNNN-T01
+id: RCLUSTER-WP-NNNN-T01
 status: wait | todo | progress | done | cancel
 priority: high | medium | low
 state_hub_task_id: "<uuid>"         # written by fix-consistency — do not edit

AGENTS.md

@@ -169,7 +169,7 @@ get wrong.
 Work items originate as files in this repo — not in the hub. The hub is a
 read/cache/index layer that rebuilds from files.
 
-**File location:** `workplans/RAIL-BS-WP-NNNN-<slug>.md`
+**File location:** `workplans/RCLUSTER-WP-NNNN-<slug>.md`
 
 **Archived location:** finished workplans may move to
 `workplans/archived/YYMMDD-RAIL-BS-WP-NNNN-<slug>.md`. The `YYMMDD` prefix is

workplans/RCLUSTER-WP-0007-threephoenix-ha-cluster.md

@@ -1,5 +1,5 @@
 ---
-id: RAIL-BS-WP-0007
+id: RCLUSTER-WP-0007
 type: workplan
 title: "ThreePhoenix - HA Cluster Implementation"
 domain: financials
@@ -46,7 +46,7 @@ exists. `6443` is not grantable as `public`. An Ingress object is not a
 grant.
 
 The bootstrap copy of this file is retired. Do not re-open
-`RAIL-BS-WP-0007` in `railiance-bootstrap`.
+`RCLUSTER-WP-0007` in `railiance-bootstrap`.
 
 ## Why This Belongs Before Forgejo
 
@@ -106,7 +106,7 @@ The minimum S2 claim is survival of any one Kubernetes server loss while:
 ### T01 - K3s HA cluster setup
 
 ```task
-id: RAIL-BS-WP-0007-T01
+id: RCLUSTER-WP-0007-T01
 status: todo
 priority: high
 state_hub_task_id: "1f8a8668-31eb-4d79-bbcd-50f6430a8d66"
@@ -133,7 +133,7 @@ and scheduling with each server removed in turn.
 ### T02 - Longhorn distributed storage
 
 ```task
-id: RAIL-BS-WP-0007-T02
+id: RCLUSTER-WP-0007-T02
 status: todo
 priority: high
 state_hub_task_id: "b1d4e0fa-da41-4b13-a7d6-34dd040cb605"
@@ -157,7 +157,7 @@ ThreePhoenix acceptance criteria.
 ### T03 - PostgreSQL HA pattern
 
 ```task
-id: RAIL-BS-WP-0007-T03
+id: RCLUSTER-WP-0007-T03
 status: cancel
 priority: high
 state_hub_task_id: "11283b4c-7e4d-490d-91b3-0d06a593bdf0"
@@ -172,7 +172,7 @@ repmgr/Pgpool or a cluster here.
 ### T04 - Reference stateful application HA
 
 ```task
-id: RAIL-BS-WP-0007-T04
+id: RCLUSTER-WP-0007-T04
 status: cancel
 priority: high
 state_hub_task_id: "4a20e593-a89d-43da-abcc-5a39a4c8b3c0"
@@ -187,7 +187,7 @@ PVC and node disruption at the cluster layer.
 ### T05 - Traefik ingress and cert-manager SSL
 
 ```task
-id: RAIL-BS-WP-0007-T05
+id: RCLUSTER-WP-0007-T05
 status: todo
 priority: medium
 state_hub_task_id: "68315a40-dd5b-4032-a9e7-1152e38f9807"
@@ -214,7 +214,7 @@ valid certificates, and an ungranted Service stays ClusterIP.
 ### T06 - Phoenix CronJob automation
 
 ```task
-id: RAIL-BS-WP-0007-T06
+id: RCLUSTER-WP-0007-T06
 status: todo
 priority: medium
 state_hub_task_id: "f658aa6a-1c48-4660-88fa-35eaa0137e12"
@@ -238,7 +238,7 @@ without risking production data.
 ### T07 - Monitoring stack and acceptance audit checklist
 
 ```task
-id: RAIL-BS-WP-0007-T07
+id: RCLUSTER-WP-0007-T07
 status: todo
 priority: medium
 state_hub_task_id: "70f6c8ab-a700-4fb2-893e-cf5a40615044"

workplans/RCLUSTER-WP-0014-capacity-utilization-and-allocation-evidence.md

@@ -1,5 +1,5 @@
 ---
-id: RAIL-BS-WP-0014
+id: RCLUSTER-WP-0014
 type: workplan
 title: "Publish cluster capacity, utilization, and allocation evidence"
 domain: financials
@@ -17,7 +17,7 @@ related:
 state_hub_workstream_id: "ea6ec98a-0d65-4afa-b6c5-6e7ed34011ac"
 ---
 
-# RAIL-BS-WP-0014 — cluster resource evidence
+# RCLUSTER-WP-0014 — cluster resource evidence
 
 ## Goal
 
@@ -41,7 +41,7 @@ fin-hub allocate. No booked EUR in this repo.
 ## T01 — Produce periodic cluster capacity observations
 
 ```task
-id: RAIL-BS-WP-0014-T01
+id: RCLUSTER-WP-0014-T01
 status: todo
 priority: high
 state_hub_task_id: "a144bf1d-0402-4526-9bda-17846390270c"
@@ -59,7 +59,7 @@ resource-control can distinguish headroom, reservations, and actual usage.
 ## T02 — Publish the failure-domain and storage contract
 
 ```task
-id: RAIL-BS-WP-0014-T02
+id: RCLUSTER-WP-0014-T02
 status: todo
 priority: high
 state_hub_task_id: "6460d9aa-3ded-420a-bf01-f0ccdeee0a02"
@@ -76,7 +76,7 @@ state remains local to `railiance01`.
 ## T03 — Define technical allocation-driver evidence
 
 ```task
-id: RAIL-BS-WP-0014-T03
+id: RCLUSTER-WP-0014-T03
 status: todo
 priority: medium
 state_hub_task_id: "e5ff9b6c-e883-4356-9eca-b31757661d2f"