docs: refresh SCOPE and INTENT↔SCOPE gap analysis post WP-0014

SCOPE.md reflects 60-repo rollout, federation compose metrics, and open
publish/dedup blockers. IntentScopeGapAnalysis maps INTENT success criteria
to delivery and proposes priorities 25–27.

SCOPE.md

@@ -62,7 +62,8 @@ The MVP registry foundation, CLI tooling (REUSE-WP-0003), federation stack
 - **Export planning cohorts** with `reuse-surface report cohorts`
 - **Bootstrap a sibling registry** with `reuse-surface establish --scaffold`
 - **Verify index publish readiness** with `reuse-surface establish --publish-check`
-- **View registry stats** with `reuse-surface stats`
+- **View registry stats** with `reuse-surface stats` (per-repo or
+  `--roster registry/federation/local-repo-roster.yaml --federation-ready`)
 - **Draft or refresh entries** with `reuse-surface establish --discover` and
   `reuse-surface update` (optional llm-connect backend)
 - **Run the hub locally or in a container** with `reuse-surface serve`
@@ -79,13 +80,18 @@ index, CLI automation, and the production hub.
 
 - **Automatic hub refresh** — federated compose is on-demand; no polling or
   webhooks
-- **Cross-repo federation at scale** — hub has one registered repo; sibling
-  domains must publish capability indexes before registration (see
-  `history/2026-06-16-hub-registration-blocks.md`)
+- **Fully fetchable federation** — hub registers **60** workstation repos; **13**
+  still fail Gitea raw URL probe (operator visibility). See
+  `registry/federation/local-repo-roster.yaml` and
+  `history/2026-06-16-wp0014-remaining-work-by-repo.md`
+- **Clean federated ID namespace** — **16** duplicate IDs across reuse-surface
+  and owner-repo indexes until per-owner dedup (see
+  `history/2026-06-16-federation-deduplication-plan.md`)
+- **Multi-domain federation** — all indexed capabilities remain `helix_forge`
 - **Planning analytics beyond cohorts** — no gap reports, roadmap views, or
   standardization tracker beyond `report cohorts`, query, and export
 - **Managed platform posture** — hub runs as a container (A5 artifact) without
-  documented SLO, multi-replica, or Postgres backing
+  implemented SLO, multi-replica, or Postgres backing (criteria documented)
 - **Formal consumer feedback loop** for registry workflows (reliability evidence
   is mostly structural: CI/tests, not production telemetry)
 
@@ -93,25 +99,32 @@ See `tools/README.md` for command reference.
 
 ## Current State
 
-- **Status:** active MVP registry with CLI, federation, and production hub.
-- **Capabilities:** 20 helix_forge entries in `registry/capabilities/`.
+- **Status:** active MVP registry with CLI, federation, production hub, and
+  workstation-wide registry rollout (REUSE-WP-0014 finished).
+- **Capabilities (reuse-surface):** 20 helix_forge entries in
+  `registry/capabilities/` (18 owner-migrated; dedup pending).
+- **Workstation roster:** 60 local git repos at `~/<slug>/` tracked in
+  `registry/federation/local-repo-roster.yaml` — all **established**, **60/60**
+  hub-registered, **47/60** publish-check pass.
+- **Federation:** `registry/federation/sources.yaml` — **60** hub-synced URL
+  sources; `registry/indexes/federated.yaml` — **37** composed capability rows
+  (16 duplicate-ID warnings, 13 remote fetch warnings).
 - **CLI / service:** `reuse_surface/` — validate, query, export, overlaps,
-  catalog, federation, graph, hub client, `serve` (FastAPI hub).
-- **Production hub:** `https://reuse.coulomb.social` on Railiance01
-  (`92.205.62.239`); image `gitea.coulomb.social/coulomb/reuse-surface:cb7a6e4`;
-  TLS live; dogfood registration for `reuse-surface` (12 capabilities composed
-  on `/v1/federated`).
+  catalog, federation, graph, hub client, establish/update/stats, `serve`
+  (FastAPI hub).
+- **Production hub:** `https://reuse.coulomb.social` — **60** repo registrations;
+  `GET /v1/federated` serves composed index from published raw URLs.
 - **Specs:** `specs/FederationHubAPI.md`, `schemas/hub-registration.schema.yaml`.
 - **Docs:** `docs/CapabilityRegistryConcept.md`, `docs/RegistryFederation.md`,
   `docs/IntentScopeGapAnalysis.md`, deploy guide `docs/deploy/reuse-kubernetes.md`.
 - **CI:** `.gitea/workflows/ci.yml` — validate, federation compose, catalog,
   graph, pytest, informational `report cohorts`.
-- **Federated index:** `registry/indexes/federated.yaml` (local compose).
 - **Relation graph:** `docs/graph/capability-graph.mmd`, `docs/graph/index.html`.
 - **Searchable catalog:** `docs/catalog/search.html`.
-- **Workplans:** REUSE-WP-0001 through REUSE-WP-0012 finished/archived;
-  **REUSE-WP-0013** finished (registry establish/update/stats).
-- **Assessment history:** `history/2026-06-15-intent-scope-assessment.md`.
+- **Workplans:** REUSE-WP-0001 through REUSE-WP-0014 finished; archived under
+  `workplans/archived/`.
+- **Assessment history:** `history/` — intent/scope assessments, rollout
+  milestone, dedup plan, per-repo follow-up.
 - **Self-assessed vector:** `D5 / A4 / C5 / R3` (see `docs/IntentScopeGapAnalysis.md`).
 
 ## Repository Layout
@@ -130,7 +143,7 @@ reuse-surface/
 ├── registry/
 │   ├── capabilities/       # per-entry Markdown
 │   ├── indexes/            # capabilities.yaml, federated.yaml
-│   └── federation/         # sources.yaml, cache/
+│   └── federation/         # sources.yaml, local-repo-roster.yaml, cache/
 ├── docs/
 ├── tools/
 └── workplans/