Skip to content

merge: bring upstream T3 (ac8e9453c) into t3.14/main - #7

Merged
AmbitiousRealism2025 merged 124 commits into
t3.14/mainfrom
t3.14/merge-upstream-2026-10-06
Oct 6, 2026
Merged

AmbitiousRealism2025 merged 124 commits into
t3.14/mainfrom
t3.14/merge-upstream-2026-10-06

Conversation

@AmbitiousRealism2025

Copy link
Copy Markdown
Owner

Why

The fork was cut from upstream at 781223057 on 5 October. Upstream has merged 123 commits since then, including three refactors that rename or move code T3.14 calls. Merging now, before D03 and W03 add more T3.14 changes to orchestration, keeps the cost low. A trial merge this morning showed what it would take; this PR is that merge, done for real.

What changed

Verification

  • tsc --noEmit for apps/server: clean in all T3.14 files. The remaining errors are in src/process/externalLauncher.test.ts, which is identical to upstream's. It calls testLayer, which refactor: layer variables are named layer or layerXyz pingdotgg/t3code#16282 renamed; fix(shared): find versioned JetBrains macOS app bundles pingdotgg/t3code#16246 then added uses of the old name. That break is upstream's own and is left as is.
  • vp fmt and vp lint are clean on the touched files.
  • 334 tests pass (1 skipped) with T314_WORKER_CLI=… set: the durable fake, adapter and orchestrator suites, including the real-worker restart, steer and Pi model client cases, plus the drivers, recovery, effect worker, turn start, turn control, run execution and projection recovery suites.
  • Boot smoke test: the merged server on a temp home and port with a durable Pi instance logged "recovery completed", then the worker reconciled and became ready. It was stopped by its PID.
  • Dependencies were installed with pnpm install --frozen-lockfile from upstream's lockfile, using Node 24.21.0.

Notes for running it

  • Upstream now checks T3_SERVICE_LAUNCHER_CONTEXT at startup. A shell started by an installed T3 inherits that variable, and the server then refuses to start ("The service launcher started a different t3 version"). Run the fork with the variable unset (env -u T3_SERVICE_LAUNCHER_CONTEXT …). The check is local; it does not contact the installed launcher.
  • Upstream pins Node 24.15.0 in its toolchain config. Node 24.21.0 works.

Reviewing: the T3.14 changes are the 19 files listed above, plus the conflict resolutions in the merge commit a2fa360ef. The upstream commits need no review here.

Model and harness: Claude Opus 5.5 in Claude Code, inside T3 Code.

🤖 Generated with Claude Code

maria-rcks and others added 30 commits October 5, 2026 09:12
…of encoding a fallback (pingdotgg#16118)

Co-authored-by: Claude Opus 5.5 (1M context) <[email protected]>
Co-authored-by: Julius Marminge <[email protected]>
Co-authored-by: Claude Opus 5.5 (1M context) <[email protected]>
juliusmarminge and others added 25 commits October 5, 2026 21:41
…g#13217)

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Claude Opus 5.5 <[email protected]>
Merges upstream/main up to ac8e945 (123 commits since the fork base
7812230).

Two textual conflicts, both small:
- ProviderTurnStartService.ts imports ProviderAuthService from its new
  location, next to the T3.14 imports.
- server.ts takes upstream's `layerRuntimeCoreDependencies` naming and
  keeps `Layer.provideMerge(DurableReattach.layer)`.

Upstream refactors that git merged cleanly but that broke T3.14 code:
- pingdotgg#16295 (one module per service): `persistence/Layers/Sqlite.ts` ->
  `persistence/Sqlite.ts` (`layerFromPath`),
  `provider/Services/ProviderAuthService.ts` ->
  `provider/ProviderAuthService.ts`,
  `provider/Layers/piThinkingCapabilities.ts` ->
  `provider/piThinkingCapabilities.ts`.
- pingdotgg#16282 (layer naming): `makeSingleLayer` -> `layerSingle`,
  `makeOrchestratorV2ReplayLayerWithRegistry` -> `layerWithRegistry`.
- pingdotgg#16138 (Effect 4.0.1): `effect/unstable/process` -> `effect/process`.

No behavior change in T3.14 code.

Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
@AmbitiousRealism2025

Copy link
Copy Markdown
Owner Author

@codex review — please focus on the T3.14 files and the merge resolution in a2fa360; the upstream commits are unchanged from pingdotgg/t3code.

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 6, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-06T15:42:10.892971Z a2fa360 Manual request
ℹ️ About Codex in GitHub

Your team has set up Codex to 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. 👍

Reviewed commit: a2fa360ef6

ℹ️ About Codex in GitHub

Your team has set up Codex to 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 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@AmbitiousRealism2025
AmbitiousRealism2025 merged commit e9275de into t3.14/main Oct 6, 2026
@AmbitiousRealism2025
AmbitiousRealism2025 deleted the t3.14/merge-upstream-2026-10-06 branch October 6, 2026 16:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.