chore: version packages

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@skill-map/spec@0.49.0

Minor Changes

• Inspector action buttons are now self-projected by the dispatching Action instead of a sibling projector Analyzer: an Action may declare a ui button plus an optional deterministic scan-time project(ctx) (read-only graph) that emits its own inspector.action.button per node. The pure projector analyzers core/supersede and core/tags were removed and core/annotation-stale trimmed to its badge + issue (the Bump button moved to core/node-bump).

  User-facing

  No change to how the inspector behaves: the Supersede, Edit tags, and Bump buttons look and work exactly as before, they are just now produced by the action they trigger rather than a separate analyzer.

• Extensions declaring stability: 'deprecated' now also ship DISABLED by default, joining experimental in the ships-disabled set: a deprecated extension does not run or register until the operator opts in (sm plugins enable <plugin>/<ext>, the Settings toggle, or a settings.json / config_plugins override), the same opt-in experimental uses. beta / stable keep running. No built-in is deprecated today, so the default scan is unchanged until one is marked.

  User-facing

  Deprecated plugin extensions now start disabled, like experimental ones: they show an off toggle (with the deprecated badge) in Settings and sm plugins list, and don't run until you enable them. Enabling one keeps it working while you migrate off it.

• Extensions declaring stability: 'experimental' now ship DISABLED by default: their installed default flips from enabled to disabled, so the extension does not run or register until the operator opts in (sm plugins enable <plugin>/<ext>, the Settings toggle, or a settings.json / config_plugins override). beta / deprecated / stable keep running. Built-ins flipped to experimental: core/mcp-tools and the Supersede declarer (core/supersede button + core/node-supersede action).

  User-facing

  Experimental plugin extensions now start disabled: an off toggle (with the experimental badge) in Settings and sm plugins list, not running until you enable them. The MCP tools extractor and the Supersede button are experimental, so both are off until you turn them on.

• The scan now captures each file's modification time (mtime) from the walker's existing lstat, persisted on scan_nodes.modified_at_ms and surfaced on the node wire shape as modifiedAtMs (nullable for virtual / derived nodes). The files table gains a sortable "Modified" column at the end, rendered as an ISO short date with a full date+time tooltip; sorting orders by the raw timestamp and sinks fileless nodes to the bottom. The value never participates in bodyHash / frontmatterHash.

  User-facing

  The files table has a new Modified column showing when each file was last edited (for example 2026-06-13). Click the header to sort newest or oldest first, and hover a cell to see the exact date and time.

• sm plugins show is now extension-only: it takes a qualified <plugin>/<ext> id and renders one extension's detail. The whole-plugin view (manifest plus extension rows) moves to sm plugins list <id>, and the top-level sm plugins list index drops the per-extension name sub-lines. A bare show <plugin> id and a qualified list <plugin>/<ext> id are each rejected with a directed redirect to the other verb.

  User-facing

  Plugin commands split by altitude. sm plugins list <id> now shows a whole plugin's extensions (kinds, versions, status); sm plugins show is for a single <plugin>/<ext> extension. The plain sm plugins list stays a clean index, one row per plugin.

Patch Changes

• core/backtick-path now matches bare .md filenames inside code spans, not only slashed paths: a backticked `algo4.md` becomes a points edge the way the runtime follows it. The / separator is now optional, with the first path segment anchored to a word char so globs and placeholders ({PROJECT}-x.md, *-S.md) stay rejected. Slashless names like SKILL.md match too; a self-reference becomes a self-loop, other misses flag via core/reference-broken.

  User-facing

  Backticked filenames now become links even without a folder: writing `algo4.md` inside code formatting (not just `docs/algo4.md`) draws an arrow to that file in the graph, matching how an agent actually follows the reference.

• Broken graph edges now render fainter than resolved ones. core/markdown-link emits the spec's 0.95 (unambiguous syntax) instead of a hardcoded 1.0, and the post-walk confidence-lift transform adds a BROKEN_TARGET_CONFIDENCE = 0.5 downgrade for links that resolve to nothing (no path and no name-index match, like core/reference-broken). A dangling [x](missing.md), @missing.md, or /no-such-command now sits at 0.5, below a resolved 1.0 and above a reserved 0.1.

  User-facing

  Broken links in the graph now appear fainter than working ones: a markdown link, @file, or /command pointing at something that does not exist renders at low opacity, so dangling references stand out at a glance instead of looking like solid edges.

• The post-walk confidence-lift transform no longer bumps a link to 1.0 when its resolved target is a virtual: true node (today only core/mcp-tools' mcp://<server> nodes, reconstructed from frontmatter, never verified on disk). The edge still resolves (resolvedTarget set, navigable) but keeps its extractor emit confidence, so an MCP edge stays 0.85: an unverified entity is not full certainty, like the reserved-target downgrade.

@skill-map/cli@0.55.0

Minor Changes

• Inspector action buttons are now self-projected by the dispatching Action instead of a sibling projector Analyzer: an Action may declare a ui button plus an optional deterministic scan-time project(ctx) (read-only graph) that emits its own inspector.action.button per node. The pure projector analyzers core/supersede and core/tags were removed and core/annotation-stale trimmed to its badge + issue (the Bump button moved to core/node-bump).

  User-facing

  No change to how the inspector behaves: the Supersede, Edit tags, and Bump buttons look and work exactly as before, they are just now produced by the action they trigger rather than a separate analyzer.

• Extensions declaring stability: 'deprecated' now also ship DISABLED by default, joining experimental in the ships-disabled set: a deprecated extension does not run or register until the operator opts in (sm plugins enable <plugin>/<ext>, the Settings toggle, or a settings.json / config_plugins override), the same opt-in experimental uses. beta / stable keep running. No built-in is deprecated today, so the default scan is unchanged until one is marked.

  User-facing

  Deprecated plugin extensions now start disabled, like experimental ones: they show an off toggle (with the deprecated badge) in Settings and sm plugins list, and don't run until you enable them. Enabling one keeps it working while you migrate off it.

• Extensions declaring stability: 'experimental' now ship DISABLED by default: their installed default flips from enabled to disabled, so the extension does not run or register until the operator opts in (sm plugins enable <plugin>/<ext>, the Settings toggle, or a settings.json / config_plugins override). beta / deprecated / stable keep running. Built-ins flipped to experimental: core/mcp-tools and the Supersede declarer (core/supersede button + core/node-supersede action).

  User-facing

  Experimental plugin extensions now start disabled: an off toggle (with the experimental badge) in Settings and sm plugins list, not running until you enable them. The MCP tools extractor and the Supersede button are experimental, so both are off until you turn them on.

• The scan now captures each file's modification time (mtime) from the walker's existing lstat, persisted on scan_nodes.modified_at_ms and surfaced on the node wire shape as modifiedAtMs (nullable for virtual / derived nodes). The files table gains a sortable "Modified" column at the end, rendered as an ISO short date with a full date+time tooltip; sorting orders by the raw timestamp and sinks fileless nodes to the bottom. The value never participates in bodyHash / frontmatterHash.

  User-facing

  The files table has a new Modified column showing when each file was last edited (for example 2026-06-13). Click the header to sort newest or oldest first, and hover a cell to see the exact date and time.

• The core/node-superseded analyzer (surfaces a node's supersededBy declaration as an info finding) is now experimental, joining the rest of the supersession family (core/supersede, core/node-supersede) which already shipped experimental. As an experimental extension it ships disabled by default, so the "node is superseded by X" finding no longer appears until the operator enables the family with sm plugins enable core/node-superseded (or the Settings toggle).

  User-facing

  The supersession info finding ("this node is superseded by X") no longer shows by default: core/node-superseded is now experimental, so the whole supersession family (declare button + this finding) is off until you enable it in Settings or with sm plugins enable.

• sm plugins show is now extension-only: it takes a qualified <plugin>/<ext> id and renders one extension's detail. The whole-plugin view (manifest plus extension rows) moves to sm plugins list <id>, and the top-level sm plugins list index drops the per-extension name sub-lines. A bare show <plugin> id and a qualified list <plugin>/<ext> id are each rejected with a directed redirect to the other verb.

  User-facing

  Plugin commands split by altitude. sm plugins list <id> now shows a whole plugin's extensions (kinds, versions, status); sm plugins show is for a single <plugin>/<ext> extension. The plain sm plugins list stays a clean index, one row per plugin.

• The sm tutorial campaign's second half is now a single "daily loop" part (add, improve, publish) that operates the harness for real instead of by hand: the content-editor, check-links, and publish steps actually run, the maintenance analyzers (broken reference, orphan, reserved name, .sm sidecar) surface from real work, and the portfolio it builds ships with a styled, personalized site. MCP is parked out of the menu pending its own iteration.

  User-facing

  The interactive tutorial's second half is now a single "daily loop": you add a page with your agent, improve it, and publish, running the harness for real. The portfolio it builds ships with a clean, personalized site you can serve and deploy.

Patch Changes

• core/backtick-path now matches bare .md filenames inside code spans, not only slashed paths: a backticked `algo4.md` becomes a points edge the way the runtime follows it. The / separator is now optional, with the first path segment anchored to a word char so globs and placeholders ({PROJECT}-x.md, *-S.md) stay rejected. Slashless names like SKILL.md match too; a self-reference becomes a self-loop, other misses flag via core/reference-broken.

  User-facing

  Backticked filenames now become links even without a folder: writing `algo4.md` inside code formatting (not just `docs/algo4.md`) draws an arrow to that file in the graph, matching how an agent actually follows the reference.

• Broken graph edges now render fainter than resolved ones. core/markdown-link emits the spec's 0.95 (unambiguous syntax) instead of a hardcoded 1.0, and the post-walk confidence-lift transform adds a BROKEN_TARGET_CONFIDENCE = 0.5 downgrade for links that resolve to nothing (no path and no name-index match, like core/reference-broken). A dangling [x](missing.md), @missing.md, or /no-such-command now sits at 0.5, below a resolved 1.0 and above a reserved 0.1.

  User-facing

  Broken links in the graph now appear fainter than working ones: a markdown link, @file, or /command pointing at something that does not exist renders at low opacity, so dangling references stand out at a glance instead of looking like solid edges.

• Every built-in extractor description now ends with a concrete usage example. The markdown-link, external-url-counter, annotations, mcp-tools, backtick-path, tools-counter, and slash-command manifests keep their existing leading sentence and append a short Example: ... clause, so the text shown in sm plugins list, sm plugins show, and the Settings plugins panel illustrates what each extractor matches.

  User-facing

  Extractor descriptions in sm plugins list and Settings now include a usage example.

• The post-walk confidence-lift transform no longer bumps a link to 1.0 when its resolved target is a virtual: true node (today only core/mcp-tools' mcp://<server> nodes, reconstructed from frontmatter, never verified on disk). The edge still resolves (resolvedTarget set, navigable) but keeps its extractor emit confidence, so an MCP edge stays 0.85: an unverified entity is not full certainty, like the reserved-target downgrade.