Closed
Clarify intent-aware safe-output mutation contracts across optional and strict modes#46857
Conversation
Copilot
AI
changed the title
[WIP] Update intent-aware mutation descriptions to clarify metadata requirements
Clarify intent-aware safe-output mutation contracts across optional and strict modes
Jul 20, 2026
pelikhan
marked this pull request as ready for review
July 20, 2026 14:58
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.
Intent-aware issue mutation tools were generating ambiguous contracts: omitted
issue-intentexposed metadata but did not encourage it, while strict mode could require metadata in schema yet still describe it as optional.add_labelswas especially inconsistent by enforcing object-only labels in strict mode while still documenting plain string labels.Mode-specific intent guidance
issue-intentnow strongly encouragesrationaleandconfidencefor all intent-aware mutations while keeping both optional.issue_intent: truenow states clearly thatrationaleandconfidenceare required.issue_intent: falsecontinues to omit intent guidance and strip intent fields from generated schemas.Strict
add_labelscontract alignmentname,rationale, andconfidence.Field description cleanup
rationaleandconfidenceno longer call those fields optional.LOW,MEDIUM,HIGH.Regression coverage
issue-intentis omittedissue-intent: falseadd_labelsobject-only schema + matching descriptionExample strict
add_labelsoutput now matches both schema and description:{ "type": "add_labels", "item_number": 123, "labels": [ { "name": "bug", "rationale": "The report describes reproducible incorrect behavior.", "confidence": "HIGH" } ] }