T05 entry 6: fix core-hub relations and reflect early scaffold.

Correct related_to IDs for inter-hub and whynot-design successors,
document src/core_hub FastAPI scaffold and pytest evidence, and
keep availability at A1 until production cutover is proven.

registry/capabilities/capability.infotech.core-hub.md

@@ -26,8 +26,9 @@ maturity:
     target: A5
     confidence: medium
     rationale: >
-      The repo is currently a planning/specification home. Production availability
+      Early FastAPI/Postgres scaffold exists under src/core_hub/ (app, /api/v2 module,
-      starts after the FastAPI/Postgres implementation, migration, and cutover workplans land.
+      migrations, operator CLI) with a pytest suite, but production cutover and Inter-Hub
+      compatibility evidence are not yet complete.
 
 external_evidence:
   completeness:
@@ -39,16 +40,16 @@ external_evidence:
       - lineage and platform reset research artifact
       - specification map
       - staged workplans
+      - early FastAPI scaffold (src/core_hub/) and pytest suite
     broken_expectations:
-      - runtime implementation is not yet present
+      - production cutover and Inter-Hub /api/v2 compatibility evidence not yet complete
-      - compatibility test harness is not yet present
     out_of_scope_expectations:
       - direct secret custody
       - owning every downstream domain hub implementation
   reliability:
     level: R1
     confidence: medium
-    basis: no_runtime_yet
+    basis: early_scaffold_not_cutover
     known_reliability_risks:
       - Inter-Hub compatibility must be proven before cutover
       - data migration and API auth semantics require careful operator evidence
@@ -62,6 +63,7 @@ discovery:
   includes:
     - framework contract and IR documentation
     - API and event model specs
+    - early FastAPI /api/v2 scaffold (src/core_hub/)
     - workplan, progress, task, message, and decision coordination model
     - operator UI and component surface planning
     - migration and compatibility planning
@@ -89,9 +91,11 @@ availability:
     - SCOPE.md
     - docs/specs/README.md
     - workplans/
+    - src/core_hub/ (FastAPI app, /api/v2, migrations, operator CLI)
   consumption_modes:
     - informational
     - planning
+    - cli
 
 relations:
   depends_on:
@@ -99,8 +103,8 @@ relations:
   supports:
     - capability.registry.register
   related_to:
-    - capability.inter-hub.framework
+    - capability.infotech.interaction-hub-framework
-    - capability.whynot-design.system
+    - capability.design.whynot-system
 
 evidence:
   documentation:
@@ -108,7 +112,8 @@ evidence:
     - SCOPE.md
     - docs/research/2026-06-27-core-hub-lineage-and-platform-reset.md
     - docs/specs/README.md
-  tests: []
+  tests:
+    - tests/ (22 tests collected 2026-07-07)
 
 consumer_guidance:
   recommended_for:
@@ -119,7 +124,7 @@ consumer_guidance:
     - production cutover before compatibility and migration evidence exists
     - secret custody or credential handoff flows
   known_limitations:
-    - implementation is not yet present
+    - production cutover and Inter-Hub compatibility not proven yet (early scaffold only)
     - compatibility contract is seeded but not frozen
 ---
 

registry/indexes/capabilities.yaml

@@ -1,5 +1,5 @@
 version: 1
-updated: '2026-06-27'
+updated: '2026-07-07'
 domain: infotech
 capabilities:
   - id: capability.infotech.core-hub
@@ -11,4 +11,4 @@ capabilities:
     owner: core-hub
     path: registry/capabilities/capability.infotech.core-hub.md
     tags: [interaction-framework, state-hub, inter-hub-successor, agent-coordination, registry, api]
-    consumption_modes: [informational, planning]
+    consumption_modes: [informational, planning, cli]