docs(ACTIVITY-WP-0029): propose hub port and schedule alignment

Parent prj-state-hub-retirement SHR-WP-0001 stream S5.

workplans/ACTIVITY-WP-0029-hub-port-alignment.md

@@ -0,0 +1,78 @@
+---
+id: ACTIVITY-WP-0029
+type: workplan
+title: "Hub port and schedule alignment for State Hub retirement"
+domain: infotech
+repo: activity-core
+status: proposed
+owner: codex
+topic_slug: infotech
+created: "2026-08-09"
+updated: "2026-08-09"
+parent_project: prj-state-hub-retirement
+parent_workplan: SHR-WP-0001
+related:
+  - ACTIVITY-WP-0015
+  - ACTIVITY-WP-0017
+  - HUB-WP-0004
+  - STATE-WP-0079
+---
+
+# Hub port and schedule alignment for State Hub retirement
+
+## Goal
+
+Align activity-core sweeps, sinks, and execution with **hub-core ports** and
+**repo-manager** ownership so State Hub is no longer the permanent target for
+automation.
+
+## Map current State Hub / core-hub callers
+
+```task
+id: ACTIVITY-WP-0029-T01
+status: todo
+priority: high
+```
+
+Inventory schedules, sinks, and context resolvers that call State Hub or core-hub
+APIs; tag each with target port (`port.schedule`, interaction sink, work index).
+
+## Retarget consistency sweep
+
+```task
+id: ACTIVITY-WP-0029-T02
+status: todo
+priority: high
+```
+
+Plan and implement retarget of remote consistency sweep from State Hub-only
+endpoints to repo-manager (or dual-run adapter) without losing C-rule coverage.
+
+## Align ops evidence sink
+
+```task
+id: ACTIVITY-WP-0029-T03
+status: todo
+priority: medium
+```
+
+Ensure interaction-event sink follows consolidated hub-core runtime after
+CORE-WP-0010 / HUB-WP-0004 cutover; update smokes.
+
+## Execution queue boundary
+
+```task
+id: ACTIVITY-WP-0029-T04
+status: todo
+priority: medium
+```
+
+Clarify workplan launch/execution ownership vs State Hub execution routes
+(inventory: replace → activity-core). Implement or document port contract.
+
+## Acceptance
+
+- [ ] Caller map complete
+- [ ] Sweep retarget plan or implementation evidenced
+- [ ] Ops evidence sink aligned to hub-core
+- [ ] Execution boundary documented/implemented