[kalvenschraut]

Integrate 1,289 commits from pingdotgg/t3code main, b68aedfdb71534bfdfbe55771ef2e686742faa8e..50a2f5b9f415665f48b4d71df4ff68c858578199, into RTVision rtvision at 8e8fbe199181880acb3af297155671598ec9f01c. Preserve upstream merge ancestry and prepare release 0.0.111.

Upstream adds native resume for stopped provider threads, approval for new T3 Connect devices, keep-awake while agents work, agent-managed theme colors/CSS, improved project folder search and drag/drop, spreadsheet resizing, Antigravity goals and managed updates, OpenCode usage limits, and Codex access-program selection. Fixes cover long-thread performance, restart recovery and queued work, provider configuration, expired uploads, terminal links and startup failures, PR activity and large diffs, remote pairing/forwarding, and mobile navigation/media.

Prefer upstream's diff viewer, native annotation geometry, Forgejo PR discovery, service-home ownership locks, nonblocking startup and provider fixes. Retain Gitea integrations and granular capabilities, scoped cross-device PR refreshes, Vim navigation, terminal editors/WSL SSH runner, environment themes, compressed database backups and runtime pruning, RTVision update/registry routing, Node/npm/OpenRC and Alpine support, Windows WSL packaging and the existing release workflow. Combine upstream cancellable backups and low-disk startup handling with the fork's compressed backups; adapt the disk-recovery fixtures to select their expected plain-backup path. Keep ffi-rs@1.3.7, whose npm musl package is correctly labeled.

Validation: focused server, update/backup, Gitea/Forgejo, SSH lifecycle, Cursor, PR refresh/diff logic and version-routing suites passed after targeted repairs. Server, web, desktop and SSH scoped typechecks passed. Staged formatting, lint and knip passed. No browser/computer use or live service action. CI owns the full suites.

Release status: merged as db3e1dabf7f65efd56f45693dfaddcbb7d3f9624, with the same tree as reviewed 97fc354f1a6e292aaeda921c6889f7ff04d1b2d9. Primary and fresh GPT-6 Astra source GO and all applicable CI checks passed. CodeRabbit explicitly refused its 2,501-file diff against a 100-file limit; the maintainer-authorized large-diff fallback applies. The maintainer approved Cursor SDK 1.3.1's musl metadata exception after successful Alpine module loading; all 11 focused Cursor replay tests passed. The recurring prompt records the exception. Merged-head build, artifact/checksum verification, npm publication/integrity, clean Alpine plain-npm install, preflight, actual serve probe, and GitHub draft publication are in progress.

Model and harness: GPT-6.1 Sol through Codex in T3 Code; independent GPT-6 Astra review requested separately.

[kalvenschraut]

@coderabbitai full review

Please review final candidate 0cb34f49cc3de9be4d11d873d77f4c5533994557 at the maintainer-authorized high-level upstream integration scope: changelog, conflict resolutions, retained fork behavior, dependency changes, and concrete regression risks. Exclude vendored read-only references from substantive source review. Please state any coverage limit explicitly; a green status alone is not approval.

Primary source integration GO for this SHA after selected overlap review and passing focused validation. The Cursor SDK musl metadata exception, independent review, CI and all release qualification gates remain separate and pending.

[github-actions]

This PR changes the test suite by +1548 test cases (browser +164, unit +764, server +620).

New browser test files: apps/web/src/components/AppSidebarLayout.browser.test.tsx, apps/web/src/components/GitActionsControl.composition.browser.test.tsx, apps/web/src/components/RightPanelSheet.browser.test.tsx, apps/web/src/components/Sidebar.shiftGuard.browser.test.ts, apps/web/src/components/chat/ComposerPendingUserInputPanel.browser.test.tsx, apps/web/src/components/chat/DraftHeroHeadline.browser.test.tsx, apps/web/src/components/chat/MarkdownCodeBlock.browser.test.tsx, apps/web/src/components/chat/McpAppFrame.browser.test.tsx, apps/web/src/components/chat/ThreadDetailsPanel.browser.test.tsx, apps/web/src/components/chat/ThreadRelationshipsControl.remote-parent.browser.test.tsx, apps/web/src/components/chat/useComposerAttachmentIntake.browser.test.tsx, apps/web/src/components/chat/useComposerSelection.browser.test.tsx, apps/web/src/components/chat/useComposerStash.browser.test.tsx, apps/web/src/components/chat/useDraftEnvironmentRouting.browser.test.tsx, apps/web/src/components/cloud/CloudEnvironmentConnectList.browser.test.tsx, apps/web/src/components/diffs/DiffFileTree.browser.test.tsx, apps/web/src/components/diffs/StyledDiffCodeView.browser.test.tsx, apps/web/src/components/files/ReadOnlySourcePreview.browser.test.tsx, apps/web/src/components/files/office/sheet-resize.browser.test.ts, apps/web/src/components/preview/ThreadPreviewMiniPlayer.browser.test.tsx, apps/web/src/components/settings/AddUsageLimitSourceDialog.browser.test.tsx, apps/web/src/components/settings/IntegrationsSettings.browser.test.tsx, apps/web/src/components/settings/LinkedEnvironmentsSettings.browser.test.tsx, apps/web/src/hooks/useShownThreadRouteTarget.browser.test.tsx, apps/web/src/themeCss.browser.test.ts.
Each browser test file costs CI seconds of module loading before its first test runs; a unit test costs milliseconds.

Keep tests that would fail for a real reason, and test logic below the UI where it can be. See Testing.

[coderabbitai]

Action not completed

Review skipped: 2501 files exceed the limit of 100.

[kalvenschraut]

Independent GPT-6 Astra source integration GO received for 0cb34f49cc3de9be4d11d873d77f4c5533994557.

The reviewer verified both merge parents and 0.0.111, then reviewed the changelog and selected actual local integration diffs across PR/Gitea/Forgejo behavior, backups/low-disk startup, SSH, WSL/editors, dependencies and packaging. No source integration blocker was found at the requested high-level scope; vendored references were excluded.

Review task: node:delegated-task:command%3Amcp%3A955e0483-1e32-46c3-b361-c0551497ea39%3Adelegate-task%3A821cd7b9-cc5b-41a6-a87c-f58c23ebaa17, executed model gpt-6-astra.

CodeRabbit explicitly refused coverage: #127 (comment), "Review skipped: 2501 files exceed the limit of 100." The owning maintainer's large-diff fallback applies; the skipped status is not approval.

CI subsequently exposed a stale Codex expectation and a non-Git scheduled-task integration regression. A targeted repair is in progress. Both primary and Astra approval will be renewed for the new final SHA. The pending Cursor musl-metadata exception, passing CI and release qualification remain mandatory.

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	5.0 KiB	5.0 KiB	0 B (0.0%)	6.8 KiB	✅
Codex	Thread snapshot wire	3.8 KiB	3.8 KiB	0 B (0.0%)	4.9 KiB	✅
Codex	Live turn WebSocket wire	1.2 KiB	1.2 KiB	0 B (0.0%)	2.0 KiB	✅
Codex	Live turn WebSocket decoded	21.5 KiB	21.5 KiB	0 B (0.0%)	24.4 KiB	✅
Codex	Live turn messages	1	1	0 (0.0%)	8	✅
Claude	Total thread wire	5.0 KiB	5.0 KiB	0 B (0.0%)	6.8 KiB	✅
Claude	Thread snapshot wire	3.8 KiB	3.8 KiB	0 B (0.0%)	4.9 KiB	✅
Claude	Live turn WebSocket wire	1.2 KiB	1.2 KiB	0 B (0.0%)	2.0 KiB	✅
Claude	Live turn WebSocket decoded	21.9 KiB	21.9 KiB	+1 B (+0.0%)	24.4 KiB	✅
Claude	Live turn messages	1	1	0 (0.0%)	8	✅

Baseline: 8e8fbe1 · PR result: 97fc354 · Source CI: success

Scenario and decoded snapshot size

10 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.

• Codex decoded thread snapshot: 108.5 KiB
• Claude decoded thread snapshot: 108.8 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

[kalvenschraut]

Primary source integration GO renewed for 0cda4fbb485f3819be1c09cceeeeda6a2b9ee487 after the targeted follow-up to 0cb34f49cc3de9be4d11d873d77f4c5533994557.

The follow-up normalizes non-Git/Scratch scheduled tasks before worktree validation and returns root strategy for their default. It also restores the missing mobile View import, aligns existing startup/desktop/preview fixtures with integrated behavior, and preserves Vim find-again after the panel closes with a minimal patch over upstream @pierre/diffs beta.4. Upstream owns the rest of the new diff search implementation. The highlight test now checks the active match's position across text nodes rather than assuming the browser makes one text node.

Validation: check:changed passed on the eleven-file CI repair, including 435 tests, six affected package typechecks, scoped format/lint, GraphQL generation, knip and mobile React compiler checks. The added dependency patch installed successfully with its updated lockfile hash; web typecheck and browser-test lint passed afterward. The repository's final staged format/lint/knip hooks also passed. The two existing browser regressions are left to CI under the maintainer's no-local-browser instruction.

Fresh Astra exact-SHA renewal is being requested. CodeRabbit's recorded 100-file coverage refusal remains applicable; no full-review command was repeated. The Cursor SDK musl-metadata exception remains pending, and CI/release artifact/npm/install/preflight/serve gates are still mandatory.

[kalvenschraut]

Independent GPT-6 Astra source integration GO renewed for exact candidate 0cda4fbb485f3819be1c09cceeeeda6a2b9ee487. No blocking source findings or further repair required.

The reviewer examined the 14-file follow-up, selected actual local diffs against both integration parents, upstream summaries, dependencies and retained fork behavior, excluding .repos. Verified non-Git task normalization and Git validation, the minimal closed-panel Vim search repeat patch and installed lockfile resolution, highlight offsets across text nodes, and mobile/startup/Codex/SSH/preview repairs. Selected Gitea routing/capabilities, private registry, packaging and WSL integrations remain preserved.

Review task: node:delegated-task:command%3Amcp%3A955e0483-1e32-46c3-b361-c0551497ea39%3Adelegate-task%3A3a898b8f-28ef-45c4-9fd2-7509411aa5df, executed model gpt-6-astra. Together with the exact-SHA primary GO, this satisfies the source-review portion of the maintainer-authorized large-diff fallback. CodeRabbit's explicit 2,501-file/100-file refusal is recorded at #127 (comment).

The thread-transfer report comment concerns superseded candidate 0cb34f4 and says it will update after the next completed run. Current candidate CI is https://github.com/RTVision/t3code/actions/runs/43700460977 and was still running when checked.

Source approval does not waive the pending Cursor SDK musl-metadata user exception, passing applicable CI/no blockers, or release artifact/npm/install/preflight/serve gates. No merge or release publication yet.

[kalvenschraut]

Primary source integration GO renewed for 97fc354f1a6e292aaeda921c6889f7ff04d1b2d9 after the nine-line SSH follow-up to 0cda4fbb485f3819be1c09cceeeeda6a2b9ee487.

The previous Test job was cancelled at its 30-minute ceiling after daemonDiscovery tests failed and their worker could not terminate. Check correctly failed because Test was cancelled. Every other CI job passed, including both web shards, all eight server shards, build/typecheck, mobile native analysis, Rust and release smoke. The thread-transfer report for that head is within all enforced ceilings.

The follow-up restores the fork's two daemon ownership guards: an unusable configured daemon record cannot fall through to foreground/standalone discovery, and a live daemon whose HTTP port is unavailable cannot trigger an SSH replacement. Upstream's update-marker waits, authoritative home locks and renamed-launcher ownership transfer remain. The conditional read of the service-specific runtime record keeps ordinary upstream runtime discovery intact.

Validation: all 85 focused daemon-discovery and tunnel tests passed, including Node/archive modes, stale/corrupt records, daemon restart and ordinary SSH/update flows. check:changed for this one-file repair passed formatting, lint, both knip passes, five affected package typechecks and its selected tests. Final staged hooks passed. Fresh exact-SHA Astra renewal is requested; CodeRabbit's documented large-diff coverage limit still applies.

The Cursor SDK musl metadata exception is still awaiting the maintainer's answer. Latest-head CI and every release artifact/npm/install/preflight/serve gate remain mandatory. No merge or publication yet.

[kalvenschraut]

Independent GPT-6 Astra source integration GO for exact candidate 97fc354f1a6e292aaeda921c6889f7ff04d1b2d9. No verified source blockers.

Fresh review task: node:delegated-task:command%3Amcp%3A955e0483-1e32-46c3-b361-c0551497ea39%3Adelegate-task%3Afe3b0356-72d1-4cb1-ab18-3b7c152732c4, executed model gpt-6-astra.

The reviewer inspected the actual nine-line SSH daemon-ownership repair against 0cda4fbb, confirmed merge parents, and spot-checked the earlier scheduled-task and Vim repairs. Healthy daemon adoption and foreground discovery without daemon ownership remain intact. This renews the bounded high-level integration review without restarting a whole-tree audit. No tests were run by the reviewer.

Together with the primary GO above, this supplies the source-review portion of the authorized large-diff fallback. CodeRabbit explicitly skipped review because 2,501 files exceeded its 100-file limit; its skipped status is not approval.

CI is still running on this SHA. The Cursor SDK 1.3.1 musl-metadata exception still awaits the maintainer's explicit decision and is not waived by either source GO. Artifact validation, npm publication/integrity, clean Alpine plain-npm installation, service preflight, actual serve HTTP probe, and GitHub draft publication remain separate gates.

[kalvenschraut]

Pre-merge gate update for exact candidate 97fc354f1a6e292aaeda921c6889f7ff04d1b2d9: all applicable CI checks passed in run 43703415712, including Test, all eight server shards, both web shards, lint, build/typecheck, mobile static analysis, Rust, release smoke, and aggregate Check. Optional preview jobs and CodeRabbit are skipped. The thread-transfer report is bound to this SHA and passes every enforced ceiling. GitHub reports CLEAN/MERGEABLE.

Primary and fresh independent GPT-6 Astra source integration GO are recorded for this same SHA. CodeRabbit's explicit 2,501-file/100-file coverage refusal is covered by the maintainer-authorized large-diff fallback, rather than being treated as bot approval.

Merge remains blocked solely on the maintainer's pending Cursor SDK 1.3.1 native-package metadata exception decision. Its generic linux-x64 package lacks a musl package and libc label, contrary to the requested npm-metadata gate. Local native loading succeeds, but does not waive that requirement. The reviewed candidate retains 1.3.1 for upstream native resume; downgrading to 1.2.0 would require a source adjustment and renewed review. No merge or release publication performed. Once the decision clears this gate, continue through merged-head release build, artifacts/checksums, exact npm tarball publication/integrity, clean Alpine npm install, preflight, actual serve probe, and final GitHub release publication.

[kalvenschraut]

The maintainer explicitly approved retaining upstream Cursor SDK 1.3.1 in the owning thread: "if it loads just fine just allow it we dont use cursor anyway, record this in your future prompt". The recurring sync prompt now records this Cursor-specific metadata exception, conditional on Alpine native loading/executable compatibility and the existing focused tests plus full release install/preflight/serve gates. Other native dependencies, including ffi-rs, retain the original metadata requirement.

On exact candidate 97fc354f1a6e292aaeda921c6889f7ff04d1b2d9, all 11 Cursor replay integration fixtures passed, including recorded resume/restart scenarios. Both platform package native modules loaded on this Alpine host; bundled rg runs and both executables are statically linked. npm confirms @yuuang/ffi-rs-linux-x64-musl@1.3.7 has libc: ["musl"].

No source changed after the primary and Astra GO. Applicable CI remains passing. Fork/base/head identities match the reviewed candidate and base; merging with upstream ancestry preserved, then continuing through the 0.0.111 release workflow and all artifact/npm/install/preflight/serve gates before publishing the GitHub draft.