Repository navigation
Preserve negotiated chat roles through model execution - #75
Merged
Merged
Conversation
andersalm
marked this pull request as ready for review
September 29, 2026 12:32
This was referenced Sep 29, 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
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.
Assistant flattened each conversation into one prompt. It now sends ordered system, user, and assistant messages when the selected text offer advertises
elastos.model.input.text/v2. Runtime binds the complete message array, and the provider forwards it unchanged to the chat engine. Older offers and Responses offers retain their v1 prompt path.Schema capabilities pass through local and shared offers. They stay outside the execution revision so retained v1 terminal, active, and uncertain runs keep their recorded authority. Adapter, route, model, and policy changes still alter that revision. Readiness and retirement accept validated capability metadata while comparing execution identity and policy exactly. Marketplace receives the regenerated Assistant contract module.
Depends on #72 (
feat/0.7.1-models). Merge after or with that parent and reconcile if the parent moves.Validation:
Validation uses local fixtures. Installed-model comparison remains a later task.