feat(terminology): prose sweep tool and custodian workplan cleanup (CUST-WP-0055 T04)

Add sweep_workstream_prose.py for agent-guidance files, sweep active workplan
prose in-repo, tighten scan allowlist exclusions, and update ADR-001 closure
protocol to workplan-first terminology.

workplans/CUST-WP-0006-gems-state-hub.md

@@ -52,14 +52,14 @@ See companion document. Summary:
 | `Domain` | Complex | Ecosystem (implicit root) | 6 canonical domains |
 | `Topic` | Complex | Domain | Focus area / active project |
 | `ManagedRepo` | Complex | Domain | Managed git repo |
-| `Workstream` | Complex | **Repository** (currently Topic) | Work package — ADR-001 mismatch |
+| `Workplan` | Complex | **Repository** (currently Topic) | Work package — ADR-001 mismatch |
 | `SBOMSnapshot` | Complex | Repository | Does not yet exist as an entity |
-| `Task` | Atom | Workstream | ✓ correct |
-| `Decision` | Atom | Repository (currently Topic or Workstream) | Dual-attach ambiguity |
+| `Task` | Atom | Workplan | ✓ correct |
+| `Decision` | Atom | Repository (currently Topic or Workplan) | Dual-attach ambiguity |
 | `TechnicalDebt` | Atom | Repository (currently domain: str) | String FK inconsistency |
 | `ExtensionPoint` | Atom | Repository (currently domain: str) | String FK inconsistency |
 | `Contribution` | Atom | Repository (no domain FK) | No domain affiliation |
-| `ProgressEvent` | Atom | Workstream (or Topic) | Multi-attach ambiguity |
+| `ProgressEvent` | Atom | Workplan (or Topic) | Multi-attach ambiguity |
 | `SBOMEntry` | Atom | SBOMSnapshot (currently ManagedRepo) | No container |
 | `WorkstreamDependency` | Relation | Domain | Flat junction table |
 
@@ -83,12 +83,12 @@ to `domains.id`. The rename_domain API patches these manually via string updates
 there is no referential integrity. Dashboard filtering silently returns empty results
 when slugs drift.
 
-**I-2 — Workstream primary container is Topic, not Repository (critical severity)**
-GEMS §7 places `Workstream.primary = Repository`. ADR-001 states that workplans
-(the file backing a workstream) must originate in a repository. However, the current
-schema has `Workstream.topic_id NOT NULL` — Topic is the enforced primary container.
+**I-2 — Workplan primary container is Topic, not Repository (critical severity)**
+GEMS §7 places `Workplan.primary = Repository`. ADR-001 states that workplans
+(the file backing a workplan) must originate in a repository. However, the current
+schema has `Workplan.topic_id NOT NULL` — Topic is the enforced primary container.
 This is an ADR-001 violation embedded in the schema itself. There is currently no
-`repo_id` on Workstream.
+`repo_id` on Workplan.
 
 **I-3 — Decision dual attachment without clear hierarchy (medium severity)**
 `Decision` has both `topic_id` and `workstream_id` FKs, with a CHECK constraint
@@ -137,7 +137,7 @@ state_hub_task_id: "da639706-3b14-42b8-92de-b9de84dbb2be"
 
 Six decisions were escalated (see state-hub records):
 - DEC-GEMS-001: GEMS implementation architecture (typed tables vs. generic entity model)
-- DEC-GEMS-002: Workstream primary container — Topic vs. Repository
+- DEC-GEMS-002: Workplan primary container — Topic vs. Repository
 - DEC-GEMS-003: Domain string → FK migration for ExtensionPoint and TechnicalDebt
 - DEC-GEMS-004: SBOMSnapshot container entity
 - DEC-GEMS-005: Ecosystem root entity
@@ -164,7 +164,7 @@ See companion document for the full analysis. Summary verdict:
 The migration is **worth pursuing incrementally** (Pattern C from GEMS §9). The most
 impactful and least risky first move is:
 1. Fix I-1: migrate domain string → FK on EP/TD (low risk, high consistency gain)
-2. Fix I-2: add `repo_id` to Workstream (medium risk, fixes ADR-001 alignment)
+2. Fix I-2: add `repo_id` to Workplan (medium risk, fixes ADR-001 alignment)
 3. Add SBOMSnapshot container (medium risk, enables snapshot diffing)
 
 Full generic entity table architecture (Option A) is deferred until after the typed-table