# PASS2 round 2 — final proof-gap audit

**0/7 matrix rows complete.** This fresh audit supersedes the prior four-image-cutoff audit. It audits the completed preparation delivery, not source correctness. The two reported MERGE source reviews and seven passing tests remain separate evidence; no source blocker is claimed and those checks were not rerun.

Scope: original [#21113](https://github.com/pingdotgg/t3code/pull/21113), [#21113](https://git.cafe/pingdotgg/t3code/pulls/21113), replacement draft [#24555](https://github.com/pingdotgg/t3code/pull/24555). Governing [A–G matrix](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/0b657a579713a1e2/ev-21113-pass1-refresh.md), final [published inventory](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/d43c928dbbbb0bad/published-evidence.md), [preparation report](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/eda4c55f3be5b171/preparation-report.md), and [sanitized preparation bundle](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/31acb7bd164c8a29/sanitized-preparation.tar.gz).

## Revision, delivery and provenance

Read-only local verification: `/home/ubuntu/wt/pr-21113` has clean tracked/untracked status; HEAD is AFTER [fe552d7](https://github.com/pingdotgg/t3code/commit/fe552d7d57bef4c4b5a04dbc34628b3a1c2dd830), full `fe552d7d57bef4c4b5a04dbc34628b3a1c2dd830`. BEFORE object resolves to [eea9895](https://github.com/pingdotgg/t3code/commit/eea989536849e5b5049987ee24318b5a77326542), full `eea989536849e5b5049987ee24318b5a77326542`. Origin is GitCafe. No forge CLI, fetch, or remote-head freshness claim.

Final manifest contains exactly FIVE PNGs, all AFTER-only: ambiguity-toast, no-project-a, folder-failure, empty-hero, welcome-hero. All five were individually decoded and opened visually with the local image viewer during this audit. The directory additionally retains legacy disconnected-remote.png; it was also visually opened, but is not a sixth final-manifest image. Recursive local media inventory found six PNGs total and no recordings or diff images. The local sanitized tar lists report, four drivers, ledger and seven state/settled JSON files; it contains no image/recording/comparison evidence. Drivers were read, not executed. The launch driver pins AFTER; the probe's revision field is a literal, so it is not independent runtime SHA attestation.

All final PNGs decode to 1280×800. State snapshots declare CSS 1280×800, DPR 2 and theme `""`; light appearance is visible, explicit theme setting is unproven. Image dimensions do not independently establish DPR. No required 1440×900 or 390×844 CSS/DPR-1 capture or dark capture exists. Local clean HEAD and launcher corroborate reported AFTER provenance but do not cryptographically bind each capture to the running build. No BEFORE capture exists.

Public PNG byte-equivalence was attempted by read-only HTTP download; the first request returned `HTTP Error 403: Forbidden`. Local final-name artifacts and manifest were audited; public-byte identity and remote tar content were not independently verified. No credential workaround was attempted.

## Every final image: visual observations and limits

- **ambiguity-toast.png:** Remote work ordinary heading, unsent “Keep this draft”, reconnect warning, and full Several-machines toast are visible. Screenshot does not show shortcut input, before/after mutation state, or palette absence. Snapshot supports remembered unavailable B plus two connected rootful alternatives.
- **no-project-a.png:** No project / New thread breadcrumb, No project heading and empty composer are visible. Identical machine display names mean the screenshot alone cannot identify primary A; the preparation narrative supplies the destination/RPC account. It does not establish the preceding click or contentful-draft preservation.
- **folder-failure.png:** “Could not open the link” and “This machine could not start a thread without a project.” are visible. **No folder-error toast appears in this PNG**, despite the published alt text saying “page and toast”. Earlier state text/report retain the toast, but do not turn it into visual/recorded evidence. Existing scratch project in the actual R preparation deviates from the matrix's no-existing-project seed.
- **empty-hero.png:** Empty sidebar, “Add a project, or start without one.” and “Start without a project” button are visible. This is the correct affected empty-root render path, unlike the No project chat hero. It does not show button activation or B destination.
- **welcome-hero.png:** Connect wizard overlays a blurred underlying empty hero; two connected machine entries are visible. Underlying text/button cannot be independently read through the blur. The report identifies `/welcome`; the PNG alone does not establish URL, click-to-B outcome or comparison.

Legacy disconnected-remote.png shows Remote work, fallback subtitle, reconnect banner and empty composer; it adds only an AFTER checkpoint.

Local final PNG SHA-256:

| Image | SHA-256 |
|---|---|
| ambiguity-toast.png | fa3eda46cc15f3f22b28f8a533b85639173840c40f826e4f4925afacdda70c7f |
| no-project-a.png | 41baae74c33c08078e51bb0da70c5fc5924d88bfbbbc1616b4d60dc47397a627 |
| folder-failure.png | 71622b7aa46e79a23f9a4a792cc66a1aded03f296bc6187a143142140ddcc9a7 |
| empty-hero.png | 0bd38eefb3b4f9f599363591fb3c8730cccb8b38c55da3db6806c26dbe50d5c3 |
| welcome-hero.png | 7732119e31927037a741ae8510380ddbff3f7cfb99524c61ed62f9aaf6300aff |

## Row-by-row proof decisions

**Shared unmet contract for EVERY row:** both pinned revisions × both required CSS viewports × explicitly set light/dark; continuous labeled X11 interaction recording; two lossless samples 500 ms apart with decoded-pixel equality established independently on each revision; matched-checkpoint BEFORE/AFTER threshold-zero amplified and maximum-RGB-channel threshold-16/255 diff images, counts and amplification specification. None is delivered. No narrated action-to-recording timestamps exist. The written preparation narrative is useful but cannot substitute for recordings.

| Row | Individual status | Final evidence and remaining row-specific gaps |
|---|---|---|
| A | INSUFFICIENT | Separate No project AFTER image and legacy disconnected CTA image; report narrates empty/contentful fallback and reverse selection. No continuous B-shutdown-to-click/RPC/destination proof; no full empty/contentful reset-aware comparison; both palette entries and successful shortcut unexercised. Distinct images cannot prove the transition or preservation. |
| B | INSUFFICIENT | Own-root collision seed was not constructed/exercised. No collision heading comparison, ordinary collision selector checkpoint or transition to A scratch. Remote work is not the required collision project. |
| C | INSUFFICIENT | Final empty-root and welcome images now exist and were visually inspected; prior “no hero capture” cutoff is superseded. Report narrates real B scratch creation after click. No comparable BEFORE description/button, required sizes/themes, or recorded start-to-B interaction. Welcome overlay blurs the underlying checkpoint. |
| D | INSUFFICIENT | Final M toast is visually present; Z toast is state/report only. Narrative reports shortcut, unchanged draft and immediate zero requests, but no continuous input/no-mutation proof or BEFORE silent behavior. CTA/both palette absence checkpoints unexercised. Passive logs and empty rpc arrays alone do not prove no mutation. |
| E | INSUFFICIENT | Z bare prompt unavailable state exists; no final corresponding PNG. M persisted latest stopped-thread preference seed absent; active draft is insufficient. Missing-repository and missing-PR action paths unexercised for both M/Z. No reset-aware three-route comparison/recording. |
| F | INSUFFICIENT | Final selected-machine failure page inspected; real folder-error toast described and present in state text, absent visually. Actual seed retained an existing scratch project; exact fresh R option was only syntax checked. Missing-repo/PR routes unexercised; no exact failing-RPC/no-launch recording or BEFORE generic-reason comparison. |
| G | INSUFFICIENT | Bridge HTTP/native-file harness was neither prepared nor exercised. No HARNESS delivery, real B preview creation/maximize, BEFORE error, or file refusal/no-B-creation/no-asset-request recording. Prompt-link errors do not cover this row. |

## Independent reconstruction / pixel delta

**Unavailable, not zero.** There is no delivered BEFORE image, required recording, stable within-revision sample pair, or matched target checkpoint. No independent comparative rebuild or pixel delta can honestly be generated from these assets. The supplied fixture drivers do not provide an executed equivalent two-revision/browser-state reset, and the fresh R branch is unexecuted. Comparing different AFTER states would measure different UI states, not the revision change. Inventing a baseline, using the two hero states as a pair, or reporting zero/16 counts would be false proof. No fixture execution, browser/server launch, revision switch or alternate capture system is authorized in this round; none was performed.

## Friction and scope

FRICTION capture-runtime|happened: preparation used headless DPR2 preview while the required X11/DPR1 recording workflow remained unavailable; prior audit records ffmpeg `Cannot open display :99.0, error 1`|prevention: resolve the supported headed capture prerequisite or obtain an explicit parent-approved contract change before recording; this audit grants no override.

FRICTION fixture-state|happened: actual R retained an existing scratch project; M prompt persisted-thread seed and equivalent browser reset were not established|prevention: build exact stopped fixtures and equivalent browser state before comparative capture; keep unexecuted driver branches labeled untested.

FRICTION runbook|happened: missing revision/size/theme pairs, stability proof, diff outputs and recording timestamps; published failure alt text overstates the visible toast|prevention: manifest each checkpoint against the matrix and describe only visible evidence.

FRICTION tooling|happened: public artifact download returned HTTP 403 during byte-identity verification|prevention: disclose local-only artifact inspection and avoid claiming remote byte equivalence.

FRICTION brief|happened: stale four-image cutoff could obscure completed five-image preparation, or after-only preparation could be mistaken for matrix completion|prevention: supersede that cutoff, enumerate all five final images, retain individual A–G insufficiency and distinguish source-review/test results from proof sufficiency.

Cleanup is reported by PREP and its ledger (owned processes marked not alive, six ports closed, owned tab closed), not independently rerun here. No server/tab was started or changed by this audit. No live userdata access, production edit, test run, push, forge comment, watch, source re-review or independent fixture execution occurred. Only outside-repo audit output and its authorized ghdrop upload were produced. PR links were registered with this thread.

VERDICT: INSUFFICIENT A,B,C,D,E,F,G