From 2844ece8b6a8557e20c7e081b2f72fe40ee8edf9 Mon Sep 17 00:00:00 2001 From: tegwick Date: Sun, 7 Jun 2026 15:23:29 +0200 Subject: [PATCH] docs: record domains router import seam --- docs/hub-core-extraction-boundary.md | 12 ++++++++---- workplans/CUST-WP-0025-fos-hub-bootstrap.md | 9 +++++++++ 2 files changed, 17 insertions(+), 4 deletions(-) diff --git a/docs/hub-core-extraction-boundary.md b/docs/hub-core-extraction-boundary.md index 8c8faad..f706713 100644 --- a/docs/hub-core-extraction-boundary.md +++ b/docs/hub-core-extraction-boundary.md @@ -104,6 +104,10 @@ Current implementation status: hub-core progress router factory with State Hub's own progress model and schemas injected, preserving topic/workstream/task filters while gaining the shared risk and alert progress views. +- 2026-06-07: T08 domains router import completed. State Hub now mounts the + hub-core domains router factory with State Hub's own domain/repo models and + schemas injected, plus callbacks for dev-hub detail counts and archive + validation. ## Extract Now @@ -172,7 +176,7 @@ implementation is coupled to dev-hub concepts: | Surface | Coupling to resolve | | --- | --- | -| `Domain` and `domains.py` detail views | Counts topics, workstreams, extension points, and technical debt. Hub-core should expose a domain summary hook that dev-hub can implement. | +| `Domain` and `domains.py` detail views | Detail counts now use a dev-hub callback behind the hub-core router factory. Domain relationships still need a later model split if State Hub stops carrying topics/goals on the core table. | | `ManagedRepo` | Contains `topic_id`, SBOM fields, and state-sync timestamps. Keep minimal repo identity in core, then add dev-hub extensions. | | `CapabilityRequest` | Adapter seam implemented with generic `request_context` and `fulfillment_context`; State Hub still needs a later refactor to map workstream/task references into those fields or a dev-hub extension table. | | `ProgressEvent` | Adapter seam implemented with generic `subject_refs`; State Hub still needs a later refactor to map topic/workstream/task/decision foreign keys into that field or a dev-hub extension table. | @@ -212,6 +216,6 @@ to import it: ## Next Step Continue T08 by applying host-model injection or callback seams to the next -lowest-risk generic routers. Repos, domains, and capability requests each need -a small dependency-injection review before replacement. Do not rename State Hub -to dev-hub until T05-T08 prove the shared package boundary. +lowest-risk generic routers. Repos and capability requests each need a small +dependency-injection review before replacement. Do not rename State Hub to +dev-hub until T05-T08 prove the shared package boundary. diff --git a/workplans/CUST-WP-0025-fos-hub-bootstrap.md b/workplans/CUST-WP-0025-fos-hub-bootstrap.md index 6e992b9..c0ddb21 100644 --- a/workplans/CUST-WP-0025-fos-hub-bootstrap.md +++ b/workplans/CUST-WP-0025-fos-hub-bootstrap.md @@ -309,6 +309,15 @@ preserves State Hub's topic/workstream/task filters and exposes the hub-core risk/alert progress views. Verification: hub-core pytest passed with 19 tests; State Hub MCP/import/core-router focused tests passed with 71 tests. +Implementation slice 8 (2026-06-07): added host-model/schema injection, +optional update-route registration, and detail/archive callbacks to +`hub_core.routers.domains.create_domains_router`, then replaced State Hub's +local `api.routers.domains` implementation with the hub-core factory. State Hub +keeps its own domain detail counts and active-topic archive guard in local +callbacks. Verification: hub-core pytest passed with 20 tests; State Hub +core/import/MCP/recently-on-scope/capability focused tests passed with 102 +tests. + ### T09 — Rename MCP server state-hub to dev-hub ```task