@skill-map/cli 0.18.0 → 0.20.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@skill-map/cli",
-  "version": "0.18.0",
+  "version": "0.20.0",
   "description": "skill-map reference implementation — kernel + CLI + adapters.",
   "license": "MIT",
   "type": "module",
@@ -66,7 +66,7 @@
   },
   "dependencies": {
     "@hono/node-server": "2.0.1",
-    "@skill-map/spec": "0.18.0",
+    "@skill-map/spec": "0.20.0",
     "ajv": "8.18.0",
     "ajv-formats": "3.0.1",
     "chokidar": "5.0.0",

package/dist/migrations/002_sidecar_columns.sql

@@ -1,53 +0,0 @@
--- Step 9.6.2 — kernel sidecar reader + drift detection.
---
--- Extends `scan_nodes` with three new columns to denormalise the
--- sidecar-derived state for fast queries:
---
---   - `sidecar_present` — boolean flag, 1 when a co-located `.sm` file
---     accompanies this node, 0 otherwise. Default 0.
---   - `sidecar_status` — fresh / stale-body / stale-frontmatter /
---     stale-both. NULL when no sidecar is present.
---   - `annotations_json` — JSON-encoded `annotations:` block from the
---     parsed sidecar (the typed surface declared by
---     `spec/schemas/annotations.schema.json`). NULL when no sidecar or
---     when the block is empty.
---
--- Hard-cut migration of the source-of-truth for three pre-existing
--- columns (Decision #3 — option (a), extend `scan_nodes`):
---
---   - `stability` — was sourced from `frontmatter.metadata.stability`,
---     now sourced from sidecar `annotations.stability`.
---   - `version`   — was `TEXT` (semver string from
---     `frontmatter.metadata.version`); now `INTEGER` (monotonic counter
---     from sidecar `annotations.version`). Pre-9.6.2 rows reset to
---     NULL — greenfield migration, no automatic semver→integer
---     conversion (Decision #125 / per-project policy).
---   - `author`    — was sourced from `frontmatter.author`, now sourced
---     from sidecar `annotations.author`.
---
--- The fallback path through `pickMetadata` for these three fields is
--- removed in the kernel; other consumers of `metadata.*` (e.g.
--- broken-ref's `metadata.related`) are out of scope for 9.6.2.
---
--- SQLite limitation note: the three pre-existing columns retain their
--- original types where possible. For `version` we change the type by
--- dropping and re-adding the column (safe: greenfield reset to NULL
--- is the documented migration outcome). DROP COLUMN requires SQLite
--- 3.35+; node:sqlite (Node 22+) ships SQLite ≥ 3.45.
-
-ALTER TABLE scan_nodes DROP COLUMN version;
-ALTER TABLE scan_nodes ADD COLUMN version INTEGER;
-
-ALTER TABLE scan_nodes ADD COLUMN sidecar_present INTEGER NOT NULL DEFAULT 0;
-ALTER TABLE scan_nodes ADD COLUMN sidecar_status TEXT;
-ALTER TABLE scan_nodes ADD COLUMN annotations_json TEXT;
-
--- Reset stability + author to NULL — they used to be populated from
--- frontmatter.metadata.{stability,author}; the new source is
--- sidecar `annotations.{stability,author}` and a re-scan repopulates.
-UPDATE scan_nodes SET stability = NULL, author = NULL;
-
--- Constraint mirrors the four legal values returned by the kernel's
--- drift detector. NULL is allowed (and required) when no sidecar is
--- present.
-CREATE INDEX ix_scan_nodes_sidecar_status ON scan_nodes(sidecar_status);

package/dist/migrations/003_drop_node_author.sql

@@ -1,20 +0,0 @@
--- Step 9.6 catalog-curation follow-up (2026-05-07).
---
--- Drop the vestigial `scan_nodes.author` column. The 9.6.2 migration
--- denormalised `annotations.author` into the column; the 2026-05-07
--- catalog curation removed `author` from `annotations.schema.json`,
--- which left the column without a canonical source. Anyone who still
--- writes `author:` in their `.sm` rides on `additionalProperties: true`
--- — the value lands in `annotations_json` (no longer in a typed
--- column), and `unknown-field` warns on it as a typo guard.
---
--- Greenfield drop: pre-9.6 rows had the column reset to NULL by
--- migration 002, and the curation rolled out before any released
--- consumer pinned the post-9.6.2 shape. No automatic salvage path —
--- if a deployed DB carried real data, it is preserved verbatim under
--- `scan_nodes.annotations_json` until the next scan rewrites the row.
---
--- DROP COLUMN requires SQLite 3.35+; node:sqlite (Node 22+) ships
--- SQLite ≥ 3.45.
-
-ALTER TABLE scan_nodes DROP COLUMN author;

package/dist/migrations/004_sidecar_root_json.sql

@@ -1,23 +0,0 @@
--- R15 closure (2026-05-07) — surface the full parsed `.sm` root on the
--- BFF wire shape (`Node.sidecar.root`).
---
--- Adds `scan_nodes.sidecar_root_json`, sibling to `annotations_json`
--- (Decision: option (b), additive — no rewrite of the existing read
--- path; duplicates the `annotations:` sub-block by design so
--- pre-R15 consumers reading `annotations_json` keep working unchanged).
---
--- Column shape:
---   - JSON-encoded full parsed YAML root of the matching `.sm` file
---     (every top-level reserved block — `for` / `annotations` /
---     `settings` / `audit` — plus `<plugin-id>:` namespaces a plugin
---     opt-in to root via `annotationContributions`).
---   - NULL when no sidecar accompanies the node, or when the sidecar
---     exists but failed to parse / validate (in that case
---     `sidecar_present` stays 1 and `sidecar_status` stays NULL).
---
--- Backfill on existing rows: NULL. Re-scan repopulates the column from
--- the live `.sm` file via `parseSidecar()`'s already-computed `raw`
--- payload. Greenfield posture per `feedback_greenfield_no_versioning.md`
--- — no released consumer depends on the prior shape.
-
-ALTER TABLE scan_nodes ADD COLUMN sidecar_root_json TEXT;

package/dist/migrations/005_node_favorites.sql

@@ -1,20 +0,0 @@
--- Per-node "favorite" flag persisted per user (single-user local DB).
---
--- Zone `state_` because favorites are user-authored preference and must
--- survive `sm scan` truncation and `sm db reset` (which drops only
--- `scan_*`). Absence of a row means "not favorited".
---
--- `node_path` is FK-semantic to `scan_nodes.path`. The rename heuristic
--- (`migrateNodeFks` in src/kernel/adapters/sqlite/history.ts) MUST migrate
--- rows here when a path is renamed, same protocol as the other state_*
--- tables. Simple PK update — no composite key, no collision shape.
---
--- The BFF's `/api/nodes` route loads the full set of paths once per
--- request (typical favorite count is small) and decorates the in-memory
--- node list with a derived `isFavorite` boolean by Set membership. No
--- SQL JOIN against `scan_nodes` is required.
-
-CREATE TABLE state_node_favorites (
-  node_path TEXT PRIMARY KEY,
-  favorited_at INTEGER NOT NULL
-);