@kazee-ds/init 0.1.9 → 0.1.11

package/README.md

@@ -1,10 +1,10 @@
 # @kazee-ds/init
 
-Version **0.1.9** pins runtime/styles **0.6.0** and lint **0.5.0**, with composition-aware agent templates. Verify publication of these prepared versions before using the registry command. Local commands target the checkout. See [release status](https://gitlab.com/kazee.indonesia/kazee-design-system/-/blob/main/docs/versions.md).
+Version **0.1.11** pins React/Vue/styles **0.8.0** and consumer lint **0.5.1**. Published init **0.1.10** pins the previous **0.7.0** release. Verify candidate publication before running its registry commands. See [release status](https://gitlab.com/kazee.indonesia/kazee-design-system/-/blob/main/docs/versions.md).
 
 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.9 -- kazee-init`; append `--apply` after reviewing the plan.
+From an existing application, preview with `npm exec --yes --package=@kazee-ds/init@0.1.11 -- 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.9",
+  "version": "0.1.11",
   "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.6.0', styles: '0.6.0', lint: '0.5.0' });
+export const RELEASE = Object.freeze({ framework: '0.8.0', styles: '0.8.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'),

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 React/Vue/styles 0.7.0 use tokens 0.5.0 and lint 0.5.1. The next MCP 0.1.11 candidate retains the verified 0.7.0 snapshot and a separate 0.8.0-workspace preview. Confirm publication before updating the client pin and reconnect. Never substitute workspace docs for installed npm packages. Avatar/date/time/dense-control APIs require 0.7.0; selectable Card and Switch/chip corrections require the next 0.8.0 artifacts.
 - 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.

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. Prepared version `0.5.0` supports the `0.6.0` React/Vue/styles composition contract; tokens stay `0.4.4`. These versions are unpublished candidates. The preceding verified lint release is `0.4.2`. See the [version matrix](versions.md). The package targets ESLint 10 and Node 22.16 or later, with TypeScript declarations and no runtime dependencies. Adding `AGENTS.md` alone does not enable these checks.
+Public npm metadata was verified on 2026-10-31 for React/Vue/styles **0.7.0**, tokens **0.5.0**, consumer ESLint **0.5.1**, and init/MCP **0.1.10**. This checkout prepares unpublished React/Vue/styles **0.8.0** and init/MCP **0.1.11**; tokens and ESLint remain unchanged. See [versions](versions.md) and [release preparation](releases/2026-10-31-selectable-card.md).
 
 ## Rules
 
@@ -53,7 +53,7 @@ The rule rejects selected unsupported props. Coverage varies by component and ve
 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.5.0
+npm install --save-dev --save-exact @kazee-ds/eslint-config@0.5.1
 ```
 
 Merge the configuration object into the application's existing flat config, after its framework/parser setup: