@expressivecss/mcp-server 0.2.0 → 0.2.2

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "expressivecss-mcp",
   "displayName": "ExpressiveCSS MCP",
-  "version": "0.2.0",
+  "version": "0.2.2",
   "description": "ExpressiveCSS workflow server with Setup Expert, Rules Enforcer, Creative Director, Page Arcjitect, Component Syntax Expert, and Quality Inspector.",
   "author": {
     "name": "BaezFJ",

package/.cursor-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "expressivecss-mcp",
   "displayName": "ExpressiveCSS MCP",
-  "version": "0.2.0",
+  "version": "0.2.2",
   "description": "ExpressiveCSS workflow server with Setup Expert, Rules Enforcer, Creative Director, Page Arcjitect, Component Syntax Expert, and Quality Inspector.",
   "author": {
     "name": "BaezFJ",

package/CHANGELOG.md

@@ -1,5 +1,28 @@
 # Changelog
 
+## 0.2.2 - 2026-10-01
+
+- Semantics findings from `rules_enforcer`, `quality_inspector`, and
+  `expressivecss-lint` report the element's line and column instead of 1:1.
+- Component guides list the API reference subsections they leave out. Their
+  examples use real link targets, and menu actions are buttons. The Buttons
+  guide calls `circle` a round common button and points icon buttons to
+  `.icon-button`.
+- The Lightbox guide includes its options and methods. The app-bar guide's
+  Search icon is a button.
+- The Cards guide uses a plain `<p>` for supporting copy. The Date picker and
+  Time picker guides use `.date-picker` and `.time-picker`, the Select guide
+  describes the `.field` wrapper instead of `.select-wrapper`, and the
+  Scrollspy example uses `hide-on-compact-only`.
+- Bundled framework guidance: ExpressiveCSS 0.12.0.
+
+## 0.2.1 - 2026-09-30
+
+- `rules_enforcer` requires an identifier boundary before a manual `.init(` call,
+  so a long identifier run no longer slows the scan.
+- Component guides say top app bars are pinned by default.
+- Bundled framework guidance: ExpressiveCSS 0.11.0.
+
 ## 0.2.0 - 2026-09-29
 
 - Add the `expressivecss-lint` bin: the `rules_enforcer` static checks as a command with a `--hook` mode for Claude Code `PostToolUse`, so agent edits are checked without a tool call. `server.js` now starts the server only when run as the entry point.

package/README.md

@@ -73,7 +73,7 @@ Static inspection uses descriptor-level, no-follow bounded reads and rechecks fi
 ## Command-line lint and agent hook
 
 `expressivecss-lint` runs the same static checks as `rules_enforcer` (bundled
-semantics rules, retired Materialize patterns, initialization checks) without
+semantics rules, retired markup patterns, initialization checks) without
 an MCP client. It exits 1 when it finds anything, so it fits `pre-commit` and CI:
 
 ```bash
@@ -111,8 +111,11 @@ files are parsed as HTML after `className` is rewritten to `class`, so
 markup built from expressions can escape a selector rule, and markup kept in
 a string prop (this repository's docs pages pass examples through
 `<Code code={...}>`) is parsed as if it were inline, which produces false
-findings. Semantics findings report line 1 because the parser keeps no
-source positions; the snippet identifies the element.
+findings. Semantics findings report the line and column of the element's
+start tag. Elements the parser creates itself, such as the `<p>` implied by a
+stray `</p>`, have no start tag and report 1:1, as do all findings in very
+large files with thousands of tags. After the `className` rewrite, later
+columns on the same line read four lower per rewritten attribute.
 
 ## Consumer browser scenarios
 
@@ -180,7 +183,7 @@ The real `projectRoot` must equal or be contained by one of those roots. A tool
 }
 ```
 
-The packaged config targets the npm release, following the same `npx ...@latest` shape as daisyUI Blueprint. Before the first publish, configure local development with `node` and an absolute path to this folder's `server.js` instead.
+The packaged config targets the npm release through `npx ...@latest`. Before the first publish, configure local development with `node` and an absolute path to this folder's `server.js` instead.
 
 ### Hermes
 

package/capability-roadmap.json

@@ -1,6 +1,6 @@
 {
   "schemaVersion": 1,
-  "frameworkVersion": "0.10.1",
+  "frameworkVersion": "0.12.0",
   "sourceRevision": "b3821bb0390b985c31a858ab7f4e3dbf0de2d71c",
   "basis": "Reviewed checkout snapshot, not proof of published package contents or target-browser conformance. Implemented means only the named scope. Full Material parity remains unassessed.",
   "browserRun": {

package/component-decisions.json

@@ -1,7 +1,7 @@
 {
   "schemaVersion": 1,
   "generatedBy": "mcp/expressivecss/scripts/sync-guides.mjs",
-  "frameworkVersion": "0.10.1",
+  "frameworkVersion": "0.12.0",
   "authority": "This catalogue owns component-selection metadata. Component guides own syntax and semantics.json owns authored semantics.",
   "components": [
     {