docs: add scoped registrar recovery guidance
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s

This commit is contained in:
codex 2026-08-21 21:38:35 +02:00
parent 456a80c2f6
commit 105a34784b
4 changed files with 38 additions and 7 deletions

View file

@ -17,7 +17,7 @@ roadmap phase. **Wait for approval before creating.**
**Step 4 — Write the workplan file; fix-consistency registers it (ADR-001)**
```
workplans/RAILIANCE-WP-NNNN-<slug>.md ← write this, commit it
workplans/RPF-WP-NNNN-<slug>.md ← write this, commit it
```
Then register by running the consistency check — do **not** call
`create_workplan`/`create_task` yourself; manual registration duplicates what
@ -29,6 +29,11 @@ C-06 creates the hub workplan + tasks and writes `state_hub_workstream_id`
(legacy frontmatter name — holds the workplan UUID) and `state_hub_task_id`
back into the file.
If C-06/C-11 is skipped on a non-registrar host, commit and push the workplan,
then run `uv run --project ~/repo-manager rmgr registrar-reconcile --path .
--confirm-primary --push` once. Never export registrar authority directly or
create hub rows by hand.
**Step 5 — Record the setup**
```
add_progress_event(

View file

@ -61,6 +61,10 @@ If no workplans: follow First Session Protocol (`first-session.md`).
> and run `fix-consistency`; C-06 registers the workplan and tasks and writes
> IDs back into the file. Manual registration creates duplicates when
> fix-consistency runs. Work structure belongs in repo files (ADR-001).
> A non-registrar C-06/C-11 skip is handled once with
> `uv run --project ~/repo-manager rmgr registrar-reconcile --path .
> --confirm-primary --push` after committing and pushing file-backed work.
> Never set registrar authority directly or retry the same sync repeatedly.
>
> Legacy: `create_workstream` and `/workstreams/` remain as metered aliases —
> see `workplan-convention.md` (compatibility footnote).

View file

@ -26,6 +26,18 @@ visible at session start. Pick one up by creating the workplan file, committing,
and running `statehub fix-consistency` — C-06 registers the workplan in the hub.
Never register by hand with `create_workplan` (legacy MCP alias: `create_workstream`).
If C-06/C-11 is skipped because this host is not the identifier registrar,
further retries cannot help. Do not set `STATEHUB_REGISTRAR` or create hub rows
manually. Commit and push the file-backed work, then run once:
```bash
uv run --project ~/repo-manager rmgr registrar-reconcile \
--path . --confirm-primary --push
```
If unavailable, send one deduplicated request to `repo-manager` and continue
from the authoritative files.
Task blocks use this shape:
```task
@ -46,7 +58,7 @@ fix-consistency. Do not edit or rename it.
**Workplan** is the fleet term — see
`the-custodian/canon/standards/workplan-terminology-fleet_v0.1.md`.
**Workplan** is legacy only: some API routes (`/workstreams/`), params
**Workstream** is legacy only: some API routes (`/workstreams/`), params
(`workstream_id`), MCP aliases (`create_workstream`), and the frontmatter field
above remain until `STATE-WP-0069` retires them via legacy-meter. Treat those
identifiers as workplan IDs. Prefer `GET /workplans/` and `workplan_id` in new