Commit Graph

3 Commits

Author SHA1 Message Date
Aaddrick
6fceb39d60 docs(triage): sync README with shipped pipeline; drop plan + research (#480)
The README was drafted as a design spec before implementation. Now
that the pipeline is live and the design has been validated end-to-
end, bring the doc into agreement with the code and retire the two
companion files.

README updates:
- Intro: state the production trigger (`issues: [opened]`) and the
  workflow_dispatch fallback; note v1 is manual-only
- Stage 7 table: reorder by actual priority (drift is no longer a
  top-of-gate veto); drift section rewritten to describe the banner-
  and-candidates-modifier behavior landed in PR #476
- Stage 8a rendered-output example: show the conditional drift
  banner + drift-bridge candidates block that actually render
- Stage 8b reason enum: add `reference-source unavailable` that was
  missing from the list
- Rollout posture: describe the cutover as completed, not deferred
- Implementation layout: drop "during rollout" qualifier; add
  helper-scripts row (validate.sh / drift-bridge.sh /
  suspicious-input-scan.sh / extract-json.py)
- Artifacts list: full set with 14-day retention, not just the
  original four
- Reasons.json SSOT pointer: actual path `.claude/scripts/reasons.json`
  instead of the aspirational `lib/templates/reasons.json`
- Potential future improvements: drop "Cutover to issues:[opened]"
  subsection (done)
- Clean up "v1" usage where it means "first version of the pipeline"
  (confusable with legacy v1 workflow)

Deleted:
- docs/issue-triage/implementation-plan.md — phased build sequence
  is complete; commit history preserves the record
- docs/issue-triage/research-trail.md — design-pass sources are cited
  inline in the README where needed

Workflow banner updated to drop the `implementation-plan.md` pointer.

Co-authored-by: Claude <claude@anthropic.com>
2026-04-21 15:46:13 -04:00
Aaddrick
7d083d9163 refactor(triage): rename feature classification to enhancement (#466)
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>
2026-04-20 22:58:33 -04:00
Aaddrick
b308c0ffd2 docs: add issue triage pipeline design (#455)
Adds the issue triage pipeline design under docs/issue-triage/:

- README.md — base pipeline spec
- implementation-plan.md — stage-by-stage plan
- research-trail.md — references that informed the design

Replaces the original single-file docs/issue-triage.md that was
reverted from main in f829d3b. Squash of 28 drafting commits from
the prior docs/triage-pipeline-design branch (backup at
backup/docs-triage-pipeline-design-pre-rebase).

Co-authored-by: Claude <claude@anthropic.com>
2026-04-20 17:13:39 -04:00