Skip to content

chore: merge upstream T3 Code through 024dba27 - #179

Merged
ScriptedAlchemy merged 97 commits into
mainfrom
codex/sync-upstream-024dba27
Nov 22, 2026
Merged

ScriptedAlchemy merged 97 commits into
mainfrom
codex/sync-upstream-024dba27

Conversation

@ScriptedAlchemy

@ScriptedAlchemy ScriptedAlchemy commented Nov 22, 2026 •

Copy link
Copy Markdown
Owner

Why

PR #177 completed the saved sync through upstream 122d3bf853da716652d5066b54d05d7654c46e36. This continuation brings in the next 95 upstream commits through the frozen snapshot 024dba275d9e5ade1b29a0a240c5f8661cdbdb51, starting from fork main b7fd440bdf4487ea572384fc49b9db321aeddf9a.

The integration retains both parents so future upstream merges keep their ancestry. It includes upstream fixes for queued attachments, linked-thread navigation, native slash-command context deferral, stalled provider requests, source-control checks/private PRs, and peer-session revocation.

Fork integration

  • Preserve migration IDs and names 1–128. Append upstream 106/107 as fork 129/130, update upstream receipt reconciliation, and rebuild the deferred-command index without changing existing receipts. Port the malformed-JSON guard from upstream 75 to fork 84 so older databases can reach the new migrations.
  • Revoke a linked SSH peer's session through the HTTP endpoint that answered the identity probe, then disconnect the tunnel. A changed identity receives no bearer token. The old combined path incorrectly passed the raw SSH URL to the HTTP client.
  • Attach Codex's config/read deadline to the actual request, including the pre-resume read, and retain the fork's process-exit distinction. Preserve per-attempt pending-context delivery when upstream adds prompted resume support.
  • Keep project-bound memory, automatic curation, sender/provenance protections, group conversations, and existing provider fallbacks. Keep the legacy export catalog removed. Combine upstream workflow-run identity with the fork's check-attempt handles, and regenerate the GitHub GraphQL bindings.
  • Keep the existing CI runner policy and agent-context gate. Equivalent wording in four PR-tool descriptions offsets the new private-PR input schema: MCP context is 76,425 bytes versus main's 76,429; Claude and Codex instruction sizes remain 9,557 and 10,947 bytes.

Validation

  • Hosted CI passed on final head 79716fcbfdaefbd906c4e34e12a1d519b206394d, tree 834959676d3dfc9ef0ec723e5986cb5de5e1559c. Fork CI completed successfully with 17 passing jobs and one unaffected native-mobile skip. All eight server shards, all four web shards, package/mobile tests, checks/build, Rust, and the final aggregate passed. Agent Context Budget also passed on the same head.
  • Meaningful fail-before/pass-after regressions cover malformed JSON during the 83→84 upgrade, SSH peer revocation, and an unanswered Codex configuration read before resume. Migration tests also exercise existing fork databases. A separate scratch SQLite database was built from all 107 pinned-upstream migrations, seeded with synthetic test data, and upgraded to fork 130: all 104 mapped receipt timestamps, seed data, and both indexes survived; fork knowledge tables were created; and a rerun applied no migrations. No user database was used.
  • Local targeted checks passed: 641 server/migration/adapter tests; 129 client tests; 207 GitHub parser/API tests; 28 peer-link tests; 19 CLI tests; 36 PR-handler tests; 534 deterministic MCP eval tests; 2 context-budget tests. Direct typechecks passed for the server, contracts, client-runtime, web, mobile, source-control-github, and evals. Native project-memory release build, locale parity, scoped formatting/lint, and GraphQL regeneration passed.
  • PR request-construction dry runs passed for 72 Codex and 75 Claude cases. Before/after comparisons preserve the request structures and differ only in the reviewed descriptions. No live-model eval API key or proxy is configured here, so these are deterministic/request checks, not paid model-behavior results.
  • Local environment limits: six DirectEndpoints integration cases cannot enumerate network interfaces (uv_interface_addresses permission error); its 12 pure endpoint cases pass. Browser bootstrap cannot download Chromium from the configured CDN (HTTP 403), and system dependency installation cannot elevate. Hosted CI covers those suites.
  • Required changed-file gate ran. Format, lint, knip, GraphQL, unused-patch, native-build, and React Compiler checks passed. The compiler gate covered all 83 changed source files with 88 targeted test cases across two suites. The aggregate exited 1 for exactly two remaining stages: its cached typecheck wrapper failed before compilation because this environment cannot initialize the seccomp supervisor, and the 177-file adjacent-test stage reached its configured 900-second timeout. Direct typechecks above passed. The timeout wrapper discarded partial output, so its cause is unknown; that stage is incomplete and is not counted as passed. The two final description clarifications have separate passing format/lint, budget, and request-construction checks. The final hosted matrix passed as recorded above.
  • The initial hosted run exposed exactly three stale expected prefixes across the restart and provider-switch replay fixtures: upstream expected User message:, while the fork emits Current message:. Server 1 failed the restart case and Server 2 failed the two provider-switch cases. All other test/build jobs and the changed-file/context-budget gates passed; Fork Check reflected those two shard failures. The follow-up changes only those three expected literals across two test files, retaining all surrounding assertions, UUID normalization, and production behavior. Both complete affected suites passed locally (118 test cases).
  • The scoped follow-up gate passed format, lint, both knip checks, GraphQL, and native build; its cached typecheck hit the same pre-compilation restriction. Its adjacent step finished with 119 passing cases and one timeout across three files. The unchanged provider-switch restart/recovery scenario hit its existing 120-second test limit; it is separate from the three corrected labels, and its cause is not established. That scenario passed in the independent 118-case run and in the initial hosted ProviderSwitch results. No timeout, matcher, or production behavior was changed.
  • On corrected head 79716fcbfdaefbd906c4e34e12a1d519b206394d (tree 834959676d3dfc9ef0ec723e5986cb5de5e1559c), hosted Server 2 passed all 1,051 test cases across 75 files. All 115 ProviderSwitch cases passed, including the locally timed-out restart/recovery case in 1.688 seconds. The local timeout's cause remains unestablished.

Implemented with GPT-6 Astra Pro in ChatGPT/Codex, with three parallel workers.

MIT-Consulting and others added 30 commits November 21, 2026 22:27
…-foreground-muted (pingdotgg#40676)

Co-authored-by: Julius Marminge <julius0216@outlook.com>
…gdotgg#40701)

Co-authored-by: MarcoDotIO <20867620+MarcoDotIO@users.noreply.github.com>
Co-authored-by: Julius Marminge <julius0216@outlook.com>
…not generate text (pingdotgg#40699)

Co-authored-by: Julius Marminge <julius0216@outlook.com>
…s the draft (pingdotgg#40708)

Co-authored-by: Julius Marminge <julius0216@outlook.com>
…its (pingdotgg#39822)

Co-authored-by: Julius Marminge <julius0216@outlook.com>
Co-authored-by: charlesbine <charlesbine@users.noreply.github.com>
…ow or steer survive a dropped socket (pingdotgg#40703)

Co-authored-by: Julius Marminge <julius0216@outlook.com>
…n a broken character (pingdotgg#40726)

Co-authored-by: MarcoDotIO <20867620+MarcoDotIO@users.noreply.github.com>
Co-authored-by: Julius Marminge <julius0216@outlook.com>
…anch (pingdotgg#40736)

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Julius Marminge <julius0216@outlook.com>
…its destination (pingdotgg#40739)

Co-authored-by: Julius Marminge <julius0216@outlook.com>
Co-authored-by: Julius Marminge <julius0216@outlook.com>
…g#40767)

Co-authored-by: Julius Marminge <julius0216@outlook.com>
…#40783)

Co-authored-by: geezoria <25051260+geezoria@users.noreply.github.com>
Co-authored-by: Julius Marminge <julius0216@outlook.com>
…ation (pingdotgg#33916)

Co-authored-by: Julius Marminge <julius0216@outlook.com>
…#40781)

Co-authored-by: Abhiram-745 <237478249+Abhiram-745@users.noreply.github.com>
Co-authored-by: Julius Marminge <julius0216@outlook.com>
Co-authored-by: shadowfeind <travestroy007@gmail.com>
Abhiram-745 and others added 27 commits November 22, 2026 06:43
…nder its full name (pingdotgg#40877)

Co-authored-by: Abhiram-745 <237478249+Abhiram-745@users.noreply.github.com>
Co-authored-by: Julius Marminge <julius0216@outlook.com>
…l finds no match (pingdotgg#40886)

Co-authored-by: Julius Marminge <julius0216@outlook.com>
Co-authored-by: Abhiram-745 <237478249+Abhiram-745@users.noreply.github.com>
Co-authored-by: Julius Marminge <julius0216@outlook.com>
…ingdotgg#40858)

Co-authored-by: LVC-Chakresh <chakresh@example.com>
Co-authored-by: Julius Marminge <julius0216@outlook.com>
…as "1024.0 MiB" (pingdotgg#40952)

Co-authored-by: MarcoDotIO <20867620+MarcoDotIO@users.noreply.github.com>
…0951)

Co-authored-by: Julius Marminge <julius0216@outlook.com>
…gdotgg#40965)

Co-authored-by: Julius Marminge <julius0216@outlook.com>
Co-authored-by: Julius Marminge <julius0216@outlook.com>
…#40991)

Co-authored-by: Grok 4.7 <noreply@x.ai>
Co-authored-by: Julius Marminge <julius0216@outlook.com>
pingdotgg#40945)

Co-authored-by: gemini-4-neon <me+ai@stefanmirea.com>
Co-authored-by: Julius Marminge <julius0216@outlook.com>
…41025)

Co-authored-by: Julius Marminge <julius0216@outlook.com>
Co-authored-by: Julius Marminge <julius0216@outlook.com>
…gdotgg#40986)

Co-authored-by: Julius Marminge <julius0216@outlook.com>
)

Co-authored-by: Julius Marminge <julius0216@outlook.com>
…ingdotgg#38791)

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: shivam <91240327+shivamhwp@users.noreply.github.com>
The fork's last completed sync ended at 122d3bf; upstream has advanced by 95 commits.
Merge the frozen upstream snapshot while preserving the fork's migration receipts,
memory and provenance behavior, SSH links, and source-control check identities.

Append upstream migrations as fork 129/130, port the old-upgrade JSON guard to 084,
and correct the combined SSH revocation, Codex deadline, and pending-context paths.
Keep the existing agent-context cap with equivalent PR-tool wording.

Implemented with GPT-6 Astra Pro in ChatGPT/Codex, with three parallel workers.
@changeset-bot

changeset-bot Bot commented Nov 22, 2026 •

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 79716fc

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

New upstream restart and provider-switch fixtures expected User message while the
fork's context wrapper emits Current message to preserve sender attribution.

Correct the three expected prefixes in two integration tests. Keep all command,
history, provider, and completion assertions, UUID normalization, and production
behavior unchanged. Both complete affected suites pass (118 tests).

Implemented with GPT-6 Astra Pro in ChatGPT/Codex, with three parallel workers.
@ScriptedAlchemy
ScriptedAlchemy merged commit f4ddc56 into main Nov 22, 2026
20 checks passed
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.