T3 Code 0.1.9-netpro2k.1

T3 Code 0.1.9-netpro2k.1 rebuilds the revised seven-patch fork stack on exact upstream v0.1.9 (24e77473ecf41bc1f7142529c7911c1c1aae1d76). This revision supersedes the original 0.1.9-netpro2k draft; that draft and its artifacts remain preserved as backup. Later upstream/main commits are excluded apart from the explicit unchanged pingdotgg#21661 backport described below.

Release remains on hold. This draft requires a new explicit approval of this exact rebuilt candidate before publication.

Upstream highlights

• New T3 Connect sign-in approval for external agents, including approval on app.t3.codes without copying a pairing code.
• New native OpenCode goals, synchronized across clients on OpenCode 2.2.5 and later. Use /goal in the composer; pause and resume are supported.
• New screen-reader announcement settings in Settings → Chat for turn status, completed messages, and agent steps.
• Expanded Usage → Limits support: Muse session/weekly limits after its first thread, plus xAI and Antigravity accounts from configured CLIProxyAPI hubs.
• Improvements to attachment uploads, pull-request deep links, GitLab reviews/reverts, image visibility, and preview layout.
• Fixes for long-thread memory and database reads, provider switching, queued turns, Desktop shutdown, and stable-release notes.

Upstream release and full changelog

Revised fork stack

Source: 3586b387d967bccdf2f8605bf3cba99d7c9df962.

The mandatory packaged-Desktop attachment patch has been removed, including private Desktop authentication provisioning/renewal, attachment IPC/contracts, and obsolete monitoring/update assumptions. Upstream's Local environment default is unchanged. Before eventual migration or installation, manually turn Local environment OFF and pair the same-home background service as a normal saved environment. Standard paired-credential expiry applies; renewal is outside this revision. No live settings have been changed.

Saved-host file/editor/Finder actions and pickers come from an unchanged backport of upstream pingdotgg#21661, commit 52d621a6f10f5a80ec433e3f3515eafbeabac74b. Its stable patch ID is cc88916f64a43b4ee7edfec00fa84c08fd62d4ee, identical to upstream. It reuses the existing host environment identity and destination-specific editor configuration, and should be dropped once the selected upstream base includes it. File intake, folder references, and uploads are unchanged.

Agent browser uses upstream streamed server Chromium. No unpublished native-browser repair from Studio's old 0.1.8 branch is included. Independent background-service installation/update/readiness/cutover, fork update feeds, signing, and release automation remain. Grok skill/session behavior, package-manager recency, and per-instance native Claude policy remain reachable and unchanged.

The audit compared the original 4f1d222148 stack with this rewritten source and traced production consumers for all seven patches. No old attachment commits were merged back. The original ready claim, source ref, receipts, and draft remain preserved separately.

Verification

• Required vp run check:changed ba787dfe598da457c29586d6c5110d3b4354e21d passed on Oma: 7,799 tests across 368 files, three existing skips, five Node tests, all 41 affected package typechecks, and React compiler checks for 255 files (260 compiler tests).
• Focused Oma checks passed: 62 saved-host file-action tests in three files and 55 OpenCode/maintenance tests in two files. All five release-state Python tests passed.
• Studio's earlier wider run remains recorded as non-green: four unchanged OpenCode maintenance tests failed (unknown versus current), with 675 tests passing and nine skipped as reported by the source author. Oma reproduced exactly those four failures using a process-local seven-day npm release-age cutoff; the no-cutoff control passed all five selected cases. Studio sets npm min-release-age=7, while Oma has no cutoff. The test refresh callback uses the default age service, and its fake registry response lacks publication timestamps required by the cutoff path. This is a configuration-sensitive fixture issue; no source, host npm settings, or tests were changed or silently skipped to obtain the required normal-configuration Oma gate.
• Linux x64 AppImage/DEB and signed Mac ARM64 DMG/updater ZIP were built from this exact commit. The Mac app passed strict signature and configured leaf-certificate checks using the existing dedicated identity. These personal builds are not notarized.
• Both standalone server archives passed version, service-launcher, and isolated HTTP-server smoke checks.
• Combined validation passed: both receipts bind to the exact candidate and matching public configuration; asset SHA-256, updater-manifest SHA-512, versions, and sizes match.
• No runtime Electron/client pass was performed, as requested. No Electron client was launched and no login/system Keychain settings were changed.

Publication remains on hold. Only the candidate branch was pushed. Preparation did not move main, publish a release, install into live applications, change live settings, or restart production services. A new explicit approval of this exact rebuilt candidate in its owning thread is required before publication; the original draft's approval context does not apply.