Repository navigation
fix: resolve worktree and Evaluation follow-ups - #480
Merged
Merged
Conversation
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.
Summary
Closes #474.
Checked every item against
0048b70a92(2.2.6-shuv.2, including #477/#479) before changing it. Full evidence and the focused security/access-flow assessment are indocs/issue-474-followups.md.run --worktreesetup hangsworktree.create. Stalled lookup and create now fail with clear phase-specific timeouts; prompt execution/event streaming stay unbounded.headersthrough schema construction and normalization. Merge configuration → per-call (case-insensitively) → authentication, matching existing transport behavior. Document that historicalhttp.headersis unsupported.f39aa60608(upstream anomalyco#62102), included in #477, adds retryable refresh failures/timeouts. Re-ran its production-build browser regressions from both dialog and popover; no duplicate fix.66071f9edd).permission.cancelledandsession.tool.subagent.preparedschemas/references. Client generation rerun; no client diff.Feature flag: none; regression fixes, tests, documentation, and generated-document reconciliation only.
Verification
bun run check: lint and 39/39 typecheck tasks passed.bun run typecheck:tsc: 32/32 tasks passed.git diff --checkpassed.Final execution checks use throwaway HOME/XDG/database state, loopback fixtures or in-page API mocks. No live Shuvcode service was targeted or stopped. The first broad run encountered an unrelated host listener on GitLab OAuth's fixed callback port 8080; it was left alone and Core passed in a disposable network namespace after dropping capabilities (otherwise root invalidates two filesystem-permission tests). The exact command is in the checked-in report.
The release smoke script initially inherited
OPENCODE_CONFIG_DIRdespite replacing HOME/XDG. Fixed that test-isolation gap with the existingcleanProcessEnv()helper and a disposable cwd. Deliberately invalid throwaway config plus disabled project-config discovery fails the old smoke script and passes the corrected script for both compiled runtimes.Deferred: macOS/Windows/ARM release-matrix execution to release CI; this Linux x64 host cannot execute those native artifacts. No merge or release performed.
Visual
Review fixes
jev.systemOne(feat(core): add experimental jev.systemOne session tool #397), following upstream removal in feat(ai): replace experimental evaluation with Decision anomalyco/opencode#58758 (097a93e511) in favour of Decision.bun run checkpassed (39/39 typecheck tasks; lint warnings, no errors), touched-file Prettier andgit diff --checkpassed.