coulomb/the-custodian
Archived
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Record Core Hub replacement evidence handoff

Browse Source
This commit is contained in:
Bernd Worsch
2026-06-27 21:45:06 +02:00
parent 7cf821de59
commit 12600c5565
4 changed files with 124 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
workplans/CUST-WP-0047-ops-hub-service-inventory-now-view.md
View File

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

8
workplans/CUST-WP-0049-interhub-bootstrap-access-lane.md
View File

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

17
workplans/CUST-WP-0052-core-hub-fos-reset.md
View File

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