Scope work accross repos

SCOPE.md

@@ -123,7 +123,7 @@ characteristics support those claims.
 
 ---
 
-## Related / Overlapping Repositories
+## Related / Overlapping
 
 - `the-custodian` - coordination layer, State Hub, workplans, and capability
   catalog.

docs/scope-md-spec.md

@@ -57,7 +57,7 @@ Generated files must contain these sections, in this order:
 | `## Current State` | Observed facts aggregated by scanner: status, language, framework, tests, routes, docs, manifests | generated |
 | `## How It Fits` | Evidence/support references to other characteristics or repos; dependency facts | generated, curator-reviewed |
 | `## Terminology` | Domain term facts, names, aliases, and classification labels | generated, curator-reviewed |
-| `## Related / Overlapping Repositories` | Cross-repo support references and comparison/discovery data | generated when known, curator-reviewed |
+| `## Related / Overlapping` | Cross-repo support references and comparison/discovery data | generated when known, curator-reviewed |
 | `## Getting Oriented` | Source refs, content chunks, key files, entry points, docs, tests | generated |
 | `## Provided Capabilities` | Approved capability characteristics rendered as machine-readable `capability` blocks | generated, file-origin truth |
 | `## Notes` | Human-maintained remarks that do not fit the structured sections | curator-owned |
@@ -164,7 +164,7 @@ Generate from:
 
 Mark ambiguous or overlapping terms for curator review.
 
-### Related / Overlapping Repositories
+### Related / Overlapping
 
 Generate only when there is cross-repo evidence, comparison data, or explicit
 curator input. Do not invent related repositories from name similarity alone.
@@ -234,7 +234,7 @@ Repo-registry-generated sections:
 - Current State
 - How It Fits
 - Terminology
-- Related / Overlapping Repositories
+- Related / Overlapping
 - Getting Oriented
 - Provided Capabilities
 

src/repo_registry/scope/generator.py

@@ -17,7 +17,7 @@ SCOPE_SECTIONS = [
     "Current State",
     "How It Fits",
     "Terminology",
-    "Related / Overlapping Repositories",
+    "Related / Overlapping",
     "Getting Oriented",
     "Provided Capabilities",
     "Notes",
@@ -47,7 +47,7 @@ class ScopeGenerator:
             "Current State": self._current_state(repository.status, facts),
             "How It Fits": self._how_it_fits(ability_map),
             "Terminology": self._terminology(ability_map, facts),
-            "Related / Overlapping Repositories": self._curator_stub(),
+            "Related / Overlapping": self._curator_stub(),
             "Getting Oriented": self._getting_oriented(ability_map, facts),
             "Provided Capabilities": self._provided_capabilities(ability_map),
             "Notes": self._curator_stub(),

workplans/RREG-WP-0006-rename-to-repo-scoping-and-integrate.md

@@ -3,8 +3,8 @@ id: RREG-WP-0006
 type: workplan
 title: "Rename to repo-scoping and Full Custodian Integration"
 domain: capabilities
-repo: repo-registry
-status: active
+repo: repo-scoping
+status: done
 owner: codex
 topic_slug: foerster-capabilities
 created: "2026-04-30"
@@ -137,7 +137,7 @@ catalog entries for `scope.generate` and `scope.update` now have provider
 
 ```task
 id: RREG-WP-0006-T04
-status: in_progress
+status: done
 priority: high
 state_hub_task_id: "3f25317f-5d4e-464c-8c76-80f61d6724d3"
 ```
@@ -177,11 +177,19 @@ Custodian task `b5d5a1f2-4148-4a1e-86e0-2249f6d633cc` under `CUST-WP-0034`
 to provide the structured C5a/C5b/C5c and dispatch signals needed to unblock
 this refresh.
 
+Implementation note 2026-05-01: After State Hub exposed structured C5a/C5b/C5c
+and dispatch scope details, refreshed reachable SCOPE.md files without
+overwriting curator-owned content. Most repos needed heading-only compatibility
+updates (`Related / Overlapping`, and Railiance `Out of Scope` headings);
+`llm-connect` was upgraded from the older SCOPE format to canonical sections
+with capability blocks. Dispatch now reports `scope_needs_review: false` for
+all reachable repos.
+
 ## T05: Validate full DoI C5 pass and run consistency sync
 
 ```task
 id: RREG-WP-0006-T05
-status: todo
+status: done
 priority: medium
 state_hub_task_id: "860bbc02-c7f4-46cd-9898-41d3454c3ea5"
 ```
@@ -200,6 +208,14 @@ Acceptance: no C5a failures ecosystem-wide; the DoI summary endpoint at
 `GET /repos/doi/summary` shows improved aggregate C5 scores compared to
 pre-workplan baseline.
 
+Implementation note 2026-05-01: Refreshed the capability catalog from updated
+SCOPE.md files with the State Hub ingestion script; four new ecosystem entries
+were created, then the `llm-connect` host path was corrected and three
+llm-connect capability entries were ingested. Ran the repo-scoping consistency
+checker with `--fix`; it reported 0 fail / 0 warn / 0 info. Dispatch checks for
+repo-scoping, the-custodian, llm-connect, and markitect-project report
+`scope_needs_review: false` and C5a/C5b/C5c all pass.
+
 ## T06: Update SCOPE.md for repo-scoping itself
 
 ```task