Normalize agent instructions and workplan frontmatter (STATE-WP-0067)

- Align agent files with on-disk workplan prefixes (infer from workplan ids)
- Set workplan domain to registered domain_slug; add topic_slug where applicable
- Repair frontmatter delimiter formatting; migrate legacy task status literals
- Regenerate AGENTS.md, CLAUDE.md, and .claude/rules from State Hub templates

.claude/rules/first-session.md

@@ -1,11 +1,11 @@
 ## First Session Protocol
 
-Triggered when `get_domain_summary("railiance")` shows **no workstreams**.
+Triggered when `get_domain_summary("financials")` shows **no workstreams**.
 The project is registered but work has not yet been structured.
 
 **Step 1 — Read, don't write**
-- `~/the-custodian/canon/projects/railiance/project_charter_v0.1.md` — purpose, scope
+- `~/the-custodian/canon/projects/financials/project_charter_v0.1.md` — purpose, scope
-- `~/the-custodian/canon/projects/railiance/roadmap_v0.1.md` — planned phases
+- `~/the-custodian/canon/projects/financials/roadmap_v0.1.md` — planned phases
 - Scan repo root: README, directory structure, existing code or docs
 
 **Step 2 — Survey in-progress work**
@@ -17,7 +17,7 @@ roadmap phase. **Wait for approval before creating.**
 
 **Step 4 — Create workplan file first, then DB record (ADR-001)**
 ```
-workplans/railiance-apps-WP-NNNN-<slug>.md   ← write this first
+workplans/RAILIANCE-WP-NNNN-<slug>.md   ← write this first
 ```
 Then register in the hub:
 ```
@@ -28,7 +28,7 @@ create_task(workstream_id="<id>", title="...", priority="high|medium|low")
 **Step 5 — Record the setup**
 ```
 add_progress_event(
-    summary="First session: structured railiance into N workstreams, M tasks",
+    summary="First session: structured financials into N workstreams, M tasks",
     event_type="milestone",
     topic_id="ca369340-a64e-442e-98f1-a4fa7dc74a38",
     detail={"workstreams": [...], "tasks_created": M}

.claude/rules/repo-identity.md

@@ -1,5 +1,5 @@
 **Purpose:** OAS S5 Workloads & Experience Endpoints — application Helm releases, Gitea, coulomb services
 
-**Domain:** railiance
+**Domain:** financials
 **Repo slug:** railiance-apps
 **Topic ID:** ca369340-a64e-442e-98f1-a4fa7dc74a38

.claude/rules/session-protocol.md

@@ -1,6 +1,7 @@
 ## Session Protocol
 
-State Hub: http://127.0.0.1:8000
+Dev Hub (State Hub API): http://127.0.0.1:8000
+MCP server name in `~/.claude.json`: `dev-hub`
 
 **Step 1 — Orient**
 
@@ -10,7 +11,7 @@ cat .custodian-brief.md
 ```
 Then call the MCP tool for richer cross-domain context when MCP tools are exposed:
 ```
-get_domain_summary("railiance")
+get_domain_summary("financials")
 ```
 If MCP tools are unavailable in the current agent session, use the REST API:
 ```bash
@@ -39,11 +40,11 @@ curl -s -X PATCH "http://127.0.0.1:8000/messages/<id>/read" \
 ls workplans/
 ```
 For each file with `status: ready`, `active`, or `blocked`, note pending
-`todo`/`in_progress` tasks.
+`wait`/`todo`/`progress` tasks.
 
 **Step 4 — Present brief**
 
-1. **Active workstreams** for `railiance` — title, task counts, blocking decisions
+1. **Active workstreams** for `financials` — title, task counts, blocking decisions
 2. **Pending tasks** from `workplans/` + any `[repo:railiance-apps]` hub tasks
 3. **Goal guidance** — if `goal_guidance` in summary:
    - `needs_workplan`: surface as top action — *"Repo goal '{title}' has no workplan yet"*

.claude/rules/workplan-convention.md

@@ -1,7 +1,7 @@
 ## Workplan Convention (ADR-001)
 
-File location: `workplans/railiance-apps-WP-NNNN-<slug>.md`
+File location: `workplans/RAILIANCE-WP-NNNN-<slug>.md`
-ID prefix: `RAILIANCE-WP`
+ID prefix: `RAILIANCE-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-apps-WP-NNNN-<slug>.md`. The frontmatter id remains
+prefix: `YYMMDD-RAILIANCE-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**:
@@ -25,4 +25,16 @@ Ecosystem todos from other agents arrive as `[repo:railiance-apps]` hub tasks
 visible at session start. Pick one up by creating the workplan file, then registering
 the workstream.
 
+Task blocks use this shape:
+
+```task
+id: RAILIANCE-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
+```
+
+Status progression is `todo` → `progress` → `done`; use `wait` for waiting or
+blocked work and `cancel` for stopped work.
+
 <!-- Ralph Loop rules and HEUREKA sequence: ~/.claude/CLAUDE.md — do not duplicate here -->

AGENTS.md

@@ -2,9 +2,9 @@
 
 ## Repo Identity
 
-**Purpose:** OAS S5 Workloads & Experience Endpoints — application Helm releases, app runbooks, and deployment guardrails
+**Purpose:** OAS S5 Workloads & Experience Endpoints — application Helm releases, Gitea, coulomb services
 
-**Domain:** railiance
+**Domain:** financials
 **Repo slug:** railiance-apps
 **Topic ID:** `ca369340-a64e-442e-98f1-a4fa7dc74a38`
 **Workplan prefix:** `RAILIANCE-WP-`
@@ -83,7 +83,7 @@ curl -s -X PATCH "http://127.0.0.1:8000/tasks/<task_id>" \
 1. `cat .custodian-brief.md` — domain goal and open workstreams (offline-safe)
 2. Check inbox: `GET /messages/?to_agent=railiance-apps&unread_only=true`; mark read
 3. Scan workplans: `ls workplans/` — note `status: ready`, `active`, or `blocked` files and open tasks
-4. Check blocked tasks: `GET /tasks/?needs_human=true`
+4. Check human-needed tasks: `GET /tasks/?needs_human=true`
 
 **During work:**
 - Update task statuses in workplan files as tasks progress
@@ -151,6 +151,11 @@ every repo's agent instructions because it is high-frequency, high-risk, and eas
 get wrong.
 
 **Canon:** `~/ops-warden/wiki/CredentialRouting.md` · catalog `~/ops-warden/registry/routing/catalog.yaml`
+
+<!-- REPO-AGENTS-EXTENSIONS -->
+<!-- Append repo-specific agent instructions below this marker.
+     The state-hub template sync preserves content after this line. -->
+
 ---
 
 ## Workplan Convention (ADR-001)
@@ -176,7 +181,7 @@ anything needing analysis, design, approval, dependencies, or multiple phases.
 id: RAILIANCE-WP-NNNN
 type: workplan
 title: "..."
-domain: railiance
+domain: financials
 repo: railiance-apps
 status: proposed | ready | active | blocked | backlog | finished | archived
 owner: codex
@@ -206,7 +211,7 @@ state_hub_task_id: "<uuid>"         # written by fix-consistency — do not edit
 Task description text.
 ```
 
-Status progression: `wait` → `todo` → `progress` → `done` (or `cancel`)
+Status progression: `todo` → `progress` → `done`; use `wait` for waiting/blocked work and `cancel` for stopped work.
 
 To create a new workplan:
 1. Write the file following the format above

workplans/RAILIANCE-WP-0005-s5-app-release-readiness.md

@@ -2,7 +2,7 @@
 id: RAILIANCE-WP-0005
 type: workplan
 title: "S5 app release readiness and scope alignment"
-domain: railiance
+domain: financials
 repo: railiance-apps
 status: finished
 owner: codex

workplans/RAILIANCE-WP-0006-railiance-forge-extraction.md

@@ -2,7 +2,7 @@
 id: RAILIANCE-WP-0006
 type: workplan
 title: "Extract railiance-forge and formalize forge-layer contracts"
-domain: railiance
+domain: financials
 repo: railiance-apps
 status: finished
 owner: codex

workplans/RAILIANCE-WP-0007-reuse-surface-hub-on-railiance01.md

@@ -2,7 +2,7 @@
 id: RAILIANCE-WP-0007
 type: workplan
 title: "Deploy reuse-surface federation service on railiance01"
-domain: railiance
+domain: financials
 repo: railiance-apps
 status: finished
 owner: codex

workplans/RAILIANCE-WP-0008-service-landing-pages.md

@@ -2,7 +2,7 @@
 id: RAILIANCE-WP-0008
 type: workplan
 title: "Add friendly landing pages for S5 service endpoints"
-domain: railiance
+domain: financials
 repo: railiance-apps
 status: finished
 owner: codex

workplans/RAILIANCE-WP-0009-inter-hub-chart-handoff.md

@@ -2,7 +2,7 @@
 id: RAILIANCE-WP-0009
 type: workplan
 title: "Inter-hub chart handoff"
-domain: railiance
+domain: financials
 repo: railiance-apps
 status: finished
 owner: codex

workplans/RAILIANCE-WP-0010-inbox-suggestion-guardrails.md

@@ -2,7 +2,7 @@
 id: RAILIANCE-WP-0010
 type: workplan
 title: "Inbox suggestion guardrails"
-domain: railiance
+domain: financials
 repo: railiance-apps
 status: finished
 owner: codex

workplans/RAILIANCE-WP-0011-inter-hub-production-trigger-hardening.md

@@ -2,7 +2,7 @@
 id: RAILIANCE-WP-0011
 type: workplan
 title: "Inter-Hub production trigger hardening"
-domain: railiance
+domain: financials
 repo: railiance-apps
 status: finished
 owner: codex

workplans/railiance-apps-WP-0002-vergabe-teilnahme-on-railiance01.md

@@ -2,7 +2,7 @@
 id: RAILIANCE-WP-0002
 type: workplan
 title: "Establish vergabe-teilnahme as an Application on railiance01"
-domain: railiance
+domain: financials
 repo: railiance-apps
 status: finished
 owner: railiance

workplans/railiance-apps-WP-0004-app-deployment-improvements.md

@@ -2,7 +2,7 @@
 id: RAILIANCE-WP-0004
 type: workplan
 title: "App deployment improvements (lessons from RAILIANCE-WP-0002)"
-domain: railiance
+domain: financials
 repo: railiance-apps
 status: finished
 owner: railiance