Adopt repo-owned workplan prefix per ADR-007
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s

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>
This commit is contained in:
tegwick 2026-08-17 10:48:58 +02:00
parent 295ccf4e18
commit 4e655ae797
3 changed files with 13 additions and 13 deletions

View file

@ -1,7 +1,7 @@
## Workplan Convention (ADR-001)
File location: `workplans/RAIL-BS-WP-NNNN-<slug>.md`
ID prefix: `RAIL-BS-WP-`
File location: `workplans/RBS-WP-NNNN-<slug>.md`
ID prefix: `RBS-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-RBS-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: RBS-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

View file

@ -1,9 +0,0 @@
# ThreePhoenix is not owned here
`RAIL-BS-WP-0007` is S2 cluster work. The canonical file is
`railiance-cluster/workplans/RAIL-BS-WP-0007-threephoenix-ha-cluster.md`
This repo bootstraps a host and then hands off. It does not implement
k3s HA, ingress, or storage. Do not re-register `RAIL-BS-WP-0007` here
— the cluster file already holds the State Hub workstream.

View file

@ -0,0 +1,9 @@
# ThreePhoenix is not owned here
`RCLUSTER-WP-0007` is S2 cluster work. The canonical file is
`railiance-cluster/workplans/RCLUSTER-WP-0007-threephoenix-ha-cluster.md`
This repo bootstraps a host and then hands off. It does not implement
k3s HA, ingress, or storage. Do not re-register `RCLUSTER-WP-0007` here
— the cluster file already holds the State Hub workstream.