Complete REUSE-WP-0003: registry CLI, docs alignment, and coverage

Align INTENT.md with delivered layout, add CapabilityRegistryConcept guide,
extend schema with promotion_history, ship reuse-surface validate/query/export
CLI, register three more helix_forge capabilities, and refresh SCOPE and gap
analysis to reflect A3 tooling and D5/A3/C4/R2 self-assessment.

registry/capabilities/capability.registry.register.md

@@ -20,34 +20,38 @@ maturity:
       registry model is bounded in INTENT.md, but concrete promotion workflows
       are not yet grounded in registry artifacts.
   availability:
-    current: A0
+    current: A3
     target: A3
     confidence: medium
     rationale: >
-      Registration is currently manual through Markdown entries and the index.
-      A CLI validator/query tool would raise availability to A3.
+      Registration and maintenance are automatable through the reuse-surface CLI
+      for validate, query, and export workflows.
 
 external_evidence:
   completeness:
-    level: C1
-    name: Fragmentary
-    confidence: low
+    level: C2
+    name: Partial
+    confidence: medium
     basis: scope_vs_intent_and_consumer_expectations
     satisfied_expectations:
       - capability IDs can be assigned in registry entries
       - maturity vectors can be recorded at registration time
+      - CLI validate, query, and export support registry workflows
+      - promotion history can be recorded in entries
     broken_expectations:
       - no automated duplicate detection yet
-      - no promotion history tracking yet
     out_of_scope_expectations:
       - hosting registered capabilities
       - enforcing implementation architecture
   reliability:
-    level: R0
-    confidence: low
+    level: R2
+    name: Tolerable
+    confidence: medium
     basis: consumer_quality_signals
     known_reliability_risks:
-      - registry consistency depends on manual index maintenance
+      - index drift still possible if authors skip validate
+      - CLI requires local venv install
+      - schema ID pattern required a fix during WP-0003 dogfooding
 
 discovery:
   intent: >
@@ -72,17 +76,17 @@ discovery:
     - specs/ProductRequirementsDocument.md
 
 availability:
-  current_level: A0
+  current_level: A3
   target_level: A3
   current_artifacts:
     - templates/capability-entry.template.md
     - registry/indexes/capabilities.yaml
-  target_artifacts:
-    - tools/validate-registry
-    - tools/query-registry
+    - reuse_surface/cli.py
+  target_artifacts: []
   consumption_modes:
     - informational
     - markdown authoring
+    - cli
 
 relations:
   depends_on: []
@@ -111,6 +115,26 @@ consumer_guidance:
   known_limitations:
     - manual index updates are required after adding an entry
     - duplicate detection is guidance-only in the MVP
+
+promotion_history:
+  - date: "2026-06-14"
+    dimension: discovery
+    from: D0
+    to: D1
+    rationale: Added name, summary, and registry-first intent from INTENT.md.
+    author: reuse-surface
+  - date: "2026-06-15"
+    dimension: discovery
+    from: D1
+    to: D3
+    rationale: Bounded scope with UC-RS-001 and MVP registry artifacts in specs/.
+    author: reuse-surface
+  - date: "2026-06-15"
+    dimension: availability
+    from: A0
+    to: A3
+    rationale: reuse-surface CLI shipped validate, query, and export commands.
+    author: reuse-surface
 ---
 
 # Capability Registration