docs: record TPSC hub-core import seam
This commit is contained in:
@@ -85,6 +85,9 @@ Current implementation status:
|
||||
- 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.
|
||||
- 2026-06-07: T08 schema imports expanded. Hub-core's TPSC schema/report
|
||||
contract now matches State Hub, and State Hub re-exports `api.schemas.tpsc`
|
||||
from `hub_core.schemas.tpsc`.
|
||||
|
||||
## Extract Now
|
||||
|
||||
@@ -192,7 +195,8 @@ to import it:
|
||||
|
||||
## Next Step
|
||||
|
||||
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.
|
||||
Continue T08 by replacing the next lowest-risk generic schema/router imports,
|
||||
likely policy or non-mutating router seams. 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