@kazee-ds/init 0.1.8 → 0.1.10

package/README.md

@@ -1,8 +1,10 @@
 # @kazee-ds/init
 
-Preview-first setup for an existing standalone React or Vue application. Published CLI 0.1.8 pins React/Vue/styles at 0.5.5 and consumer lint at 0.4.2. Verify the available npm versions before installing. Earlier CLI releases targeted private GitLab.
+Version **0.1.10** pins runtime/styles **0.7.0** and lint **0.5.1**. Verify all target versions before using registry commands. Local candidate verification uses matching packed artifacts. See [release status](https://gitlab.com/kazee.indonesia/kazee-design-system/-/blob/main/docs/versions.md).
 
-From an existing application, preview with `npm exec --yes --package=@kazee-ds/init@0.1.8 -- kazee-init`; append `--apply` after reviewing the plan.
+Preview-first setup for an existing standalone React or Vue application. Preserve the application's framework, package manager and configuration. Earlier CLI releases targeted private GitLab.
+
+From an existing application, preview with `npm exec --yes --package=@kazee-ds/init@0.1.10 -- kazee-init`; append `--apply` after reviewing the plan.
 
 From the design-system checkout, run:
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@kazee-ds/init",
-  "version": "0.1.8",
+  "version": "0.1.10",
   "description": "Preview-first setup for Kazee Design System consumers",
   "type": "module",
   "bin": {

package/src/content.mjs

@@ -1,6 +1,6 @@
 import { readFileSync } from 'node:fs';
 
-export const RELEASE = Object.freeze({ framework: '0.5.5', styles: '0.5.5', lint: '0.4.2' });
+export const RELEASE = Object.freeze({ framework: '0.7.0', styles: '0.7.0', lint: '0.5.1' });
 export const REGISTRY = 'https://registry.npmjs.org/';
 const INIT_VERSION = JSON.parse(
   readFileSync(new URL('../package.json', import.meta.url), 'utf8'),
@@ -15,7 +15,7 @@ export function managedRules(framework) {
   ).replaceAll('\r\n', '\n');
   const other = framework === 'react' ? 'Vue' : 'React';
   const filtered = template.replace(new RegExp(`## ${other} API\\n[\\s\\S]*?(?=\\n## |$)`), '');
-  return `${START}\n<!-- Template revision: 2026-10-28; init ${INIT_VERSION}; ${framework} -->\n${filtered.trim()}\n${END}`;
+  return `${START}\n<!-- Template revision: 2026-10-30; init ${INIT_VERSION}; ${framework} -->\n${filtered.trim()}\n${END}`;
 }
 
 export function installCommand(manager, framework) {

package/templates/AGENTS.md

@@ -5,7 +5,7 @@ Apply these rules to UI work in this application alongside its existing project
 ## Check the installed contract first
 
 - Read this application's `package.json` and lockfile before changing UI. Use its installed package version as the API contract.
-- Use the installed version's public catalog. Framework/styles 0.5.5 include the Toast keyboard guard and shared subtle borders; tokens are 0.4.4 and lint is 0.4.2. MCP 0.1.8 retains verified 0.5.1, 0.5.2, 0.5.3 and 0.5.5 catalogs; confirm that exact MCP patch is published before pinning it. Older MCP 0.1.4 labels 0.5.1 as a workspace candidate. Use installed public types if the matching verified catalog is unavailable. Do not assume a component exists in an older version.
+- Use the exact installed version public catalog. Published framework/styles 0.6.0 use tokens 0.4.4 and lint 0.5.0. Published MCP 0.1.9 lacks the verified 0.6.0 snapshot; the 0.1.10 candidate adds it alongside a separate 0.7.0-workspace preview. Confirm publication before updating the client pin and reconnect. Never substitute workspace docs for an installed registry package. New Avatar/date/time/dense-control APIs require matching 0.7.0 artifacts; do not assume they exist in earlier packages.
 - When Kazee MCP is connected, read `get_catalog_versions`, then `list_components`, `get_component_docs`, and `get_component_examples` using this framework and exact installed version. Otherwise inspect the installed package's public types when uncertain. A prop accepted by React Aria, Reka UI, or another UI library is not automatically supported by Kazee components.
 - Start file discovery in application source, manifests, and the installed Kazee package's public entry points/types. Do not recursively list all of `node_modules` or investigate React Aria/Reka UI internals for routine component usage.
 - Investigate dependency internals only when a concrete type, build, or runtime failure remains unexplained by the public contract. Identify that failure and the relevant file before expanding the search. When the requested behavior, build, and typecheck pass, report the result and any unrun checks instead of continuing speculative API research.
@@ -22,7 +22,7 @@ MCP is a read-only reference, not an installer or validator. It needs no token a
 - Import from `@kazee-ds/react` or `@kazee-ds/vue` public entry points. Do not copy package source into the application or import private build files.
 - Do not bypass these components by importing React Aria or Reka UI directly to recreate their behavior. Keep unrelated existing integrations outside the task unchanged.
 - Import `@kazee-ds/styles/index.css` once at the application's global CSS entry. It includes the tokens; do not add a duplicate token stylesheet.
-- Use the public props for supported component styling. Do not rely on `className` or `style` on Kazee wrappers, or override their internal classes to create undocumented variants. Style application layout on surrounding elements.
+- Check the installed version before styling. In versions that expose composition, pass Tailwind classes directly to public parts (for example Select.Trigger), use root className/style in React or class/style in Vue, and use the typed classNames map for compact APIs. Older versions may not forward these props. Do not target undocumented internal DOM selectors. Style application layout with application-owned wrappers.
 - Common Button variants include `primary`, `secondary`, and `danger`; sizes are `sm`, `md`, and `lg`. Read the exact versioned contract for additional variants, icon-only and pending support. Defaults are `primary` and `md`; use `danger` for destructive actions.
 
 ## React API

package/templates/consumer-lint.md

@@ -1,6 +1,6 @@
 # Consumer lint rules
 
-[`@kazee-ds/eslint-config`](../packages/eslint-config) provides a reusable ESLint flat configuration. Published version `0.4.2` implements public-import boundaries and selected component API checks, including Input and extended Button variants. Current React/Vue/styles are `0.5.5`; tokens are `0.4.4`. See the [version matrix](versions.md). It is an ESM package for ESLint 10 and Node 22.16 or later, with TypeScript declarations and no runtime dependencies. Adding `AGENTS.md` alone does not enable these checks.
+The next consumer lint **0.5.1** candidate accepts the expanded size/variant APIs while preserving import, event and accessible-name checks. Published lint **0.5.0** accompanies runtime/styles **0.6.0**. New runtime/styles **0.7.0** and tokens **0.5.0** remain unpublished candidates. See [versions](versions.md).
 
 ## Rules
 
@@ -46,14 +46,14 @@ import { Button, Select } from '@kazee-ds/vue';
 </template>
 ```
 
-The rule rejects selected unsupported props. Coverage varies by component and version; consult installed public types rather than treating this rule as a complete API schema. Apply application layout and feedback outside the component. It reports diagnostics only; it does not autofix events, change application state, or rewrite imports.
+The rule rejects selected unsupported props. Coverage varies by component and version; consult installed public types rather than treating this rule as a complete API schema. The unpublished composition update allows root className/style (React), class/style (Vue), and typed classNames maps; earlier published versions can still reject these. Public compound parts accept their documented styling props. Framework callback, variant, accessible-name and import checks remain active. It reports diagnostics only; it does not autofix events, change application state, or rewrite imports.
 
 ## Enable in a consuming application
 
 Configure public npm access without read credentials using the [installation guide](installation.md). Keep the application's existing ESLint configuration, parsers, plugins, package manager, and lockfile, then install:
 
 ```sh
-npm install --save-dev --save-exact @kazee-ds/eslint-config@0.4.2
+npm install --save-dev --save-exact @kazee-ds/eslint-config@0.5.0
 ```
 
 Merge the configuration object into the application's existing flat config, after its framework/parser setup: