chore: refresh registry metadata and docs

README.md

@@ -12,6 +12,13 @@ default styling with its own tokens, motion recipes, and component contract.
 - `registry`: generated registry metadata plus the source-copy install contract
 - `tests/e2e`: Playwright smoke coverage for high-value Storybook flows
 
+## Current status
+
+- The foundation, token layer, authoring contract, Storybook docs, and unit coverage are in place.
+- The public UI surface now includes the core form and overlay set plus advanced patterns such as `DataTable`, `Command`, `Combobox`, `Sheet`, and `EmptyState`.
+- The internal source-copy registry flow is live and validated with `pnpm registry:check` and `pnpm test:registry:consumer`.
+- The main remaining release work is publish policy and tagging automation, not initial component bootstrapping.
+
 ## System principles
 
 - Source owned: components live in this repo and are modified directly.
@@ -128,6 +135,7 @@ Consumers pin this repo to a reviewed commit or tag, then run the local installe
 copy selected items into their own codebase.
 
 - Registry metadata lives in `registry/index.json` and is generated by `pnpm registry:build`.
+- The generated index tracks transitive local helpers in addition to component entrypoints, so helper-import changes need a registry rebuild before merge.
 - The installer copies components into `src/cadence-ui`, adds missing package dependencies,
   and writes `src/cadence-ui/.install-manifest.json` so upgrades can reuse the same item set.
 - `pnpm test:registry:consumer` creates a temporary consumer app, runs the installer, and