chore: add implementation strategy guidance for compatibility decisions#2600
Merged
chore: add implementation strategy guidance for compatibility decisions#2600
Conversation
github-actions
bot
added
the
documentation
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
1 participant
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.
This pull request adds repo guidance for deciding when Python SDK changes need compatibility handling and when unreleased interfaces can be rewritten directly. It introduces a new
.agents/skills/implementation-strategy/SKILL.mdfile, updatesAGENTS.mdto require that skill for runtime and user-facing changes, and narrows ExecPlan compatibility callouts to behavior shipped in the latest release tag or durable external state.It also updates
.agents/skills/pr-draft-summary/SKILL.mdso PR summaries judge compatibility risk against the latest release tag instead of unreleased branch-only churn. The new guidance is Python-specific where needed, explicitly calling out durable surfaces such asRunState, session persistence, exported dataclass constructor order, and documented model/provider configuration.