docs: record TPSC hub-core import seam

docs/hub-core-extraction-boundary.md

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

workplans/CUST-WP-0025-fos-hub-bootstrap.md

@@ -264,6 +264,14 @@ compatibility re-exports from `hub_core.schemas`. Added
 `tests/test_hub_core_imports.py` to pin the import seam. Verification:
 `python -m pytest` in State Hub passed with 349 tests.
 
+Implementation slice 2 (2026-06-07): aligned hub-core's TPSC schemas and GDPR
+report payload with the existing State Hub contract, then converted State Hub's
+`api.schemas.tpsc` module into a compatibility re-export from
+`hub_core.schemas.tpsc`. Verification: hub-core `pytest` passed with 15 tests;
+State Hub import/core-router/recently-on-scope focused tests passed. A full
+State Hub run reached 349 passed / 1 failed; the lone recently-on-scope failure
+passed when rerun alone and with the new import seam tests.
+
 ### T09 — Rename MCP server state-hub to dev-hub
 
 ```task