CUST-WP-0025-T16 done: deployed Core Hub API + activity-core sink smokes both proven

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
codex
2026-07-02 18:13:49 +02:00
parent 440154802f
commit 0a52cdd858

View File

@@ -505,10 +505,17 @@ database, migrate job complete). The deployed smoke ran in-cluster with the
operator token confined to the namespace: run `20260702143544-6c8f18`,
`ok=true`, 10/10 API checks plus the full ops-hub bootstrap sequence (hub
`6798723a`, activated manifest, API consumer prefix `ch_N0ZhsXIbD`, widget,
interaction event `21d09f99`, hub registry containment true). Remaining T16
evidence: the deployed activity-core Core Hub sink smoke (runtime token +
widget mapping), then the supersede decision for `CUST-WP-0047-T05` /
`CUST-WP-0049-T06` becomes decidable on evidence.
interaction event `21d09f99`, hub registry containment true). Completed 2026-07-02: the
deployed activity-core Core Hub sink smoke also passed — activity-core's real
sink code posted interaction event `ae43db56-902d-411a-a495-25acd464fdd8`
(`ops-endpoint-verified`) to deployed Core Hub staging with an approved runtime
token (consumer `6cfcbc56`, prefix `ch_ztkSv9PK`) and widget mapping (widget
`6768aaa2`); server-side containment confirmed. `CORE-WP-0004` is finished. Both
minimum-evidence bullets (deployed API smoke + activity-core sink smoke) are met,
so T16 is done. Follow-on (not blocking T16): the supersede decision for
`CUST-WP-0047-T05` / `CUST-WP-0049-T06` is now decidable on this deployed
evidence; and the staging import `CORE-WP-0005-T02` plus dual-run/cutover
readiness remain the Core Hub cutover path.
### T17 — Core Hub, dev-hub, and cutover decision coupling