docs: workplan-first agent guidance prose (CUST-WP-0055 T04 batch 2)

.claude/rules/workplan-convention.md

@@ -46,7 +46,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`.
-**Workstream** is legacy only: some API routes (`/workstreams/`), params
+**Workplan** 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

SCOPE.md

@@ -146,7 +146,7 @@ lessons into reusable S5 app release patterns.
   SOPS age-key checks, server-side manifest dry-run, and persistent-pod smoke
   testing.
 - Workplan files are now the source artifacts for planned work. State Hub
-  indexes those files as workstreams and task blocks after
+  indexes those files as workplans and task blocks after
   `make fix-consistency REPO=railiance-apps`.
 
 ---
@@ -172,7 +172,7 @@ lessons into reusable S5 app release patterns.
 ## Workplan And State Hub Model
 
 Work items originate as files in this repository under `workplans/`. State Hub
-does not own the canonical file; it indexes workplan files as hub workstreams
+does not own the canonical file; it indexes workplan files as hub workplans
 and indexes each fenced task block as a hub task.
 
 After editing workplan files, run from `~/state-hub`:
@@ -181,7 +181,7 @@ After editing workplan files, run from `~/state-hub`:
 make fix-consistency REPO=railiance-apps
 ```
 
-Use "workplan" for the repo file and "workstream" for the State Hub row created
+Use "workplan" for the repo file and "workplan" for the State Hub row created
 from that file.
 
 ---