Record proposed third Whitehat E2 attempt
All checks were successful
CI Smoke / host-smoke (push) Successful in 1s
CI Smoke / container-smoke (push) Successful in 1s

Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a02991-be07-7bb3-8b6d-e9701b5621de
This commit is contained in:
tegwick 2026-08-22 23:26:19 +02:00
parent c221921142
commit 69c55889c6

View file

@ -482,6 +482,19 @@ engagement must wait for the receipt-to-broker adapter and an actual
multi-driver sequence. Evidence:
`docs/evidence/AUDIT-WP-0008-T05-whitehat-e2-02-abort-2026-08-22.md`.
Third-attempt preparation is now proposed, not yet authorized. Whitehat commit
`96d6781` adds terminal-unique engagement `WH-ENG-20260822-AUDIT-E2-03`, unique
`-03` identities, tenants, fixtures, runner pod and mounted Secret, plus an
explicit authorization-id argument and cleanup-bound report finalization.
Platform commit `2a5c002` adds the matching canonical WP-0025 contract and a
mode-`0600` raw broker-receipt export. The proposed window is 22:0022:15Z,
with projection closing at 22:03Z. Platform's 141 tests and Whitehat's 81 tests
pass; the runner manifest passes Kubernetes server-side dry-run; both contract
validators derive the same approved-form digest `55595341…7d12` and resource
names. The proposed engagement still fails closed pending explicit operator
approval, subsequent audit-core acknowledgement, and Whitehat's direct broker
receipt. No live `-03` resource exists.
```task
id: AUDIT-WP-0008-T06
status: done