# Proof audit pass 1 — issue 25000

Issue: [#25000](https://git.cafe/pingdotgg/t3code/issues/25000)
Branch: `fix/issue-25000`
Head: [8cfa0bbc8c](https://git.cafe/pingdotgg/t3code/commit/8cfa0bbc8ca0c0403edb3498f2c15e62acae42b2)
Base: [dd5b5401e1](https://git.cafe/pingdotgg/t3code/commit/dd5b5401e1)

## Applicability and fixture matrix

Matrix: **empty (0 rows)**.

The complete base-to-head diff contains only EventSink.ts, Orchestrator.ts, and DelegatedCompletionDelivery.test.ts under apps/server/src/orchestration-v2. There are no changed render paths, components, client contracts, styles, or navigation. The user-authorized server-only exception applies. No still captures, recordings, viewport combinations, or theme combinations are required.

The changed command caller is notification.delivery.accept: it opts into a transactional merge that retains the current persisted run and changes only delegatedCompletion. The existing writeWithEffects cohort writer reuses the extracted merge helper. Relevant data branches are run.updated with an existing run (merge), run.updated without an existing run (retain incoming event), and non-run events (unchanged). These are server persistence branches, not visual fixtures.

## Explicit proof requirements

1. A deterministic regression test must fail on the base implementation when checkpoint.capture commits a completed run after delivery acceptance planned from a waiting snapshot but before acceptance commits. It must assert delivery reaches delivered while the parent retains completed status and its checkpoint ID.
2. The same test must pass on the audited head, with the relevant existing delegated-completion tests green. Retain the exact command and red/green output in the lead proof package. The lead reports a deterministic red reproduction and 29 green tests; this audit inspected the regression test but did not rerun or independently verify those test outputs.
3. A short runtime transcript from isolated state must show parent completion/checkpoint while a late command remains outstanding, child completion and delivery acceptance without regressing that parent, a successful manual follow-up, and eventual late-command completion and notification settlement. Keep persisted events and final projections as evidence. Browser reproduction or new captures are not required for this pass.
4. Do not claim late-command-only runtime reproduces the race. The lead reports that attempt settled on main; the forced interleaving regression test supplies the red proof. The runtime supplies integrated head behavior, not a demonstrated pre-fix reproduction.

## Runtime evidence checked read-only

Ran the supplied transcript.py against the isolated .t3/userdata/statev2.sqlite using its mode=ro connection. Confirmed checkout HEAD equals the audited head. UTC event evidence:

- Parent run 7 completed with checkpoint at 21:43:00.138 while sleep45 remained outstanding.
- Child sleep15 command completed at 21:43:16.156; child run completed with checkpoint at 21:43:18.003.
- Delivery claim at 21:43:18.677 preserved run 7 completion/checkpoint. Run 8 completed at 21:43:22.879. Delivery became delivered at 21:43:23.379; run 7 still retained its original completion/checkpoint.
- Manual follow-up run 9 completed with checkpoint at 21:43:30.036.
- Late command completed at 21:43:36.518; notification run 10 completed with checkpoint at 21:43:39.052.
- Final projections show parent runs 7–10 and child run 1 all completed with checkpoints.

The lead's integrated browser pass is supplied context, not independently repeated by this audit. No source edits, push, issue/PR comments, server launch, or browser use occurred.

## FRICTION

None blocking. Red/green execution logs remain a lead-supplied proof dependency; this read-only pass verified the diff, regression-test shape, and persisted head runtime transcript. Visual matrix expansion would add no proof for this server-only change.