Record activity-core Core Hub sink proof

This commit is contained in:
2026-06-27 20:34:23 +02:00
parent 50c6ff224e
commit 8838167b3d
2 changed files with 19 additions and 1 deletions

View File

@@ -63,3 +63,9 @@ state_hub_task_id: "c3d1c153-0059-470c-bb2d-0b14f2d77b94"
Waiting on a deployed Core Hub runtime or an explicit State Hub fallback decision for the transition path. Waiting on a deployed Core Hub runtime or an explicit State Hub fallback decision for the transition path.
2026-06-27 continuation: `CORE-WP-0008-T03` owns the activity-core Core Hub sink or explicit fallback decision. 2026-06-27 continuation: `CORE-WP-0008-T03` owns the activity-core Core Hub sink or explicit fallback decision.
2026-06-27 continuation update: `CORE-WP-0008-T03` and `ACTIVITY-WP-0017`
implemented and locally proved the direct activity-core -> Core Hub
interaction-event sink. This removes the consumer implementation blocker;
this task still waits for a deployed Core Hub runtime plus approved runtime
token and widget mapping before it can be marked done.

View File

@@ -124,7 +124,7 @@ therefore remains the deployed execution gate.
```task ```task
id: CORE-WP-0008-T03 id: CORE-WP-0008-T03
status: todo status: done
priority: high priority: high
state_hub_task_id: "a24bcbd8-35a3-471b-bd7c-3a75e014c233" state_hub_task_id: "a24bcbd8-35a3-471b-bd7c-3a75e014c233"
``` ```
@@ -143,6 +143,18 @@ Done when an activity-core smoke emits a known-safe event that is visible in
Core Hub or the fallback decision is recorded with non-secret evidence. This Core Hub or the fallback decision is recorded with non-secret evidence. This
closes or supersedes `CORE-WP-0004-T04`. closes or supersedes `CORE-WP-0004-T04`.
Completed 2026-06-27: implemented the direct activity-core Core Hub path in
`ACTIVITY-WP-0017` via a `core-hub-interaction-event` ops evidence sink.
The sink reads runtime credentials from `CORE_HUB_RUNTIME_TOKEN_FILE` or a
named environment variable, posts sanitized ops-inventory probe metadata to
Core Hub `/api/v2/interaction-events`, verifies the event is visible, and
returns only non-secret ids/statuses. Verified with activity-core unit tests
and a disposable local Core Hub runtime that accepted an
`ops-endpoint-verified` event from activity-core and listed it back. The
deployed activity-core smoke still requires approved `CORE_HUB_BASE_URL`,
runtime token, and widget id/mapping, so `CORE-WP-0004-T04` remains the
deployed execution gate rather than an implementation blocker.
## Task: Define staging deployment profile ## Task: Define staging deployment profile
```task ```task