merge(main): bring fork main up to upstream main e5c82d79a - #65
Merged
Conversation
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
Co-authored-by: t3-code[bot] <269035359+t3-code[bot]@users.noreply.github.com>
Co-authored-by: t3-code[bot] <269035359+t3-code[bot]@users.noreply.github.com>
…res (pingdotgg#5664) Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
…ngdotgg#5673) Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-authored-by: t3-code[bot] <269035359+t3-code[bot]@users.noreply.github.com>
…bagents (pingdotgg#5677) Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
…as focus (pingdotgg#5691) Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
…nts (pingdotgg#5684) Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
…nder (pingdotgg#5697) Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
…#5745) Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
… never ran (pingdotgg#5710) Co-authored-by: t3-turbo-simulation <simulation@t3turbo.local> Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
pingdotgg#5756) Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
…gdotgg#5757) Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
…dotgg#5767) Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
…otgg#5768) Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
…5928) Co-authored-by: Simone <185146821+Lucenx9@users.noreply.github.com>
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
…ing (pingdotgg#5659) Co-authored-by: Rodrigo Brechard <rodrigo@clubtidy.fr> Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-authored-by: codex <codex@users.noreply.github.com>
…g#4849) Co-authored-by: Julius Marminge <julius0216@outlook.com> Co-authored-by: Claude Fable 5 <noreply@anthropic.com> Co-authored-by: maria <maria@kuuro.net> Co-authored-by: maria-rcks <254055478+maria-rcks@users.noreply.github.com> Co-authored-by: codex <codex@users.noreply.github.com>
…dotgg#5878) Co-authored-by: tsouth89 <tsouth89@users.noreply.github.com>
…tgg#5988) Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
77 upstream commits including sidebar v2 as default (SidebarV2.tsx -> Sidebar.tsx, fork's PR-updatedAt threading ported), the multi-provider PR page, the mobile usage dashboard, and upstream's own background-liveness reaper skip (pingdotgg#5677). Conflict resolutions per SEAM.md: - ProviderSessionReaper: adopt upstream's thread-shell backgroundLiveness read; keep the fork's wedge cap (backgroundWorkMaxIdleMs). Tests converted to the shell style; the reaper no longer needs the liveness service directly. - release.yml: restore upstream's new publish_cli job (dropped by the auto-merge), gated behind connect_enabled like every Connect job; the release job tolerates it being skipped. Fork stays on public runners. - mobile-eas-production.yml: upstream's auto-mode name, fork's runner. - RightPanelTabs: fork branding + upstream's new terminal reason. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…skip inside the wedge cap Upstream pingdotgg#5757 made ProviderService require ServerConfig; the fork's stale-exit-guard and pump tests build their own layer stacks and needed the test config layer. Upstream's background-liveness reaper test now idles inside the fork's wedge cap (past it, reaping is the intended behavior), and the fork's duplicate skip test is dropped. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
Important Review skippedToo many files! This PR contains 406 files, which is 106 over the limit of 300. To get a review, reduce the PR to 300 files or fewer by splitting it into smaller PRs or changing its base branch. Usage-priced reviews support at most 300 files. ⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (406)
You can disable this status message by setting the Comment |
github-actions
Bot
added
vouch:trusted
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. |
mobile-fingerprint-check and web-preview arrived pinned to Blacksmith runners the fork does not have, so their jobs queue forever. Use the same repository-conditional runner pattern upstream already uses in ci.yml. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
github-actions
Bot
added
the
📱 Native Change
The fork never publishes the CLI package; the turbo seam test asserts the job's absence, and this fork's Cloudflare credentials would have let the Connect gate wave the publish through to a guaranteed failure. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
19 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Brings fork main up to upstream
pingdotgg/t3codemaine5c82d79a(77 commits, includes everything shipped through nightlyv0.0.34-nightly.20260811.1063).What came in
SidebarV2.tsx→Sidebar.tsx)Seam resolutions (per SEAM.md)
infra/relayordeploy-relay.yml.backgroundWorkMaxIdleMs). Reaper now reads liveness off the thread shell like upstream; tests converted; SEAM.md updated.updatedAtgate reapplied; the SidebarV2 threading was ported into the newSidebar.tsx.publish_clijob was silently dropped by the auto-merge; restored and gated behindconnect_enabled, withreleasetolerating the skip. Fork stays on public runners.Verification
🤖 Generated with Claude Code