@decantr/mcp-server 1.0.0-beta.8 → 1.0.0

package/README.md

@@ -1,5 +1,8 @@
 # @decantr/mcp-server
 
+Support status: `core-supported`  
+Release channel: `stable`
+
 Design intelligence for AI-generated UI. Make Claude, Cursor, and Windsurf generate better code.
 
 - **Structured design context** -- gives your AI assistant patterns, layouts, and component specs instead of letting it guess
@@ -57,24 +60,40 @@ Add to your Windsurf MCP config (`~/.windsurf/mcp.json`):
 }
 ```
 
-## Tools
+## Key Tools
+
+The server exposes Decantr registry, context, benchmark, and verification tools. Highlights:
 
 | Tool | Description | Example Input |
 |------|-------------|---------------|
 | `decantr_create_essence` | Generate an Essence spec skeleton from a project description | `{ "description": "SaaS dashboard with analytics and billing", "framework": "react" }` |
 | `decantr_read_essence` | Read the current `decantr.essence.json` from the working directory | `{}` or `{ "path": "./custom.essence.json" }` |
 | `decantr_validate` | Validate an Essence file against the schema and guard rules | `{ "path": "./decantr.essence.json" }` |
-| `decantr_search_registry` | Search the community registry for patterns, archetypes, recipes, and styles | `{ "query": "kanban", "type": "pattern" }` |
+| `decantr_search_registry` | Search the community registry for patterns, archetypes, themes, and shells | `{ "query": "kanban", "type": "pattern" }` |
 | `decantr_resolve_pattern` | Get full pattern details: layout spec, components, presets, code examples | `{ "id": "data-table", "preset": "product" }` |
 | `decantr_resolve_archetype` | Get archetype details: default pages, layouts, features, suggested theme | `{ "id": "saas-dashboard" }` |
-| `decantr_resolve_recipe` | Get recipe decoration rules: shell styles, spatial hints, visual effects | `{ "id": "auradecantism" }` |
 | `decantr_resolve_blueprint` | Get a full app composition with page structure and personality traits | `{ "id": "ecommerce" }` |
 | `decantr_suggest_patterns` | Given a page description, get ranked pattern suggestions | `{ "description": "dashboard with metrics and charts" }` |
 | `decantr_check_drift` | Check if generated code violates the design intent in the Essence spec | `{ "page_id": "overview", "components_used": ["Card", "LineChart"], "theme_used": "auradecantism" }` |
+| `decantr_get_execution_pack` | Read compiled scaffold, section, page, review, or mutation execution packs, with hosted fallback when local context is missing | `{ "pack_type": "page", "id": "overview", "format": "json" }` |
+| `decantr_compile_execution_packs` | Compile a hosted execution-pack bundle from a local or inline essence document | `{ "path": "./decantr.essence.json", "namespace": "@official" }` |
+| `decantr_audit_project` | Run the schema-backed Decantr project audit against essence and compiled packs, with hosted fallback when local pack artifacts are missing | `{ "namespace": "@official" }` |
+| `decantr_critique` | Critique a file against the compiled review contract, with hosted fallback when local review packs are missing | `{ "file_path": "./src/pages/Overview.tsx", "namespace": "@official" }` |
+| `decantr_get_showcase_benchmarks` | Read the audited showcase corpus manifest, shortlist, or verification report | `{ "view": "verification" }` |
+
+For the broader product surface and support policy, see the root Decantr docs and package support matrix.
+
+## Compatibility
+
+`@decantr/mcp-server` is stable in the `1.x` line for the documented MCP tool surface.
+
+- new tools may be added in compatible releases
+- existing documented tool names and envelopes should not break without a major version
+- breaking changes to established tool contracts require a major version and migration note
 
 ## How It Works
 
-An Essence spec (`decantr.essence.json`) captures your design intent -- archetype, theme, page structure, patterns, and guard rules -- in a single declarative file. The MCP server exposes this spec and the Decantr registry to your AI assistant, giving it concrete layout specs, component lists, and decoration rules instead of relying on the model's generic training data. The result is generated code that follows a coherent design system, and drift detection that catches deviations before they ship.
+An Essence spec (`decantr.essence.json`) captures your design intent -- archetype, theme, page structure, patterns, and guard rules -- in a single declarative file. The MCP server exposes this spec and the Decantr registry to your AI assistant, giving it concrete layout specs, component lists, and visual treatments instead of relying on the model's generic training data. The result is generated code that follows a coherent design system, and drift detection that catches deviations before they ship.
 
 ## Example Workflow
 
@@ -86,8 +105,11 @@ The AI assistant calls these tools behind the scenes:
 2. `decantr_resolve_archetype` -- pulls default pages, layouts, and features for a SaaS dashboard
 3. `decantr_suggest_patterns` -- recommends `kpi-grid`, `chart-grid`, `data-table`, and `form-sections` for the described pages
 4. `decantr_resolve_pattern` -- fetches layout specs and component lists for each pattern
-5. `decantr_resolve_recipe` -- loads decoration rules (spacing, borders, effects) for the theme
-6. `decantr_check_drift` -- validates the generated code against the Essence spec before presenting it
+5. `decantr_get_execution_pack` -- loads the compiled scaffold/page/review packs as the task contract, falling back to hosted compilation when local pack artifacts are missing
+6. `decantr_compile_execution_packs` -- compiles the hosted pack bundle when the task needs a fresh remote contract from the essence document
+7. `decantr_check_drift` -- validates the generated code against the Essence spec before presenting it
+8. `decantr_critique` -- critiques a specific file, falling back to the hosted verifier when the local review pack is missing
+9. `decantr_audit_project` -- runs the stronger project-level audit once the implementation is in place
 
 The AI now generates code with the right layout structure, correct components, and consistent styling -- not a generic guess.
 

package/dist/bin.js

@@ -1,2 +1,2 @@
 #!/usr/bin/env node
-import "./chunk-NZBC33FN.js";
+import "./chunk-WN4I3BY6.js";