diff --git a/.changeset/activity-plugin-file-module-type.md b/.changeset/activity-plugin-file-module-type.md deleted file mode 100644 index 97f3dad1..00000000 --- a/.changeset/activity-plugin-file-module-type.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -"@skill-map/cli": patch -"@skill-map/spec": patch ---- - -`sm activity install` for `plugin-file` providers (opencode-style) now writes an ESM-pinning `package.json` (`{ "type": "module" }`) next to the generated in-process plugin so the vendor runtime loads its `export`-based `.js` without a `MODULE_TYPELESS_PACKAGE_JSON` warning (or a hard parse error under a CommonJS host). Written only when the plugin dir has no `package.json` (never clobbering the vendor's shared dir); uninstall removes it only when it is exactly ours. - -## User-facing - -`sm activity install` now drops a small package.json next to a plugin-file provider's hook so your tool loads it without a module-type warning. It won't overwrite a package.json already in that folder. diff --git a/.changeset/bare-sm-init-offer.md b/.changeset/bare-sm-init-offer.md deleted file mode 100644 index 222eae22..00000000 --- a/.changeset/bare-sm-init-offer.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -"@skill-map/cli": minor -"@skill-map/spec": minor ---- - -Bare `sm` (no arguments) in a folder that has files but no `.skill-map/` project now offers to bootstrap it: on an interactive terminal it shows a yes/no confirm (default yes) that runs `sm init` and, on success, continues into the Web UI server (`sm serve`). Declining, a non-interactive stdin, or an empty folder keep the previous behavior (the getting-started menu or the one-line hint plus exit 2). - -## User-facing - -Run `sm` in a folder that already has files but no project and it now offers to set skill-map up for you; accept and it initializes, scans, and opens the map. diff --git a/.changeset/inspector-activity-live-refresh.md b/.changeset/inspector-activity-live-refresh.md deleted file mode 100644 index 5e0ef999..00000000 --- a/.changeset/inspector-activity-live-refresh.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -"@skill-map/cli": patch ---- - -The inspector's Activity section now refreshes live off the `node.activity` / `agent.spawn` streams (debounced), so a node's recent-execution rows, counters, and spawn threads update the moment the assistant runs, instead of waiting for the next watcher re-scan. - -## User-facing - -The inspector's Activity panel now updates live while your assistant runs: recent executions, counters, and spawn threads refresh as they happen, not only on the next scan. diff --git a/.changeset/mcp-config-discovery-live-invocation-and-server.md b/.changeset/mcp-config-discovery-live-invocation-and-server.md deleted file mode 100644 index bfae111a..00000000 --- a/.changeset/mcp-config-discovery-live-invocation-and-server.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -"@skill-map/spec": minor -"@skill-map/cli": minor ---- - -MCP support lands in three parts. A declarative `mcpConfig` Provider capability and a shared kernel MCP parser materialise `mcp://` nodes from a project's config files, canonical over the consumer-side `core/mcp-tools` emission. Live MCP tool calls light the same node: `node.activity` gains `detail`/`access` and the recent ring records typed `mcp`/`read` entries with `caller`/`target`. A read-only MCP server (`spec/mcp-server.md`) is specified on `sm serve` at `/mcp` (off by default). - -## User-facing - -The map now shows the MCP servers your project configures and lights them live when an agent calls a tool. The inspector logs each MCP tool call and file read with who ran it. `sm serve` gains an opt-in read-only MCP server at `/mcp` (spec only so far). diff --git a/.changeset/plugin-package-json-scaffold.md b/.changeset/plugin-package-json-scaffold.md deleted file mode 100644 index 15e36e2b..00000000 --- a/.changeset/plugin-package-json-scaffold.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -"@skill-map/cli": patch -"@skill-map/spec": patch ---- - -`sm plugins create` now emits a root `package.json` (`{ "private": true, "type": "module" }`) so Node loads a plugin's ESM `.js` extensions without the `MODULE_TYPELESS_PACKAGE_JSON` warning, and `sm plugins upgrade []` backfills it on older plugins (adding a missing `type` without clobbering a non-module one). The plugin author guide documents the module-type requirement and the Provider `activity` capability, and the quickstart adds the `sm plugins trust` step. - -## User-facing - -New drop-in plugins now ship a package.json so Node loads them without a module-type warning. Run `sm plugins upgrade` to add it to plugins you created earlier. The plugin docs now cover the trust step and how a provider wires live activity. diff --git a/.changeset/plugin-trust-restart-warning-and-sm-wording.md b/.changeset/plugin-trust-restart-warning-and-sm-wording.md deleted file mode 100644 index 4e49c9dc..00000000 --- a/.changeset/plugin-trust-restart-warning-and-sm-wording.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -"@skill-map/cli": patch ---- - -Enabling the project plugin-trust toggle in Settings now surfaces a restart warning (a `p-message` banner under the row plus a note on its own line in the trust confirm dialog), the workspace files-follow toggle uses a clearer swap icon, and user-facing strings that pointed at `sm serve` now use the bare `sm` alias across settings, inspector, server advisories, activity hints, and the `sm example` next-steps. - -## User-facing - -Turning on "Trust plugins this project enables" in Settings now reminds you to restart so the change takes effect, and hints across the app and CLI now show the bare `sm` command instead of `sm serve`. diff --git a/.changeset/read-only-mcp-server.md b/.changeset/read-only-mcp-server.md deleted file mode 100644 index 1fbc54cc..00000000 --- a/.changeset/read-only-mcp-server.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -"@skill-map/cli": minor -"@skill-map/spec": minor ---- - -Implements the read-only MCP server for `sm serve`: an opt-in Streamable HTTP endpoint at `/mcp` (stateful sessions) exposing four query tools (query_graph, get_node, list_issues, get_branch) and skillmap:// resources for graph, issues, activity, and per-node views, with live `notifications/resources/updated` off the scan broadcaster. Enabled via `--mcp` / `--no-mcp` or the project-local `mcp.server.enabled` (off by default, toggleable from Settings > Project), behind the loopback-Origin gate. - -## User-facing - -`sm serve --mcp`, `mcp.server.enabled`, or a Settings > Project toggle now exposes an opt-in, read-only Model Context Protocol server at `/mcp`, so an MCP host like Claude Code can query your project graph as tools and read it as resources, with live updates as the map changes. diff --git a/.changeset/remove-plugin-trust-project-enabled.md b/.changeset/remove-plugin-trust-project-enabled.md deleted file mode 100644 index 5314f0b9..00000000 --- a/.changeset/remove-plugin-trust-project-enabled.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -"@skill-map/spec": minor -"@skill-map/cli": minor ---- - -The blanket `pluginTrust.projectEnabled` opt-in (the config key plus its Settings toggle that trusted every plugin the project enables) is removed. Plugin import trust is now per-plugin only: `sm plugins trust ` / the Settings Trust button, or `sm plugins trust --all` to trust every discovered drop-in at once. A single config toggle can no longer widen the local code-execution surface. Settings > Plugins also gains a consolidated restart notice when a drop-in changes trust or enable state. - -## User-facing - -The "Trust plugins this project enables" setting is gone. Trust plugins one by one (the Trust button, or `sm plugins trust `), or run `sm plugins trust --all` to trust them all. Settings now shows a clear "restart to apply" notice after a plugin trust or enable change. diff --git a/CHANGELOG.md b/CHANGELOG.md index 949f3572..bf65ac9e 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -6,6 +6,33 @@ > Forward-looking plan: [`ROADMAP.md`](./ROADMAP.md).
+0.86.0 · 2026-07-10 + +### CLI Minor +- Bare `sm` (no arguments) in a folder that has files but no `.skill-map/` project now offers to bootstrap it: on an interactive terminal it shows a yes/no confirm (default yes) that runs `sm init` and, on success, continues into the Web UI server (`sm serve`). Declining, a non-interactive stdin, or an empty folder keep the previous behavior (the getting-started menu or the one-line hint plus exit 2). +- MCP support lands in three parts. A declarative `mcpConfig` Provider capability and a shared kernel MCP parser materialise `mcp://` nodes from a project's config files, canonical over the consumer-side `core/mcp-tools` emission. Live MCP tool calls light the same node: `node.activity` gains `detail`/`access` and the recent ring records typed `mcp`/`read` entries with `caller`/`target`. A read-only MCP server (`spec/mcp-server.md`) is specified on `sm serve` at `/mcp` (off by default). +- Implements the read-only MCP server for `sm serve`: an opt-in Streamable HTTP endpoint at `/mcp` (stateful sessions) exposing four query tools (query_graph, get_node, list_issues, get_branch) and skillmap:// resources for graph, issues, activity, and per-node views, with live `notifications/resources/updated` off the scan broadcaster. Enabled via `--mcp` / `--no-mcp` or the project-local `mcp.server.enabled` (off by default, toggleable from Settings > Project), behind the loopback-Origin gate. +- The blanket `pluginTrust.projectEnabled` opt-in (the config key plus its Settings toggle that trusted every plugin the project enables) is removed. Plugin import trust is now per-plugin only: `sm plugins trust ` / the Settings Trust button, or `sm plugins trust --all` to trust every discovered drop-in at once. A single config toggle can no longer widen the local code-execution surface. Settings > Plugins also gains a consolidated restart notice when a drop-in changes trust or enable state. + +### CLI Patch +- `sm activity install` for `plugin-file` providers (opencode-style) now writes an ESM-pinning `package.json` (`{ "type": "module" }`) next to the generated in-process plugin so the vendor runtime loads its `export`-based `.js` without a `MODULE_TYPELESS_PACKAGE_JSON` warning (or a hard parse error under a CommonJS host). Written only when the plugin dir has no `package.json` (never clobbering the vendor's shared dir); uninstall removes it only when it is exactly ours. +- The inspector's Activity section now refreshes live off the `node.activity` / `agent.spawn` streams (debounced), so a node's recent-execution rows, counters, and spawn threads update the moment the assistant runs, instead of waiting for the next watcher re-scan. +- `sm plugins create` now emits a root `package.json` (`{ "private": true, "type": "module" }`) so Node loads a plugin's ESM `.js` extensions without the `MODULE_TYPELESS_PACKAGE_JSON` warning, and `sm plugins upgrade []` backfills it on older plugins (adding a missing `type` without clobbering a non-module one). The plugin author guide documents the module-type requirement and the Provider `activity` capability, and the quickstart adds the `sm plugins trust` step. +- Enabling the project plugin-trust toggle in Settings now surfaces a restart warning (a `p-message` banner under the row plus a note on its own line in the trust confirm dialog), the workspace files-follow toggle uses a clearer swap icon, and user-facing strings that pointed at `sm serve` now use the bare `sm` alias across settings, inspector, server advisories, activity hints, and the `sm example` next-steps. + +### Spec Minor (0.78.0) +- Bare `sm` (no arguments) in a folder that has files but no `.skill-map/` project now offers to bootstrap it: on an interactive terminal it shows a yes/no confirm (default yes) that runs `sm init` and, on success, continues into the Web UI server (`sm serve`). Declining, a non-interactive stdin, or an empty folder keep the previous behavior (the getting-started menu or the one-line hint plus exit 2). +- MCP support lands in three parts. A declarative `mcpConfig` Provider capability and a shared kernel MCP parser materialise `mcp://` nodes from a project's config files, canonical over the consumer-side `core/mcp-tools` emission. Live MCP tool calls light the same node: `node.activity` gains `detail`/`access` and the recent ring records typed `mcp`/`read` entries with `caller`/`target`. A read-only MCP server (`spec/mcp-server.md`) is specified on `sm serve` at `/mcp` (off by default). +- Implements the read-only MCP server for `sm serve`: an opt-in Streamable HTTP endpoint at `/mcp` (stateful sessions) exposing four query tools (query_graph, get_node, list_issues, get_branch) and skillmap:// resources for graph, issues, activity, and per-node views, with live `notifications/resources/updated` off the scan broadcaster. Enabled via `--mcp` / `--no-mcp` or the project-local `mcp.server.enabled` (off by default, toggleable from Settings > Project), behind the loopback-Origin gate. +- The blanket `pluginTrust.projectEnabled` opt-in (the config key plus its Settings toggle that trusted every plugin the project enables) is removed. Plugin import trust is now per-plugin only: `sm plugins trust ` / the Settings Trust button, or `sm plugins trust --all` to trust every discovered drop-in at once. A single config toggle can no longer widen the local code-execution surface. Settings > Plugins also gains a consolidated restart notice when a drop-in changes trust or enable state. + +### Spec Patch (0.78.0) +- `sm activity install` for `plugin-file` providers (opencode-style) now writes an ESM-pinning `package.json` (`{ "type": "module" }`) next to the generated in-process plugin so the vendor runtime loads its `export`-based `.js` without a `MODULE_TYPELESS_PACKAGE_JSON` warning (or a hard parse error under a CommonJS host). Written only when the plugin dir has no `package.json` (never clobbering the vendor's shared dir); uninstall removes it only when it is exactly ours. +- `sm plugins create` now emits a root `package.json` (`{ "private": true, "type": "module" }`) so Node loads a plugin's ESM `.js` extensions without the `MODULE_TYPELESS_PACKAGE_JSON` warning, and `sm plugins upgrade []` backfills it on older plugins (adding a missing `type` without clobbering a non-module one). The plugin author guide documents the module-type requirement and the Provider `activity` capability, and the quickstart adds the `sm plugins trust` step. + +
+ +
0.85.0 · 2026-07-08 ### CLI Minor diff --git a/spec/CHANGELOG.md b/spec/CHANGELOG.md index b6c8ca6a..549d4319 100644 --- a/spec/CHANGELOG.md +++ b/spec/CHANGELOG.md @@ -1,5 +1,47 @@ # Spec changelog +## 0.78.0 + +### Minor Changes + +- Bare `sm` (no arguments) in a folder that has files but no `.skill-map/` project now offers to bootstrap it: on an interactive terminal it shows a yes/no confirm (default yes) that runs `sm init` and, on success, continues into the Web UI server (`sm serve`). Declining, a non-interactive stdin, or an empty folder keep the previous behavior (the getting-started menu or the one-line hint plus exit 2). + + ## User-facing + + Run `sm` in a folder that already has files but no project and it now offers to set skill-map up for you; accept and it initializes, scans, and opens the map. + +- MCP support lands in three parts. A declarative `mcpConfig` Provider capability and a shared kernel MCP parser materialise `mcp://` nodes from a project's config files, canonical over the consumer-side `core/mcp-tools` emission. Live MCP tool calls light the same node: `node.activity` gains `detail`/`access` and the recent ring records typed `mcp`/`read` entries with `caller`/`target`. A read-only MCP server (`spec/mcp-server.md`) is specified on `sm serve` at `/mcp` (off by default). + + ## User-facing + + The map now shows the MCP servers your project configures and lights them live when an agent calls a tool. The inspector logs each MCP tool call and file read with who ran it. `sm serve` gains an opt-in read-only MCP server at `/mcp` (spec only so far). + +- Implements the read-only MCP server for `sm serve`: an opt-in Streamable HTTP endpoint at `/mcp` (stateful sessions) exposing four query tools (query_graph, get_node, list_issues, get_branch) and skillmap:// resources for graph, issues, activity, and per-node views, with live `notifications/resources/updated` off the scan broadcaster. Enabled via `--mcp` / `--no-mcp` or the project-local `mcp.server.enabled` (off by default, toggleable from Settings > Project), behind the loopback-Origin gate. + + ## User-facing + + `sm serve --mcp`, `mcp.server.enabled`, or a Settings > Project toggle now exposes an opt-in, read-only Model Context Protocol server at `/mcp`, so an MCP host like Claude Code can query your project graph as tools and read it as resources, with live updates as the map changes. + +- The blanket `pluginTrust.projectEnabled` opt-in (the config key plus its Settings toggle that trusted every plugin the project enables) is removed. Plugin import trust is now per-plugin only: `sm plugins trust ` / the Settings Trust button, or `sm plugins trust --all` to trust every discovered drop-in at once. A single config toggle can no longer widen the local code-execution surface. Settings > Plugins also gains a consolidated restart notice when a drop-in changes trust or enable state. + + ## User-facing + + The "Trust plugins this project enables" setting is gone. Trust plugins one by one (the Trust button, or `sm plugins trust `), or run `sm plugins trust --all` to trust them all. Settings now shows a clear "restart to apply" notice after a plugin trust or enable change. + +### Patch Changes + +- `sm activity install` for `plugin-file` providers (opencode-style) now writes an ESM-pinning `package.json` (`{ "type": "module" }`) next to the generated in-process plugin so the vendor runtime loads its `export`-based `.js` without a `MODULE_TYPELESS_PACKAGE_JSON` warning (or a hard parse error under a CommonJS host). Written only when the plugin dir has no `package.json` (never clobbering the vendor's shared dir); uninstall removes it only when it is exactly ours. + + ## User-facing + + `sm activity install` now drops a small package.json next to a plugin-file provider's hook so your tool loads it without a module-type warning. It won't overwrite a package.json already in that folder. + +- `sm plugins create` now emits a root `package.json` (`{ "private": true, "type": "module" }`) so Node loads a plugin's ESM `.js` extensions without the `MODULE_TYPELESS_PACKAGE_JSON` warning, and `sm plugins upgrade []` backfills it on older plugins (adding a missing `type` without clobbering a non-module one). The plugin author guide documents the module-type requirement and the Provider `activity` capability, and the quickstart adds the `sm plugins trust` step. + + ## User-facing + + New drop-in plugins now ship a package.json so Node loads them without a module-type warning. Run `sm plugins upgrade` to add it to plugins you created earlier. The plugin docs now cover the trust step and how a provider wires live activity. + ## 0.77.0 ### Minor Changes diff --git a/spec/index.json b/spec/index.json index bcdd03ef..9c257ff6 100644 --- a/spec/index.json +++ b/spec/index.json @@ -178,11 +178,11 @@ } ] }, - "specPackageVersion": "0.77.0", + "specPackageVersion": "0.78.0", "integrity": { "algorithm": "sha256", "files": { - "CHANGELOG.md": "c02d452b261734585c6e349d7a99bf6b4c0cf8c4ef772a6668cad68f1dd7ee70", + "CHANGELOG.md": "ea7b4fe3d6407b2921d6c8860a92ad95e0e3e3cd8f4dee910dd358395fcf4996", "README.md": "a790cd010b46d47883d1f37e3893cea9d7aa69ec4750c0202e6a0c99991e7980", "architecture.md": "3806fbdc45c8e7da0ebec1b50b6893f185e151f66959812798beccf862463fd9", "cli-contract.md": "d97fc659ac8e40a97a63ca6a0b373487bc25992f52ebcaa1a37466640174c2b8", diff --git a/spec/package.json b/spec/package.json index 58408440..20b2ce91 100644 --- a/spec/package.json +++ b/spec/package.json @@ -1,6 +1,6 @@ { "name": "@skill-map/spec", - "version": "0.77.0", + "version": "0.78.0", "description": "JSON Schemas, prose contracts, and conformance suite for the skill-map specification.", "license": "MIT", "type": "module", diff --git a/src/CHANGELOG.md b/src/CHANGELOG.md index 0a7aaf20..2130f242 100644 --- a/src/CHANGELOG.md +++ b/src/CHANGELOG.md @@ -1,5 +1,59 @@ # skill-map +## 0.86.0 + +### Minor Changes + +- Bare `sm` (no arguments) in a folder that has files but no `.skill-map/` project now offers to bootstrap it: on an interactive terminal it shows a yes/no confirm (default yes) that runs `sm init` and, on success, continues into the Web UI server (`sm serve`). Declining, a non-interactive stdin, or an empty folder keep the previous behavior (the getting-started menu or the one-line hint plus exit 2). + + ## User-facing + + Run `sm` in a folder that already has files but no project and it now offers to set skill-map up for you; accept and it initializes, scans, and opens the map. + +- MCP support lands in three parts. A declarative `mcpConfig` Provider capability and a shared kernel MCP parser materialise `mcp://` nodes from a project's config files, canonical over the consumer-side `core/mcp-tools` emission. Live MCP tool calls light the same node: `node.activity` gains `detail`/`access` and the recent ring records typed `mcp`/`read` entries with `caller`/`target`. A read-only MCP server (`spec/mcp-server.md`) is specified on `sm serve` at `/mcp` (off by default). + + ## User-facing + + The map now shows the MCP servers your project configures and lights them live when an agent calls a tool. The inspector logs each MCP tool call and file read with who ran it. `sm serve` gains an opt-in read-only MCP server at `/mcp` (spec only so far). + +- Implements the read-only MCP server for `sm serve`: an opt-in Streamable HTTP endpoint at `/mcp` (stateful sessions) exposing four query tools (query_graph, get_node, list_issues, get_branch) and skillmap:// resources for graph, issues, activity, and per-node views, with live `notifications/resources/updated` off the scan broadcaster. Enabled via `--mcp` / `--no-mcp` or the project-local `mcp.server.enabled` (off by default, toggleable from Settings > Project), behind the loopback-Origin gate. + + ## User-facing + + `sm serve --mcp`, `mcp.server.enabled`, or a Settings > Project toggle now exposes an opt-in, read-only Model Context Protocol server at `/mcp`, so an MCP host like Claude Code can query your project graph as tools and read it as resources, with live updates as the map changes. + +- The blanket `pluginTrust.projectEnabled` opt-in (the config key plus its Settings toggle that trusted every plugin the project enables) is removed. Plugin import trust is now per-plugin only: `sm plugins trust ` / the Settings Trust button, or `sm plugins trust --all` to trust every discovered drop-in at once. A single config toggle can no longer widen the local code-execution surface. Settings > Plugins also gains a consolidated restart notice when a drop-in changes trust or enable state. + + ## User-facing + + The "Trust plugins this project enables" setting is gone. Trust plugins one by one (the Trust button, or `sm plugins trust `), or run `sm plugins trust --all` to trust them all. Settings now shows a clear "restart to apply" notice after a plugin trust or enable change. + +### Patch Changes + +- `sm activity install` for `plugin-file` providers (opencode-style) now writes an ESM-pinning `package.json` (`{ "type": "module" }`) next to the generated in-process plugin so the vendor runtime loads its `export`-based `.js` without a `MODULE_TYPELESS_PACKAGE_JSON` warning (or a hard parse error under a CommonJS host). Written only when the plugin dir has no `package.json` (never clobbering the vendor's shared dir); uninstall removes it only when it is exactly ours. + + ## User-facing + + `sm activity install` now drops a small package.json next to a plugin-file provider's hook so your tool loads it without a module-type warning. It won't overwrite a package.json already in that folder. + +- The inspector's Activity section now refreshes live off the `node.activity` / `agent.spawn` streams (debounced), so a node's recent-execution rows, counters, and spawn threads update the moment the assistant runs, instead of waiting for the next watcher re-scan. + + ## User-facing + + The inspector's Activity panel now updates live while your assistant runs: recent executions, counters, and spawn threads refresh as they happen, not only on the next scan. + +- `sm plugins create` now emits a root `package.json` (`{ "private": true, "type": "module" }`) so Node loads a plugin's ESM `.js` extensions without the `MODULE_TYPELESS_PACKAGE_JSON` warning, and `sm plugins upgrade []` backfills it on older plugins (adding a missing `type` without clobbering a non-module one). The plugin author guide documents the module-type requirement and the Provider `activity` capability, and the quickstart adds the `sm plugins trust` step. + + ## User-facing + + New drop-in plugins now ship a package.json so Node loads them without a module-type warning. Run `sm plugins upgrade` to add it to plugins you created earlier. The plugin docs now cover the trust step and how a provider wires live activity. + +- Enabling the project plugin-trust toggle in Settings now surfaces a restart warning (a `p-message` banner under the row plus a note on its own line in the trust confirm dialog), the workspace files-follow toggle uses a clearer swap icon, and user-facing strings that pointed at `sm serve` now use the bare `sm` alias across settings, inspector, server advisories, activity hints, and the `sm example` next-steps. + + ## User-facing + + Turning on "Trust plugins this project enables" in Settings now reminds you to restart so the change takes effect, and hints across the app and CLI now show the bare `sm` command instead of `sm serve`. + ## 0.85.0 ### Minor Changes diff --git a/src/package.json b/src/package.json index 391d928f..885c1b6f 100644 --- a/src/package.json +++ b/src/package.json @@ -1,6 +1,6 @@ { "name": "@skill-map/cli", - "version": "0.85.0", + "version": "0.86.0", "description": "skill-map reference implementation: kernel + CLI + adapters.", "license": "MIT", "type": "module", diff --git a/ui/src/data/user-changelog.json b/ui/src/data/user-changelog.json index 7a2120cd..a896aa40 100644 --- a/ui/src/data/user-changelog.json +++ b/ui/src/data/user-changelog.json @@ -1,6 +1,67 @@ { "schemaVersion": 1, "entries": [ + { + "version": "0.86.0", + "date": "2026-07-10", + "kind": "user-facing", + "highlights": [ + { + "body": "`sm activity install` now drops a small package.json next to a plugin-file provider's hook so your tool loads it without a module-type warning. It won't overwrite a package.json already in that folder.", + "packages": [ + "@skill-map/cli", + "@skill-map/spec" + ] + }, + { + "body": "Run `sm` in a folder that already has files but no project and it now offers to set skill-map up for you; accept and it initializes, scans, and opens the map.", + "packages": [ + "@skill-map/cli", + "@skill-map/spec" + ] + }, + { + "body": "The inspector's Activity panel now updates live while your assistant runs: recent executions, counters, and spawn threads refresh as they happen, not only on the next scan.", + "packages": [ + "@skill-map/cli" + ] + }, + { + "body": "The map now shows the MCP servers your project configures and lights them live when an agent calls a tool. The inspector logs each MCP tool call and file read with who ran it. `sm serve` gains an opt-in read-only MCP server at `/mcp` (spec only so far).", + "packages": [ + "@skill-map/cli", + "@skill-map/spec" + ] + }, + { + "body": "New drop-in plugins now ship a package.json so Node loads them without a module-type warning. Run `sm plugins upgrade` to add it to plugins you created earlier. The plugin docs now cover the trust step and how a provider wires live activity.", + "packages": [ + "@skill-map/cli", + "@skill-map/spec" + ] + }, + { + "body": "Turning on \"Trust plugins this project enables\" in Settings now reminds you to restart so the change takes effect, and hints across the app and CLI now show the bare `sm` command instead of `sm serve`.", + "packages": [ + "@skill-map/cli" + ] + }, + { + "body": "`sm serve --mcp`, `mcp.server.enabled`, or a Settings > Project toggle now exposes an opt-in, read-only Model Context Protocol server at `/mcp`, so an MCP host like Claude Code can query your project graph as tools and read it as resources, with live updates as the map changes.", + "packages": [ + "@skill-map/cli", + "@skill-map/spec" + ] + }, + { + "body": "The \"Trust plugins this project enables\" setting is gone. Trust plugins one by one (the Trust button, or `sm plugins trust `), or run `sm plugins trust --all` to trust them all. Settings now shows a clear \"restart to apply\" notice after a plugin trust or enable change.", + "packages": [ + "@skill-map/cli", + "@skill-map/spec" + ] + } + ] + }, { "version": "0.85.0", "date": "2026-07-08",