Close Core Hub operator UI gate
This commit is contained in:
@@ -527,7 +527,7 @@ local-only evidence.
|
||||
|
||||
```task
|
||||
id: CUST-WP-0025-T18
|
||||
status: todo
|
||||
status: done
|
||||
priority: medium
|
||||
state_hub_task_id: "5b6cea8b-3982-49be-bacf-7269a3d2104e"
|
||||
```
|
||||
@@ -549,6 +549,17 @@ Use whynot-design tokens/components wherever practical and preserve
|
||||
route, and non-secret assertions. Start implementation from Core Hub
|
||||
`docs/specs/operator-ui-rebuild-backlog.md`, not from old Inter-Hub screens.
|
||||
|
||||
Completed 2026-06-27: Core Hub `CORE-WP-0006` is finished with a protected
|
||||
server-rendered `/console` prototype, whynot-aligned shell/classes, readiness
|
||||
gates, registry explorer, migration state, action-required gates, access
|
||||
metadata, recent evidence events, auth tests, and full-key non-disclosure tests.
|
||||
`CORE-WP-0008-T06` extracted the compact rebuild backlog in
|
||||
`/home/worsch/core-hub/docs/specs/operator-ui-rebuild-backlog.md` so broader UI
|
||||
work stays behind API/CLI readiness. Fresh verification passed with
|
||||
`make visual-check`, producing desktop/mobile screenshots and no-overlap,
|
||||
horizontal-overflow, protected-route, PNG, and non-secret assertions. This
|
||||
closes the first-screen UI gate without expanding old Inter-Hub screens.
|
||||
|
||||
### T19 — Ops-hub MCP server registration decision
|
||||
|
||||
```task
|
||||
|
||||
@@ -456,9 +456,9 @@ Recommended order:
|
||||
|
||||
1. Keep the completed `CUST-WP-0025-T03` IAM Profile verifier/test as the
|
||||
template for Core Hub auth consumers and future production issuer wiring.
|
||||
2. Execute the rewritten Core Hub Phase 3 lane: ops evidence contract/read-model
|
||||
gaps, deployed Core Hub smoke, activity-core Core Hub sink smoke,
|
||||
migration/cutover readiness, and whynot-aligned first UI screens.
|
||||
2. Execute the remaining rewritten Core Hub Phase 3 lane: deployed Core Hub
|
||||
smoke, activity-core Core Hub sink smoke, and migration/cutover readiness;
|
||||
the whynot-aligned first UI screens are now closed as `CUST-WP-0025-T18`.
|
||||
3. Keep `CUST-WP-0047-T05` and `CUST-WP-0049-T06` as legacy/fallback Inter-Hub
|
||||
records until deployed Core Hub evidence or an explicit supersede decision
|
||||
closes them.
|
||||
@@ -501,8 +501,8 @@ Progress 2026-06-27 Core Hub ops evidence contract:
|
||||
- The spec defines API resources, non-secret evidence fields, event vocabulary,
|
||||
service-inventory-to-widget/event mapping, readiness-summary inputs, and
|
||||
read-model gaps to close before UI expansion or cutover claims.
|
||||
- T07 sequencing now keeps `T16`, `T17`, and `T18` open; T14 no longer blocks
|
||||
the Core Hub replacement lane.
|
||||
- T07 sequencing now keeps `T16` and `T17` open; T14 no longer blocks the Core
|
||||
Hub replacement lane.
|
||||
|
||||
Progress 2026-06-27 CUST-WP-0052 closeout:
|
||||
|
||||
@@ -511,9 +511,8 @@ Progress 2026-06-27 CUST-WP-0052 closeout:
|
||||
HelixForge/Railiance Forge practice, and posted non-secret State Hub
|
||||
requirements to `railiance-apps` and `railiance-forge`.
|
||||
- The remaining T07 gates are execution gates, not sequencing ambiguity:
|
||||
`T16/T17` deployed evidence/cutover waits and `T18` Core Hub operator UI
|
||||
first screens. `T14` is complete as the ops evidence contract definition
|
||||
gate.
|
||||
`T16/T17` deployed evidence/cutover waits. `T14` is complete as the ops
|
||||
evidence contract definition gate.
|
||||
|
||||
Progress 2026-06-27 IAM Profile integration:
|
||||
|
||||
@@ -522,8 +521,21 @@ Progress 2026-06-27 IAM Profile integration:
|
||||
discovery, JWKS, authorization-code + PKCE token issuance, protected endpoint
|
||||
access, required IAM Profile claims, missing-token rejection, wrong-audience
|
||||
rejection, and production rejection of local-development issuers.
|
||||
- Remaining T07 gates are now `CUST-WP-0025-T16`, `T17`, and `T18`; identity no
|
||||
longer blocks the Core Hub replacement lane.
|
||||
- Remaining T07 gates are now `CUST-WP-0025-T16` and `T17`; identity no longer
|
||||
blocks the Core Hub replacement lane.
|
||||
|
||||
Progress 2026-06-27 Core Hub operator UI first screens:
|
||||
|
||||
- Completed `CUST-WP-0025-T18` from Core Hub evidence: `CORE-WP-0006` is
|
||||
finished with the protected `/console` prototype and `CORE-WP-0008-T06`
|
||||
extracted the compact rebuild backlog in
|
||||
`/home/worsch/core-hub/docs/specs/operator-ui-rebuild-backlog.md`.
|
||||
- Fresh Core Hub verification passed with `make visual-check`, covering
|
||||
desktop/mobile screenshots, protected-route behavior, no-overlap,
|
||||
horizontal-overflow, PNG validation, and full-key non-disclosure.
|
||||
- Remaining T07 execution gates are now `CUST-WP-0025-T16` deployed evidence and
|
||||
`T17` cutover decision coupling; both still require staging/runtime custody or
|
||||
migration evidence.
|
||||
|
||||
## Task: Create The Stable Pickup Checkpoint
|
||||
|
||||
|
||||
Reference in New Issue
Block a user