chore: sync T3 Code upstream through 6ea01f8d - #92
Conversation
…otgg#14025) Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
…pingdotgg#14027) Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
…sh (pingdotgg#14029) Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
… parent's model (pingdotgg#14540) Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
…d plugins (pingdotgg#14542) Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
…nup (pingdotgg#14553) Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
…ingdotgg#14573) Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
…otgg#12045) Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
pingdotgg#12046) Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
…tale (pingdotgg#12047) Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
…ingdotgg#12048) Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
…URL (pingdotgg#12049) Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
…UIScreen.main (pingdotgg#12050) Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
…bers (pingdotgg#12051) Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
…ingdotgg#12052) Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
…ard (pingdotgg#13487) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: t3-code[bot] <269035359+t3-code[bot]@users.noreply.github.com>
…tgg#14635) Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Thread transfer impact✅ Thread transfer remains within every enforced ceiling.
Baseline: Scenario and decoded snapshot size10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.
Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed. |
Workbench demoOpen the private 20-minute demo. Sign in to Vercel, then choose Open demo. Reopening this link in the same browser resumes its running demo; Start new demo creates a fresh one. Jira starts disconnected. Application, runtime startup, fixtures, and native smoke: PR Expired? Return to this link and launch again. Use synthetic content with the free OpenCode model. |
Summary
Merge 23 upstream commits through
6ea01f8d24419019588f2be589681929d8e26b0cinto product mainda6a067bc56db69cb5d988f5abf903df01581614, preserving upstream ancestry. PR #91's first-use Ticket repository review and staged Save/Cancel remain intact.Changes
0.88.0-rc.3, scene-aware native controls, notification changes, and Android subscription widgets..github/workflows/ci.ymlwith upstream's parallel jobs, six weighted server shards, and aggregate Check. Retain the fork's runners, timeouts, serialized package tests, and release guard. Guard APT source edits by file existence.pnpm-lock.yamlfrom merged manifests with pnpm11.10.0and Node24.13.1; frozen installation passes.Isolation assessment
Compared pre-PR90
c108a3077e, post-PR90c91a29326a, and current productda6a067bcagainst the same pinned upstream SHA, before synchronization:All share merge base
67b175a4; conflicts remain CI and the lockfile. These results do not establish reduced overlap or conflict frequency.Isolation commits
3d006d0873,9ef1b328e0,a4e0ba14f4,79e1444d98, and97ea2a041bmoved RPC service acquisition, sidebar/context slots, desktop policy, and Ticket summary ownership into fork modules. PR #90 also changed notifications and demos; its full diff is not an isolation metric. Earlier isolation work already exists in the selected baseline.Every affected shared integration was reviewed, including clean merges in CommandPalette, RPC authorization/contracts, WebSocket composition, server tests/build configuration, and release policy. The RPC service adapter survived upstream project/session changes without manual repair. Its fork delta against the common merge base shrank from 25 to 13 added lines across PR #90. This is a smaller integration footprint, not a measured reduction in sync intervention. CommandPalette, auth, and schema adapters predate PR #90. Sidebar, desktop policy, and summary extraction were not stressed by this upstream range. Package boundaries held; explicit shared seams and CI/dependency conflicts remain maintenance costs.
Verification
TMPDIR=/private/tmp.da6a067bc..7f5df57dd.To reproduce the focused lifecycle checks, run from
scripts:vp exec playwright test --config workbench-regression/playwright.config.ts planning.spec.ts threads.spec.ts ticket-workspace.spec.ts. The fixture owns disposable state and services.Limits
Exact-product Expo/RN native compilation and device runtime are unverified: this host has Command Line Tools, without
simctl, CocoaPods, or Android tools. Mobile type/unit checks and current-head native static analysis pass. The fingerprint check confirms changes to both iOS and Android, requiring new native clients before compatible OTAs.Upstream's Expo migration and native release validation report successful iOS and Android Release previews, Xcode/device smoke, and 120 Android native tests. Those records cover upstream refs; they do not verify this exact product merge. Matching product native builds and device validation remain required before mobile release.
Existing local changes and the demo on ports 7580/15620 are preserved. No release is tagged, published, or deployed by this sync.
The merge automatically queued the unchanged Mobile EAS Production workflow. That run was canceled before any job started. The pre-existing workflow has no repository guard and can submit builds or publish OTAs when credentials are configured; guarding future fork-main runs is separate follow-up work.
Implemented and reviewed with GPT-6 in Codex.