chore: treat hub bootstrap as proposed and adopt RTEL-WP- prefix

Do not deploy a monitoring stack here. Next real workplan is the
emission contract, private by default.

workplans/RAILIANCE-WP-0001-statehub-bootstrap.md

@@ -4,17 +4,29 @@ type: workplan
 title: "Bootstrap State Hub integration"
 domain: financials
 repo: railiance-telemetry
-status: ready
+status: proposed
 owner: codex
 topic_slug: railiance
 created: "2026-08-11"
-updated: "2026-08-11"
+updated: "2026-08-15"
+related:
+  - ADR-0008
+  - RMASTER-WP-0023
 state_hub_workstream_id: "60f5fe7c-9749-40be-9945-6ad608398b3f"
 ---
 
 # Bootstrap State Hub integration
 
-Observability for Railiance — monitoring, metrics, logs, traces, and alerting that turn running behaviour into evidence and give the self-organizing control loop a signal to close on.
+## Goal
+
+Finish State Hub onboarding for `railiance-telemetry`: confirm the
+generated contract files, record that this repo has no runtime yet, and
+seed the first *signal-contract* workplan. Do not deploy a monitoring
+stack here. Placement is Quality / Q2 (INTENT/SCOPE). That is not an
+open `railiance-master` question.
+
+This id uses the historical `RAILIANCE-WP-` prefix. New telemetry
+workplans use `RTEL-WP-`. Do not change this file's `id` or hub UUID.
 
 ## Review Generated Integration Files
 
@@ -25,8 +37,10 @@ priority: high
 state_hub_task_id: "de712c57-79fa-49be-97a2-873e9e1a8bec"
 ```
 
-Review `INTENT.md`, `SCOPE.md`, `AGENTS.md`, and `.custodian-brief.md`.
-Replace generated placeholders with repo-specific facts where needed.
+Confirm INTENT/SCOPE/AGENTS match the seeded Q2 evidence-plane
+boundary. Close leftover README contradictions (placement is Q2, not an
+open S3-vs-Quality question). Set the *next* workplan prefix to
+`RTEL-WP-`, not `RAILIANCE-WP-`.
 
 ## Verify Local Developer Workflow
 
@@ -37,9 +51,9 @@ priority: high
 state_hub_task_id: "79febfbb-6a67-40e0-9c24-96ff83ab706e"
 ```
 
-Identify the repo's install, test, lint, build, and run commands. Add or refine
-those commands in the agent instructions so future coding sessions can verify
-changes confidently.
+There is no implementation yet. Record that in AGENTS.md (no install /
+test / run). Do not invent a Makefile that deploys monitoring. T03 owns
+the first verification command.
 
 ## Seed First Real Workplan
 
@@ -50,8 +64,15 @@ priority: medium
 state_hub_task_id: "adea3657-c074-443b-9c5e-3c2095dd7c5b"
 ```
 
-Create the first implementation workplan for the repository's most important
-next change. After workplan file updates, run the sync locally from this repo
+Seed `RTEL-WP-0002` for the **emission contract**: what other layers
+emit, retention for restore/rollout proof, and the operator-facing
+health surface. Out of that plan: the deployable monitoring package
+(future `rapp-*`), conformance *meaning* (owning repos /
+`railiance-master`), and any public scrape/UI (forbidden until ADR-0006
+`production-approved` plus an ADR-0008 grant; default `exposure` is
+`private`).
+
+After workplan file updates, run the sync locally from this repo
 checkout:
 
 ```bash