consolidateExperiencesToPatterns() filtered out every row tagged
agent='cli-hook' because issue #348 had observed low-quality Bash
telemetry (quality ~0.40, success_rate ~0.24) flooding the pipeline.
But post-edit also uses agent='cli-hook', and those rows have
quality ~0.75 / success_rate ~1.0 — well above the HAVING thresholds.
The agent-name filter blanket-excluded the dominant share of high-quality
experiences (reporter saw 128 cli-hook rows ineligible, 0 patterns
created). The HAVING clause below the WHERE is the real quality gate
(avg_quality >= 0.5 AND success_rate >= 0.6 AND cnt >= 3) and already
filters out the #348 shape. Drop the agent-name filter; tighten HAVING
if the concern resurfaces.
4 regression tests verify: high-quality cli-hook rows now create a
pattern, low-quality cli-hook rows are still gated by HAVING, non-cli-hook
agents consolidate as before, and processed rows get
application_count bumped.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Dragan Spiridonov