Findings first:

1. **A1 remains INSUFFICIENT for its prescribed entry path.** [A1-after-r2.mp4](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/d92d4cd4ee22d838/A1-after-r2.mp4) begins on the persisted source thread, then the driver invokes `openAddProjectToMachine`. It proves zero selected files, recovery to Target owner, a fresh empty draft and completed clone. It does not prove BranchToolbar machine menu → target from the context required by A1. The index acknowledges this honestly. Supply a reachable physical entry path from a context without an eligible draft, or explicitly revise/accept that fixture requirement; the current capture does not satisfy it.

2. **The recording indexes contain contradicted timing claims.** In [A2-after-sheet.png](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/c76f0713fcef81b0/A2-after-sheet.png), the 4.40s and 8.80s tiles show the clone dialog. The actual encoded video holds the machine menu frame, PTS 1.837800, until the next frame at PTS 10.996200. At 4.40s, the dialog is therefore not on screen. The narrative's “4–13 ignored-file query resolves” starts too early. A1 has the same problem: the sheet's 5.14s tile shows zero selected files, whereas decoded footage still shows the selected-file dialog at that time; deselection occurs around 12.5s and owner navigation around 13.3s, rather than the narrated submit near 10s. The linked `make-review-sheets.py` uses `ffmpeg -ss` and labels the requested seek time instead of the returned frame's actual PTS. Regenerate the contact sheets using decoded presentation timestamps and correct the written timing claims. The actual recordings still contain the required outcome transitions; these corrections do not require re-recording A2.

![Left: delivered A2 tile labelled 4.40 seconds. Right: the frame actually displayed at 4.40 seconds.](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/ae12c12350e211da/A2-timestamp-contradiction.png)

3. **The web recording resolution in the index is incorrect.** All seven web videos encode at 2730×1800, not 1920×1266. This agrees with the stated 1365×900 CSS viewport and DPR 2; it is an index correction, not evidence of a wrong CSS viewport. See independent [W1 video metadata](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/7ce1a669d661e4e6/W1-after-r2-metadata.json) and [A2 video metadata](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/cb4bcdbb32e27cd4/A2-after-metadata.json).

| Row | Status | Coverage |
| --- | --- | --- |
| W1 | SUFFICIENT outcome proof | Base error and head recovery recorded; master and ready draft visible. Both stills and both diffs reviewed. Independent head rebuild matches the delivered after still exactly. |
| L1 | SUFFICIENT outcome proof | Missing repository → clone → existing owner's draft with Proof prompt → master. RPC/draft notes identify proof-L1-owner. |
| L2 | SUFFICIENT outcome proof | Missing repository → clone → expected reopen-link notice; completion toast appears and expires. RPC identifies proof-L2-owner. No automatic PR checkout claimed. |
| A1 | INSUFFICIENT | Production dialog, no-files branch and new owner draft are shown; prescribed physical entry path is absent. Timing labels also need correction. |
| A2 | INSUFFICIENT narration; outcome covered | Physical machine menu, selected synthetic file, same draft text on Copy owner, clone completion and real copied bytes are supported. Written timing/contact sheet contradict encoded video. |
| A3 | SUFFICIENT outcome proof | Real read-error banner on Copy error owner, followed by dismissal and same draft. Long path uses the product's intentional ellipsis; the filename/read-failure outcome is readable. |
| M1 | SUFFICIENT outcome proof | Native chooser → URL → exact stranded destination → empty Native owner draft. Actual last frame at 68.922600s shows master. Settled end state is very brief; the reviewed last frame and owner-draft notes establish it. |
| M2 | SUFFICIENT outcome proof | Native prompt link → Clone → destination → Prompt owner draft with Proof prompt and master, retained through the end. |

Scope and inspection: read the pinned head [8d4aa41a22](https://git.cafe/pingdotgg/t3code/commit/8d4aa41a22d17d4c6e1b1d6d1b8044fedd78d4ae), not a moving branch tip, against [4f0b74e190](https://git.cafe/pingdotgg/t3code/commit/4f0b74e190261c8233ae52af17b0fd1734e99e50). Confirmed that base is the merge-base. Read the nine-file change and runtime transcript. Downloaded and opened every uploaded app still, both diff images and all nine delivered contact sheets. Independently extracted and visually inspected one-second frames spanning all nine videos, plus exact final frames and PTS-selected frames where the narration was questionable. No ghosting, unrendered outcome text, stale unrelated overlay, or blank outcome capture found. Intermediate clone/loading/keyboard states are legitimate parts of the recorded interactions, not settled proof frames. The actual native dimensions are 1080×2424, matching the recorded logical dimensions and DPR; dark theme is visible. The declared shared-hostname and live OS-clock deviations do not obscure the ownership result.

Only W1 requires paired base/head footage under the supplied fixture matrix; the other rows are explicitly head-only, so missing per-row before footage/diffs are not additional findings. All displayed column SHA labels use the specified base/head.

Diff verification: independently regenerated the zero-threshold binary mask and ImageMagick 5% fuzz diff. Both match the delivered diff images exactly. Counts are AE 445944 at 0% and AE 122812 at 5%. The broad changed area is consistent with the documented modal dimming/blur removal, error disappearance, project breadcrumb, composer relocation and repository refs. The incidental Add project highlight is disclosed. There is no unexplained styling change in those diffs.

Independent rebuild: created a detached sibling worktree at the pinned head, installed its dependencies, and ran its own dev server with `T3CODE_DEV_SEED=0` and a new scratch home. Used the uploaded observer/RPC/fixture helpers to start the real nonexistent-repository clone as `audit-w1-owner`; awaited the failed clone milestone and verified the destination was empty. Stopped that tracked server group and restarted on the same home. In the real Browser panel, used Add project → Git URL → Hello-World → exact stranded destination → Ctrl+Enter. Requested id `6d7ef42f-8de4-4bfb-af8e-a84ee16e8bc5` returned `audit-w1-owner`; the UI opened its draft and master. The clone contains `.git` and README, with fixture commit [7fd1a60](https://github.com/octocat/Hello-World/commit/7fd1a60b01f91b314f59955a4e4d4e80d8edf11d).

Rendering environment: T3 Browser panel; Chrome/Chromium 156 on Linux; no emulation; 1365×900 CSS; DPR 2; zoom 100%; default root font 16px; dark; browser Date frozen to 2026-11-09 12:00 UTC; tool PNG 1280×844. Fonts were loaded and no image resource was pending. Initial capture differed by 693 pixels, entirely inside Add project's hover background (x179–205/y58–84), matching the index's incidental focus/hover note. Matching that pointer state and blurring the restored composer focus produced **AE=0 against the delivered W1-after.png**. Two final captures more than 500ms apart also have **AE=0**. No residual pixel delta or anti-aliasing exception remains. [Rebuilt capture A](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/c2570caa65c6bf1c/W1-rebuilt-final-a.png), [rebuilt capture B](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/8d8e2b2f31b37382/W1-rebuilt-final-b.png).

A2 file claim: independently read the original synthetic source and target `.env.proof` files. Both contain exactly `PROOF_FIXTURE=1\n` and SHA-256 d4a9a8e39270d0dbf5fcb33e205bedb15919ebc4e6524f62a15a0bba12a10a85. Source mode is restored to 0644. This corroborates the permitted companion file/identity transcript; the screen recording shows selection and retained draft, not file bytes.

Cleanup: stopped only the two replay process groups captured at spawn, closed the audit browser tab, and verified the replay ports are no longer listening. Removed only the audit's detached sibling worktree and scratch subdirectory after preserving public artifacts. No edits, pushes, comments, PRs, or changes to the lead's worktree/state.

FRICTION:
- tool | Python urllib downloads returned HTTP 403; curl downloaded every artifact successfully | use curl for these artifact URLs.
- tool | same-page pairing-fragment navigation left the token form empty; explicitly filling the existing token completed pairing | enter the startup token in the pairing form when a same-page fragment is not consumed.
- brief | scratch instructions name both proof-audit-2 and proof-audit-1 | use one consistent path; followed the later cleanup clause and used the previously absent proof-audit-1 directory.

VERDICT: INSUFFICIENT A1 physical entry path; A1/A2 contradicted recording timelines; web recording resolution metadata