@adaptabletools/adaptable-mcp 0.1.0 → 1.0.0

package/README.md

@@ -9,8 +9,6 @@ The agent still writes the code; this package looks things up and checks them. T
 
 Requires Node 20+. Full guide: [getting-started-ai-cli](https://www.adaptabletools.com/docs/getting-started-ai-cli).
 
-> This package is being rebuilt. The commands below describe the target contract; the published `canary` line fills them in milestone by milestone, and `adaptable --help` lists what the installed version supports.
-
 ## Skills first
 
 Install the AdapTable Agent Skills into a project; they tell the agent when to run the CLI and how to read its output:

package/data/manifest.snapshot.json

@@ -1,6 +1,6 @@
 {
   "schemaVersion": 2,
-  "adaptableVersion": "24.0.0-canary.10",
+  "adaptableVersion": "24.0.0",
   "major": 24,
   "agGridPeer": ">=36.2.0",
   "agGridPairings": [
@@ -148,7 +148,7 @@
     "requiredAgGrid": ">=36.2.0"
   },
   "skills": {
-    "version": "0.1.0-canary.2"
+    "version": "0.1.0"
   },
   "cli": {
     "minVersion": "0.1.0"
@@ -160,7 +160,7 @@
     "vue"
   ],
   "baseUrl": "https://www.adaptabletools.com",
-  "builtAt": "2026-10-30T10:23:02.127Z",
+  "builtAt": "2026-10-30T11:25:44.075Z",
   "pageCount": 1191,
   "files": {
     "llmsTxt": {

package/dist/skills/adaptable-debug/SKILL.md

@@ -67,8 +67,8 @@ instance list is empty, the problem is mounting, not State (symptoms.md).
 ## Phase 4 — Validate what you collected
 
 ```bash
-npx -y @adaptabletools/adaptable-mcp@^0 check state persistent.json --columns columns.json --kind persistent
-npx -y @adaptabletools/adaptable-mcp@^0 check expression "<suspect rule>" --module <Module> --columns columns.json
+npx -y @adaptabletools/adaptable-mcp@^1 check state persistent.json --columns columns.json --kind persistent
+npx -y @adaptabletools/adaptable-mcp@^1 check expression "<suspect rule>" --module <Module> --columns columns.json
 ```
 
 A persisted State that fails explains most "impossible" behaviour in one
@@ -126,7 +126,7 @@ snippet with keys stripped; the logs.
 **Ask** before including any row-data values. The default is scrubbed:
 
 ```bash
-npx -y @adaptabletools/adaptable-mcp@^0 anonymise <bundle file> --out anonymised.json
+npx -y @adaptabletools/adaptable-mcp@^1 anonymise <bundle file> --out anonymised.json
 ```
 
 Try to reproduce the symptom in the public support template linked from

package/dist/skills/adaptable-debug/VERSION.md

@@ -1 +1 @@
-0.1.0
+1.0.0

package/dist/skills/adaptable-debug/references/_shared/agents-snippet.md

@@ -1,3 +1,3 @@
 <!-- BEGIN:adaptable-agent-rules -->
-AdapTable (`@adaptabletools/*`) is used in this project. Its Options, State shapes, API and AdapTableQL change between majors, so do not rely on recalled knowledge. Before writing or changing AdapTable code use the `adaptable-dev` skill; for first-time integration `adaptable-setup`; for a misbehaving running grid `adaptable-debug`; for version upgrades `adaptable-upgrade`. Validate State, expressions and setup with `npx -y @adaptabletools/adaptable-mcp@^0 check …` (or the `check_*` MCP tools when configured); read the docs for the installed version with `npx -y @adaptabletools/adaptable-mcp@^0 docs search "<topic>"`. The columnDefs, gridOptions and AG Grid modules of an AdapTable grid are covered by these skills too; consult the `ag-dev` / `ag-update` skills or AG Grid's documentation only for what the AdapTable docs and checks do not cover.
+AdapTable (`@adaptabletools/*`) is used in this project. Its Options, State shapes, API and AdapTableQL change between majors, so do not rely on recalled knowledge. Before writing or changing AdapTable code use the `adaptable-dev` skill; for first-time integration `adaptable-setup`; for a misbehaving running grid `adaptable-debug`; for version upgrades `adaptable-upgrade`. Validate State, expressions and setup with `npx -y @adaptabletools/adaptable-mcp@^1 check …` (or the `check_*` MCP tools when configured); read the docs for the installed version with `npx -y @adaptabletools/adaptable-mcp@^1 docs search "<topic>"`. The columnDefs, gridOptions and AG Grid modules of an AdapTable grid are covered by these skills too; consult the `ag-dev` / `ag-update` skills or AG Grid's documentation only for what the AdapTable docs and checks do not cover.
 <!-- END:adaptable-agent-rules -->

package/dist/skills/adaptable-debug/references/_shared/capabilities.md

@@ -29,7 +29,7 @@ Every capability of `@adaptabletools/adaptable-mcp` (response schema 1) has a CL
 
 ## Choosing a binding
 
-- Prefer the MCP tool when the harness has the `adaptable` MCP server configured. Otherwise run the CLI command as `npx -y @adaptabletools/adaptable-mcp@^0 <command> [options]`; add `--json` to read fields instead of Markdown.
+- Prefer the MCP tool when the harness has the `adaptable` MCP server configured. Otherwise run the CLI command as `npx -y @adaptabletools/adaptable-mcp@^1 <command> [options]`; add `--json` to read fields instead of Markdown.
 - If neither binding exists for what you need — the capability is not in this table, not in `adaptable --capabilities`, or not in the MCP tool list — say so and fall back to the docs (see `docs-protocol.md`). Never improvise the result a missing capability would have produced.
 - All bindings return the same envelope: `ok`, `data`, `issues`, `warnings`, and on failure `error { code, message, hint }`. CLI exit codes: `0` ok, `1` findings, `2` usage, `3` environment.
 - Skill scripts cannot reach the agent's MCP session: a script only ever runs the CLI. When the CLI is unavailable, the agent performs the fallback itself.

package/dist/skills/adaptable-debug/references/_shared/grounding.md

@@ -7,7 +7,7 @@ or diagnosing anything, establish what is actually installed.
 ## 1. Detect the project
 
 ```bash
-npx -y @adaptabletools/adaptable-mcp@^0 detect --json
+npx -y @adaptabletools/adaptable-mcp@^1 detect --json
 ```
 
 (or the `detect_environment` MCP tool when the `adaptable` MCP server is

package/dist/skills/adaptable-dev/VERSION.md

@@ -1 +1 @@
-0.1.0
+1.0.0

package/dist/skills/adaptable-dev/references/_shared/agents-snippet.md

@@ -1,3 +1,3 @@
 <!-- BEGIN:adaptable-agent-rules -->
-AdapTable (`@adaptabletools/*`) is used in this project. Its Options, State shapes, API and AdapTableQL change between majors, so do not rely on recalled knowledge. Before writing or changing AdapTable code use the `adaptable-dev` skill; for first-time integration `adaptable-setup`; for a misbehaving running grid `adaptable-debug`; for version upgrades `adaptable-upgrade`. Validate State, expressions and setup with `npx -y @adaptabletools/adaptable-mcp@^0 check …` (or the `check_*` MCP tools when configured); read the docs for the installed version with `npx -y @adaptabletools/adaptable-mcp@^0 docs search "<topic>"`. The columnDefs, gridOptions and AG Grid modules of an AdapTable grid are covered by these skills too; consult the `ag-dev` / `ag-update` skills or AG Grid's documentation only for what the AdapTable docs and checks do not cover.
+AdapTable (`@adaptabletools/*`) is used in this project. Its Options, State shapes, API and AdapTableQL change between majors, so do not rely on recalled knowledge. Before writing or changing AdapTable code use the `adaptable-dev` skill; for first-time integration `adaptable-setup`; for a misbehaving running grid `adaptable-debug`; for version upgrades `adaptable-upgrade`. Validate State, expressions and setup with `npx -y @adaptabletools/adaptable-mcp@^1 check …` (or the `check_*` MCP tools when configured); read the docs for the installed version with `npx -y @adaptabletools/adaptable-mcp@^1 docs search "<topic>"`. The columnDefs, gridOptions and AG Grid modules of an AdapTable grid are covered by these skills too; consult the `ag-dev` / `ag-update` skills or AG Grid's documentation only for what the AdapTable docs and checks do not cover.
 <!-- END:adaptable-agent-rules -->

package/dist/skills/adaptable-dev/references/_shared/capabilities.md

@@ -29,7 +29,7 @@ Every capability of `@adaptabletools/adaptable-mcp` (response schema 1) has a CL
 
 ## Choosing a binding
 
-- Prefer the MCP tool when the harness has the `adaptable` MCP server configured. Otherwise run the CLI command as `npx -y @adaptabletools/adaptable-mcp@^0 <command> [options]`; add `--json` to read fields instead of Markdown.
+- Prefer the MCP tool when the harness has the `adaptable` MCP server configured. Otherwise run the CLI command as `npx -y @adaptabletools/adaptable-mcp@^1 <command> [options]`; add `--json` to read fields instead of Markdown.
 - If neither binding exists for what you need — the capability is not in this table, not in `adaptable --capabilities`, or not in the MCP tool list — say so and fall back to the docs (see `docs-protocol.md`). Never improvise the result a missing capability would have produced.
 - All bindings return the same envelope: `ok`, `data`, `issues`, `warnings`, and on failure `error { code, message, hint }`. CLI exit codes: `0` ok, `1` findings, `2` usage, `3` environment.
 - Skill scripts cannot reach the agent's MCP session: a script only ever runs the CLI. When the CLI is unavailable, the agent performs the fallback itself.

package/dist/skills/adaptable-dev/references/_shared/grounding.md

@@ -7,7 +7,7 @@ or diagnosing anything, establish what is actually installed.
 ## 1. Detect the project
 
 ```bash
-npx -y @adaptabletools/adaptable-mcp@^0 detect --json
+npx -y @adaptabletools/adaptable-mcp@^1 detect --json
 ```
 
 (or the `detect_environment` MCP tool when the `adaptable` MCP server is

package/dist/skills/adaptable-setup/SKILL.md

@@ -48,7 +48,7 @@ no obvious unique column. One round of questions, then proceed.
 ## Phase 3 — Shell (path C only)
 
 ```bash
-npx -y @adaptabletools/adaptable-mcp@^0 scaffold --dry-run --framework <framework> --out <dir> [--data <file> | --sample <file.json> | --source-url <url>]
+npx -y @adaptabletools/adaptable-mcp@^1 scaffold --dry-run --framework <framework> --out <dir> [--data <file> | --sample <file.json> | --source-url <url>]
 ```
 
 Pass the data source agreed in Phase 2 (without it the dry run previews the
@@ -72,7 +72,7 @@ re-run `detect` in the new folder.
 3. Migrate ColDef-owned layout and styling:
 
    ```bash
-   npx -y @adaptabletools/adaptable-mcp@^0 convert coldefs <columnDefs file>
+   npx -y @adaptabletools/adaptable-mcp@^1 convert coldefs <columnDefs file>
    ```
 
    It returns a Layout for the new Initial State, a `remove[]` list of
@@ -112,7 +112,7 @@ re-run `detect` in the new folder.
 ### Paths B/C — scaffold the overlay
 
 ```bash
-npx -y @adaptabletools/adaptable-mcp@^0 scaffold --dry-run --out <dir> [--data <file> | --sample <file.json> | --source-url <url>]
+npx -y @adaptabletools/adaptable-mcp@^1 scaffold --dry-run --out <dir> [--data <file> | --sample <file.json> | --source-url <url>]
 ```
 
 **Gate — columns and primary key.** **Show** the inferred columns (field,
@@ -145,7 +145,7 @@ confirmed columns (column ids and Scopes change; shapes come from the demo),
 and validate the merged Initial State:
 
 ```bash
-npx -y @adaptabletools/adaptable-mcp@^0 check state <adaptableOptions file> --columns <columnDefs file>
+npx -y @adaptabletools/adaptable-mcp@^1 check state <adaptableOptions file> --columns <columnDefs file>
 ```
 
 **Ask** which suggestions to include (default: none — a clean minimal grid

package/dist/skills/adaptable-setup/VERSION.md

@@ -1 +1 @@
-0.1.0
+1.0.0

package/dist/skills/adaptable-setup/references/_shared/agents-snippet.md

@@ -1,3 +1,3 @@
 <!-- BEGIN:adaptable-agent-rules -->
-AdapTable (`@adaptabletools/*`) is used in this project. Its Options, State shapes, API and AdapTableQL change between majors, so do not rely on recalled knowledge. Before writing or changing AdapTable code use the `adaptable-dev` skill; for first-time integration `adaptable-setup`; for a misbehaving running grid `adaptable-debug`; for version upgrades `adaptable-upgrade`. Validate State, expressions and setup with `npx -y @adaptabletools/adaptable-mcp@^0 check …` (or the `check_*` MCP tools when configured); read the docs for the installed version with `npx -y @adaptabletools/adaptable-mcp@^0 docs search "<topic>"`. The columnDefs, gridOptions and AG Grid modules of an AdapTable grid are covered by these skills too; consult the `ag-dev` / `ag-update` skills or AG Grid's documentation only for what the AdapTable docs and checks do not cover.
+AdapTable (`@adaptabletools/*`) is used in this project. Its Options, State shapes, API and AdapTableQL change between majors, so do not rely on recalled knowledge. Before writing or changing AdapTable code use the `adaptable-dev` skill; for first-time integration `adaptable-setup`; for a misbehaving running grid `adaptable-debug`; for version upgrades `adaptable-upgrade`. Validate State, expressions and setup with `npx -y @adaptabletools/adaptable-mcp@^1 check …` (or the `check_*` MCP tools when configured); read the docs for the installed version with `npx -y @adaptabletools/adaptable-mcp@^1 docs search "<topic>"`. The columnDefs, gridOptions and AG Grid modules of an AdapTable grid are covered by these skills too; consult the `ag-dev` / `ag-update` skills or AG Grid's documentation only for what the AdapTable docs and checks do not cover.
 <!-- END:adaptable-agent-rules -->

package/dist/skills/adaptable-setup/references/_shared/capabilities.md

@@ -29,7 +29,7 @@ Every capability of `@adaptabletools/adaptable-mcp` (response schema 1) has a CL
 
 ## Choosing a binding
 
-- Prefer the MCP tool when the harness has the `adaptable` MCP server configured. Otherwise run the CLI command as `npx -y @adaptabletools/adaptable-mcp@^0 <command> [options]`; add `--json` to read fields instead of Markdown.
+- Prefer the MCP tool when the harness has the `adaptable` MCP server configured. Otherwise run the CLI command as `npx -y @adaptabletools/adaptable-mcp@^1 <command> [options]`; add `--json` to read fields instead of Markdown.
 - If neither binding exists for what you need — the capability is not in this table, not in `adaptable --capabilities`, or not in the MCP tool list — say so and fall back to the docs (see `docs-protocol.md`). Never improvise the result a missing capability would have produced.
 - All bindings return the same envelope: `ok`, `data`, `issues`, `warnings`, and on failure `error { code, message, hint }`. CLI exit codes: `0` ok, `1` findings, `2` usage, `3` environment.
 - Skill scripts cannot reach the agent's MCP session: a script only ever runs the CLI. When the CLI is unavailable, the agent performs the fallback itself.

package/dist/skills/adaptable-setup/references/_shared/grounding.md

@@ -7,7 +7,7 @@ or diagnosing anything, establish what is actually installed.
 ## 1. Detect the project
 
 ```bash
-npx -y @adaptabletools/adaptable-mcp@^0 detect --json
+npx -y @adaptabletools/adaptable-mcp@^1 detect --json
 ```
 
 (or the `detect_environment` MCP tool when the `adaptable` MCP server is

package/dist/skills/adaptable-upgrade/SKILL.md

@@ -61,7 +61,7 @@ silently — a stale SCOPE from another target poisons every later phase.
 ### Phase 3 — Scope → `ADAPTABLE_UPGRADE_SCOPE.md`
 
 ```bash
-npx -y @adaptabletools/adaptable-mcp@^0 detect --all-projects --json
+npx -y @adaptabletools/adaptable-mcp@^1 detect --all-projects --json
 ```
 
 Record per project: path, framework and wrapper package, AdapTable range and
@@ -79,8 +79,8 @@ run against such a project.
 manifest reports:
 
 ```bash
-npx -y @adaptabletools/adaptable-mcp@^0 compat --adaptable <target>
-npx -y @adaptabletools/adaptable-mcp@^0 compat --adaptable <target> --ag-grid <installed AG Grid major>
+npx -y @adaptabletools/adaptable-mcp@^1 compat --adaptable <target>
+npx -y @adaptabletools/adaptable-mcp@^1 compat --adaptable <target> --ag-grid <installed AG Grid major>
 ```
 
 `compat` returns the target's AG Grid pairing, wrapper packages and
@@ -134,7 +134,7 @@ index) is the CLI's own chrome: read it, act on the warnings, leave it out
 of the plan.
 
 ```bash
-npx -y @adaptabletools/adaptable-mcp@^0 changes --from <current> --to <target> \
+npx -y @adaptabletools/adaptable-mcp@^1 changes --from <current> --to <target> \
   --repo <repository root> --projects <project folders from SCOPE> --with-docs
 ```
 
@@ -159,7 +159,7 @@ Then, for every file in each project's `initialStateLiterals`:
 
 ```bash
 mkdir -p ADAPTABLE_UPGRADE_STATE
-npx -y @adaptabletools/adaptable-mcp@^0 migrate state <project>/<file> --from <current> --to <target> \
+npx -y @adaptabletools/adaptable-mcp@^1 migrate state <project>/<file> --from <current> --to <target> \
   --kind initial --columns <project>/<columnDefs file> --out ADAPTABLE_UPGRADE_STATE/<project>--<file>.json \
   > ADAPTABLE_UPGRADE_STATE/<project>--<file>.md
 ```

package/dist/skills/adaptable-upgrade/VERSION.md

@@ -1 +1 @@
-0.1.0
+1.0.0

package/dist/skills/adaptable-upgrade/references/_shared/agents-snippet.md

@@ -1,3 +1,3 @@
 <!-- BEGIN:adaptable-agent-rules -->
-AdapTable (`@adaptabletools/*`) is used in this project. Its Options, State shapes, API and AdapTableQL change between majors, so do not rely on recalled knowledge. Before writing or changing AdapTable code use the `adaptable-dev` skill; for first-time integration `adaptable-setup`; for a misbehaving running grid `adaptable-debug`; for version upgrades `adaptable-upgrade`. Validate State, expressions and setup with `npx -y @adaptabletools/adaptable-mcp@^0 check …` (or the `check_*` MCP tools when configured); read the docs for the installed version with `npx -y @adaptabletools/adaptable-mcp@^0 docs search "<topic>"`. The columnDefs, gridOptions and AG Grid modules of an AdapTable grid are covered by these skills too; consult the `ag-dev` / `ag-update` skills or AG Grid's documentation only for what the AdapTable docs and checks do not cover.
+AdapTable (`@adaptabletools/*`) is used in this project. Its Options, State shapes, API and AdapTableQL change between majors, so do not rely on recalled knowledge. Before writing or changing AdapTable code use the `adaptable-dev` skill; for first-time integration `adaptable-setup`; for a misbehaving running grid `adaptable-debug`; for version upgrades `adaptable-upgrade`. Validate State, expressions and setup with `npx -y @adaptabletools/adaptable-mcp@^1 check …` (or the `check_*` MCP tools when configured); read the docs for the installed version with `npx -y @adaptabletools/adaptable-mcp@^1 docs search "<topic>"`. The columnDefs, gridOptions and AG Grid modules of an AdapTable grid are covered by these skills too; consult the `ag-dev` / `ag-update` skills or AG Grid's documentation only for what the AdapTable docs and checks do not cover.
 <!-- END:adaptable-agent-rules -->

package/dist/skills/adaptable-upgrade/references/_shared/capabilities.md

@@ -29,7 +29,7 @@ Every capability of `@adaptabletools/adaptable-mcp` (response schema 1) has a CL
 
 ## Choosing a binding
 
-- Prefer the MCP tool when the harness has the `adaptable` MCP server configured. Otherwise run the CLI command as `npx -y @adaptabletools/adaptable-mcp@^0 <command> [options]`; add `--json` to read fields instead of Markdown.
+- Prefer the MCP tool when the harness has the `adaptable` MCP server configured. Otherwise run the CLI command as `npx -y @adaptabletools/adaptable-mcp@^1 <command> [options]`; add `--json` to read fields instead of Markdown.
 - If neither binding exists for what you need — the capability is not in this table, not in `adaptable --capabilities`, or not in the MCP tool list — say so and fall back to the docs (see `docs-protocol.md`). Never improvise the result a missing capability would have produced.
 - All bindings return the same envelope: `ok`, `data`, `issues`, `warnings`, and on failure `error { code, message, hint }`. CLI exit codes: `0` ok, `1` findings, `2` usage, `3` environment.
 - Skill scripts cannot reach the agent's MCP session: a script only ever runs the CLI. When the CLI is unavailable, the agent performs the fallback itself.

package/dist/skills/adaptable-upgrade/references/_shared/grounding.md

@@ -7,7 +7,7 @@ or diagnosing anything, establish what is actually installed.
 ## 1. Detect the project
 
 ```bash
-npx -y @adaptabletools/adaptable-mcp@^0 detect --json
+npx -y @adaptabletools/adaptable-mcp@^1 detect --json
 ```
 
 (or the `detect_environment` MCP tool when the `adaptable` MCP server is

package/dist/skills/adaptable-upgrade/references/apply-order.md

@@ -68,7 +68,7 @@ say so in the report.
 payload, a test — are not reached by State migration. Rewrite each one:
 
 ```bash
-npx -y @adaptabletools/adaptable-mcp@^0 migrate expression "<expression>" --from <n> --to <m> --module <Module> --columns <columnDefs file>
+npx -y @adaptabletools/adaptable-mcp@^1 migrate expression "<expression>" --from <n> --to <m> --module <Module> --columns <columnDefs file>
 ```
 
 The output carries `original`, `migrated`, `changed` and, for targets 24
@@ -96,9 +96,9 @@ The validation loop applies (three rounds at most, then the remaining
 issues verbatim):
 
 ```bash
-npx -y @adaptabletools/adaptable-mcp@^0 check state <file with the literal> --major <target> --columns <columnDefs file>
-npx -y @adaptabletools/adaptable-mcp@^0 check expression "<rewritten string>" --module <Module> --columns <columnDefs file>
-npx -y @adaptabletools/adaptable-mcp@^0 check setup
+npx -y @adaptabletools/adaptable-mcp@^1 check state <file with the literal> --major <target> --columns <columnDefs file>
+npx -y @adaptabletools/adaptable-mcp@^1 check expression "<rewritten string>" --module <Module> --columns <columnDefs file>
+npx -y @adaptabletools/adaptable-mcp@^1 check setup
 ```
 
 - `check state` on every rewritten literal — the shape against the target

package/dist/skills/adaptable-upgrade/scripts/adaptable.mjs

@@ -11,7 +11,7 @@ import { spawnSync } from 'node:child_process';
 
 const windows = process.platform === 'win32';
 const override = process.env.ADAPTABLE_CLI?.trim();
-const [command, ...lead] = override ? override.split(/\s+/) : [windows ? 'npx.cmd' : 'npx', '-y', '@adaptabletools/adaptable-mcp@^0'];
+const [command, ...lead] = override ? override.split(/\s+/) : [windows ? 'npx.cmd' : 'npx', '-y', '@adaptabletools/adaptable-mcp@^1'];
 const result = spawnSync(command, [...lead, ...process.argv.slice(2)], {
   stdio: 'inherit',
   shell: windows,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@adaptabletools/adaptable-mcp",
-  "version": "0.1.0",
+  "version": "1.0.0",
   "description": "AdapTable CLI and MCP server for coding agents: version-matched docs, State and AdapTableQL checks, migration, scaffolding",
   "homepage": "https://www.adaptabletools.com/",
   "license": "contact sales@adaptabletools.com for details",