chore: sync upstream pingdotgg/t3code (20260721)

[wizzoapp]

Nightly upstream sync of pingdotgg/t3code → agriffiths-bots/t3code.

Cherry-picked 31 upstream commits (2640e6d..c0bb237, upstream/main). One commit (pingdotgg#4186 "Pass CLI OAuth config to hosted web deploy") applied empty — its 2-line change targets upstream's hosted web-deploy job, which this fork's Windows-only release pipeline does not have.

Notable conflict resolutions

The bulk of the work was reconciling two large upstream rewrites of the shell/thread synchronization protocol (pingdotgg#4163 "Synchronize mobile threads with authoritative shell snapshots" and pingdotgg#4177 "speed up new-chat propagation and offline catch-up") against the fork's audience-scoping and thread-reconciliation features.

• Client shell (state/shell.ts, shell-sync.test.ts): adopted upstream's versions. Upstream's server rewrite (perf(orchestration): speed up new-chat propagation and offline catch-up pingdotgg/t3code#4177) supersedes the fork's Fix shell replay gaps #142 replay-gap watchdog (server no longer emits a caught-up marker), so the fork's client-side watchdog was orphaned. Removed the now-dead caught-up contract member and the obsolete fork shell server tests; upstream's coalescing tests cover the behavior.
• Client threads (state/threads.ts): kept the fork's reconciliation subsystem (storage-epoch cursors, revision reconciliation, audience-scoped resume) and re-wired it onto upstream's subscribeDynamic model — establish the base snapshot once, then resume via the live cursor on foreground/session resubscribes (completion-marker + foregroundResubscriptions grafted in).
• Server (ws.ts): took upstream's coalescing subscribeShell + projectUpsertOrRemove/threadUpsertOrRemove helpers while preserving the fork's requireAudienceOpaqueEventCursor guard and project.data-audience-set full-refresh path (projection reads are audience-scoped, so coalescing stays audience-safe).
• Additive/import merges: ClaudeAdapter (SDK executable path + worker isolation), OpenCodeAdapter (resume + MCP session), Sidebar (archive-from-context-menu + tree rows), DesktopWindow (window-bounds restore + backend-status splash), ChatComposer, model/registry tests, and the fork's superset of test files were kept.
• .github/workflows/release.yml: kept the fork's Windows-only reusable pipeline.

Verification

• vp run typecheck ✅
• vp check ✅
• vp test run ✅ — 6380 passed, 17 skipped, 0 failed (702 files)

Gated by CI + the upstream-sync procedure (per-commit factory gate skipped via the audited sync escape hatch).

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit:aeb936280a

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[adamfgr]

Auto-approved by wizzo-approve: all policy conditions verified against HEAD 7366840.

[wizzoapp]

Nightly upstream sync of pingdotgg/t3code → agriffiths-bots/t3code.

Cherry-picked 31 upstream commits (2640e6d..c0bb237, upstream/main). One commit (pingdotgg#4186 "Pass CLI OAuth config to hosted web deploy") applied empty — its 2-line change targets upstream's hosted web-deploy job, which this fork's Windows-only release pipeline does not have.

Notable conflict resolutions

The bulk of the work was reconciling two large upstream rewrites of the shell/thread synchronization protocol (pingdotgg#4163 "Synchronize mobile threads with authoritative shell snapshots" and pingdotgg#4177 "speed up new-chat propagation and offline catch-up") against the fork's audience-scoping and thread-reconciliation features.

• Client shell (state/shell.ts, shell-sync.test.ts): adopted upstream's versions. Upstream's server rewrite (perf(orchestration): speed up new-chat propagation and offline catch-up pingdotgg/t3code#4177) supersedes the fork's Fix shell replay gaps #142 replay-gap watchdog (server no longer emits a caught-up marker), so the fork's client-side watchdog was orphaned. Removed the now-dead caught-up contract member and the obsolete fork shell server tests; upstream's coalescing tests cover the behavior.
• Client threads (state/threads.ts): kept the fork's reconciliation subsystem (storage-epoch cursors, revision reconciliation, audience-scoped resume) and re-wired it onto upstream's subscribeDynamic model — establish the base snapshot once, then resume via the live cursor on foreground/session resubscribes (completion-marker + foregroundResubscriptions grafted in).
• Server (ws.ts): took upstream's coalescing subscribeShell + projectUpsertOrRemove/threadUpsertOrRemove helpers while preserving the fork's requireAudienceOpaqueEventCursor guard and project.data-audience-set full-refresh path (projection reads are audience-scoped, so coalescing stays audience-safe).
• Additive/import merges: ClaudeAdapter (SDK executable path + worker isolation), OpenCodeAdapter (resume + MCP session), Sidebar (archive-from-context-menu + tree rows), DesktopWindow (window-bounds restore + backend-status splash), ChatComposer, model/registry tests, and the fork's superset of test files were kept.
• .github/workflows/release.yml: kept the fork's Windows-only reusable pipeline.

Verification

• vp run typecheck ✅
• vp check ✅
• vp test run ✅ — 6380 passed, 17 skipped, 0 failed (702 files)

Gated by CI + the upstream-sync procedure (per-commit factory gate skipped via the audited sync escape hatch).

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit:aeb936280a

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[adamfgr]

Auto-approved by wizzo-approve: all policy conditions verified against HEAD 7366840.

[wizzoapp]

Nightly upstream sync of pingdotgg/t3code → agriffiths-bots/t3code.

Cherry-picked 31 upstream commits (2640e6d..c0bb237, upstream/main). One commit (pingdotgg#4186 "Pass CLI OAuth config to hosted web deploy") applied empty — its 2-line change targets upstream's hosted web-deploy job, which this fork's Windows-only release pipeline does not have.

Notable conflict resolutions

The bulk of the work was reconciling two large upstream rewrites of the shell/thread synchronization protocol (pingdotgg#4163 "Synchronize mobile threads with authoritative shell snapshots" and pingdotgg#4177 "speed up new-chat propagation and offline catch-up") against the fork's audience-scoping and thread-reconciliation features.

• Client shell (state/shell.ts, shell-sync.test.ts): adopted upstream's versions. Upstream's server rewrite (perf(orchestration): speed up new-chat propagation and offline catch-up pingdotgg/t3code#4177) supersedes the fork's Fix shell replay gaps #142 replay-gap watchdog (server no longer emits a caught-up marker), so the fork's client-side watchdog was orphaned. Removed the now-dead caught-up contract member and the obsolete fork shell server tests; upstream's coalescing tests cover the behavior.
• Client threads (state/threads.ts): kept the fork's reconciliation subsystem (storage-epoch cursors, revision reconciliation, audience-scoped resume) and re-wired it onto upstream's subscribeDynamic model — establish the base snapshot once, then resume via the live cursor on foreground/session resubscribes (completion-marker + foregroundResubscriptions grafted in).
• Server (ws.ts): took upstream's coalescing subscribeShell + projectUpsertOrRemove/threadUpsertOrRemove helpers while preserving the fork's requireAudienceOpaqueEventCursor guard and project.data-audience-set full-refresh path (projection reads are audience-scoped, so coalescing stays audience-safe).
• Additive/import merges: ClaudeAdapter (SDK executable path + worker isolation), OpenCodeAdapter (resume + MCP session), Sidebar (archive-from-context-menu + tree rows), DesktopWindow (window-bounds restore + backend-status splash), ChatComposer, model/registry tests, and the fork's superset of test files were kept.
• .github/workflows/release.yml: kept the fork's Windows-only reusable pipeline.

Verification

• vp run typecheck ✅
• vp check ✅
• vp test run ✅ — 6380 passed, 17 skipped, 0 failed (702 files)

Gated by CI + the upstream-sync procedure (per-commit factory gate skipped via the audited sync escape hatch).

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit:aeb936280a

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[adamfgr]

Auto-approved by wizzo-approve: all policy conditions verified against HEAD 7366840.

[wizzoapp]

Nightly upstream sync of pingdotgg/t3code → agriffiths-bots/t3code.

Cherry-picked 31 upstream commits (2640e6d..c0bb237, upstream/main). One commit (pingdotgg#4186 "Pass CLI OAuth config to hosted web deploy") applied empty — its 2-line change targets upstream's hosted web-deploy job, which this fork's Windows-only release pipeline does not have.

Notable conflict resolutions

The bulk of the work was reconciling two large upstream rewrites of the shell/thread synchronization protocol (pingdotgg#4163 "Synchronize mobile threads with authoritative shell snapshots" and pingdotgg#4177 "speed up new-chat propagation and offline catch-up") against the fork's audience-scoping and thread-reconciliation features.

• Client shell (state/shell.ts, shell-sync.test.ts): adopted upstream's versions. Upstream's server rewrite (perf(orchestration): speed up new-chat propagation and offline catch-up pingdotgg/t3code#4177) supersedes the fork's Fix shell replay gaps #142 replay-gap watchdog (server no longer emits a caught-up marker), so the fork's client-side watchdog was orphaned. Removed the now-dead caught-up contract member and the obsolete fork shell server tests; upstream's coalescing tests cover the behavior.
• Client threads (state/threads.ts): kept the fork's reconciliation subsystem (storage-epoch cursors, revision reconciliation, audience-scoped resume) and re-wired it onto upstream's subscribeDynamic model — establish the base snapshot once, then resume via the live cursor on foreground/session resubscribes (completion-marker + foregroundResubscriptions grafted in).
• Server (ws.ts): took upstream's coalescing subscribeShell + projectUpsertOrRemove/threadUpsertOrRemove helpers while preserving the fork's requireAudienceOpaqueEventCursor guard and project.data-audience-set full-refresh path (projection reads are audience-scoped, so coalescing stays audience-safe).
• Additive/import merges: ClaudeAdapter (SDK executable path + worker isolation), OpenCodeAdapter (resume + MCP session), Sidebar (archive-from-context-menu + tree rows), DesktopWindow (window-bounds restore + backend-status splash), ChatComposer, model/registry tests, and the fork's superset of test files were kept.
• .github/workflows/release.yml: kept the fork's Windows-only reusable pipeline.

Verification

• vp run typecheck ✅
• vp check ✅
• vp test run ✅ — 6380 passed, 17 skipped, 0 failed (702 files)

Gated by CI + the upstream-sync procedure (per-commit factory gate skipped via the audited sync escape hatch).

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit:aeb936280a

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[adamfgr]

Auto-approved by wizzo-approve: all policy conditions verified against HEAD 7366840.

[wizzoapp]

Nightly upstream sync of pingdotgg/t3code → agriffiths-bots/t3code.

Cherry-picked 31 upstream commits (2640e6d..c0bb237, upstream/main). One commit (pingdotgg#4186 "Pass CLI OAuth config to hosted web deploy") applied empty — its 2-line change targets upstream's hosted web-deploy job, which this fork's Windows-only release pipeline does not have.

Notable conflict resolutions

The bulk of the work was reconciling two large upstream rewrites of the shell/thread synchronization protocol (pingdotgg#4163 "Synchronize mobile threads with authoritative shell snapshots" and pingdotgg#4177 "speed up new-chat propagation and offline catch-up") against the fork's audience-scoping and thread-reconciliation features.

• Client shell (state/shell.ts, shell-sync.test.ts): adopted upstream's versions. Upstream's server rewrite (perf(orchestration): speed up new-chat propagation and offline catch-up pingdotgg/t3code#4177) supersedes the fork's Fix shell replay gaps #142 replay-gap watchdog (server no longer emits a caught-up marker), so the fork's client-side watchdog was orphaned. Removed the now-dead caught-up contract member and the obsolete fork shell server tests; upstream's coalescing tests cover the behavior.
• Client threads (state/threads.ts): kept the fork's reconciliation subsystem (storage-epoch cursors, revision reconciliation, audience-scoped resume) and re-wired it onto upstream's subscribeDynamic model — establish the base snapshot once, then resume via the live cursor on foreground/session resubscribes (completion-marker + foregroundResubscriptions grafted in).
• Server (ws.ts): took upstream's coalescing subscribeShell + projectUpsertOrRemove/threadUpsertOrRemove helpers while preserving the fork's requireAudienceOpaqueEventCursor guard and project.data-audience-set full-refresh path (projection reads are audience-scoped, so coalescing stays audience-safe).
• Additive/import merges: ClaudeAdapter (SDK executable path + worker isolation), OpenCodeAdapter (resume + MCP session), Sidebar (archive-from-context-menu + tree rows), DesktopWindow (window-bounds restore + backend-status splash), ChatComposer, model/registry tests, and the fork's superset of test files were kept.
• .github/workflows/release.yml: kept the fork's Windows-only reusable pipeline.

Verification

• vp run typecheck ✅
• vp check ✅
• vp test run ✅ — 6380 passed, 17 skipped, 0 failed (702 files)

Gated by CI + the upstream-sync procedure (per-commit factory gate skipped via the audited sync escape hatch).

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit:aeb936280a

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[adamfgr]

Auto-approved by wizzo-approve: all policy conditions verified against HEAD 7366840.

[wizzoapp]

Nightly upstream sync of pingdotgg/t3code → agriffiths-bots/t3code.

Cherry-picked 31 upstream commits (2640e6d..c0bb237, upstream/main). One commit (pingdotgg#4186 "Pass CLI OAuth config to hosted web deploy") applied empty — its 2-line change targets upstream's hosted web-deploy job, which this fork's Windows-only release pipeline does not have.

Notable conflict resolutions

The bulk of the work was reconciling two large upstream rewrites of the shell/thread synchronization protocol (pingdotgg#4163 "Synchronize mobile threads with authoritative shell snapshots" and pingdotgg#4177 "speed up new-chat propagation and offline catch-up") against the fork's audience-scoping and thread-reconciliation features.

• Client shell (state/shell.ts, shell-sync.test.ts): adopted upstream's versions. Upstream's server rewrite (perf(orchestration): speed up new-chat propagation and offline catch-up pingdotgg/t3code#4177) supersedes the fork's Fix shell replay gaps #142 replay-gap watchdog (server no longer emits a caught-up marker), so the fork's client-side watchdog was orphaned. Removed the now-dead caught-up contract member and the obsolete fork shell server tests; upstream's coalescing tests cover the behavior.
• Client threads (state/threads.ts): kept the fork's reconciliation subsystem (storage-epoch cursors, revision reconciliation, audience-scoped resume) and re-wired it onto upstream's subscribeDynamic model — establish the base snapshot once, then resume via the live cursor on foreground/session resubscribes (completion-marker + foregroundResubscriptions grafted in).
• Server (ws.ts): took upstream's coalescing subscribeShell + projectUpsertOrRemove/threadUpsertOrRemove helpers while preserving the fork's requireAudienceOpaqueEventCursor guard and project.data-audience-set full-refresh path (projection reads are audience-scoped, so coalescing stays audience-safe).
• Additive/import merges: ClaudeAdapter (SDK executable path + worker isolation), OpenCodeAdapter (resume + MCP session), Sidebar (archive-from-context-menu + tree rows), DesktopWindow (window-bounds restore + backend-status splash), ChatComposer, model/registry tests, and the fork's superset of test files were kept.
• .github/workflows/release.yml: kept the fork's Windows-only reusable pipeline.

Verification

• vp run typecheck ✅
• vp check ✅
• vp test run ✅ — 6380 passed, 17 skipped, 0 failed (702 files)

Gated by CI + the upstream-sync procedure (per-commit factory gate skipped via the audited sync escape hatch).

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit:aeb936280a

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[adamfgr]

Auto-approved by wizzo-approve: all policy conditions verified against HEAD 7366840.

[wizzoapp]

Nightly upstream sync of pingdotgg/t3code → agriffiths-bots/t3code.

Cherry-picked 31 upstream commits (2640e6d..c0bb237, upstream/main). One commit (pingdotgg#4186 "Pass CLI OAuth config to hosted web deploy") applied empty — its 2-line change targets upstream's hosted web-deploy job, which this fork's Windows-only release pipeline does not have.

Notable conflict resolutions

The bulk of the work was reconciling two large upstream rewrites of the shell/thread synchronization protocol (pingdotgg#4163 "Synchronize mobile threads with authoritative shell snapshots" and pingdotgg#4177 "speed up new-chat propagation and offline catch-up") against the fork's audience-scoping and thread-reconciliation features.

• Client shell (state/shell.ts, shell-sync.test.ts): adopted upstream's versions. Upstream's server rewrite (perf(orchestration): speed up new-chat propagation and offline catch-up pingdotgg/t3code#4177) supersedes the fork's Fix shell replay gaps #142 replay-gap watchdog (server no longer emits a caught-up marker), so the fork's client-side watchdog was orphaned. Removed the now-dead caught-up contract member and the obsolete fork shell server tests; upstream's coalescing tests cover the behavior.
• Client threads (state/threads.ts): kept the fork's reconciliation subsystem (storage-epoch cursors, revision reconciliation, audience-scoped resume) and re-wired it onto upstream's subscribeDynamic model — establish the base snapshot once, then resume via the live cursor on foreground/session resubscribes (completion-marker + foregroundResubscriptions grafted in).
• Server (ws.ts): took upstream's coalescing subscribeShell + projectUpsertOrRemove/threadUpsertOrRemove helpers while preserving the fork's requireAudienceOpaqueEventCursor guard and project.data-audience-set full-refresh path (projection reads are audience-scoped, so coalescing stays audience-safe).
• Additive/import merges: ClaudeAdapter (SDK executable path + worker isolation), OpenCodeAdapter (resume + MCP session), Sidebar (archive-from-context-menu + tree rows), DesktopWindow (window-bounds restore + backend-status splash), ChatComposer, model/registry tests, and the fork's superset of test files were kept.
• .github/workflows/release.yml: kept the fork's Windows-only reusable pipeline.

Verification

• vp run typecheck ✅
• vp check ✅
• vp test run ✅ — 6380 passed, 17 skipped, 0 failed (702 files)

Gated by CI + the upstream-sync procedure (per-commit factory gate skipped via the audited sync escape hatch).

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit:aeb936280a

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[adamfgr]

Auto-approved by wizzo-approve: all policy conditions verified against HEAD 7366840.

[wizzoapp]

Nightly upstream sync of pingdotgg/t3code → agriffiths-bots/t3code.

Cherry-picked 31 upstream commits (2640e6d..c0bb237, upstream/main). One commit (pingdotgg#4186 "Pass CLI OAuth config to hosted web deploy") applied empty — its 2-line change targets upstream's hosted web-deploy job, which this fork's Windows-only release pipeline does not have.

Notable conflict resolutions

The bulk of the work was reconciling two large upstream rewrites of the shell/thread synchronization protocol (pingdotgg#4163 "Synchronize mobile threads with authoritative shell snapshots" and pingdotgg#4177 "speed up new-chat propagation and offline catch-up") against the fork's audience-scoping and thread-reconciliation features.

• Client shell (state/shell.ts, shell-sync.test.ts): adopted upstream's versions. Upstream's server rewrite (perf(orchestration): speed up new-chat propagation and offline catch-up pingdotgg/t3code#4177) supersedes the fork's Fix shell replay gaps #142 replay-gap watchdog (server no longer emits a caught-up marker), so the fork's client-side watchdog was orphaned. Removed the now-dead caught-up contract member and the obsolete fork shell server tests; upstream's coalescing tests cover the behavior.
• Client threads (state/threads.ts): kept the fork's reconciliation subsystem (storage-epoch cursors, revision reconciliation, audience-scoped resume) and re-wired it onto upstream's subscribeDynamic model — establish the base snapshot once, then resume via the live cursor on foreground/session resubscribes (completion-marker + foregroundResubscriptions grafted in).
• Server (ws.ts): took upstream's coalescing subscribeShell + projectUpsertOrRemove/threadUpsertOrRemove helpers while preserving the fork's requireAudienceOpaqueEventCursor guard and project.data-audience-set full-refresh path (projection reads are audience-scoped, so coalescing stays audience-safe).
• Additive/import merges: ClaudeAdapter (SDK executable path + worker isolation), OpenCodeAdapter (resume + MCP session), Sidebar (archive-from-context-menu + tree rows), DesktopWindow (window-bounds restore + backend-status splash), ChatComposer, model/registry tests, and the fork's superset of test files were kept.
• .github/workflows/release.yml: kept the fork's Windows-only reusable pipeline.

Verification

• vp run typecheck ✅
• vp check ✅
• vp test run ✅ — 6380 passed, 17 skipped, 0 failed (702 files)

Gated by CI + the upstream-sync procedure (per-commit factory gate skipped via the audited sync escape hatch).

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit:aeb936280a

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[adamfgr]

Auto-approved by wizzo-approve: all policy conditions verified against HEAD 7366840.