RPF-WP-0015: T02 synthetic sender lane, T03 checklist revision, ops-warden re-acceptance

Addresses round-1 owner review requests from audit-core, rapp-postgres,
railiance-cluster and railiance-infra; refreshes the review contract.

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

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 680842@bnt-lap001
Assistant-Session: 54eb9e8e-7d6b-4f0c-b7a6-a6db62075883
This commit is contained in:
codex 2026-10-14 12:49:40 +02:00
parent aee6fe79d7
commit ce8286dff9
13 changed files with 2032 additions and 52 deletions

View file

@ -392,3 +392,27 @@ checklist revisions requested by cluster/infra/postgres/platform (full-cluster r
checks, pre-reboot failing-pod baseline, all CNPG clusters, firewall/boot-id/time sync,
named console path, infra abort ownership, ops-warden login revision re-acceptance and
stop-on-credential-output rule, PVC/cluster UID capture).
Revision for the second owner-review round (2026-10-14):
- T02: attended synthetic-sender lane `scripts/audit_core_synthetic_sender_lane.py`
(+ Makefile targets, tests) projects exactly one receipt-named
`tenant:trial:` identity, restarts audit-core before the baseline and cleans up only
after recorded evidence; the lease harness now requires the receipt's
`synthetic_sender` block. The lane reuses helpers from the dated -02 script; move
them to a shared module before that script is retired.
- T03: `docs/railiance01-coordinated-reboot.md` and the node-reboot preflight cover
named core workloads, a failing-pod baseline diff, every CNPG cluster (UID, PVC UID,
systemID), all stores/ExternalSecrets, firewall/tunnel/boot-id, NTP, Forgejo pull
lag, infra abort ownership, a same-day `RAIL01-CONSOLE-` receipt
(railiance-infra docs/railiance01-console-access.md), new scenario/decision ids and
an accepted ops-warden revision; running-pod image digest is now checked too.
- ops-warden: re-acceptance first rejected HEAD 11b2a9d (b4c1d39 had dropped the
login-output fail-closed check); fixed locally in ops-warden 244f1ae/6e14300 and
accepted at 6e14300 (reviews/RPF-WP-0017-ops-warden-reacceptance-2026-10-14.json).
The OIDC stderr prompt is an allowlisted relaxation. WARDEN-WP-0036-T02's
2026-09-01 live op ran while the relaxed check was in source (railiance-infra follow-up).
Remaining before any window: second-round owner approvals; console access proven
(RAIL-HO-WP-0011-T09); fresh backups or waivers for state-hub-db, user-engine-pg,
net-kingdom-pg, target-revenue-pg; stuck PVC platform-pg-drill/platform-pg-drill-1;
ops-warden 6e14300 published and installed; then window ids, abort operator, snapshot
receipt and 2-of-3 unseal quorum.