Repository navigation
fix(lastcode): restore main test expectations - #62
Merged
Merged
Conversation
Loading
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.
Repaired
lastcode/maincombined newer test contracts with stale harness expectations, blocking every guarded push. The desktop update harness still used the removedstopBackendoption and read real settings for explicitly configured local-nightly scenarios; one web timeline assertion also omitted the currentshowThinkingfield.This updates the test harness to use the backend pool shape, selects in-memory settings only for explicit local-nightly fixtures, and aligns the working-row expectation. Product behavior is unchanged.
Validated with the complete Node 24
lastcode:ci:quickpre-push gate.Implemented by GPT-5.6 Sol in the T3 Code Codex harness.