@adaptabletools/adaptable-mcp 0.1.0-canary.3 → 0.1.0

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

@@ -33,8 +33,11 @@ package and the environment minimums.
 
 **Gate — AG Grid edition and version.** AdapTable needs AG Grid Enterprise at
 the paired version. If `detect` shows AG Grid Community, or an AG Grid below
-the pairing: **ask** — upgrade AG Grid first (hand over to `ag-update` when it
-is installed) or stop. Do not install AdapTable onto an unpaired grid and hope.
+the pairing: **ask** — upgrade AG Grid first or stop. The upgrade bumps every
+`ag-grid-*` package to the pairing `compat` names (adding `ag-grid-enterprise`
+when only Community is installed); AG Grid's own breaking changes go through
+the AG Grid fallback (grounding). Do not install AdapTable onto an unpaired
+grid and hope.
 
 **Ask once, for everything this phase needs:** the AdapTable and AG Grid
 licence keys (or confirmation to use trial placeholders — keys go to the
@@ -45,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@canary scaffold --dry-run --framework <framework> --out <dir> [--data <file> | --sample <file.json> | --source-url <url>]
+npx -y @adaptabletools/adaptable-mcp@^0 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
@@ -69,7 +72,7 @@ re-run `detect` in the new folder.
 3. Migrate ColDef-owned layout and styling:
 
    ```bash
-   npx -y @adaptabletools/adaptable-mcp@canary convert coldefs <columnDefs file>
+   npx -y @adaptabletools/adaptable-mcp@^0 convert coldefs <columnDefs file>
    ```
 
    It returns a Layout for the new Initial State, a `remove[]` list of
@@ -80,21 +83,50 @@ re-run `detect` in the new folder.
 
    **Gate — ColDef migration.** **Ask** which Layout-owned properties to move
    (default: all — leaving them in the ColDef means the Layout and the ColDef
-   fight) and which candidates to re-express now (default: none; they keep
-   working and can move later with `adaptable-dev`). Apply the agreed edits,
-   then `check setup` and `check state` on the new Initial State.
+   fight) and which candidates to re-express now (default: every candidate
+   AdapTable can express — AdapTable objects persist in State, are editable at
+   run time and are seen by the rest of AdapTable; a ColDef function is none
+   of these). Before asking, map each candidate to its AdapTable object:
+
+   - `valueFormatter` → a Format Column `DisplayFormat` when the built-in
+     Number, Date or String formatter options reproduce it; otherwise a
+     `formatColumnOptions.customDisplayFormatters` entry referenced from the
+     Format Column's `CustomDisplayFormats`. One formatter shared by several
+     columns is one Format Column whose Scope lists those columns.
+   - `cellStyle` / `cellClassRules` → a Format Column `Style`, with a `Rule`
+     for the conditional cases.
+   - `valueGetter` → a Calculated Column when an AdapTableQL Expression can
+     compute the value.
+   - `cellRenderer` → a Styled Column (gradient, percent bar, sparkline,
+     badge, bullet chart, rating, range bar, icon) or an Action Column
+     (buttons).
+
+   Recommend keeping a candidate in the ColDef only when it has no AdapTable
+   equivalent (a `valueGetter` that needs JavaScript state an Expression
+   cannot reach, a bespoke renderer), and say why for each. Take every target
+   shape from `docs search`, not memory, and remove the ColDef property you
+   re-express — the ColDef and the AdapTable object would otherwise both
+   apply. Apply the agreed edits, then `check setup` and `check state` on the
+   new Initial State.
 
 ### Paths B/C — scaffold the overlay
 
 ```bash
-npx -y @adaptabletools/adaptable-mcp@canary scaffold --dry-run --out <dir> [--data <file> | --sample <file.json> | --source-url <url>]
+npx -y @adaptabletools/adaptable-mcp@^0 scaffold --dry-run --out <dir> [--data <file> | --sample <file.json> | --source-url <url>]
 ```
 
 **Gate — columns and primary key.** **Show** the inferred columns (field,
 type, nullability) and the primary-key choice from the dry run and **ask**
 the user to confirm or correct them — a wrong type or key here is baked into
-every file. Then run without `--dry-run` (add `--force` only for files the
-user has agreed to overwrite). The run writes `columnDefs.ts`, `rowData.ts`,
+every file. When source column names contain spaces, the dry run has already
+renamed them to camelCase fields (`Order Cost` → `orderCost`, the header
+stays `Order Cost`; each renamed column carries its `sourceField`): **show**
+the renames and **ask** whether to keep them (default: yes — recommended;
+kept as they are, the names are quoted in the row type and every row access,
+and the column id, `Order_Cost`, differs from the field) or to use the
+names as they are (`--field-names keep`). Then run without `--dry-run`
+with the agreed flags (add `--force` only for files the user has agreed to
+overwrite). The run writes `columnDefs.ts`, `rowData.ts`,
 `adaptableOptions.ts`, `gridOptions.ts`, `agGridModules.ts`, `licenses.ts` and
 `onAdaptableReady.ts` into the framework's source folder, pins the paired
 dependencies in `package.json`, and writes the `AGENTS.md` snippet when the
@@ -113,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@canary check state <adaptableOptions file> --columns <columnDefs file>
+npx -y @adaptabletools/adaptable-mcp@^0 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-canary.2
+0.1.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@canary check …` (or the `check_*` MCP tools when configured); read the docs for the installed version with `npx -y @adaptabletools/adaptable-mcp@canary docs search "<topic>"`. Pure AG Grid questions go to the `ag-dev` skill or AG Grid's documentation.
+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.
 <!-- 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@canary <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@^0 <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@canary detect --json
+npx -y @adaptabletools/adaptable-mcp@^0 detect --json
 ```
 
 (or the `detect_environment` MCP tool when the `adaptable` MCP server is
@@ -45,10 +45,26 @@ AdapTable N, not M". Pass `--docs-host https://<branch>.adaptabletools.com`
 (or set `ADAPTABLE_MCP_DOCS_HOST`) on every command from then on so each
 lookup below reads the pre-release docs.
 
-## 3. AG Grid siblings
+## 3. AG Grid: AdapTable first
 
-Note whether the `ag-dev` and `ag-update` skills are installed. Column
-definitions, AG Grid modules, row models, themes and the grid API belong to
-AG Grid: hand that work to `ag-dev`, and AG Grid version bumps to `ag-update`,
-rather than improvising either here. Everything that imports from
-`@adaptabletools/*` stays in these skills.
+AdapTable sets its own rules for the AG Grid side of the grid it runs on, so
+that work stays in these skills too. Column definitions follow the ownership
+matrix in adaptable-dev (`cellDataType` and column ids stay in the ColDef;
+layout, styling and derived values move to State); `gridOptions`, AG Grid
+modules and the AG Grid version pairing are covered by `check setup` and
+`compat`; runtime calls go through `adaptableApi` before `gridApi`. Use the
+AdapTable docs, demos and checks for all of it.
+
+Fall back to AG Grid only when one of these holds:
+
+- the AdapTable docs say nothing about an AG Grid-only property or API the
+  task needs;
+- a problem stays inside AG Grid: an AG Grid console error, or an AG Grid
+  type error after a version bump.
+
+Then use the `ag-dev` / `ag-update` skills when `detect` reports them
+installed, otherwise AG Grid's documentation (or the AG Grid MCP server when
+it is configured). Whatever comes back goes through `check setup` /
+`check state` like any other change, and AdapTable ownership wins over AG
+Grid guidance: a suggested ColDef `hide`, `pinned` or `cellStyle` becomes a
+Layout or a Format Column instead.

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@canary detect --all-projects --json
+npx -y @adaptabletools/adaptable-mcp@^0 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@canary compat --adaptable <target>
-npx -y @adaptabletools/adaptable-mcp@canary compat --adaptable <target> --ag-grid <installed AG Grid major>
+npx -y @adaptabletools/adaptable-mcp@^0 compat --adaptable <target>
+npx -y @adaptabletools/adaptable-mcp@^0 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@canary changes --from <current> --to <target> \
+npx -y @adaptabletools/adaptable-mcp@^0 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@canary migrate state <project>/<file> --from <current> --to <target> \
+npx -y @adaptabletools/adaptable-mcp@^0 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-canary.2
+0.1.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@canary check …` (or the `check_*` MCP tools when configured); read the docs for the installed version with `npx -y @adaptabletools/adaptable-mcp@canary docs search "<topic>"`. Pure AG Grid questions go to the `ag-dev` skill or AG Grid's documentation.
+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.
 <!-- 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@canary <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@^0 <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@canary detect --json
+npx -y @adaptabletools/adaptable-mcp@^0 detect --json
 ```
 
 (or the `detect_environment` MCP tool when the `adaptable` MCP server is
@@ -45,10 +45,26 @@ AdapTable N, not M". Pass `--docs-host https://<branch>.adaptabletools.com`
 (or set `ADAPTABLE_MCP_DOCS_HOST`) on every command from then on so each
 lookup below reads the pre-release docs.
 
-## 3. AG Grid siblings
+## 3. AG Grid: AdapTable first
 
-Note whether the `ag-dev` and `ag-update` skills are installed. Column
-definitions, AG Grid modules, row models, themes and the grid API belong to
-AG Grid: hand that work to `ag-dev`, and AG Grid version bumps to `ag-update`,
-rather than improvising either here. Everything that imports from
-`@adaptabletools/*` stays in these skills.
+AdapTable sets its own rules for the AG Grid side of the grid it runs on, so
+that work stays in these skills too. Column definitions follow the ownership
+matrix in adaptable-dev (`cellDataType` and column ids stay in the ColDef;
+layout, styling and derived values move to State); `gridOptions`, AG Grid
+modules and the AG Grid version pairing are covered by `check setup` and
+`compat`; runtime calls go through `adaptableApi` before `gridApi`. Use the
+AdapTable docs, demos and checks for all of it.
+
+Fall back to AG Grid only when one of these holds:
+
+- the AdapTable docs say nothing about an AG Grid-only property or API the
+  task needs;
+- a problem stays inside AG Grid: an AG Grid console error, or an AG Grid
+  type error after a version bump.
+
+Then use the `ag-dev` / `ag-update` skills when `detect` reports them
+installed, otherwise AG Grid's documentation (or the AG Grid MCP server when
+it is configured). Whatever comes back goes through `check setup` /
+`check state` like any other change, and AdapTable ownership wins over AG
+Grid guidance: a suggested ColDef `hide`, `pinned` or `cellStyle` becomes a
+Layout or a Format Column instead.

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

@@ -16,12 +16,10 @@ files are not edited in apply mode.
 ## 1. Packages
 
 1. **AG Grid**, per SCOPE's `## AG Grid plan`:
-   - *ag-update*: apply `AG_UPDATE_*.md` first, with that skill. AdapTable
-     work waits until AG Grid builds.
-   - *bump only*: set every `ag-grid-*` package (and `ag-charts-*` when
-     present) to the version SCOPE names, same version for all of them.
-     AG Grid's own breaking changes are the user's; name the guide, do not
-     run AG Grid's codemod from here.
+   - *bump in this plan*: set every `ag-grid-*` package (and `ag-charts-*`
+     when present) to the version SCOPE names, same version for all of them.
+     Do not run AG Grid's codemod from here; AG Grid's own breaking changes
+     are handled in step 4.
    - *already handled*: check `package.json` carries the pairing; if it does
      not, stop and tell the user — nothing below works against a mismatched
      AG Grid.
@@ -70,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@canary migrate expression "<expression>" --from <n> --to <m> --module <Module> --columns <columnDefs file>
+npx -y @adaptabletools/adaptable-mcp@^0 migrate expression "<expression>" --from <n> --to <m> --module <Module> --columns <columnDefs file>
 ```
 
 The output carries `original`, `migrated`, `changed` and, for targets 24
@@ -98,9 +96,9 @@ The validation loop applies (three rounds at most, then the remaining
 issues verbatim):
 
 ```bash
-npx -y @adaptabletools/adaptable-mcp@canary check state <file with the literal> --major <target> --columns <columnDefs file>
-npx -y @adaptabletools/adaptable-mcp@canary check expression "<rewritten string>" --module <Module> --columns <columnDefs file>
-npx -y @adaptabletools/adaptable-mcp@canary check setup
+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
 ```
 
 - `check state` on every rewritten literal — the shape against the target
@@ -113,7 +111,11 @@ npx -y @adaptabletools/adaptable-mcp@canary check setup
   the packages, AG Grid modules, wrapper wiring, ColDef ownership.
 - Then the project's own type-check and build. Type errors at this point are
   usually a record applied to one match and not another: search the plan
-  for the identifier before reading the codebase.
+  for the identifier before reading the codebase. An error the plan does not
+  explain and that names an AG Grid identifier (a ColDef or `gridOptions`
+  property, a grid API call, an AG Grid type) is one of AG Grid's own
+  breaking changes: resolve it through the AG Grid fallback (grounding) and
+  list it in the report.
 
 ## 5. Run and read the console
 

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@canary'];
+const [command, ...lead] = override ? override.split(/\s+/) : [windows ? 'npx.cmd' : 'npx', '-y', '@adaptabletools/adaptable-mcp@^0'];
 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-canary.3",
+  "version": "0.1.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",