@stonedogcode/style 0.20.2 → 0.20.3

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@stonedogcode/style",
-  "version": "0.20.2",
+  "version": "0.20.3",
   "description": "A Panda CSS design system: a themeable Panda preset plus the React components built on it.",
   "license": "Apache-2.0",
   "author": "StoneDogCode L.L.C.",
@@ -49,6 +49,8 @@
     "//publish:stonedog-style": "Publish to npm, end to end. Run from a terminal, interactively — npm prompts for the 2FA one-time password and the login flow needs a browser. It refuses a checkout that is detached, dirty, or behind origin/main: a submodule sits detached at the consumer's gitlink by default, and publishing from one commit behind ships a tarball missing the very thing you are publishing for while looking like a success (it did, on 2026-08-04, without TitleLogo.tsx). Runs the gate, prints the tarball listing, then proves the result by installing from the registry into a temp directory.",
     "publish:stonedog-style": "bash scripts/publish-package.sh",
     "publishnpm": "npm run publish:stonedog-style",
+    "//release": "One memorable command per repo. It cannot be called `publish`: that is a reserved npm lifecycle name, so `npm publish` inside scripts/publish-package.sh would fire it and run the whole gate and publish a second time, hitting the already-published guard and reporting a successful release as a failure.",
+    "release": "npm run publish:stonedog-style",
     "version:bump:patch": "npm version patch --no-git-tag-version",
     "version:bump:minor": "npm version minor --no-git-tag-version",
     "audit": "npm audit --audit-level=moderate"

package/src/components/StyledHeading.tsx

@@ -1,3 +1,30 @@
+"use client";
+
+/**
+ * `"use client"`, and it is load-bearing.
+ *
+ * This component calls `useFontSizeProfile()` (a client hook) during its
+ * render. Without the directive above, the module is a Server Component in a
+ * consumer's App Router tree, the hook is invoked on the server, and React
+ * throws:
+ *
+ *     Attempted to call useFontSizeProfile() from the server but
+ *     useFontSizeProfile is on the client.
+ *
+ * Next serves that as its blank "This page couldn't load" page with no detail
+ * anywhere in the browser, so a consumer sees a dead route and nothing naming
+ * this component. Every PRD and how-to page on stonedogcode.com was unreachable
+ * this way (NEH-1290).
+ *
+ * Every other component here that calls the hook already declared it — this was
+ * the only one that did not, which is why the failure looked like something
+ * specific to whichever page happened to render a heading on the server.
+ *
+ * `src/components/__tests__/client-directive.test.ts` keeps this honest. It has
+ * to be a source assertion: a jsdom render imports the module directly, so no
+ * RSC boundary exists and every test here passes with or without the directive.
+ */
+
 import React from "react";
 import StyledSeparator from "./StyledSeparator";
 import StyledText from "./StyledText";