[fireboltdude1357]

Fork builds don't carry the fixes for threads stuck on "Syncing messages..." while agents run. Both fixes sit on their own patch branches. This adds those branches to .github/fork-patches.txt so the nightly build merges them:

• patch/v2-transcript-cache follows fix(server): cache absent legacy transcripts for V2 threads pingdotgg/t3code#24707 (fork PR fix(server): opening a v2 thread stops re-checking its legacy transcript #107). Opening a thread created in v2 stops re-checking its legacy transcript.
• patch/sqlite-reader-pool follows fix(shared): let SQLite reads proceed beside slow reads pingdotgg/t3code#24762 (fork PR fix(shared): thread opens stop waiting behind every other SQLite read #110). The pool of four readers, with reads admitted in the order they asked.

Merge #107 and #110 first, so the build picks up the reviewed patches. The build was also failing on upstream conflicts in two existing patches; #108 and #109 fix those, and they need to merge before the next build passes.

Verification. In a scratch worktree at upstream 0b0417a, the patch list as it will be merged cleanly in order (release from #108, cache-compaction from #109, then the existing patches, then these two). On the merged tree the build's checks pass:

• pnpm install --no-frozen-lockfile --fix-lockfile: done.
• vp run typecheck: 35 of 35 tasks pass.
• The 17 test files the patches add or change: 580 passed.

Review tier: 7/10; once this merges, the nightly build pulls in whatever is on these patch branches, which changes how every server read is scheduled

Two-way door: removing the lines drops the patches from the next build

Blast radius: which patches the fork nightly merges

Changes made by Claude Opus 5.5 in Claude Code, running in T3 Code.

🤖 Generated with Claude Code

[fireboltdude1357]

Manual review round 1: crev (claude-opus-5-5 + gpt-6.1-sol) (tier 7/10, deep review)

1 verified finding: 0 critical, 1 major, 0 minor. 1 posted inline, best first; 0 below.

Reviewed 1 files (+2 -0), 43c7bebe..2c3d2db7 against origin/patch/release.

Severity	Location	Finding	Raised by	Evidence
major	.github/fork-patches.txt:12-13	Land both fixes before enabling their patch branches	1 finder, one model	L3

Tier 7/10 from claude-opus-5-5: Build config line pulls whole patch branches (sqlite reader pool scheduling, transcript caching) into every nightly fork build; failures may not show up right away

Complexity low: Two config lines in a patch list; the complex logic lives in separately reviewed PRs