docs(readme): badges, accurate EmDash peer, registry next-bet

[cavewebs]

Summary

CEO daily (22 Sep): growth-facing README polish — no runtime/publish impact.

• Add npm version/downloads + GitHub stars + MIT shields for social proof
• Correct misleading EmDash 0.37+ copy: published peer is >=0.37.0 <0.38.0; point to ready PR #28 for 0.38 → 0.2.1
• Reaffirm 0.1.x stays unbricked for EmDash 0.28.x
• Call out EmDash experimental plugin registry as the next organic discovery bet (needs Atmosphere publisher credentials — not publishing in this PR)

Test plan

• Docs-only change
• Skim rendered README on GitHub after merge

Safe to merge anytime; does not require a release.

[cavewebs]

CEO daily note (23 Sep): EmDash 0.39.0 shipped today and makes the plugin registry the default discovery path (Marketplace browse/install deprecated). This README still calls the registry “experimental” — hold merge until we retarget that sentence, or I can push a tiny follow-up commit. Separately, EmDash 0.39 compat is being extended on PR #28 (its current peer upper bound <0.39.0 already excludes today’s release).

[cavewebs]

CEO daily 24 Sep: EmDash 0.39.0 made the registry default discovery (no longer experimental). Opened tracking issue for listing DashCommerce on plugins.emdashcms.com — will link once created. This PR’s “next-bet / experimental registry” wording should be refreshed after that issue number lands (or amend here before merge). Safe docs-only merge still OK anytime.

[cavewebs]

Tracking issue: #33

[cavewebs]

CEO daily 25 Sep

Still mergeable (mergeable_state: clean). Docs-only — badges + accurate peer wording + registry next-bet.

Holding the merge for Timchosen per pairing (Auto-review also requires confirmation on PR merges). Safe to merge anytime; no release required. Note: peer copy still points at #28 for 0.38 — once #28 covers 0.39 we should tweak that sentence in a tiny follow-up.