# Late Duplicate Authentic E2E Postmortem

## Summary

Existing-root authentic E2E with `bpat` and `bi-boss` caught a late duplicate answer after original request resolution.

## Evidence

- Root: `/Users/mak/.amq-bridge/mail`
- Model: `openai-codex/gpt-5.4-mini`, medium thinking
- Run: `e2e-existing-root-20260802-230715`
- Leftover: `bpat/inbox/new/2026-08-02T17-39-52.116Z_pid34564_6ad9ef7f.md`
- Subject: run-unique bridge subject
- Kind: `answer`
- Body: `ack`
- Ref: original ping ID

## What passed

Attach, bidirectional authentic conversation, explicit read/reply/resolve IDs, and thread routing all passed.

## Failure

Strict zero-actionable quiet-window assertion failed. Duplicate answer arrived after original ping was already replied and resolved. Harness stopped before urgent/reconnect phases.

## Likely cause

An already-running model turn emitted a stale reply after message completion. Existing bridge semantics deliver and deduplicate inbox notifications, but do not hard-cancel an active model generation or prevent an application send after resolution.

## Required fix

Add explicit model-turn cancellation/stop semantics and a per-message completion/send guard. Keep strict actionable-leftover E2E assertion.