Use the registered REINAH-WP prefix; rename HARNESS-WP-0008 to REINAH-WP-0008

AGENTS.md named HARNESS-WP- as the prefix, but the hub's canonical prefix
for this repo is REINAH-WP- (fix-consistency C-26). Hub ids are kept so
the existing record is updated, not duplicated. Also fixes the README link
to the renamed REINAH-WP-0002 file.

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

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 269692@bnt-lap001
Assistant-Session: 8077e68a-0985-4b41-898c-2dc602b0d6be

.custodian-brief.md

@@ -2,11 +2,23 @@
 # Custodian Brief — rein-aharness
 
 **Domain:** agents  
-**Last synced:** 2026-10-13 18:43 UTC  
+**Last synced:** 2026-10-13 20:53 UTC  
 **State Hub:** http://127.0.0.1:8000 *(adjust if running on a remote machine)*
 
 ## Active Workstreams
 
+### Simpler metered retry: free rehearsal, zero-cost hold release, one-command renewal
+Progress: 0/7 done  |  workplan_id: `187c2599-84a6-5764-a14f-7e9121975bf2`
+
+**Open tasks:**
+- ! C. Envelopes that cover several attempts (decision)  `898e02af`
+- ! E. Ship the owner runtime as a container image (decision)  `b486e86b`
+- ! F. Approvals per envelope (decision)  `4cf721e6`
+- ! Retry on the corrected runtime  `80318842`
+- · A. Free rehearsal on the host  `c6536c8d`
+- · B. Release holds that provably cost nothing  `6a413f5a`
+- · D. One owner command for renewal  `87457216`
+
 ### Governed runtime integrity and intent convergence
 Progress: 3/6 done  |  workplan_id: `eba2eff1-10a7-50a3-a70b-14e7d398f27f`
 

AGENTS.md

@@ -7,12 +7,13 @@
 **Domain:** infotech
 **Repo slug:** rein-aharness
 **Topic ID:** `cee7bedf-2b48-46ef-8601-006474f2ad7a`
-**Workplan prefix:** `HARNESS-WP-`
+**Workplan prefix:** `REINAH-WP-`
 
 `REIN-A-0001` through `REIN-A-0004` are immutable historical identifiers from
-before the fleet `PREFIX-WP-NNNN` convention. Preserve them in references and
-archives, but use the registered `HARNESS-WP-` prefix for every new workplan
-and task.
+before the fleet `PREFIX-WP-NNNN` convention. `HARNESS-WP-0001` through
+`HARNESS-WP-0003` and `HARNESS-WP-ADHOC-2026-09-04` are older ids from the
+agent-harness name. Preserve all of these in references and archives, but use
+the hub-registered `REINAH-WP-` prefix for every new workplan and task.
 
 ---
 
@@ -196,10 +197,10 @@ 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/HARNESS-WP-NNNN-<slug>.md`
+**File location:** `workplans/REINAH-WP-NNNN-<slug>.md`
 
 **Archived location:** finished workplans may move to
-`workplans/archived/YYMMDD-HARNESS-WP-NNNN-<slug>.md`. The `YYMMDD` prefix is
+`workplans/archived/YYMMDD-REINAH-WP-NNNN-<slug>.md`. The `YYMMDD` prefix is
 the completion/archive date; the frontmatter `id` does not change.
 
 **Ad Hoc Tasks:** small opportunistic fixes discovered during a session use
@@ -211,7 +212,7 @@ anything needing analysis, design, approval, dependencies, or multiple phases.
 
 ```yaml
 ---
-id: HARNESS-WP-NNNN
+id: REINAH-WP-NNNN
 type: workplan
 title: "..."
 domain: infotech
@@ -239,7 +240,7 @@ API/MCP/frontmatter bridges until `STATE-WP-0069` retires them — see
 ## Task Title
 
 ` ` `task
-id: HARNESS-WP-NNNN-T01
+id: REINAH-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
@@ -252,7 +253,7 @@ Status progression: `todo` → `progress` → `done`; use `wait` for waiting/blo
 
 **Residuals when finishing:** actionable leftovers become live work records
 before `status: finished` — usually an intake (`origin: residual`,
-`origin_ref: HARNESS-WP-NNNN`) or a spawned workplan. Residual is a *role*,
+`origin_ref: REINAH-WP-NNNN`) or a spawned workplan. Residual is a *role*,
 not a kind. Fleet list lives on State Hub, not in `SCOPE.md`.
 
 To create a new workplan:

README.md

@@ -19,7 +19,7 @@ renamed. Deploy artifacts (Docker image tag, k8s namespace, Railiance host
 paths) are renamed in this repo too, but the live Railiance cutover itself
 (moving the host-side checkout + secrets dir, redeploying) is a separate,
 deliberate step — tracked in
-[workplans/HARNESS-WP-0002](workplans/HARNESS-WP-0002-rename-and-glas-harness-alignment.md)
+[workplans/REINAH-WP-0002](workplans/REINAH-WP-0002-rename-and-glas-harness-alignment.md)
 and [deploy/README.md](deploy/README.md)'s rename cutover checklist.
 
 - Why and boundaries: [INTENT.md](INTENT.md)

workplans/REINAH-WP-0008-simpler-metered-retry.md

@@ -1,5 +1,5 @@
 ---
-id: HARNESS-WP-0008
+id: REINAH-WP-0008
 type: workplan
 title: "Simpler metered retry: free rehearsal, zero-cost hold release, one-command renewal"
 domain: infotech
@@ -12,9 +12,10 @@ created: "2026-10-13"
 updated: "2026-10-13"
 related:
   - REINAH-WP-0003
+state_hub_workstream_id: "187c2599-84a6-5764-a14f-7e9121975bf2"
 ---
 
-# HARNESS-WP-0008 — Simpler metered retry
+# REINAH-WP-0008 — Simpler metered retry
 
 ## Origin
 
@@ -44,9 +45,10 @@ once, run.
 ## A. Free rehearsal on the host
 
 ```task
-id: HARNESS-WP-0008-T01
+id: REINAH-WP-0008-T01
 status: todo
 priority: high
+state_hub_task_id: "c6536c8d-7862-5de6-ad2b-401077b60c04"
 ```
 
 Add `rein-aharness owner check --rehearse <owner.json>`. It runs everything
@@ -68,9 +70,10 @@ step before any paid attempt.
 ## B. Release holds that provably cost nothing
 
 ```task
-id: HARNESS-WP-0008-T02
+id: REINAH-WP-0008-T02
 status: todo
 priority: high
+state_hub_task_id: "6a413f5a-4ac2-5d5e-9b19-71b33445c0a9"
 ```
 
 `SpendLedger.reconcile` keeps the full hold (`max(held, observed)`). Add an
@@ -92,9 +95,10 @@ release.
 ## D. One owner command for renewal
 
 ```task
-id: HARNESS-WP-0008-T03
+id: REINAH-WP-0008-T03
 status: todo
 priority: high
+state_hub_task_id: "87457216-2371-51ca-b3d4-3917e6f180a2"
 ```
 
 Add `rein-aharness owner renew --owner <owner.json> --runtime <digest>
@@ -117,9 +121,10 @@ reservation refuses. No digest has to be typed by hand.
 ## C. Envelopes that cover several attempts (decision)
 
 ```task
-id: HARNESS-WP-0008-T04
+id: REINAH-WP-0008-T04
 status: wait
 priority: medium
+state_hub_task_id: "898e02af-51bb-5e8d-93d0-ae908466c612"
 ```
 
 Owner decision: should future envelopes be admitted as "up to N attempts
@@ -130,9 +135,10 @@ as a decision note in `docs/`. T03's envelope format then reflects it.
 ## E. Ship the owner runtime as a container image (decision)
 
 ```task
-id: HARNESS-WP-0008-T05
+id: REINAH-WP-0008-T05
 status: wait
 priority: low
+state_hub_task_id: "b486e86b-9d0f-501d-a394-771b40f771ee"
 ```
 
 Decision for later, with Platform (railiance) and Sand-boxer: should the
@@ -143,9 +149,10 @@ here. If accepted, hand it off as a residual intake to the owning repos.
 ## F. Approvals per envelope (decision)
 
 ```task
-id: HARNESS-WP-0008-T06
+id: REINAH-WP-0008-T06
 status: wait
 priority: low
+state_hub_task_id: "4cf721e6-724b-5c64-91bb-67b098bb97af"
 ```
 
 Decision for later, with Secrets Engine: should one approval set cover an
@@ -155,9 +162,10 @@ lives outside this repo. If accepted, hand it off as a residual intake.
 ## Retry on the corrected runtime
 
 ```task
-id: HARNESS-WP-0008-T07
+id: REINAH-WP-0008-T07
 status: wait
 priority: high
+state_hub_task_id: "80318842-ccaa-5484-a54a-3d9981eaec8b"
 ```
 
 Waits on T01 and T03. It does not need T02.