Repository navigation
Conversation
Validate developer history as instruction content during snapshot and journal loading. Preserve its role through autosave, exports, and resumed Responses requests. Cover native SDK continuation, saved identity and usage, legacy formats, and malformed message rejection.
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.
A valid Responses session containing developer messages could complete a model turn but fail during autosave or restore because the session store rejected that role.
Include developer in the existing role allowlist and apply the same text-content validation used for system and user messages. Preserve its original role through snapshots, journals, checkpoints, legacy JSON and JSONL, exports and subsequent model requests.
The new regressions passed all 48 cases and related persistence tests passed all 204 cases. The native SDK before-and-after probe verifies autosave, restore, a second user turn, cumulative usage and session identity. Unknown roles and malformed message content remain rejected. Repository Ruff, import constraints and dependency checks passed.