docs: start state-hub hub-core imports
This commit is contained in:
@@ -82,6 +82,9 @@ Current implementation status:
|
||||
- 2026-06-07: T06/T07 completed in hub-core with orientation and DoI MCP tools,
|
||||
canonical FOS §10 risk/alert event types, `/progress/risks` and
|
||||
`/progress/alerts` REST views, and matching MCP read tools.
|
||||
- 2026-06-07: T08 started in State Hub. `hub-core` is now an editable
|
||||
dependency, and State Hub re-exports message and DoI response schemas from
|
||||
`hub_core.schemas` with full pytest coverage passing.
|
||||
|
||||
## Extract Now
|
||||
|
||||
@@ -189,7 +192,7 @@ to import it:
|
||||
|
||||
## Next Step
|
||||
|
||||
Start T08 by introducing `/home/worsch/hub-core` as an editable dependency of
|
||||
`/home/worsch/state-hub`, then replace the lowest-risk generic imports first.
|
||||
Do not rename State Hub to dev-hub until T05-T08 prove the shared package
|
||||
boundary.
|
||||
Continue T08 by replacing the next lowest-risk generic schema/router imports.
|
||||
Do not import hub-core SQLAlchemy models into State Hub until the shared
|
||||
metadata/migration strategy is explicit. Do not rename State Hub to dev-hub
|
||||
until T05-T08 prove the shared package boundary.
|
||||
|
||||
Reference in New Issue
Block a user