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

INTENT.md

@@ -111,6 +111,6 @@ issue-core is intentionally narrow. The following live elsewhere:
 
 - `SCOPE.md` — concrete in/out-of-scope decisions and integration boundaries.
 - `ROADMAP.md` — feature trajectory.
-- `workplans/` — active workstreams.
+- `workplans/` — active workplans.
 - activity-core `docs/adr/adr-001-event-bridge-architecture.md` — the IssueSink
   contract that issue-core honors at `POST /issues/`.

SCOPE.md

@@ -165,6 +165,6 @@ mutate it.
 - `INTENT.md` — why issue-core exists and how it fits in the Coulomb org.
 - `ROADMAP.md` — feature trajectory.
 - `workplans/ISSC-WP-0001-rename-and-task-ingestion.md` — current rename +
-  ingestion workstream.
+  ingestion workplan.
 - activity-core `docs/adr/adr-001-event-bridge-architecture.md` — the upstream
   side of the IssueSink contract.

workplans/ISSC-WP-0001-rename-and-task-ingestion.md

@@ -59,7 +59,7 @@ in the Coulomb org architecture:
   Handles task creation and tracking. Has no incoming task-ingestion API from
   external callers like activity-core.
 - **State hub gap**: issue-facade is not registered in the Custodian State Hub.
-  This makes cross-repo workstream tracking impossible.
+  This makes cross-repo workplan tracking impossible.
 
 See: `docs/adr/adr-001-event-bridge-architecture.md` in activity-core for the
 IssueSink adapter design and the task emission flow.