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:59 +02:00
parent e2958489c4
commit 05a71e702f
3 changed files with 10 additions and 10 deletions

View file

@ -1,7 +1,7 @@
## Workplan Convention (ADR-001)
File location: `workplans/RAILIANCE-WP-NNNN-<slug>.md`
ID prefix: `RAILIANCE-WP-`
File location: `workplans/RFORGE-WP-NNNN-<slug>.md`
ID prefix: `RFORGE-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-RAILIANCE-WP-NNNN-<slug>.md`. The frontmatter id remains
prefix: `YYMMDD-RFORGE-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: RAILIANCE-WP-NNNN-T01
id: RFORGE-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

@ -19,7 +19,7 @@ Progress: 0/3 done | workplan_id: `72f935a5-d921-48a4-96e4-2365556c7374`
**Stale unread:** 2 message(s) older than 3 day(s) — triage at session start.
**Missing thread_id:** 2 unread message(s) lack supersession chains.
- ! resource-control: RAILIANCE-WP-0002 resource evidence handoff `2ff8381d`
- ! resource-control: RFORGE-WP-0002 resource evidence handoff `2ff8381d`
---
## MCP Orientation (when available)

View file

@ -1,5 +1,5 @@
---
id: RAILIANCE-WP-0002
id: RFORGE-WP-0002
type: workplan
title: "Publish Forgejo resource economics evidence"
domain: financials
@ -15,7 +15,7 @@ related:
state_hub_workstream_id: "72f935a5-d921-48a4-96e4-2365556c7374"
---
# RAILIANCE-WP-0002 — Forgejo resource economics evidence
# RFORGE-WP-0002 — Forgejo resource economics evidence
## Goal
@ -42,7 +42,7 @@ a separate granted surface, not this plan. Do not treat
## T01 — Measure Forgejo demand and utilization
```task
id: RAILIANCE-WP-0002-T01
id: RFORGE-WP-0002-T01
status: todo
priority: high
state_hub_task_id: "7048e354-0844-4f6c-aeaa-acf188b04ce2"
@ -58,7 +58,7 @@ idle capacity without accessing repository content or credentials.
## T02 — Declare service objectives and operations labor
```task
id: RAILIANCE-WP-0002-T02
id: RFORGE-WP-0002-T02
status: todo
priority: high
state_hub_task_id: "643c2393-2ee5-4264-972c-04c3b358dc86"
@ -74,7 +74,7 @@ constraints and labor assumptions.
## T03 — Publish shared-consumer allocation evidence
```task
id: RAILIANCE-WP-0002-T03
id: RFORGE-WP-0002-T03
status: todo
priority: medium
state_hub_task_id: "498cc0c7-ba07-4e7f-a0ef-2e6b34bef04c"