docs: clarify technical issue requirements - #2226
Merged
Merged
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.
Summary
Clarify repository guidance so technical issues are concise implementation contracts with a purpose, concrete API or data examples when a boundary changes, required behavior, observable completion conditions, and dependencies.
Route issue-writing tasks through the existing focused guidance without adding another template, checker, or workflow. Two documentation files changed; scope did not grow beyond issue-authoring guidance.
Validation
The affected selector ran only the agent-guidance gate, and all four ownership and context-budget tests passed. Runtime validation does not apply to this documentation-only change.