1 Commits

Author SHA1 Message Date
74e3b24f7a fix(classify): close lexicon gaps behind the lexical engine's shared-word mislabels
The classify CLI's lexical engine had zero lexicon coverage for "feature"
and "praise" (only "bug" was covered) and none at all for generic
sentiment (positive/negative/neutral), so bare-label runs of the CLI's
own README example either tied on everything or confidently mislabeled a
praise/feature row as a bug whenever a bug-shaped word like "crash"
appeared. Add two small, additive synonym groups to the existing lexicon.

Measured on a new 65-row synthetic gold set (examples/classify-eval.jsonl,
run via `npm run classify-eval`, scripts/classify-eval.mjs): 32.3% -> 49.2%
accuracy counting ties as wrong, 67.7% -> 71.1% on rows the engine
actually committed to; the sentiment set alone went 5.0% -> 35.0%. The
product-wide gold regression suite (`npm run gold`) still passes 61/61 —
every change is a new synonym entry, not an edit to an existing one.

README now documents the measured numbers, the --threshold tradeoff
(0.55 raises decided-row accuracy to 83.8% at the cost of more abstains),
and the real remaining limit: a bag-of-words engine can't fully resolve
a praise sentence that mentions "crash" from an actual bug report.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2026-11-11 14:26:12 +03:00