WP-0015: complete compose acceptance after Gitea visibility fix

Refresh federated index (20 capabilities, 0 duplicate warnings). Update
workplan, SCOPE, gap analysis, and tests for 59/60 publish pass. Mark
T04/T06 done; T01 remains on tegwick-control repo creation.

Note: production hub whynot URLs still need REUSE_SURFACE_TOKEN update.

docs/CapabilityCatalog.md

@@ -2,23 +2,12 @@
 
 **Domain:** helix_forge  
 **Updated:** 2026-06-16  
-**Entries:** 3
+**Entries:** 2
 
 Generated by `reuse-surface catalog`. Do not edit manually.
 
 ## helix_forge
 
-### Organizational Event Coordination
-
-- **ID:** `capability.activity.event-coordinate`
-- **Vector:** D3 / A1 / C1 / R0
-- **Owner:** activity-core
-- **Path:** `registry/capabilities/capability.activity.event-coordinate.md`
-- **Summary:** Coordinate structured responses to cross-domain events through activity workflows and automation.
-
-**Known limitations:**
-- early discovery stage
-
 ### Capability Registration
 
 - **ID:** `capability.registry.register`

docs/IntentScopeGapAnalysis.md

@@ -35,7 +35,7 @@ dimensions, and human/agent consumers.
 
 **Open gaps** (operator or follow-on workplans):
 
-1. **Gitea publish visibility** — 12/60 repos fail raw URL probe (federation fetch).
+1. **Gitea publish visibility** — 1/60 repo (`tegwick-control`) not HTTP-fetchable.
 2. **Planning analytics breadth** — gap report shipped; no roadmap views or
    standardization tracker.
 3. **Hub automation** — no polling/webhooks for federated refresh.
@@ -74,8 +74,8 @@ What `INTENT.md` still expects beyond current `SCOPE.md` delivery.
 | INTENT claim | SCOPE reality | Gap |
 |---|---|---|
 | Capabilities reusable across repos, products, orgs | 60 repos on hub; 20 federated rows | Single domain (`helix_forge`) |
-| Find capabilities before rebuilding at network scale | Hub + compose + roster | 12 indexes not HTTP-fetchable |
-| Identify duplicates (success criterion) | `overlaps` + compose (0 duplicate warnings) | `activity-core` stub until publish passes |
+| Find capabilities before rebuilding at network scale | Hub + compose + roster | `tegwick-control` not HTTP-fetchable |
+| Identify duplicates (success criterion) | `overlaps` + compose (0 duplicate warnings) | — |
 
 **Follow-up:** `history/2026-06-16-wp0014-remaining-work-by-repo.md` (Gitea);
 `history/2026-06-16-federation-deduplication-plan.md` (reuse-surface dedup).
@@ -119,7 +119,7 @@ What `INTENT.md` still expects beyond current `SCOPE.md` delivery.
 | WP-0012 | `hub sync`, cohort reports, INTENT layout, hub hardening doc | `hub_sync.py`, `docs/deploy/` |
 | WP-0013 | Registry bootstrap in sibling repos | `establish`, `update`, `stats` |
 | WP-0014 | Workstation registry rollout; hub 60 registrations | `local-repo-roster.yaml`; milestone history |
-| WP-0015-T02 | Federated ID deduplication | 3 local entries; 0 compose duplicate warnings |
+| WP-0015-T02 | Federated ID deduplication | 2 local entries; 0 compose duplicate warnings |
 | WP-0015-T03 | Planning gap report | `reuse-surface report gaps` |
 | Priority 18 | Sibling / workstation hub membership | 60/60 `hub list` |
 | Priority 19–24 | See §8 | WP-0012/0013 deliveries |
@@ -132,14 +132,14 @@ From `INTENT.md` §Success Criteria:
 
 | # | Criterion | Met? | SCOPE evidence | Remaining gap |
 |---|---|---|---|---|
-| 1 | Find reusable capabilities before rebuilding | **Yes** | Index, query, catalog, hub `/v1/federated`, federation compose | 12 sources not fetchable |
+| 1 | Find reusable capabilities before rebuilding | **Yes** | Index, query, catalog, hub `/v1/federated`, federation compose | `tegwick-control` optional source |
 | 2 | Compare maturity consistently | **Yes** | Vectors, schema, graph relations | — |
 | 3 | Distinguish conceptual readiness from delivery | **Yes** | D vs A in model and index | — |
 | 4 | Distinguish internal assessment from external evidence | **Yes** | `maturity` vs `external_evidence` | — |
 | 5 | Plan prototype/MVP/enhancement/platform work | **Partial** | `report cohorts`, `report gaps`, query | No roadmap views |
 | 6 | Identify gaps, duplicates, overlaps, standardization | **Partial** | `overlaps`, `report gaps`, deduped index | Standardization tracker |
 | 7 | Track progress to generalized capabilities (D7) | **Partial** | `promotion_history` per entry | No org-wide D7 view |
-| 8 | Make reuse normal in architecture work | **Partial** | AGENTS.md, 60-repo rollout | 12 publish blockers remain |
+| 8 | Make reuse normal in architecture work | **Partial** | AGENTS.md, 60-repo rollout | `tegwick-control` publish blocker |
 
 **Score:** 4 fully met, 4 partial — consistent with **C5** product completeness for
 known registry expectations, not yet saturated (**C6**).
@@ -158,7 +158,7 @@ known registry expectations, not yet saturated (**C6**).
 | Validation | Tooling | `validate` + CI | C5 |
 | Search / filter | Supported | query, catalog HTML | C4 |
 | Federation membership | Cross-repo | 60 hub members; compose + sync | C5 |
-| Federation fetch reliability | Published indexes | 48/60 publish pass | C4 |
+| Federation fetch reliability | Published indexes | 59/60 publish pass | C5 |
 | Workstation bootstrap | Org-wide visibility | Roster + establish tooling | C4 |
 | Agent instructions | Expected | AGENTS.md, tools README | C4 |
 | Technical consumption | A3+ tools | CLI A3, hub A4 | C4 |
@@ -166,7 +166,7 @@ known registry expectations, not yet saturated (**C6**).
 | Documentation canon | Concept + living delta | Concept doc + this file | C4 |
 
 **Overall completeness vs INTENT:** **C5** for reuse-surface product scope;
-**C4** for end-to-end fetchable federation until remaining Gitea blockers clear.
+**C5** for fetchable federation (one optional `tegwick-control` exception).
 
 ---
 
@@ -179,7 +179,7 @@ known registry expectations, not yet saturated (**C6**).
 | Production hub | `reuse.coulomb.social` — TLS, 60 registrations |
 | Workstation rollout | Deterministic establish/validate; roster tracked |
 | Consumer feedback | Informal; 3 entries with structured `consumer_feedback` |
-| Known friction | 12 Gitea 404; hub SQLite single-replica |
+| Known friction | `tegwick-control` Gitea HTTP gap; hub SQLite single-replica |
 
 **Overall reliability vs INTENT consumer-evidence framing:** **R3 (Usable)** —
 CI and production paths support normal agent/operator workflows with documented
@@ -198,7 +198,7 @@ See §4 and archived workplans `workplans/archived/`.
 
 | Priority | Gap | Suggested outcome | Status |
 |---|---|---|---|
-| 25 | Gitea publish visibility (12 repos) | Raw URL HTTP 200 for all roster rows | **REUSE-WP-0015-T01** (in progress) |
+| 25 | Gitea publish visibility (`tegwick-control`) | Raw URL HTTP 200 for all roster rows | **REUSE-WP-0015-T01** (59/60) |
 | 26 | Federated ID deduplication | Per-owner removal from reuse-surface index | **Closed** (WP-0015-T02) |
 | 27 | Planning analytics + standardization | Gap report or standardization tracker | **Partial** — gap report shipped (T03); tracker deferred |
 

docs/catalog/index.html

@@ -15,14 +15,8 @@
 </head>
 <body>
   <h1>Capability Catalog</h1>
-  <p class="subtitle">Updated 2026-06-16 · 3 entries</p>
+  <p class="subtitle">Updated 2026-06-16 · 2 entries</p>
   <section><h2>helix_forge</h2>
-<article class="card">
-  <h3>Organizational Event Coordination</h3>
-  <p class="meta"><code>capability.activity.event-coordinate</code> · D3 / A1 / C1 / R0</p>
-  <p>Coordinate structured responses to cross-domain events through activity workflows and automation.</p>
-  <p class="path">registry/capabilities/capability.activity.event-coordinate.md</p>
-</article>
 <article class="card">
   <h3>Capability Registration</h3>
   <p class="meta"><code>capability.registry.register</code> · D3 / A4 / C2 / R3</p>

docs/catalog/registry.json

@@ -2,24 +2,6 @@
   "domain": "helix_forge",
   "updated": "2026-06-16",
   "capabilities": [
-    {
-      "id": "capability.activity.event-coordinate",
-      "name": "Organizational Event Coordination",
-      "summary": "Coordinate structured responses to cross-domain events through activity workflows and automation.",
-      "vector": "D3 / A1 / C1 / R0",
-      "domain": "helix_forge",
-      "status": "draft",
-      "owner": "activity-core",
-      "path": "registry/capabilities/capability.activity.event-coordinate.md",
-      "tags": [
-        "activity",
-        "coordination",
-        "automation"
-      ],
-      "consumption_modes": [
-        "informational"
-      ]
-    },
     {
       "id": "capability.registry.register",
       "name": "Capability Registration",

docs/graph/capability-graph.mmd

@@ -1,9 +1,6 @@
 graph LR
-  capability_activity_event_coordinate["capability.activity.event-coordinate<br/>D3 / A1 / C1 / R0"]
   capability_registry_register["capability.registry.register<br/>D3 / A4 / C2 / R3"]
   capability_registry_validate["capability.registry.validate<br/>D4 / A3 / C3 / R3"]
-  capability_activity_event_coordinate -->|related_to| capability_statehub_workstream_coordinate
-  capability_activity_event_coordinate -->|related_to| capability_audit_event_retain
   capability_registry_register -->|supports| capability_feature_control_evaluate
   capability_registry_register -->|supports| capability_identity_vocabulary_canonicalize
   capability_registry_register -->|related_to| capability_registry_validate

docs/graph/index.html

@@ -17,7 +17,7 @@
   <p class="legend">Generated from entry <code>relations</code> fields. Regenerate with <code>reuse-surface graph</code>.</p>
   <pre class="mermaid" id="graph"></pre>
   <script>
-    document.getElementById('graph').textContent = "graph LR\n  capability_activity_event_coordinate[\"capability.activity.event-coordinate<br/>D3 / A1 / C1 / R0\"]\n  capability_registry_register[\"capability.registry.register<br/>D3 / A4 / C2 / R3\"]\n  capability_registry_validate[\"capability.registry.validate<br/>D4 / A3 / C3 / R3\"]\n  capability_activity_event_coordinate -->|related_to| capability_statehub_workstream_coordinate\n  capability_activity_event_coordinate -->|related_to| capability_audit_event_retain\n  capability_registry_register -->|supports| capability_feature_control_evaluate\n  capability_registry_register -->|supports| capability_identity_vocabulary_canonicalize\n  capability_registry_register -->|related_to| capability_registry_validate\n  capability_registry_validate -->|depends_on| capability_registry_register\n  capability_registry_validate -->|related_to| capability_registry_register\n";
+    document.getElementById('graph').textContent = "graph LR\n  capability_registry_register[\"capability.registry.register<br/>D3 / A4 / C2 / R3\"]\n  capability_registry_validate[\"capability.registry.validate<br/>D4 / A3 / C3 / R3\"]\n  capability_registry_register -->|supports| capability_feature_control_evaluate\n  capability_registry_register -->|supports| capability_identity_vocabulary_canonicalize\n  capability_registry_register -->|related_to| capability_registry_validate\n  capability_registry_validate -->|depends_on| capability_registry_register\n  capability_registry_validate -->|related_to| capability_registry_register\n";
   </script>
 </body>
 </html>