Tooling adoption bars #13

Why

"What does the winning stack look like" is a question every team asks. Adoption counts answer it.

In this repo today

repos.dependencies already holds the Stellar packages found in manifests with their versions (config/hackmeridian-2026.yaml lists the fingerprints), and repo_integrations records partner packages and APIs (config/integrations.yaml). Reuse both.

What to build

• Adoption counts for: OpenZeppelin Stellar contracts, Stellar Wallets Kit, Freighter API, Passkey Kit, soroban-sdk major versions, stellar-sdk JS versions, Next vs Vite vs other, and the presence of CLAUDE.md, AGENTS.md, Cursor rules and Copilot instructions (detected from the file tree in github/scan.py).
• A new column or table for what is not already stored, an API route, and a /tooling page that renders grouped bars with a reusable DistributionBar component in components/charts/.

Acceptance criteria

• Every detector has a fixture package.json or Cargo.toml and a test, following tests/test_dependencies.py.

See CONTRIBUTING.md for conventions.