# Final whole-PR audit — [#20825](https://github.com/pingdotgg/t3code/pull/20825)

**Merge at the code and accepted headless-proof level; no blockers on local HEAD `1b3b634297c4f12ead8d0325e6ba1e14c5e9b852`.** Reviewed the complete eight-file `origin/main...HEAD` diff against base `e3e89f4b2ec21020f380fdba4a79207e3d5fcd56`, plus relevant picker, draft, runtime, server, and contract paths. Target is fork `shivamhwp/t3code`, branch `t3android/issue-20810`. The saved 23:09 GitHub snapshot still shows published `db4d4060677a6706962cbb05e4b81d62e10c494d`; this verdict applies to the local later commit, not to that published SHA.

The change is worth having. Both mobile entry points now refresh and paginate an exact local-branch lookup, reuse its occupied worktree without changing the project checkout, and carry that path into draft creation. Remote reuse requires the full `refs/remotes/<selected ref>` upstream, including remotes with slashes. Current-branch selection clears the worktree override so a nested project retains its cwd. Reusing a different worktree requires the server's physical-root determination; nested projects and older servers visibly refuse when safe cwd mapping cannot be established. The optional wire fields use existing RPC and Git snapshots, with no extra per-ref process or new cache. New-worktree mode remains unchanged.

The latest Macroscope stale-path finding is fixed in this head: successful `switchRef` explicitly returns `worktreePath: null`. The existing checkout test now creates a real old linked worktree, frees the branch there, switches the original checkout to that branch, and requires a null override. The saved failing-before log and final passing log support that regression. Prior wrong-remote, nested-current-cwd, nested-other-worktree, and symlink-root concerns are also addressed in the full diff. I found no further concrete defect or needless complexity that should block merging.

Verification: `git diff --check origin/main...HEAD` passed in this read-only review. Existing logs for this head show 41 focused mobile tests passing; earlier applicable logs show 8 server ref tests and 25 runtime VCS/action tests passing, four affected-package typechecks and scoped lint/format passing. I did not rerun suites or use a browser, dev server, or device. Native draft submission and final agent cwd remain unobserved on this head; the maintainer accepted headless proof. Published CI and Android media in the saved snapshot are for the prior SHA. The saved PR body also describes old behavior (including no upstream metadata), so publication should update that description and obtain checks for the pushed final head before claiming GitHub merge readiness.

Read-only audit: no repository edits, commits, pushes, GitHub calls, browser/device work, or delegation.