[codex] Phase 3C: fork-compatible diagnostics#10
Merged
sukar0972 merged 23 commits intoJun 26, 2026
Merged
Conversation
Co-authored-by: codex <codex@users.noreply.github.com> (cherry picked from commit 57d25c9)
Co-authored-by: codex <codex@users.noreply.github.com> (cherry picked from commit 90dc76b)
Co-authored-by: codex <codex@users.noreply.github.com> (cherry picked from commit 5edf7c5)
Co-authored-by: codex <codex@users.noreply.github.com> (cherry picked from commit a9460bb)
Co-authored-by: codex <codex@users.noreply.github.com> (cherry picked from commit 1a59277)
Co-authored-by: codex <codex@users.noreply.github.com> (cherry picked from commit a3dadc0)
Co-authored-by: codex <codex@users.noreply.github.com> (cherry picked from commit d389cfd)
Co-authored-by: codex <codex@users.noreply.github.com> (cherry picked from commit 61e6d89)
Co-authored-by: codex <codex@users.noreply.github.com> (cherry picked from commit 3c246f5)
Co-authored-by: codex <codex@users.noreply.github.com> (cherry picked from commit 6155f5c)
Co-authored-by: codex <codex@users.noreply.github.com> (cherry picked from commit 8c1605b)
Co-authored-by: codex <codex@users.noreply.github.com> (cherry picked from commit 2a29de7)
(cherry picked from commit 0debeba)
Co-authored-by: codex <codex@users.noreply.github.com> (cherry picked from commit 1b2f39d)
github-actions
Bot
added
size:XXL
vouch:trusted
Restore friendly HTTP error messages on PrimaryEnvironmentRequestError while keeping structured diagnostics for logging. Harden OpenCode session payload validation, palette storage writes, schema issue summaries, and provider runtime list decoding concurrency.
Stop auto-opening the browser by default and emit localhost and LAN pairing URLs (plus token and QR code) when the web server starts.
sukar0972
marked this pull request as ready for review
June 26, 2026 05:59
sukar0972
merged commit Jun 26, 2026
ded385a
into
codex/upstream-phase3b-workspace-checkpoints
7 of 13 checks passed
sukar0972
added a commit
that referenced
this pull request
Jun 26, 2026
Brings PR #10 (codex/upstream-phase3c-vcs-provider-hardening) onto main after it was merged into the phase3b branch by mistake.
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
2 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.
Summary
Fork adaptation
The original Phase 3C candidate set included upstream source-control provider and VCS-process error commits. Those depend on a newer VCS error-contract/service refactor not present in this fork. They were intentionally deferred rather than pulling that dependency chain into this PR. The favicon/asset resolver sub-change was also deferred because it introduces a WorkspacePaths requirement throughout server bootstrap.
No apps/desktop, apps/mobile, browser-simulation, preview-automation, release-tooling, or .repos changes are included.
Validation
vp check(passes; 9 pre-existing lint warnings outside this diff)vp run typecheckDeferred upstream commits
These should be revisited alongside the required VCS contract/service refactor in a dedicated follow-up PR.