chore: add implementation strategy guidance for compatibility decisions#1056
Merged
chore: add implementation strategy guidance for compatibility decisions#1056
Conversation
|
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 a repo-local
implementation-strategyskill so Codex chooses the correct compatibility boundary before changing runtime behavior, exported APIs, schemas, configuration, or wire protocols.It updates
AGENTS.mdto require that skill for compatibility-sensitive work and clarifies that ExecPlans should treat only behavior shipped in the latest release tag, or durable external state, as compatibility-sensitive by default. Branch-local interface churn and unreleased post-tag changes onmainare explicitly not treated as breaking changes unless they already define durable external state or a migration path is requested.This pull request also updates the local
pr-draft-summaryandchangeset-validationguidance so the same latest-release-tag rule is applied consistently when summarizing compatibility risk and deciding version bump expectations. The result is a simpler implementation default: rewrite unreleased interfaces directly, and reserve shims or migration layers for real released contracts.