Add capability registry scaffold and seed entries from reuse-surface

Bootstrap registry/indexes/capabilities.yaml and migrate helix_forge
capability entries owned by this repository for federation publishing.

registry/README.md

@@ -0,0 +1,12 @@
+# Capability Registry
+
+Markdown-first capability index for federation and reuse planning.
+
+## Authoring
+
+1. Copy a capability entry template (see reuse-surface `templates/capability-entry.template.md`).
+2. Add the row to `indexes/capabilities.yaml`.
+3. Run `reuse-surface validate` from a checkout with the CLI installed.
+4. Merge to `main` and verify publish with `reuse-surface establish --publish-check`.
+
+Federation contract: reuse-surface `docs/RegistryFederation.md`.

registry/capabilities/capability.statehub.progress-log.md

@@ -0,0 +1,91 @@
+---
+id: capability.statehub.progress-log
+name: Work Progress Logging
+summary: Record progress events, decisions, and session notes against workstreams and tasks in State Hub.
+owner: state-hub
+status: draft
+domain: helix_forge
+tags: [state-hub, progress, coordination]
+
+maturity:
+  discovery:
+    current: D4
+    target: D5
+    confidence: medium
+    rationale: Progress API and agent session protocol are documented in state-hub AGENTS.md.
+  availability:
+    current: A4
+    target: A6
+    confidence: medium
+    rationale: Available via State Hub HTTP POST /progress/ endpoint.
+
+external_evidence:
+  completeness:
+    level: C3
+    name: Functional Core
+    confidence: medium
+    basis: scope_vs_intent_and_consumer_expectations
+    satisfied_expectations:
+      - progress events attach to workstreams
+      - agents can log session summaries
+    broken_expectations: []
+    out_of_scope_expectations:
+      - replacing git commit history
+  reliability:
+    level: R3
+    name: Usable
+    confidence: medium
+    basis: consumer_quality_signals
+    known_reliability_risks:
+      - depends on hub availability and tunnel health for remote agents
+    evidence:
+      satisfied_signals:
+        - reuse-surface AGENTS.md session-close protocol cites POST /progress/
+        - cross-repo agents log progress with workstream_id linkage
+
+discovery:
+  intent: Provide auditable progress memory for cross-repo agent and operator work.
+  includes:
+    - progress event creation
+    - workstream and task linkage
+    - author attribution
+  excludes:
+    - canonical workplan storage
+  use_cases: []
+
+availability:
+  current_level: A4
+  target_level: A6
+  current_artifacts:
+    - state-hub/api/
+  consumption_modes:
+    - service API
+
+relations:
+  depends_on:
+    - capability.statehub.workstream-coordinate
+  supports: []
+  related_to:
+    - capability.statehub.workstream-coordinate
+
+evidence:
+  documentation:
+    - AGENTS.md
+  consumer_feedback:
+    - >
+        reuse-surface agents (REUSE-WP-0012): session-close progress posts to State
+        Hub succeeded for workstream fb0b6067 during federation workplan work.
+
+consumer_guidance:
+  recommended_for:
+    - closing agent sessions with hub progress notes
+  not_recommended_for:
+    - authoritative task status (use workplan files + fix-consistency)
+  known_limitations:
+    - hub must be running locally or via tunnel
+---
+
+# Work Progress Logging
+
+Progress logging complements file-backed workplans with live session memory in
+State Hub.

registry/capabilities/capability.statehub.workstream-coordinate.md

@@ -0,0 +1,117 @@
+---
+id: capability.statehub.workstream-coordinate
+name: Workstream And Task Coordination
+summary: Track active workstreams, tasks, progress, and consistency across domain repositories through a local-first coordination service.
+owner: state-hub
+status: draft
+domain: helix_forge
+tags:
+  - state-hub
+  - coordination
+  - workplans
+
+maturity:
+  discovery:
+    current: D4
+    target: D5
+    confidence: medium
+    rationale: >
+      State Hub intent, scope, and ADR-001 workplan conventions are documented;
+      concrete agent workflows are still being standardized across repos.
+  availability:
+    current: A4
+    target: A6
+    confidence: medium
+    rationale: >
+      Consumers integrate through the State Hub HTTP API and custodian scripts.
+      Managed platform operation is the natural target for multi-repo agents.
+
+external_evidence:
+  completeness:
+    level: C3
+    name: Functional Core
+    confidence: medium
+    basis: scope_vs_intent_and_consumer_expectations
+    satisfied_expectations:
+      - workstream and task tracking via HTTP API
+      - workplan file to database consistency sync
+      - progress event logging
+    broken_expectations:
+      - no native MCP server for all agent environments
+    out_of_scope_expectations:
+      - replacing git-backed workplan canon
+      - identity authority
+  reliability:
+    level: R2
+    name: Tolerable
+    confidence: low
+    basis: consumer_quality_signals
+    known_reliability_risks:
+      - depends on local hub availability and operator maintenance
+
+discovery:
+  intent: >
+    Give agents and operators a live, queryable memory of work across domains
+    without replacing file-backed workplans and governance canon.
+  includes:
+    - workstream and task indexing
+    - progress and decision events
+    - repo consistency synchronization
+    - inbox and human-review flags
+  excludes:
+    - canon ownership
+    - task factory for all work origins
+    - identity authority
+  assumptions:
+    - workplans remain authoritative in git for ADR-001 repos
+  use_cases:
+    - UC-RS-013
+  research_memos:
+    - state-hub/INTENT.md
+
+availability:
+  current_level: A4
+  target_level: A6
+  current_artifacts:
+    - state-hub/api/
+    - state-hub/scripts/consistency_check.py
+  target_artifacts:
+    - state-hub/platform/state-hub-service
+  consumption_modes:
+    - service API
+    - HTTP REST
+
+relations:
+  depends_on: []
+  supports:
+    - capability.registry.register
+  related_to:
+    - capability.statehub.progress-log
+
+evidence:
+  documentation:
+    - state-hub/INTENT.md
+    - state-hub/AGENTS.md
+  tests: []
+  consumer_feedback: []
+  bug_reports: []
+  incidents: []
+
+consumer_guidance:
+  recommended_for:
+    - cross-repo agent orientation and task status sync
+    - logging progress after workplan changes
+  not_recommended_for:
+    - storing canonical requirements or architecture canon
+    - assuming hub state overrides git workplan files
+  known_limitations:
+    - requires running State Hub locally or via tunnel
+---
+
+# Workstream And Task Coordination
+
+## Overview
+
+State Hub provides live coordination for helix_forge repositories while
+workplans remain file-backed. This entry represents the service/API consumption
+mode for cross-repo agent work.

registry/indexes/capabilities.yaml

@@ -0,0 +1,35 @@
+version: 1
+updated: '2026-06-16'
+domain: helix_forge
+capabilities:
+- id: capability.statehub.progress-log
+  name: Work Progress Logging
+  summary: Record progress events, decisions, and session notes against workstreams
+    and tasks in State Hub.
+  vector: D4 / A4 / C3 / R3
+  domain: helix_forge
+  status: draft
+  owner: state-hub
+  path: registry/capabilities/capability.statehub.progress-log.md
+  tags:
+  - state-hub
+  - progress
+  - coordination
+  consumption_modes:
+  - service API
+- id: capability.statehub.workstream-coordinate
+  name: Workstream And Task Coordination
+  summary: Track active workstreams, tasks, progress, and consistency across domain
+    repositories.
+  vector: D4 / A4 / C3 / R2
+  domain: helix_forge
+  status: draft
+  owner: state-hub
+  path: registry/capabilities/capability.statehub.workstream-coordinate.md
+  tags:
+  - state-hub
+  - coordination
+  - workplans
+  consumption_modes:
+  - service API
+  - HTTP REST