Repository navigation
chore(fork): merge upstream v0.1.7-nightly.20261103.4119 - #27
Merged
Merged
Conversation
…server (pingdotgg#29127) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Completion alerts waited two seconds after the client received a completed thread state. Audio was also fetched and decoded only when an alert needed to play, adding a first-play delay. Notify immediately when the thread shell reports completion, and preload both sounds when a user gesture unlocks audio. Keep completion deduplication and suppression for existing, archived, and stopped runs. This intentionally removes the continuation grace for completion alerts. A completed run can now notify before an automatic continuation starts. The sidebar's two-second placement grace and server settlement behavior remain in place. Validation: `vp run check:changed` passes after merging current main, including 40 affected tests, formatting, lint, unused-code checks, affected typechecks, and React compiler checks. Tests cover immediate completion, duplicate suppression across reconnects, preloaded audio reuse, and retrying failed loads on alerts without retrying on every gesture. Audible timing has not been verified in a live client. Model: GPT 6.1 Sol. Harness: Codex through T3 Code.
…unched T3 (pingdotgg#29169) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…dotgg#29348) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…29465) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…tates (pingdotgg#29486) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…ingdotgg#27138) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: maria-rcks <maria@kuuro.net>
…und Agent (pingdotgg#27139) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: maria-rcks <maria@kuuro.net>
…ingdotgg#27756) Signed-off-by: Yordis Prieto <yordis.prieto@gmail.com> Co-authored-by: maria-rcks <maria@kuuro.net>
pingdotgg#29480) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…PR update (pingdotgg#29369) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…hile this device's sign-in loads (pingdotgg#29352) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…time (pingdotgg#29301) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
) ## Problem PR watches stopped after eight failed host reads, so a prolonged network outage prevented later CI and review updates from reaching the thread. ## Change Keep watches active after provider failures reported as `failed`. Read detail and activity concurrently without allowing an activity failure to cancel or hide a permanent detail failure. Repeated known permanent failures still stop the watch and notify the agent; rate limits still pause reads. Non-rate-limited GitHub HTTP 403 responses and GraphQL `FORBIDDEN` responses now use a distinct `forbidden` reason so access refusals are counted instead of retried indefinitely. GraphQL error types survive the client mapping, after the existing requested-reviewer fallback. The provider's `failed` category also includes unclassified host and decode errors. Those continue retrying at the existing two-minute cadence until the watch ends or is stopped. A fixed outage deadline would recreate the recovery failure for longer outages. ## Scope and approval This is a focused fix for an obvious bug in existing PR watch recovery, covered by the small bug-fix exception in CONTRIBUTING.md. The changes cover watcher recovery, a GitHub failure classification needed to preserve permanent-error handling, and their regression tests. The new server-side `forbidden` reason does not change RPC contracts or add settings. ## Verification `vp run check:changed` passed, including 154 tests across five files. Regression coverage includes a 30-minute outage followed by one CI-success notification, mixed activity/detail failures, resetting a prior failure count, and repeated forbidden reads stopping the watch. Provider tests distinguish HTTP 403 and exclusively permanent GraphQL refusals from retryable HTTP 503 and mixed or untyped GraphQL errors. The mixed-failure and GraphQL classification cases failed before their fixes. Seven focused requested-reviewer fallback/refusal tests also pass. Model: GPT 6.1 Sol. Harness: Codex.
…g#29419) Co-authored-by: maria-rcks <maria@kuuro.net>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…ingdotgg#29623) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…diff load (pingdotgg#27833) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…es (pingdotgg#23456) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…#23373) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…gdotgg#23211) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…tance (pingdotgg#23198) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…turn absorbed its wake (pingdotgg#28010) Co-authored-by: maria-rcks <254055478+maria-rcks@users.noreply.github.com>
…ory scan ends (pingdotgg#29535) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…tch (pingdotgg#29476) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…n starts (pingdotgg#28431) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…ching origin (pingdotgg#27961) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…pingdotgg#27957) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…3804) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…g#23326) Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…ingdotgg#23561) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Exotic209093 <134711311+Exotic209093@users.noreply.github.com> Co-authored-by: Issue triage verification <triage@localhost> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…#22661) Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
… limit (pingdotgg#23192) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…gdotgg#23219) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…ngdotgg#29922) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…29909) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude <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
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.
Merge this with Create a merge commit, not squash, so upstream history stays intact.
Merges upstream
v0.1.7-nightly.20261103.4119into the fork'smain(previous:v0.1.7-nightly.20261102.4066).Conflicted files:
apps/server/src/orchestration-v2/Adapters/ClaudeAdapterV2.ts: both sides added declarations at the same spot. The fork'ssessionClosingflag (fix(server): background work an agent waits on survives settles, crashes and failed wakes #14, lost background work) and upstream'sendSubagentsOfClosedQuery/endSubagentsOfReplacedQueryhelpers (fix(server): Claude subagents left by a stopped process no longer stay Running pingdotgg/t3code#28356) are independent, so the resolution keeps both. The fork's lost-work report and upstream's subagent cleanup now run one after the other infinalizeActiveTurnAfterQueryExit, and the code otherwise merged cleanly.One fix outside the conflict: upstream's Effect 4.1.2 upgrade (pingdotgg#26833) moved
SecureRandomout ofNodeServices.layer. Two of the fork's #14 test blocks inClaudeAdapterV2.test.tsnow also provideNodeCrypto.layer, as upstream's own tests do.Server, shared, web and mobile typecheck pass on this commit, as do
ClaudeAdapterV2.test.ts,ProviderSessionManager.test.ts,ThreadSettlementService.test.ts,runtimeLayer.test.tsand the Claude replay and background-note integration tests.🤖 Generated with Claude Code