Unhandled duplicate-key exception terminates Orbit after session resume

[leoafarias]

Orbit exits with an unhandled exception when a Codex conversation is reopened from local history and a follow-up is submitted.

Reproduction

1. Start a Codex session in Orbit and complete a prompt.
2. Open session history and reopen that conversation.
3. Submit a follow-up prompt.

Observed with Noir pinned to b78527895411c69a6528a942bd58882f1a23faf0, Dart 3.11.0, macOS arm64, and iTerm2.

Actual

The terminal app exits during a transcript rebuild:

Bad state: Duplicate key ValueKey(entry-acp-v1-local-1) found in Column. Sibling keys must be unique.
#0 MultiChildRenderObjectElement._validateUniqueChildKeys (package:noir/src/framework/element.dart:1123)
#1 MultiChildRenderObjectElement.update (package:noir/src/framework/element.dart:1001)

Expected

The follow-up renders without terminating the terminal app.

Please investigate the duplicate-key failure and error handling. The duplicate may originate in Orbit's transcript IDs after resume; this report does not establish that Noir generates the duplicate key.