design-driftlisted

# design-drift > A read-only nightly review. Scans PRs merged since the last run for **design > drift** — the AI-era smell where an agent adds a NEW primitive instead of > reusing/extending an existing one, leaving N overlapping surfaces that work but > are messy and hard to improve. Ranks the findings, names the primitive that > should have absorbed the new code, files/drafts Linear tickets, and messages the > owner. **It never edits code** — it exists to flag messy code, so it must not add > any. Fixes are the owner's call, per-issue. The canonical smell to catch (the operator's own example): `agents feed`, `agents activity`, `agents notify`, `agents message`, `agents send` all exist to get a message to a human — overlapping surfaces one well-extended primitive could have covered. ## Why this reuses `quality` (do not write a parallel analyzer) The repo already has a read-only code-health engine — the **`quality`** skill — whose `signatures.ts` clusters parallel implementations by behavioral signature and whose architecture pass flags "new abstraction that duplicates an existing canonical one." Those are exactly the drift detectors. This skill is an **orchestrator + a consolidation lens on top of that engine**, not a second analyzer. Writing a parallel analyzer here would itself be the drift this routine exists to catch. Resolve the engine dir once (installed plugin, or vendored in-repo): ```bash QDIR="$HOME/.agents/plugins/code/skills/quality" [ -d "$QDIR" ] || QDIR="