Prepare State Hub retirement baseline
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s
Build and Publish Multi-Context Image / build-and-push (push) Successful in 1m0s

This commit is contained in:
tegwick 2026-08-09 16:19:53 +02:00
parent 2217bdd9f5
commit 5927591be8
46 changed files with 32583 additions and 62 deletions

View file

@ -0,0 +1,63 @@
---
id: ADHOC-2026-08-08
type: workplan
title: "Ad hoc fixes — 2026-08-08"
domain: infotech
repo: state-hub
status: finished
owner: codex
topic_slug: state-hub
created: "2026-08-08"
updated: "2026-08-08"
state_hub_workstream_id: "f0175ce9-452b-4e52-b835-b8736d94e3d5"
state_hub_workstream_id: "f0175ce9-452b-4e52-b835-b8736d94e3d5"
---
## Integrate State Hub connectivity into Codex setup
```task
id: ADHOC-2026-08-08-T01
status: done
priority: medium
state_hub_task_id: "5ad8b6f7-f005-43da-9d01-1fe7b0a5c8f8"
```
Add an idempotent Codex configuration step to the operator bootstrap, verify
State Hub loopback access from the Codex sandbox, distinguish managed-policy
isolation from an actual hub outage, and propagate accurate agent guidance.
## Repair Codex stdio MCP launcher
```task
id: ADHOC-2026-08-08-T02
status: done
priority: high
```
Remove the stdio MCP launcher's runtime dependency on the read-only global uv
cache, execute the repository virtual environment directly, and verify an MCP
initialize exchange through the registered launcher.
## Split a slim Codex MCP surface from full dev-hub administration
```task
id: ADHOC-2026-08-08-T03
status: done
priority: high
```
Limit Codex registration to essential repository coordination tools while
leaving the full State Hub MCP server and SSE transport available to clients
that need the administrative surface.
## Make Codex MCP opt-in
```task
id: ADHOC-2026-08-08-T04
status: done
priority: high
```
Remove the default Codex dev-hub registration after bridge-level latency and
startup interruption persisted, retain the slim server for explicit testing,
and make REST plus the statehub CLI the documented Codex default.

View file

@ -4,19 +4,18 @@ type: workplan
title: "Ops run read projection for fleet visibility"
domain: infotech
repo: state-hub
status: ready
owner: grok
status: finished
owner: codex
topic_slug: state-hub
priority: low
created: "2026-08-03"
updated: "2026-08-03"
updated: "2026-08-08"
depends_on:
- ACTIVITY-WP-0026
related:
- ACT-ADR-005
- STATE-WP-0074
state_hub_workstream_id: "57b75246-ef6d-4d6e-93dc-7f47e7200d1d"
state_hub_workstream_id: "57b75246-ef6d-4d6e-93dc-7f47e7200d1d"
---
# STATE-WP-0078 — Ops run read projection
@ -39,7 +38,7 @@ coulombcore-oriented agents see automation health without claiming work.
```task
id: STATE-WP-0078-T01
status: todo
status: done
priority: medium
state_hub_task_id: "399b4985-3578-4fff-97dd-0f68e1e266b3"
```
@ -50,13 +49,17 @@ push (actcore posts progress summary) is v1.
**Done when:** short contract note in `docs/` or linked from ACT-ADR-005.
Implemented in `docs/ops-run-read-projection.md`: v1 is an authenticated,
cached pull from activity-core `GET /ops-runs`; activity-core remains the only
claim/lease/completion authority.
---
### T02 — Read API + summary field
```task
id: STATE-WP-0078-T02
status: todo
status: done
priority: medium
state_hub_task_id: "192be2e0-0335-46da-ba22-17e3e8f0d28c"
```
@ -68,13 +71,18 @@ Minimal:
**Done when:** MCP/summary consumers can show stuck automation.
Implemented `GET /ops-runs/summary` and the `/state/summary.ops_runs` projection,
including open/claimed/failed-24h counts, SLA-stuck count, bounded run details,
and stale/unavailable behavior. No write endpoints exist under State Hub's
`/ops-runs` route.
---
### T03 — Edge/federation notes
```task
id: STATE-WP-0078-T03
status: todo
status: done
priority: low
state_hub_task_id: "09afc52e-e1c6-454f-ac1d-33d6e773f47f"
```
@ -84,11 +92,21 @@ may lag if edge relay down — alert preference.
**Done when:** cluster-operating-model or ops doc updated.
Documented in `docs/cluster-operating-model.md` and
`docs/ops-run-read-projection.md`.
## Acceptance
- [ ] Hub does not claim ops_runs
- [ ] Operators see automation backlog on primary hub views
- [ ] No Forgejo/Gitea dependency
- [x] Hub does not claim ops_runs
- [x] Operators see automation backlog on primary hub views
- [x] No Forgejo/Gitea dependency
## Residual handoff
Production deployment wiring is tracked as State Hub intake
`019fe359-debb-71a6-958c-b8f4ac3574a0` (`origin: residual`,
`origin_ref: STATE-WP-0078`). It covers the private activity-core URL,
OpenBao/ESO token injection, rollout, and live fleet verification.
## Out of scope