feat: emit behavior.* change codes from probe failures (#61) - #125
Merged
Merged
Conversation
Map model-backed probe and stability outcomes to stable behavior.* Change codes with documented severities. Missing-data is info-only; unstable vs deterministic failures use distinct codes. Probe JSON reports include behavior_changes; merge_behavior_changes attaches them to CompatibilityReport. Co-authored-by: Abhinaysai Kamineni <askmy-stack@users.noreply.github.com>
askmy-stack
marked this pull request as ready for review
September 18, 2026 18:22
Co-authored-by: Abhinaysai Kamineni <askmy-stack@users.noreply.github.com>
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
2 participants
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.
Summary
Implements #61 — emit stable
behavior.*change codes from model-backed probe and stability outcomes so CI can treat selection/arg failures as first-class changes.Type of change
What changed
tool_semantics.behavior_codeshelpers:changes_from_model_probe_report/changes_from_stability_reportmerge_behavior_changesto attach onto aCompatibilityReportbehavior.tool_selection_failed,arguments_invalid,risk_expectation_failed,confirmation_expectation_failed,unstable_probe,deterministic_failure,missing_data(info),evaluation_failedprobeJSON (model + stability modes) includesbehavior_changesdocs/change-codes.mdSeverity impact for adopters
Merging behavior changes into a structural report can flip
is_compatible/ exit1under defaultbreakingpolicy when probes fail selection or args. Info-levelbehavior.missing_dataalone does not fail. Treat as a behavior-compatible adoption step when wiring into compare/eval gates.Test plan
ModelProbeResult/StabilityReporttestsruff/mypy/ fullpytestCloses #61