Repository navigation
Conversation
Pi 1.x sessions store the harness preamble as a leading 'system' message
and record commands the user runs from the pi prompt (e.g. an editor
launch) as 'bashExecution' messages. The v3 validator only accepted
user/assistant/toolResult, so every newer Pi session failed migration
with 'Pi message entry has an unsupported role'.
- validate 'system' and 'bashExecution' message roles
- project 'system' as a privileged system event (dropped deliberately
by targets that refuse privileged roles)
- project 'bashExecution' as a user message ('[bash] <cmd> (exit N)')
so user-run command history survives migration
- allow these roles to omit the 'content' field, as Pi does
Verified end-to-end against real Pi 1.4.0 session files that
previously required manual sanitization.
Co-Authored-By: Claude Code <noreply@anthropic.com>
|
🟢 Contributor eligibility requirements met for @honlu.
|
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.
Pi 1.x sessions store the harness preamble as a leading 'system' message and record commands the user runs from the pi prompt (e.g. an editor launch) as 'bashExecution' messages. The v3 validator only accepted user/assistant/toolResult, so every newer Pi session failed migration with 'Pi message entry has an unsupported role'.
Verified end-to-end against real Pi 1.4.0 session files that previously required manual sanitization.