coulomb/the-custodian
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: record additional hub-core schema imports

Browse Source
This commit is contained in:
Bernd Worsch
2026-06-07 16:34:13 +02:00
parent 2844ece8b6
commit 50fbdef307
2 changed files with 15 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
docs/hub-core-extraction-boundary.md
View File

@@ -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. |

9
workplans/CUST-WP-0025-fos-hub-bootstrap.md
View File

@@ -318,6 +318,15 @@ callbacks. Verification: hub-core pytest passed with 20 tests; State Hub
core/import/MCP/recently-on-scope/capability focused tests passed with 102
tests.
Implementation slice 9 (2026-06-07): converted State Hub's matching generic
schema classes to hub-core imports: capability catalog create/patch/read,
capability request status/dispute, and repo path registration. State Hub's repo
create/read schemas now extend hub-core contracts while keeping dev-hub-only
fields local, and repo creation now persists `host_paths` from the shared
create contract. State Hub keeps dev-hub-specific capability request, reroute,
repo dispatch, onboarding, and scope-health schemas local. Verification: State
Hub import/capability/core/DoI scope/MCP focused tests passed with 100 tests.
### T09 — Rename MCP server state-hub to dev-hub
```task