RPF-WP-0015-T03: E2 proves a fresh write (accepted then duplicate); honest retention note

Driver baseline reports ready for accepted or duplicate and its cleanup owns no
server-side object (railiance-platform round-8 review).

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-15 00:24:15 +02:00
parent 6fc2dae86a
commit 748fe6c7db
5 changed files with 47 additions and 33 deletions

View file

@ -216,11 +216,13 @@ State Hub.
one separately approved synthetic E2. The E2 runs through the reviewed sender lane in
its own attended login: `make audit-t02-attended-window` with
`AUDIT_T02_MODE=e2` and an approval receipt whose `task_id` is
`RAILIANCE-WP-0024-T03`. It projects one synthetic sender, sends one event
(`baseline`, must be accepted), resends it (`expect-recovered`, must be
`duplicate`: accepted exactly once), cleans up, and touches no lease. The
harness refuses unless the replay is a duplicate, cleanup removes that
fixture, and the pod UID and restart count are unchanged. Confirm no chain
`RAILIANCE-WP-0024-T03`. It projects one synthetic sender and sends one event
twice through the driver's `expect-recovered` phase: the first answer must be a
fresh `accepted` (HTTP 200/202), the second `duplicate` for the same fixture
(accepted exactly once); it touches no lease. The harness refuses unless both
hold and the pod UID and restart count are unchanged. The driver owns no
server-side object; the synthetic event stays permanently in the append-only
chain under its trial tenant, and only the sender identity is removed. Confirm no chain
break, the prior marker remains readable, and the new event is accepted
exactly once.
Window `rpf-wp-0015-t03-window-20261014-01` does not run this E2. Founder