docs: record messages router import seam
This commit is contained in:
@@ -91,6 +91,9 @@ Current implementation status:
|
||||
- 2026-06-07: T08 domain schema imports started. State Hub now imports base
|
||||
domain schemas from `hub_core.schemas.domain` while keeping dev-hub-specific
|
||||
domain detail and summary schemas local.
|
||||
- 2026-06-07: T08 router imports started. State Hub now mounts the hub-core
|
||||
messages router factory with State Hub's own `AgentMessage` model injected,
|
||||
proving the router seam can avoid cross-metadata SQLAlchemy model imports.
|
||||
|
||||
## Extract Now
|
||||
|
||||
@@ -198,8 +201,8 @@ to import it:
|
||||
|
||||
## Next Step
|
||||
|
||||
Continue T08 by replacing the next lowest-risk generic schema imports. Router
|
||||
imports should wait until the model metadata/migration strategy is explicit,
|
||||
or use host-model injection rather than importing hub-core SQLAlchemy models
|
||||
directly into State Hub. Do not rename State Hub to dev-hub until T05-T08 prove
|
||||
the shared package boundary.
|
||||
Continue T08 by applying the host-model injection pattern to the next
|
||||
lowest-risk generic routers. Repos, domains, TPSC, progress, 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.
|
||||
|
||||
Reference in New Issue
Block a user