Repository navigation
docs(contributing): add issue templates and evaluation tasks - #272
Open
lanyue-llk wants to merge 4 commits into
Open
lanyue-llk wants to merge 4 commits into
lanyue-llk wants to merge 4 commits into
Conversation
lanyue-llk
changed the title
![lexmount-ocr[bot]](https://avatars.githubusercontent.com/u/277637559?s=60&v=4){kind=small}
There was a problem hiding this comment.
✅ Re-review complete · 6e94493
No findings in this incremental review.
There was a problem hiding this comment.
✅ Re-review complete · d5e65ab
No findings in this incremental review.
There was a problem hiding this comment.
✅ Re-review complete · 83586ff
No findings in this incremental review.
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.
The repository has no reusable issue templates and only a one-line bug-report instruction. Add templates for bugs, feature requests and evaluation tasks, expand the contribution guide, and link it from AGENTS.md for repository and upstream reports.
Bug reports lead with reproducible behavior, expected/actual results and environment details. Evaluation findings belong to one report-linked Task with native sub-issues; different report batches stay separate. The guidance requires verification of the original failure before closing or checking an item, keeps primary explanatory diagrams visible near the opening, and reserves links or collapsed sections for long supporting evidence. Evaluation task summaries include failure-type counts, denominators and repair links alongside the detailed cases.
Validation: 23 documentation tests passed; track naming/reference-boundary check passed; all three template metadata blocks parsed successfully;
git diff --checkpassed. No runtime or scoring changes.Evaluation findings bind to the task’s required output scope. A richer baseline does not make navigation, media or file delivery mandatory for body extraction. Tracking tasks separate deferred capabilities and label task-family subsets while retaining full-report counts.
Latest validation: documented-path and README-navigation checks — 33 passed.