[Maneek21]

Reply opening repeated independent locator, destination-existence, hydration and browser-recovery reads. App10 now explicitly opts source-seeded Reply/Reply all/Forward forms into Host137's compound read-only seed snapshot. The Worker keeps its original local intent; opening still creates no draft. Plain Compose keeps its current flow.

Runtime27 requires non-null data consent and exact expected account, target, policy and consent pins before reading data. An existing saved destination wins, retaining its files and source references; otherwise the exact original supplies the quote. Fresh entry/session/disclosure authority, cold pre-provider authority, source/custody/session/expiry checks and final destination concurrency pins remain. First-save source/mode/digest revalidation and exact user edits are unchanged. Imported native records retain their existing local read permission during provider reauth, without authorizing a new seed or provider I/O. No permission or consent is extended. Kit42 bytes and source offers remain unchanged; this unpublished Email29/App10/Runtime27 candidate now requires Host137.

Validation:

• Baseline RED: current Runtime rejected the compound operation; native compatibility regression separately RED then GREEN.
• App build, packed App tests 8/8, UI tests 48/48, provenance and IMAP tests 5/5 passed.
• Runtime coverage includes plain/HTML originals with attachments and every reply mode; no opening write; saved destination/files/source references after restart; first-save edits; five expected-pin mismatches; missing consent; source, custody, session/account switch, revocation, abort, expiry and concurrent create/save/archive denial; native saved-record reauth compatibility.
• At 350ms per fresh authority callback, isolated real Runtime fixtures measured warm 1.16-1.23s (3 online checks, zero MIME reads) and cold 1.63-1.65s (4 checks, one MIME read). Packed Worker opens locally in about 40ms with all further network responses held. These are component measurements; final visible full-pipeline acceptance remains pending the coordinated Host137/Email29 deployment.
• Shared Windows load causes the unchanged strict 2s cold timing assertion to vary: the last full targeted run passed 8/9 and measured cold HTML 2.43s, while isolated runs passed. The assertion is retained; dedicated Linux CI is required before merge. An unrelated pre-existing foreground-cache concurrency expectation also fails on baseline505a243 and the earlier candidate; it has not been suppressed.
• Existing per-line CRLF/LF endings were preserved; no unchanged-line EOL changes. No release, tag, deployment, activation, Send or demo data change was performed.

This supersedes previously staged unpublished Email29 artifacts; rebuild from the reviewed merged follow-up before publication. Hold merge/publication for the coordinator.

🤖 Generated with Claude Code