fix: consolidate open correctness fixes - #246
Merged
Merged
Conversation
This was referenced May 22, 2026
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
Consolidates the valid/current correctness fixes from the remaining stale open PRs onto current
mainafter the Agy/Antigravity removal. I reviewed the old PR intent and ported the pieces that still apply instead of taking the branches wholesale; stale backend-specific changes and broad logging/bootstrap churn were intentionally left out.Key areas covered:
chat_id=0routing.last_runduring running/failure states.Supersedes
Intended to supersede/replace #232, #220, #212, #205, #200, #168, #162, #152, and the still-relevant low-risk parts of #90.
Validation
npm run typechecknpm run lint(passes with existing warnings)npx vitest run --exclude src/__tests__/package.functional.test.ts --reporter=dotThe full package install smoke test was not rerun successfully on this Windows machine because local disk space hit
ENOSPC; the broad suite excluding that package smoke passed.