fix: plan todos re-check after async backend write, release 0.11.2 - #68
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
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.
Companion fix that landed in the working tree alongside the review batch (#66): the backend writes the projection's todos asynchronously AFTER the tool-result event, so
dispatchPlanIfChanged's single read at result-time raced that write and intermittently kept the editor's todo panel stale until the next tool completed. Now one delayed (600 ms) re-check runs when the todos signature is unchanged — single-shot, unref'd, best-effort.Also includes
tests/audit-fixes.test.tscovering the whole audit-fix batch (settle-once, turn-idle grace, plan re-check — 5 tests) and the 0.11.2 release bump + changelog.Verification: typecheck / lint / 45 files, 670 tests pass.