coulomb/core-hub
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Add deployed API smoke harness

Browse source
This commit is contained in:
tegwick 2026-06-27 20:17:08 +02:00
parent 451c82f1b7
commit 2cddf8c94c
6 changed files with 788 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

16
workplans/CORE-WP-0008-api-first-ops-evidence-continuation.md
View file

@ -83,7 +83,7 @@ Completed 2026-06-27: created this workplan as the Core Hub counterpart to
```task
id: CORE-WP-0008-T02
status: todo
status: done
priority: high
state_hub_task_id: "6a594f9e-01ab-4be5-bf9f-2571722818c5"
```
@ -106,6 +106,20 @@ Minimum behavior:
This closes the practical gap behind `CORE-WP-0004-T03` when run against a
real deployed Core Hub runtime with approved custody.
Completed 2026-06-27: added the reusable deployed API smoke harness
(`scripts/core_hub_deployed_smoke.py`, `core_hub.smoke`) plus `make
deployed-smoke`, documentation, and unit coverage. The harness probes
health/readiness, public catalogs, OpenAPI compatibility, unauthenticated
protected-route `401` behavior, operator auth, and a repeatable ops-hub
bootstrap-equivalent sequence that creates a smoke hub, manifest, API
consumer, API key prefix evidence, widget, interaction event, and hub
registry proof. It emits non-secret JSON evidence only. Verified with
`make lint`, `make test`, and `make deployed-smoke` against a disposable
local HTTP Core Hub runtime. The harness was not executed against a real
deployed endpoint in this session because no approved deployed
`CORE_HUB_BASE_URL` and operator token were available; `CORE-WP-0004-T03`
therefore remains the deployed execution gate.
## Task: Prove activity-core consumer path
```task