@adia-ai/adia-ui-forge 0.8.17 → 0.8.18

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "adia-forge",
-  "version": "0.8.17",
+  "version": "0.8.18",
   "description": "Maintain the adia-ui (@adia-ai) framework itself \u2014 author primitives and shells, run the A2UI generation pipeline and its corpus, review gen-UI quality, sweep QA, cut releases, deploy. The maintainer counterpart to adia-factory (the consumer/app-author plugin).",
   "author": {
     "name": "Kim",

package/CHANGELOG.md

@@ -1,5 +1,14 @@
 # Changelog — adia-forge
 
+## [0.8.18] — 2026-07-27
+
+### Added
+- **`adia-author` writes down the tag-naming rule across tiers** (`references/code-style.md`) — primitives and standalone feature composites carry `-ui`; shell/bespoke-cluster children and runtime roots are bare, namespaced by their cluster prefix. Ratified when `form-popover` shipped as the only unsuffixed standalone composite (renamed `form-popover-ui` the next release); `theme-panel` is explicitly grandfathered, not precedent.
+
+### Maintenance
+- **`.claude-plugin/plugin.json` version bump** — moves in lockstep with package.json (the `/plugin update` cache key).
+- **`skills/` touched in this release window** (1 file(s), e.g. `references/code-style.md`) — carried by the entries above.
+
 ## [0.8.17] — 2026-07-27
 
 ### Changed

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@adia-ai/adia-ui-forge",
-  "version": "0.8.17",
+  "version": "0.8.18",
   "description": "Maintain the adia-ui (@adia-ai) framework itself \u2014 author primitives and shells, run the A2UI generation pipeline and its corpus, review gen-UI quality, sweep QA, cut releases, deploy. The maintainer counterpart to adia-factory (the consumer/app-author plugin).",
   "keywords": [
     "adia-ui",

package/skills/adia-author/references/code-style.md

@@ -24,6 +24,24 @@ Every interactive surface, form control, layout container, and content block shi
 
 The catalog has 125 component directories under `packages/web-components/components/`. Before composing, confirm via `get_component_map` (the a2ui MCP) that the one you want exists — and what its real prop names are.
 
+### Tag naming across tiers (`-ui` or bare)
+
+Two rules cover every tag in the monorepo (ratified 2026-07-27, when
+`form-popover` shipped as the only standalone composite without the
+suffix and was renamed to `form-popover-ui` one release later):
+
+| Tier | Convention | Examples |
+| --- | --- | --- |
+| Primitives (`packages/web-components`) | **always `-ui`** | `button-ui`, `select-ui`, `nav-item-ui` |
+| Standalone feature composites (`packages/web-modules`) — drop-in anywhere, consumer-facing | **always `-ui`** | `confirm-dialog-ui`, `plan-picker-ui`, `date-range-selector-ui`, `form-popover-ui` |
+| Shell/bespoke-cluster children + runtime roots | **bare** — the cluster prefix is the namespace | `admin-topbar`, `chat-composer`, `editor-canvas`, `simple-shell`, `a2ui-root`, `gen-root` |
+
+`theme-panel` (bare, standalone) predates this rule and is grandfathered —
+do not copy it as precedent for a new standalone composite. The DIRECTORY
+name never carries the suffix in either tier (`plan-picker/` →
+`<plan-picker-ui>`), and the a2ui `component:` name is unaffected
+(`FormPopover`).
+
 ## Layout primitives
 
 Use `<col-ui>`, `<row-ui>`, `<grid-ui>`, `<stack-ui>` for layout — never a bare `<div>`. The primitives carry the project's spacing scale (`gap`, padding tokens) and respond to density / theme providers; a plain `<div>` strands content outside that system.