coulomb/railiance-platform
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

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

Browse source
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
Download patch file Download diff file Expand all files Collapse all files

14
.claude/rules/workplan-convention.md
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