diff --git a/docs/core-hub-replacement-evidence.md b/docs/core-hub-replacement-evidence.md new file mode 100644 index 0000000..6d599e3 --- /dev/null +++ b/docs/core-hub-replacement-evidence.md @@ -0,0 +1,91 @@ +# Core Hub Replacement Evidence Handoff + +Date: 2026-06-27 + +Related workplans: `CUST-WP-0052`, `CUST-WP-0025`, `CUST-WP-0047`, +`CUST-WP-0049`, `CORE-WP-0008`, `CORE-WP-0004`, `CORE-WP-0005`, +`CORE-WP-0007`. + +## Current Evidence + +Core Hub now has the API-first replacement lane needed to stop expanding the +old Inter-Hub-first ops-hub path: + +- `CORE-WP-0008-T02`: repeatable deployed-smoke harness exists through + `make deployed-smoke`. It probes health/readiness, OpenAPI compatibility, + public catalogs, protected-route `401` behavior, operator auth, ops-hub + bootstrap-equivalent creation, widget/event write, key-prefix evidence, and + hub-registry visibility. It was verified against a disposable local HTTP Core + Hub runtime, not a live staging endpoint. +- `CORE-WP-0008-T03`: activity-core has a direct Core Hub + `core-hub-interaction-event` sink, verified locally against a disposable Core + Hub runtime. Deployed execution still needs `CORE_HUB_BASE_URL`, runtime key, + and widget mapping from approved custody. +- `CORE-WP-0008-T04`: staging deployment profile, Kubernetes manifests, + migration job shape, secret references, health/readiness probes, rollback + notes, and container build checks are documented. +- `CORE-WP-0008-T05`: `make operator-cli` wraps the same API behavior for + deployed smoke, ops-hub bootstrap status, migration validate/import, and + cutover readiness summaries. +- `CORE-WP-0008-T06`: the web UI is gated behind API/CLI readiness and has a + compact whynot-aligned first-screen backlog. The UI should not start by + recreating every old Inter-Hub screen. + +No live deployed smoke report was available in this session. Therefore there +are no deployed Core Hub smoke ids/counts to claim yet. The next live report +should record only non-secret fields: `runId`, hub id/slug/status, manifest +id/status, API consumer id/status/key prefix, widget count, interaction event +id/type, and hub-registry containment booleans. + +## 0047 And 0049 Decision + +`CUST-WP-0047-T05` should remain `wait` as the legacy Inter-Hub evidence record. +Do not close it from local Core Hub evidence alone. It can close later through a +Core Hub deployed compatibility/evidence smoke or an explicit supersede +decision that states the legacy production widget activation is no longer +required. + +`CUST-WP-0049-T06` should remain `wait` as the legacy/fallback access routine. +Do not request Inter-Hub operator keys or new ops-warden work for the preferred +replacement lane. Use it only if the operator deliberately chooses legacy +Inter-Hub bootstrap or rollback validation. + +## CUST-WP-0025 Phase 3 Reset Recommendation + +`CUST-WP-0025-T13` through `T19` should be rewritten before execution: + +- T13: replace "create standalone ops-hub repo" with Core Hub-owned API-first + ops evidence and registry work. Defer any standalone ops-hub repo until after + Core Hub cutover proves the boundary still needs a separate service. +- T14: replace standalone ops-specific models with Core Hub resources and + migration/read-model gaps, preserving `CUST-WP-0047` service inventory as + input evidence. +- T15: replace MCP-first ops tools with API and CLI parity first. Any MCP layer + should consume the proven Core Hub API later. +- T16: route infrastructure evidence through activity-core probes and Core Hub + interaction/deployment evidence, with credential ownership resolved through + approved custody routes rather than chat or workplans. +- T17: reframe cross-hub coupling around Core Hub events, State Hub progress, + and activity-core evidence sinks. Keep NATS as a later transport decision. +- T18: replace the old dashboard task with the whynot-aligned Core Hub operator + UI backlog from `CORE-WP-0008-T06`. +- T19: cancel or defer ops-hub MCP server registration until post-cutover + demand proves it is needed. + +This is enough to rewrite `CUST-WP-0025` safely, but not enough to declare Core +Hub production cutover complete. + +## Remaining Gates + +- Run `make deployed-smoke` or `make operator-cli CLI_ARGS="deployed-smoke ..."` + against a real Core Hub staging URL with an approved operator token. +- Import the approved Inter-Hub export bundle into a staging Core Hub database + and keep dry-run reports visibly open until a reviewed non-dry-run import + succeeds. +- Run the deployed activity-core Core Hub sink smoke with approved runtime + token and widget mapping. +- Build a `readiness-summary` evidence report from deployed smoke, migration, + activity-core, and optional legacy Inter-Hub reference evidence. +- Keep `CORE-WP-0007` Haskell retirement blocked until staging import, dual-run + smokes, cutover, rollback notes, and operator approval are complete. + diff --git a/workplans/CUST-WP-0047-ops-hub-service-inventory-now-view.md b/workplans/CUST-WP-0047-ops-hub-service-inventory-now-view.md index 0510f01..91416dd 100644 --- a/workplans/CUST-WP-0047-ops-hub-service-inventory-now-view.md +++ b/workplans/CUST-WP-0047-ops-hub-service-inventory-now-view.md @@ -170,6 +170,15 @@ API-first replacement evidence. T05 can close through a Core Hub deployed compatibility/evidence smoke or by an explicit supersede decision that preserves the non-secret Inter-Hub facts above. +2026-06-27 Core Hub replacement evidence handoff: keep T05 in `wait`. +`docs/core-hub-replacement-evidence.md` records that Core Hub now has the +repeatable API smoke harness, activity-core sink, staging profile, CLI wrappers, +and UI rebuild backlog, but no live deployed Core Hub smoke ids/counts were +available in this session. Close this task only after a deployed Core Hub +compatibility/evidence smoke proves the replacement path or after an explicit +supersede decision says the legacy Inter-Hub widget activation is no longer +required. + ## Task: Build First Ops-Hub Service Catalog View ```task diff --git a/workplans/CUST-WP-0049-interhub-bootstrap-access-lane.md b/workplans/CUST-WP-0049-interhub-bootstrap-access-lane.md index 47a1cab..d92e20c 100644 --- a/workplans/CUST-WP-0049-interhub-bootstrap-access-lane.md +++ b/workplans/CUST-WP-0049-interhub-bootstrap-access-lane.md @@ -193,6 +193,14 @@ toward Core Hub API-first work. Any new ops-warden capability need discovered from this lane should be posted as a State Hub requirement/suggestion for the separate ops-warden worker rather than implemented here. +2026-06-27 Core Hub replacement evidence handoff: keep T06 in `wait` as a +legacy/fallback access routine. `docs/core-hub-replacement-evidence.md` records +that Core Hub now owns the preferred replacement lane, but the session did not +produce live deployed smoke ids/counts or cutover proof. Do not request +Inter-Hub operator keys or new ops-warden work for the preferred replacement +path; use this lane only for deliberate legacy Inter-Hub bootstrap or rollback +validation. + ## Acceptance Criteria - The repeatable access lane is documented in the owning repos. diff --git a/workplans/CUST-WP-0052-core-hub-fos-reset.md b/workplans/CUST-WP-0052-core-hub-fos-reset.md index 1d001ac..23fb387 100644 --- a/workplans/CUST-WP-0052-core-hub-fos-reset.md +++ b/workplans/CUST-WP-0052-core-hub-fos-reset.md @@ -177,6 +177,14 @@ Likely changes: Done when CUST-WP-0025 reflects the current Core Hub architecture and no longer points future agents at the obsolete mega-hub/Inter-Hub scaffold sequence. +2026-06-27 evidence handoff: `docs/core-hub-replacement-evidence.md` now +summarizes the Core Hub replacement proof from `CORE-WP-0008-T02` through +`T06`, records why `CUST-WP-0047-T05` and `CUST-WP-0049-T06` should remain +legacy/fallback wait tasks for now, and gives rewrite guidance for +`CUST-WP-0025-T13` through `T19`. The actual `CUST-WP-0025` rewrite is still +open because no live deployed Core Hub smoke ids/counts or cutover proof exist +yet. + ## Task: Align Helixforge Build And Environment Practices ```task @@ -204,7 +212,7 @@ rather than one-off shell recipes. ```task id: CUST-WP-0052-T06 -status: todo +status: done priority: medium state_hub_task_id: "f4dbc298-997a-497c-a56c-0d2293f3aec9" ``` @@ -223,6 +231,13 @@ Rules: Done when the Core Hub UI workplan has a compact first-screen backlog and acceptance checks grounded in real operator workflows. +Completed 2026-06-27: Core Hub `CORE-WP-0008-T06` added +`docs/specs/operator-ui-rebuild-backlog.md`, a compact first-screen backlog +for readiness, registry, evidence stream, migration/cutover, +action-required gates, and access metadata. The backlog gates UI work behind +deployed API evidence and CLI parity, requires whynot-design primitives where +practical, and preserves desktop/mobile/no-overlap/non-secret visual checks. + ## Task: Route External Requirements Through State Hub ```task