chore(sve-ui): changeset for the README component listing

[rodriabregu]

What & why

A changeset so the README fix from #78 actually reaches npm.

No code changes. The README is the npm page, and npm only re-renders it when a version is published — so until something ships, npmjs.com/package/sve-ui keeps showing a catalog that lists 18 of 61 exports and calls a sixty-component library sixteen.

patch is the right size: documentation and a build-time guard, no behaviour change.

Review path

One file: .changeset/plenty-readers-count.md. Read the changeset body — it becomes the changelog entry verbatim.

What happens after merge

1. The release workflow opens a "Version Packages" PR bumping 0.13.1 → 0.13.2.
2. Merging that PR builds, validates and publishes to npm via Trusted Publishing (OIDC).
3. npmjs.com/package/sve-ui re-renders with the complete component table.

Test plan

• Confirmed the README genuinely ships in the tarball before proposing a release — npm pack --dry-run lists README.md at root, included by npm regardless of files: ["dist","skills"]. Without that, publishing would fix nothing.
• check-readme-coverage green on main at 6e0de5d: 60 components, all listed, count matches

Checklist

• Tests added/updated and passing (pnpm test) — unchanged from docs: list every component in the README, and guard that it stays that way #78
• pnpm lint && pnpm check && pnpm build all green
• Changeset included — this PR is the changeset
• Docs updated if the public API changed — no API change
• No Tailwind / config required in consumer projects

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
sve-ui	Ready	Preview	Aug 29, 2026 10:52pm