Refresh agent instruction files

.claude/rules/architecture.md

@@ -5,4 +5,4 @@
 
 ## Quick Reference
 
-`~/the-custodian/state-hub/mcp_server/TOOLS.md` — MCP tool reference
+`~/state-hub/mcp_server/TOOLS.md` — MCP tool reference

.claude/rules/first-session.md

@@ -21,7 +21,7 @@ workplans/ihp-railiance-probe-WP-NNNN-<slug>.md   ← write this first
 ```
 Then register in the hub:
 ```
-create_workstream(topic_id="(none)", title="...", owner="...", description="...")
+create_workstream(topic_id="595afc64-bd28-47bf-aafb-ba230b28371b", title="...", owner="...", description="...")
 create_task(workstream_id="<id>", title="...", priority="high|medium|low")
 ```
 
@@ -30,7 +30,7 @@ create_task(workstream_id="<id>", title="...", priority="high|medium|low")
 add_progress_event(
     summary="First session: structured stack into N workstreams, M tasks",
     event_type="milestone",
-    topic_id="(none)",
+    topic_id="595afc64-bd28-47bf-aafb-ba230b28371b",
     detail={"workstreams": [...], "tasks_created": M}
 )
 ```

.claude/rules/repo-boundary.md

@@ -4,5 +4,5 @@ This repo owns **ihp-railiance-probe** only. It does not own:
 
 <!-- TODO: List what belongs in adjacent repos, e.g.:
 - SSH key management → railiance-infra/
-- State hub code     → the-custodian/state-hub/
+- State hub code     → state-hub/
 -->

.claude/rules/repo-identity.md

@@ -1,6 +1,5 @@
-**Purpose:** ihp-railiance-probe — (fill in purpose)
+**Purpose:** ihp-railiance-probe - (fill in purpose)
 
 **Domain:** stack
 **Repo slug:** ihp-railiance-probe
-**Topic slug:** stack
 **Topic ID:** 595afc64-bd28-47bf-aafb-ba230b28371b

.claude/rules/session-protocol.md

@@ -8,24 +8,38 @@ Read the offline-safe brief first — it works without a live hub connection:
 ```bash
 cat .custodian-brief.md
 ```
-Then call the MCP tool for richer cross-domain context (skip if unreachable):
+Then call the MCP tool for richer cross-domain context when MCP tools are exposed:
 ```
 get_domain_summary("stack")
 ```
-If the hub is offline: `cd ~/the-custodian/state-hub && make api`
+If MCP tools are unavailable in the current agent session, use the REST API:
+```bash
+curl -s "http://127.0.0.1:8000/state/summary" | python3 -m json.tool
+```
+If the hub is offline: `cd ~/state-hub && make api`
 
 **Step 2 — Check inbox**
+With MCP tools:
 ```
 get_messages(to_agent="ihp-railiance-probe", unread_only=True)
 ```
 Mark read with `mark_message_read(message_id)`. Reply or act on coordination
 requests before proceeding.
 
+Without MCP tools:
+```bash
+curl -s "http://127.0.0.1:8000/messages/?to_agent=ihp-railiance-probe&unread_only=true" \
+  | python3 -m json.tool
+curl -s -X PATCH "http://127.0.0.1:8000/messages/<id>/read" \
+  -H "Content-Type: application/json" -d '{}'
+```
+
 **Step 3 — Scan workplans**
 ```bash
 ls workplans/
 ```
-For each file with `status: active`, note pending `todo`/`in_progress` tasks.
+For each file with `status: ready`, `active`, or `blocked`, note pending
+`todo`/`in_progress` tasks.
 
 **Step 4 — Present brief**
 
@@ -45,18 +59,25 @@ If no workstreams: follow First Session Protocol (`first-session.md`).
 > are First Session Protocol only. Work structure belongs in repo files (ADR-001).
 
 **Session close:**
+With MCP tools:
 ```
-add_progress_event(summary="...", topic_id="(none)", workstream_id="<uuid>")
+add_progress_event(summary="...", topic_id="595afc64-bd28-47bf-aafb-ba230b28371b", workstream_id="<uuid>")
+```
+Without MCP tools:
+```bash
+curl -s -X POST http://127.0.0.1:8000/progress/ \
+  -H "Content-Type: application/json" \
+  -d '{"topic_id":"595afc64-bd28-47bf-aafb-ba230b28371b","workstream_id":"<uuid>","event_type":"note","summary":"what changed","author":"codex"}'
 ```
 If workplan files were modified, ensure the local copy is up to date first:
 ```bash
 git -C <repo_path> pull --ff-only
-cd ~/the-custodian/state-hub && make fix-consistency REPO=ihp-railiance-probe
+cd ~/state-hub && make fix-consistency REPO=ihp-railiance-probe
 ```
 For repos where implementation runs on a remote machine (e.g. CoulombCore),
 use the combined target which pulls before fixing:
 ```bash
-cd ~/the-custodian/state-hub && make fix-consistency-remote REPO=ihp-railiance-probe
+cd ~/state-hub && make fix-consistency-remote REPO=ihp-railiance-probe
 ```
 **C-15** (DB task ahead of file) is normal in multi-machine workflows — writeback
 will sync the file to match DB.  **C-16** (repo behind remote) blocks all writes

.claude/rules/workplan-convention.md

@@ -5,6 +5,12 @@ ID prefix: `IHP-WP`
 
 Work items originate as files in this repo **before** being registered in the hub.
 
+Canonical workplan/workstream frontmatter statuses are:
+`proposed`, `ready`, `active`, `blocked`, `backlog`, `finished`, `archived`.
+Use `proposed` for a newly drafted plan, `ready` after review against current
+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-ihp-railiance-probe-WP-NNNN-<slug>.md`. The frontmatter id remains
 unchanged; the prefix is only for quick visual reference.