Repository navigation
BUG: a checkpoint the Stop hook asks for is filed with its conversation - #122
Merged
Merged
Conversation
…on, and logos index rejoins ones that were not
Merged
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.
Fixes runningbugs #385. The Stop hook's checkpoint-asked marker carried only the 8-character cut of the conversation id, and it is the newest event when the agent answers, so those checkpoints landed in a second folder and one chat showed as two.
activity.FullSessionID).logos indexrejoins checkpoints already filed under a cut id: when exactly one UUID host_session in the project starts with it, the frontmatter is rewritten and the file moves; it prints how many. Ambiguous prefixes and non-UUID ids are left as written.Tests fail without the fix. On a copy of a real vault, index rejoined 2 and a second pass re-filed nothing.