NK-WP-0044: record first operator failure and QA proposals
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 2s

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: sonnet
Assistant-Process: 6969@bnt-lap001
Assistant-Session: e8ae73f2-8385-4c9c-b714-94c3c52cdbc0
This commit is contained in:
tegwick 2026-10-02 23:10:46 +02:00
parent acf231f298
commit 65e3af594c

View file

@ -113,6 +113,13 @@ principal `rehearsal-inert-nohost` only, 2h). This proves the signing mechanics,
until a test target exists. Dry-runs of packs 1-3 are all clean; Bernd's UI rehearsal is the remaining T05 work. A systematic
pre-production environment (ops-warden's option b) is Bernd's later topic.
**First operator run, 2026-10-02 (Bernd, project nk-rehearsal)**: `nk.ssh-certificates` step `sign` failed, recorded with a note: the
`WARDEN_CONFIG=` prefix was not applied, so warden used the production config. Retried with the prefix and it passed. Cause: the
requirement lived only as an inline prefix in the command. Pack fix to apply after the run completes (a changed revision resets the
evidence): state the rehearsal-config requirement as its own step with a check that proves which config is selected. QA proposals
(structured `env:`, `must_exist` datapoints, `rtut smoke`, failure hints, failures as pack defects) sent to runbook-tutorials
(`37848b4c-1b30-410f-bcc3-3a79a4d59ab1`).
## Retire the markdown verifier
```task