docs: record additional hub-core schema imports
This commit is contained in:
@@ -108,6 +108,10 @@ Current implementation status:
|
||||
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.
|
||||
- 2026-06-07: T08 additional schema imports completed. State Hub now imports
|
||||
generic capability catalog/status/dispute schemas and the repo path-register
|
||||
schema from hub-core, and State Hub repo create/read schemas extend the
|
||||
hub-core contracts while adding dev-hub fields.
|
||||
|
||||
## Extract Now
|
||||
|
||||
@@ -177,8 +181,8 @@ implementation is coupled to dev-hub concepts:
|
||||
| Surface | Coupling to resolve |
|
||||
| --- | --- |
|
||||
| `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. |
|
||||
| `ManagedRepo` | State Hub create/read schemas now extend hub-core contracts, with `topic_id`, SBOM fields, and state-sync timestamps kept as dev-hub extensions. The repos router still carries onboarding, DoI, dispatch, and sync behavior locally. |
|
||||
| `CapabilityRequest` | Catalog/status/dispute schemas now import from hub-core. Adapter seam is 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. |
|
||||
| MCP tools in `mcp_server/server.py` | Generic tools are still mixed into the State Hub server module. T08 should begin replacing those registrations with `HubCoreMCPServer` inheritance or composition while dev-hub keeps its own tools. |
|
||||
|
||||
|
||||
Reference in New Issue
Block a user