docs: 📝 monorepo package release distinction

Author: punkbit

README.md

@@ -37,4 +37,6 @@ yarn changeset:version
 
 ## Release
 
-See [Package Release](./packages/click-ui/docs/package-release.md) for detailed release instructions.
+See [Package Release](./packages/click-ui/docs/package-release.md) for detailed release instructions for Click UI.
+
+For releasing supporting monorepo packages (e.g. `design-tokens`), see the [Monorepo Package Release](./packages/click-ui/docs/package-release.md#monorepo-package-release) section.

packages/click-ui/docs/package-release.md

@@ -16,6 +16,7 @@
   - [Create a new release](#create-a-new-release)
   - [Updating a pending release version](#updating-a-pending-release-version)
   - [Promoting to stable release](#promoting-to-stable-release)
+  - [Monorepo Package Release](#monorepo-package-release)
 
 **TLDR;** Use the [Create a new release Pull Request](#create-a-new-release-pull-request) for automated process.
 
@@ -137,6 +138,7 @@ Always include a changeset to ensure each promotion reflects real, trackable cha
 
 ## Use-Cases
 
+
 ### Create a new release
 
 Follow these steps to create a new release:
@@ -251,3 +253,28 @@ git push origin chore/sync-v1.0.0-changes-back-to-main
 
 > [!IMPORTANT]
 > This step is critical. The `main` branch must reflect the stable release state to ensure future pre-releases start from the correct version baseline.
+
+### Monorepo Package Release
+
+The [monorepo package publisher](https://github.com/ClickHouse/click-ui/actions/workflows/monorepo-package-publisher.yml) is a simplified workflow for releasing packages under `./packages/*` that support click-ui (e.g. `design-tokens`) and can be published independently.
+
+> [!IMPORTANT]
+> This workflow does **not** automate the changeset cycle. You are responsible for preparing the version and changelog before triggering a release. Specifically:
+>
+> 1. Enter/leave pre-release mode as needed (`yarn workspace @clickhouse/design-tokens changeset pre enter <tag>` / `changeset pre exit`)
+> 2. Run `yarn workspace @clickhouse/design-tokens changeset version` to bump the version and generate the changelog
+> 3. Ensure the version bump and changelog are committed in the branch/commit you intend to release
+>
+> The automated [create release](#create-a-new-release-pull-request) workflow handles all of this for `@clickhouse/click-ui`. For other monorepo packages, use this manual workflow instead.
+
+To release a monorepo package:
+
+1. Go to [Actions > Monorepo Package Publisher](https://github.com/ClickHouse/click-ui/actions/workflows/monorepo-package-publisher.yml)
+2. Click **Run workflow**
+3. Select the package to release
+4. Choose the release type (`test`, `rc`, `stable`, `latest`)
+5. Toggle **dry run** to `true` to validate without publishing (recommended first)
+6. Type the package name to confirm
+7. For `stable`, type the branch name to confirm
+8. Click **Run workflow**
+9. Once validated, re-run with **dry run** set to `false`