test: support Muse 1.0 session frames - #2
Draft
obviyus wants to merge 1 commit into
Draft
Conversation
obviyus
marked this pull request as draft
September 1, 2026 07:10
This was referenced Sep 1, 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
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.
Problem
Muse Code 1.0 adds retained-frame records to
session.jsonl. These records do not have an eventsequence, so the live continuity test comparesundefinedas a number and fails even though both turns complete in one session.Fix
Check ordering only for records that carry a numeric event sequence. Keep the existing streamed-output assertions as the user-visible proof that both prompts use the retained session.
Verification
npm exec -- vitest run src/tests/continuity.test.tsnpm run test:run— 97 passed, 1 intentionally skippednpm run check