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

Regenerate agent instructions from state-hub templates (CUST-WP-0055 T01)
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details

Browse source 
Sync AGENTS.md, CLAUDE.md, and .claude/rules from updated project_rules
templates: workplan-first session protocol, legacy terminology footnote,
and GET /workplans/ examples.
This commit is contained in:
tegwick 2026-07-08 14:50:33 +02:00
parent b525faa896
commit 3231e10625
3 changed files with 24 additions and 16 deletions
Download patch file Download diff file Expand all files Collapse all files

10
.claude/rules/first-session.md
View file

@ -20,14 +20,14 @@ roadmap phase. **Wait for approval before creating.**
workplans/RAILIANCE-WP-NNNN-<slug>.md ← write this, commit it workplans/RAILIANCE-WP-NNNN-<slug>.md ← write this, commit it
``` ```
Then register by running the consistency check — do **not** call Then register by running the consistency check — do **not** call
`create_workplan`/`create_task` (or legacy `create_workstream`) yourself; `create_workplan`/`create_task` yourself; manual registration duplicates what
manual registration duplicates what C-06 creates from the file: C-06 creates from the file:
```bash ```bash
statehub fix-consistency --repo railiance-apps statehub fix-consistency --repo railiance-apps
``` ```
C-06 creates the hub workplan + tasks and writes `state_hub_workstream_id` / C-06 creates the hub workplan + tasks and writes `state_hub_workstream_id`
`state_hub_task_id` back into the file (legacy field names, kept for (legacy frontmatter name — holds the workplan UUID) and `state_hub_task_id`
compatibility — they hold workplan/task IDs). back into the file.
**Step 5 — Record the setup** **Step 5 — Record the setup**
``` ```

14
.claude/rules/session-protocol.md
View file

@ -57,15 +57,13 @@ If no workplans: follow First Session Protocol (`first-session.md`).
**During work:** `record_decision()` · `add_progress_event()` · `resolve_decision()` **During work:** `record_decision()` · `add_progress_event()` · `resolve_decision()`
> State Hub is a *read model*. **Never register workplans or tasks by hand** > State Hub is a *read model*. **Never register workplans or tasks by hand**
> (`create_workplan`, `create_task`, or the legacy `create_workstream`) — write > (`create_workplan`, `create_task`) — write the workplan file in `workplans/`
> the workplan file in `workplans/` and run `fix-consistency`; its C-06 check > and run `fix-consistency`; C-06 registers the workplan and tasks and writes
> registers the workplan and its tasks in the hub and writes the IDs back into > IDs back into the file. Manual registration creates duplicates when
> the file. Manual registration creates duplicates the moment fix-consistency > fix-consistency runs. Work structure belongs in repo files (ADR-001).
> runs. Work structure belongs in repo files (ADR-001).
> >
> Terminology: "workstream" is the legacy name for workplan. Some API/frontmatter > Legacy: `create_workstream` and `/workstreams/` remain as metered aliases —
> field names keep it for compatibility (`state_hub_workstream_id`, > see `workplan-convention.md` (compatibility footnote).
> `workstream_id` params) — treat them as workplan IDs.
**Session close:** **Session close:**
With MCP tools: With MCP tools:

16
.claude/rules/workplan-convention.md
View file

@ -24,7 +24,7 @@ multiple planned phases into a normal workplan.
Ecosystem todos from other agents arrive as `[repo:railiance-apps]` hub tasks — Ecosystem todos from other agents arrive as `[repo:railiance-apps]` hub tasks —
visible at session start. Pick one up by creating the workplan file, committing, 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. and running `statehub fix-consistency` — C-06 registers the workplan in the hub.
Never register by hand with `create_workplan`/`create_workstream`. Never register by hand with `create_workplan` (legacy MCP alias: `create_workstream`).
Task blocks use this shape: Task blocks use this shape:
@ -39,7 +39,17 @@ Status progression is `todo` → `progress` → `done`; use `wait` for waiting o
blocked work and `cancel` for stopped work. blocked work and `cancel` for stopped work.
Workplan frontmatter carries `state_hub_workstream_id` — a legacy field name Workplan frontmatter carries `state_hub_workstream_id` — a legacy field name
kept for compatibility ("workstream" is the old term for workplan); it holds kept for compatibility; it holds the hub workplan UUID and is written by
the hub workplan id and is written by fix-consistency. Do not edit or rename it. fix-consistency. Do not edit or rename it.
### Legacy terminology (compatibility footnote)
**Workplan** is the fleet term — see
`the-custodian/canon/standards/workplan-terminology-fleet_v0.1.md`.
**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
examples and scripts.
<!-- Ralph Loop rules and HEUREKA sequence: ~/.claude/CLAUDE.md — do not duplicate here --> <!-- Ralph Loop rules and HEUREKA sequence: ~/.claude/CLAUDE.md — do not duplicate here -->