fix: recover stale thread state and transferred sessions - #52
Draft
jimprince wants to merge 120 commits into
Draft
fix: recover stale thread state and transferred sessions#52jimprince wants to merge 120 commits into
jimprince wants to merge 120 commits into
Conversation
…ecovery, archive cleanup
…e UI, disconnect messaging
…pstream base, regenerate lockfile
Upstream added a `relay_public_config` job + artifact-based relay client tracing to release.yml, with infra/relay/scripts/deploy.test.ts asserting it. The fork ships a minimal release.yml that intentionally omits relay observability (it does not deploy the managed T3 Connect relay), so the upstream assertion cannot hold. Narrow that test to the part that applies to the fork — guard against the insecure masked cross-job token output — and drop the requirement for upstream's artifact mechanism. Add the test to the fork-owned auto-resolve allowlist so future upstream syncs keep the fork's version instead of re-conflicting. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
`re-probes when settings change the codex binaryPath` polled the injected spawner while advancing TestClock, which can drive additional background provider-refresh probes under slower CI scheduling. The exact `spawnedCommands` deepStrictEqual was therefore non-deterministic (CI saw 3-4 spawns vs the expected 2), failing the CI Test job and the Release preflight. Assert the observable settings-change behavior — boot probes the original binary and the changed binaryPath is re-probed afterward — and rely on the dedicated boot-refresh tests for the no-extra-refresh guarantee. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The fork's signed macOS path requires an Associated Domains provisioning profile + Clerk passkey config that isn't set up (and isn't needed for personal-use builds). Require the profile/team id for the signed path and otherwise fall back to an unsigned macOS artifact instead of failing the release. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
github-actions
Bot
added
vouch:trusted
jimprince
force-pushed
the
main
branch
11 times, most recently
from
July 20, 2026 03:24
bb56335 to
b7e622c
Compare
jimprince
force-pushed
the
main
branch
17 times, most recently
from
July 28, 2026 00:54
9a392a2 to
49e8b59
Compare
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
1 participant
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.
What changed
runningWhy
A response could become stale while the client was disconnected. On refresh, the server recorded the failure activity but left the session running indefinitely. Separately, a moved Codex thread retained the source machine's rollout id, so the first target-side follow-up failed with
no rollout foundeven though the UI warned that native provider context would start fresh.Impact
Refreshed threads now recover to a usable ready state with an actionable error, and cross-machine moves can continue on the target with a fresh provider session when native context is not portable.
Validation
vp check(passes with 10 pre-existing warnings)vp run typecheckThe root
vp testrun was also exercised: 4,847 tests passed; 7 unrelated baseline/root-runner failures remained (isolated affected suites pass where applicable).