mirror of
https://github.com/aaddrick/claude-desktop-debian.git
synced 2026-05-17 08:36:35 +03:00
7d083d9163
Aligns the v2 classifier vocabulary with the repo's GitHub label vocabulary. Previously `classification=feature` was mapped to label `enhancement` at Stage 9 — a redundant indirection that also caused miscalibration on defects framed as enhancement-shaped asks (e.g. #448 "breaks in-app schedulers and 'minimize to tray' expectation" classified as feature + ambiguous when the maintainer read is bug). Changes: - classify.json enum: feature → enhancement - classify-doublecheck-bugfeature.{json,txt} → classify-doublecheck-bug-vs-enhancement.{json,txt} - Doublecheck rubric tightened: added "breaks X" / "stopped working" as explicit bug signals and a rule that a broken expectation wins over enhancement-shaped framing when both are present. Reduces the chance of #448-shaped defects routing to the ambiguous bucket. - investigate.txt absence-claim ban: "feature X is missing" → "capability X is missing" - reasons.json: "ambiguous bug/feature classification" → "ambiguous bug/enhancement classification" - Workflow: doublecheck step renamed, classification checks updated, class_label map collapsed to direct (no more feature→enhancement remap). - docs/issue-triage/{README.md,implementation-plan.md}: vocabulary updated throughout (~47 occurrences). 8c variant renamed Feature-design → Enhancement-design. Planned Phase 4 file names (comment-enhancement.json, enhancement-design-questions.json) follow suit. Kept as-is: - `.github/ISSUE_TEMPLATE/feature_request.yml` filename — preserves the GitHub convention reporters recognize on the issue-chooser page; classifier buckets issues filed through it as `enhancement`. - v1 `issue-triage.yml` + `triage-classify.json` — untouched; v1 is slated for replacement and doesn't gain from this rename. No behavioral change at runtime beyond the rubric tightening; the rename collapses an indirection rather than adding logic. Co-authored-by: Claude <claude@anthropic.com>