docs(release): prep stable 0.3.0 (changelog + counts)

[bntvllnt]

Closes #432

Makes main ready to cut stable 0.3.0 (per docs/RELEASING.md). Docs-only — this PR does not release. Merge → dispatch Publish is the separate next step.

Changes

• Changelogs (CHANGELOG.md + packages/ui/CHANGELOG.md): [Unreleased] → dated [0.3.0] - 2026-06-16 (the publish workflow's release gate greps ## [0.3.0]), dropped the now-satisfied pre-release notes, added a Fixed entry (theme-adaptive CandlestickChart/SparklineGrid colors — the two pre-existing components touched by the remediation), added the v0.3.0 link reference, opened a fresh empty [Unreleased].
• Stale counts 144 → 225: README.md headline (body already said 225 — was self-contradictory), packages/ui/README.md, docs/ARCHITECTURE.md.
• ROADMAP: status planning → release prep; milestone TBD → real 0.3.0 milestone.
• RELEASING.md: documents the apps/registry version bump, the doc-sync step, and the post-publish PUBLISHED_VERSION flip.

Deliberately NOT here

• No PUBLISHED_VERSION flip. It stays ^0.2.1 until 0.3.0 is live on npm latest; flipping before publish would make the deployed registry advertise an unpublished version and break npx shadcn add. It's a documented post-publish follow-up.
• No version bump — packages/ui and apps/registry are already 0.3.0.

Changelog content audit

The [0.3.0] section already covers everything: all component families (225, up from 140), OKLCH theming + runtime presets, and the site/agent surface (MCP, templates, playground, Pagefind search, en/fr routes, /vs, design endpoints). Verified the publish-workflow awk extracts the section cleanly.

Release sequence after this merges

1. Merge this PR (canary republishes 0.3.0-canary.<sha>).
2. Actions → Publish → Run workflow on main → tags v0.3.0, publishes --tag latest, GitHub Release.
3. Post-publish PR: flip PUBLISHED_VERSION → 0.3.0 + regenerate registry (drift/integrity guards verify it).

[vllnt-pilot]

ntk preview

App	Status	Preview
ui-registry	Ready	https://pr-433-ui-registry.preview.vllnt.ai
storybook	Ready	https://pr-433-storybook.preview.vllnt.ai

Built from 1d723ad0 · public + no-index (ADR-082) · torn down on close

[bntvllnt]

Updated this release-prep PR to cover the full 0.3.0 train that landed after it was opened (commit 1d723ad):

Changelog (root + packages/ui), under [0.3.0], re-dated 2026-06-17:

• BREAKING — React 19 required (drop React 18; forwardRef → ref-as-prop; useContext → use()) — from refactor(ui)!: migrate to React 19 ref-as-prop, drop forwardRef (#268) #441.
• +70 new components: forms 18 ([feat] Missing form primitive components (18) #409/feat(ui): add 18 form primitive components (#409) #437), motion 37 ([feat] Missing motion / effect components (37) #413/feat(ui): add 37 motion & effect components (#413) #439), core 7 ([feat] Missing core primitive components (7) #412/feat(ui): add core primitive components (#412) #436), charts 5 ([feat] Missing chart / dataviz components (8) #410/feat(charts): add pie, radar, gauge, sankey & contribution-graph (#410) #438), AI 3 ([feat] Missing AI components (3) #411/feat(components): AI components — reasoning, chain-of-thought, prompt-input (#411) #434).
• Docs-sidebar category fix (~32 components restored) + shared-internals extraction — refactor: architecture deepening sweep — extract shared deep modules #425/refactor(architecture): sidebar-category fix, Zod registry seam, shared UI hooks #440.
• react-doctor sweep (no-react19-deprecated-apis 456→0, state/effects, structural) — react-doctor: React 19 migration — no-react19-deprecated-apis (439 warnings) #268/refactor(ui)!: migrate to React 19 ref-as-prop, drop forwardRef (#268) #441, react-doctor: misc — render-in-render, polymorphic children, giant components (~40 warnings) #277/refactor(ui): clear react-doctor misc warnings (#277) #435, react-doctor: state & effects — derived state, cascading setState, effect-event handlers (41 warnings) #271/refactor(ui): clear react-doctor state & effects warnings (#271) #442.
• Component count 225 → 295 across README (root + package), ARCHITECTURE, and the ROADMAP metric. Verified: exactly 70 new component dirs across the family PRs.

Two notes for the merge/release step (you're driving merges):

1. These changelog entries describe the train PRs (feat(components): AI components — reasoning, chain-of-thought, prompt-input (#411) #434/refactor(ui): clear react-doctor misc warnings (#277) #435/feat(ui): add core primitive components (#412) #436/feat(ui): add 18 form primitive components (#409) #437/feat(charts): add pie, radar, gauge, sankey & contribution-graph (#410) #438/feat(ui): add 37 motion & effect components (#413) #439/refactor(architecture): sidebar-category fix, Zod registry seam, shared UI hooks #440/refactor(ui)!: migrate to React 19 ref-as-prop, drop forwardRef (#268) #441/refactor(ui): clear react-doctor state & effects warnings (#271) #442). If you drop any of them, prune its entry here.
2. After merging the train, run pnpm registry:build to regenerate registry.json and confirm the 295 count (each family PR computed its registry in isolation; the authoritative number comes from the merged build). Adjust if it differs.

Not merged — yours to review and cut.