Per issue #61 and spec-quality-gaps.md (published as the issue's spec
comment):

- Per-component install and dependencies: registry-style libraries carry
  their documented component template; get_component answers with the exact
  command and the npm/registry dependencies.
- Compatibility truth: tracked subjects derive per library instead of the
  global union (no more Emotion on Tailwind libraries), real ranges recorded
  from registry peer metadata and official docs, and the build fails when
  recorded facts contradict a library's own getting-started text.
- Component records: kind, summary, builtOn, shared concept aliases, and a
  stacks filter on search_components.
- Search precision: word/prefix matching, separator folding, de-spaced index
  variants, and noise tokens dropped; glued and symbol spellings resolve.
- Ranking and matchedOn: spec-order key with visual effects demoted, and
  every hit states what matched.
- Self-explaining results: indexStatus and suggestions on empty results,
  component list on get_library, shared caveats once per response.
- Freshness: per-field verification identical across tools, verifiedAt and
  URL variants on records, and a maintainer-run source drift checker.

Data sweeps for kind/summary/verifiedAt coverage and the empty-shell library
fill remain open on the issue; documentation snapshots stay permission-gated.