scrub: use react components consistently in public docs and tarball each npm package as a github release asset

Author: ph33nx

.github/workflows/release.yml

@@ -144,10 +144,20 @@ jobs:
           git tag "v$VERSION"
           git push --follow-tags
 
+      - name: Pack npm tarballs for release assets
+        if: steps.diff.outputs.changed == 'true' || github.event_name == 'workflow_dispatch'
+        run: |
+          mkdir -p .release-assets
+          (cd packages/ui && npm pack --pack-destination ../../.release-assets)
+          (cd packages/ui-react && npm pack --pack-destination ../../.release-assets)
+          ls -la .release-assets/
+
       - name: Create GitHub release
         if: steps.diff.outputs.changed == 'true' || github.event_name == 'workflow_dispatch'
         uses: softprops/action-gh-release@v3
         with:
           tag_name: v${{ steps.bump.outputs.version }}
           generate_release_notes: true
           make_latest: 'true'
+          files: |
+            .release-assets/*.tgz

AGENTS.md

@@ -213,7 +213,7 @@ No field renames. No glue code. Use the decision tree above to pick the componen
 
 ### Pattern 6: Next.js RSC streaming
 
-Server fetches with the secret key, client renders with the wrapper. The API key never crosses the network.
+Server fetches with the secret key, client renders with the React component. The API key never crosses the network.
 
 ```tsx
 // app/page.tsx (Server Component)

README.md

@@ -366,7 +366,7 @@ The server component fetches, the client component renders. The API key never cr
 <details>
 <summary><strong>Tailwind v3 vs v4 compatibility?</strong></summary>
 
-Both work. Components do not consume Tailwind utilities. Tailwind utilities apply outside the components on wrappers and containers; inside the Shadow DOM, components read `--roxy-*` CSS custom properties only.
+Both work. Components do not consume Tailwind utilities. Tailwind utilities apply outside the components on parent layout elements and containers; inside the Shadow DOM, components read `--roxy-*` CSS custom properties only.
 
 For Tailwind v4 users, the shadcn registry installs a CSS bridge that maps your existing v4 design tokens onto `--roxy-*`. For Tailwind v3 users, set `--roxy-*` directly on `:root`, or write a tiny bridge:
 
@@ -400,7 +400,7 @@ useEffect(() => {
 return <roxy-location-search ref={ref} />;
 ```
 
-Upgrade to React 19 when you can; the wrappers route everything cleanly.
+Upgrade to React 19 when you can; the React components route everything cleanly.
 </details>
 
 <details>
@@ -460,7 +460,7 @@ Mock `@roxyapi/sdk` at the network boundary so unit tests do not hit the live AP
 <details>
 <summary><strong>What if I want to fork or own a component?</strong></summary>
 
-Use the shadcn registry. The registry drops the component source, a wrapper file, and a CSS theme bridge into your repo. Edit anything; the source is yours from that point.
+Use the shadcn registry. The registry drops the React component source and a CSS theme bridge into your repo. Edit anything; the source is yours from that point.
 
 ```bash
 npx shadcn@latest add https://cdn.jsdelivr.net/gh/RoxyAPI/ui@latest/registry/natal-chart.json

apps/docs/index.html

@@ -552,7 +552,7 @@
 				"name": "Does this work with React, Next.js, Vue, and Svelte?",
 				"acceptedAnswer": {
 					"@type": "Answer",
-					"text": "Yes. The @roxyapi/ui-react package gives typed React wrappers for every component. Vue, Svelte, Angular, Solid, Astro, Qwik, and other frameworks consume the same Lit web components natively without a wrapper. The same components ship to every framework via the catalog at @roxyapi/ui."
+					"text": "Yes. The @roxyapi/ui-react package ships typed React components for every entry in the catalog. Vue, Svelte, Angular, Solid, Astro, Qwik, and other frameworks consume the same Lit web components natively, no extra install required. The same components ship to every framework via the catalog at @roxyapi/ui."
 				}
 			},
 			{
@@ -712,7 +712,7 @@ <h2 id="faq-title">Frequently asked</h2>
 			</details>
 			<details>
 				<summary>Does this work with React, Next.js, Vue, and Svelte?</summary>
-				<p>Yes. The <code>@roxyapi/ui-react</code> package ships typed React wrappers. Vue, Svelte, Angular, Solid, Astro, and Qwik consume the same Lit web components natively without a wrapper.</p>
+				<p>Yes. The <code>@roxyapi/ui-react</code> package ships typed React components for every entry in the catalog. Vue, Svelte, Angular, Solid, Astro, and Qwik consume the same Lit web components natively, no extra install required.</p>
 			</details>
 			<details>
 				<summary>Can I use RoxyAPI UI with shadcn in a Next.js or React app?</summary>

packages/ui-react/README.md

@@ -360,7 +360,7 @@ The server component fetches, the client component renders. The API key never cr
 <details>
 <summary><strong>Tailwind v3 vs v4 compatibility?</strong></summary>
 
-Both work. Components do not consume Tailwind utilities. Tailwind utilities apply outside the components on wrappers and containers; inside the Shadow DOM, components read `--roxy-*` CSS custom properties only.
+Both work. Components do not consume Tailwind utilities. Tailwind utilities apply outside the components on parent layout elements and containers; inside the Shadow DOM, components read `--roxy-*` CSS custom properties only.
 
 For Tailwind v4 users, the shadcn registry installs a CSS bridge that maps your existing v4 design tokens onto `--roxy-*`. For Tailwind v3 users, set `--roxy-*` directly on `:root`, or write a tiny bridge:
 
@@ -394,7 +394,7 @@ useEffect(() => {
 return <roxy-location-search ref={ref} />;
 ```
 
-Upgrade to React 19 when you can; the wrappers route everything cleanly.
+Upgrade to React 19 when you can; the React components route everything cleanly.
 </details>
 
 <details>
@@ -454,7 +454,7 @@ Mock `@roxyapi/sdk` at the network boundary so unit tests do not hit the live AP
 <details>
 <summary><strong>What if I want to fork or own a component?</strong></summary>
 
-Use the shadcn registry. The registry drops the component source, a wrapper file, and a CSS theme bridge into your repo. Edit anything; the source is yours from that point.
+Use the shadcn registry. The registry drops the React component source and a CSS theme bridge into your repo. Edit anything; the source is yours from that point.
 
 ```bash
 npx shadcn@latest add https://cdn.jsdelivr.net/gh/RoxyAPI/ui@latest/registry/natal-chart.json

packages/ui/README.md

@@ -366,7 +366,7 @@ The server component fetches, the client component renders. The API key never cr
 <details>
 <summary><strong>Tailwind v3 vs v4 compatibility?</strong></summary>
 
-Both work. Components do not consume Tailwind utilities. Tailwind utilities apply outside the components on wrappers and containers; inside the Shadow DOM, components read `--roxy-*` CSS custom properties only.
+Both work. Components do not consume Tailwind utilities. Tailwind utilities apply outside the components on parent layout elements and containers; inside the Shadow DOM, components read `--roxy-*` CSS custom properties only.
 
 For Tailwind v4 users, the shadcn registry installs a CSS bridge that maps your existing v4 design tokens onto `--roxy-*`. For Tailwind v3 users, set `--roxy-*` directly on `:root`, or write a tiny bridge:
 
@@ -400,7 +400,7 @@ useEffect(() => {
 return <roxy-location-search ref={ref} />;
 ```
 
-Upgrade to React 19 when you can; the wrappers route everything cleanly.
+Upgrade to React 19 when you can; the React components route everything cleanly.
 </details>
 
 <details>
@@ -460,7 +460,7 @@ Mock `@roxyapi/sdk` at the network boundary so unit tests do not hit the live AP
 <details>
 <summary><strong>What if I want to fork or own a component?</strong></summary>
 
-Use the shadcn registry. The registry drops the component source, a wrapper file, and a CSS theme bridge into your repo. Edit anything; the source is yours from that point.
+Use the shadcn registry. The registry drops the React component source and a CSS theme bridge into your repo. Edit anything; the source is yours from that point.
 
 ```bash
 npx shadcn@latest add https://cdn.jsdelivr.net/gh/RoxyAPI/ui@latest/registry/natal-chart.json

scripts/brand-grep.ts

@@ -130,6 +130,16 @@ const CATEGORY_A_PATTERNS: Pattern[] = [
 		label: 'forbidden-phrase',
 		test: ci(/thin\s+(wrapper|shell|shells)/i),
 	},
+	{
+		category: 'A',
+		label: 'forbidden-phrase',
+		test: ci(/\b(react|typed)\s+wrappers?\b/i),
+	},
+	{
+		category: 'A',
+		label: 'forbidden-phrase',
+		test: ci(/\bwrapper\s+(file|around)\b/i),
+	},
 	{
 		category: 'A',
 		label: 'forbidden-phrase',
@@ -288,6 +298,8 @@ const EXTRACTION_RES: RegExp[] = [
 	/jsdelivr\s+UMD/i,
 	/lazy[-\s]?load(?:s|ing)?/i,
 	/thin\s+(wrapper|shell|shells)/i,
+	/\b(react|typed)\s+wrappers?\b/i,
+	/\bwrapper\s+(file|around)\b/i,
 	/decoupled\s+release|coordinated\s+release/i,
 	/no\s+runtime\s+(dependency|deps)/i,
 	/\bforwardRef\b/,