WP-0015: roster publish sweep 59/60, dedup activity-core stub

Mark 11 formerly-blocked repos publish pass after Gitea visibility fix.
Point whynot-control/design federation URLs at whynot/ org paths.
Remove activity-core owner stub from reuse-surface index (owner index
now fetchable). tegwick-control remains blocked (no HTTP-visible repo).

registry/capabilities/capability.activity.event-coordinate.md

@@ -1,77 +0,0 @@
----
-id: capability.activity.event-coordinate
-name: Organizational Event Coordination
-summary: Coordinate structured responses to cross-domain events through activity workflows and automation.
-owner: activity-core
-status: draft
-domain: helix_forge
-tags: [activity, coordination, automation]
-
-maturity:
-  discovery:
-    current: D3
-    target: D5
-    confidence: medium
-    rationale: activity-core INTENT defines org-wide event response boundary.
-  availability:
-    current: A1
-    target: A4
-    confidence: low
-    rationale: Conceptual workflows exist; consumable API surface still emerging.
-
-external_evidence:
-  completeness:
-    level: C1
-    name: Fragmentary
-    confidence: low
-    basis: scope_vs_intent_and_consumer_expectations
-    satisfied_expectations:
-      - problem and boundary documented in INTENT
-    broken_expectations:
-      - no registry-native automation artifacts indexed yet
-    out_of_scope_expectations:
-      - owning domain-specific business logic
-  reliability:
-    level: R0
-    confidence: low
-    basis: consumer_quality_signals
-    known_reliability_risks: []
-
-discovery:
-  intent: >
-    Give the organization a structural home for responding to events across repos
-    and domains in an auditable, automation-ready way.
-  includes:
-    - event-triggered coordination
-    - cross-domain maintenance workflows
-  excludes:
-    - single-repo cron replacements only
-  use_cases: []
-
-availability:
-  current_level: A1
-  target_level: A4
-  current_artifacts:
-    - activity-core/INTENT.md
-  consumption_modes:
-    - informational
-
-relations:
-  depends_on: []
-  related_to:
-    - capability.statehub.workstream-coordinate
-    - capability.audit.event-retain
-
-consumer_guidance:
-  recommended_for:
-    - planning org-wide event response patterns
-  not_recommended_for:
-    - assuming production automation is available
-  known_limitations:
-    - early discovery stage
----
-
-# Organizational Event Coordination
-
-activity-core coordinates how the org responds to events—not the domain logic
-inside each repo.