chore(monorepo): 🤖 split mono-repository into libs and packages (semantic distinction)

[punkbit]

Why?

The monorepo had no clear structural distinction between the core Click UI (we ship) and the packages we build with. The PR makes "packages/" the ingredients and "libs/" the core component library we ship!

Alternatively, the project could become a Design System. But since the goal is Click UI, we're mainly ensuring that the main component library is the core of this whole setup, e.g. lib/click-ui or lib/core or packages/core, something that determines its goal!

⚠️ Depends on #938 and https://github.com/ClickHouse/click-ui/tree/chore/monorepo-assets-as-package that should be merged first

How?

• Moved click-ui into libs/ as the core thing the monorepo delivers
• Kept icons in packages/, it exists to support Click UI, but can also be consumed independently by other consumers
• Rewrite documentation, e.g. create a new README.md and datap libs/click-ui/README.md

Preview?

N/A

[changeset-bot]

⚠️ No Changeset found

Latest commit: ebe69ac

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[github-actions]

Claude finished @punkbit's task in 42s —— View job

---

PR Review

✅ Looks great! This is a clean structural reorganization.

The PR correctly:

• Moves click-ui from packages/click-ui → libs/click-ui
• Updates all 9 workflow files consistently with the new path
• The root package.json already has "libs/*" in workspaces, so no changes needed there
• All scripts in libs/click-ui/.scripts/bash/ are present and accounted for

No bugs, regressions, or missing path updates found. The changeset bot warning is expected — this is a pure infrastructure change with no version bump needed.

Nice work on the clear separation of intent between "what we ship" (libs/) and "ingredients" (packages/). 🙌

[github-actions]

Claude finished @punkbit's task in 1m 3s —— View job

---

PR Review

• Gather context
• Review changed files
• Post findings

---

✅ Looks great! Clean structural reorganization — no issues found.

This PR does exactly what it says: moves click-ui from packages/ into libs/ to semantically distinguish "what we ship" from "build ingredients." The scope is purely path updates — no component logic changed.

Checked:

• All 9 workflow files consistently updated packages/click-ui → libs/click-ui
• Root package.json workspaces already includes "libs/*" (no change needed)
• No stray packages/click-ui references remain anywhere in the repo
• libs/click-ui/package.json name and exports are unchanged (no public API impact)
• New root README.md accurately reflects the updated structure with correct paths in the table and examples

The changeset bot warning is expected — pure infrastructure move, no version bump needed. 🙌

[github-actions]

Claude finished @punkbit's task in 1m 7s —— View job

---

PR Review

• Gather context
• Review changed files
• Post findings

---

✅ Clean structural reorganization — looking good!

Pure path migration: packages/click-ui → libs/click-ui. No component logic, types, or public API touched. The duplicate TOC entry from previous review rounds has been fixed. Zero remaining packages/click-ui references anywhere in the repo.

💡 Suggestion (non-blocking, docs only)

• README.md line 51: The Packages table lists icons as "Internal icon generation tooling", but packages/icons/package.json shows it's @clickhouse/icons — a scoped, published package with files, exports, and types configured. The description is misleading for contributors. Suggest either updating the description to reflect it's a publishable shared package, or renaming it in the table to @clickhouse/icons to match reality. Fix this →

Otherwise the PR is good to go! 🙌

[github-actions]

Claude finished @punkbit's task in 1m 17s —— View job

---

PR Review

• Gather context
• Review changed files
• Post findings

---

✅ Clean structural reorganization — looking good!

Pure path migration: packages/click-ui → libs/click-ui. No component logic, types, or public API touched. All 9 workflow files consistently updated. Zero remaining packages/click-ui references.

---

💡 Suggestions (non-blocking, docs only)

• README.md line 51 — Packages table: icons is listed as icons with description "Internal icon generation tooling", but packages/icons/package.json shows it's @clickhouse/icons — a scoped, published package. The name and description are both misleading.

  • Change name from icons → @clickhouse/icons
  • Change description from "Internal icon generation tooling" → "ClickHouse SVG icons, logos, flags, and payment icons" (matches the package's own description)
  • Fix this →

• README.md line 103 — "Creating a New Internal Package": The guide says "Initialize with a package.json (no npm scope needed)" — but @clickhouse/icons has a scope. Consider updating this to reflect that packages can be scoped if they're intended for publication.

Otherwise the PR is in great shape! 🙌

[ariser]

It's hard to look through all of the changes in PRs like this, so I'm basing my approve on the general idea and green CI

[punkbit]

It's hard to look through all of the changes in PRs like this, so I'm basing my approve on the general idea and green CI

Yes, it'd be much easier for me, too, to keep these in context. But based on previous file architecture changes, I'll be told the branch changes are too big. This is where the comment I made during a call came from, where I said the same thing you mentioned here, e.g. single purpose. At the end of the day, I'll need runtime to confirm everything's ok, e.g. CI, scripts, so there'll be revisions surely.

Thanks for checking!

[github-actions]

Claude finished @punkbit's task in 59s —— View job

---

PR Review

• Gather context
• Review changed files
• Post findings

---

✅ Clean structural reorganization — no regressions found.

All 9 workflow files consistently updated packages/click-ui → libs/click-ui. The .changeset renames are pure moves with no content changes. Zero stray packages/click-ui references remain.

---

💡 Suggestions (non-blocking, docs only — same as prior rounds)

These were flagged in earlier reviews and are still present:

• README.md line 51 — Packages table: icons is listed with name icons and description "Internal icon generation tooling", but packages/icons/package.json shows it's @clickhouse/icons — a scoped, published package with files, exports, and types configured, with description "ClickHouse SVG icons, logos, flags, and payment icons". Both the name and description are misleading.

  • Change name: icons → @clickhouse/icons
  • Change description: "Internal icon generation tooling" → "ClickHouse SVG icons, logos, flags, and payment icons"
  • Fix this →

• README.md — "Creating a New Internal Package": Says "Initialize with a package.json (no npm scope needed)", but @clickhouse/icons is scoped. Since the architecture table marks packages/ as "Yes" for Published, this guidance contradicts the actual setup.

• README.md typo: "help us keep track fo changes" → should be "keep track of changes"

None of these block merge. 🙌

[github-actions]

Claude finished @punkbit's task in 46s —— View job

---

PR Review

• Gather context
• Review changed files
• Post findings

---

✅ Clean structural reorganization — no regressions found.

Pure path migration: packages/click-ui → libs/click-ui. No component logic, types, or public API touched. All 9 workflow files consistently updated. Zero stray packages/click-ui references remain.

---

💡 Suggestions (non-blocking, docs only — same as prior rounds, still present)

• README.md line 51 — Packages table: icons is listed with name icons and description "Internal icon generation tooling", but packages/icons/package.json confirms it's @clickhouse/icons — a scoped, published package.

  • Change name: icons → @clickhouse/icons
  • Change description: "Internal icon generation tooling" → "ClickHouse SVG icons, logos, flags, and payment icons"
  • Fix this →

• README.md line 104 — "Creating a New Internal Package": Says "Initialize with a package.json (no npm scope needed)", but @clickhouse/icons has a scope. Update to reflect that packages can be scoped if intended for publication.

• README.md line 131 — Typo: "help us keep track fo changes" → "help us keep track of changes"

None of these block merge. 🙌

[workflow-authentication-public]

📚 Storybook Preview Deployed

✅ Preview URL: https://click-mnl22mgep-clickhouse.vercel.app

Built from commit: 349bf53f85280dca3ef717dc536d8b25010b696c