@hasna/skills 0.1.63 → 0.1.66

package/migrations/postgres/0005_tag_projection.sql

@@ -0,0 +1,36 @@
+-- The hosted tag surface (T7) queries tag membership from this relational
+-- projection of skills_registry.tags_json, in both dialects with one identical
+-- shape. SQLite cannot index json_each() over the JSON column, and Postgres
+-- rows written by the current path hold the array text inside a jsonb scalar
+-- (bun's driver binds a JS string against a ::jsonb cast as a JSON string), so
+-- neither dialect can serve an indexed array-expansion query directly. The
+-- projection turns tag membership into a plain indexed lookup: the PRIMARY KEY
+-- serves (org_id, slug) maintenance and the org_tag index serves (org_id, tag)
+-- filters. The write paths keep it in step; the backfill below covers rows
+-- that predate it.
+-- No composite FK to skills_registry: the schema-parity parser cannot
+-- represent a multi-column FK identically in both dialects, and every write
+-- path here maintains the projection explicitly (publish/update replace its
+-- rows, the tombstone purge removes them with the row), so the constraint
+-- would be redundancy.
+CREATE TABLE skills_tags (
+  org_id text NOT NULL REFERENCES organizations(id) ON DELETE CASCADE,
+  slug text NOT NULL,
+  tag text NOT NULL,
+  PRIMARY KEY (org_id, slug, tag)
+);
+
+CREATE INDEX skills_tags_org_tag_idx ON skills_tags (org_id, tag);
+
+-- Backfill every existing row's tags. tags_json may be a real array or,
+-- because of the jsonb-scalar write path, the array text inside a jsonb
+-- string; both shapes are expanded here.
+INSERT INTO skills_tags (org_id, slug, tag)
+SELECT DISTINCT r.org_id, r.slug, t.tag
+FROM skills_registry r
+CROSS JOIN LATERAL jsonb_array_elements_text(
+  CASE WHEN jsonb_typeof(r.tags_json) = 'array' THEN r.tags_json
+       WHEN jsonb_typeof(r.tags_json) = 'string' THEN (r.tags_json #>> '{}')::jsonb
+       ELSE '[]'::jsonb END
+) AS t(tag)
+WHERE t.tag <> '';

package/migrations/sqlite/0004_hosted_pins.sql

@@ -0,0 +1,21 @@
+-- Hosted pins: the cloud becomes a source of truth for what the user selected.
+--
+-- SQLite dialect of 0004_hosted_pins. Read the Postgres file for the why; the
+-- only differences here are the documented dialect mapping:
+--   * timestamptz -> text holding a UTC ISO-8601 instant (pinned_at).
+--   * jsonb       -> text holding JSON (metadata_json).
+--
+-- No RLS: the tenant fence on this table is the org-scoped predicate in the
+-- store, exactly as it is for skills_registry and skills_bundles. RLS was
+-- armed in 0003 only for the run-output tables, where a worker path writes
+-- outside a tenant context; pins are written and read only by the API under
+-- the requesting principal's org, so there is no context-less writer to fence.
+
+CREATE TABLE IF NOT EXISTS skills_pins (
+  org_id text NOT NULL REFERENCES organizations(id) ON DELETE CASCADE,
+  principal text NOT NULL,
+  slug text NOT NULL,
+  pinned_at text NOT NULL DEFAULT (strftime('%Y-%m-%dT%H:%M:%fZ', 'now')),
+  metadata_json text NOT NULL DEFAULT '{}',
+  PRIMARY KEY (org_id, principal, slug)
+);

package/migrations/sqlite/0005_revision_tombstone_registry.sql

@@ -0,0 +1,18 @@
+-- SQLite dialect of 0005_revision_tombstone_registry.
+--
+-- Hand-written parallel of migrations/postgres/0005_revision_tombstone_registry.sql. Read
+-- that file for why the registry gains revision_id/revision_number (immutable revision
+-- identity), the optimistic-concurrency guard, and the tombstone contract; the rationale
+-- is not repeated here, only the dialect differences are.
+--
+-- Deliberate, shape-preserving dialect differences (same set as 0001):
+--   * timestamptz -> text holding a UTC ISO-8601 instant.
+--
+-- SQLite requires a non-null literal DEFAULT for a NOT NULL ADD COLUMN; the '' default is
+-- the legacy-row marker the store's backfill (src/lib/revision.ts) replaces with a
+-- content sha on first open, exactly as on Postgres.
+
+ALTER TABLE skills_registry ADD COLUMN revision_id text NOT NULL DEFAULT '';
+ALTER TABLE skills_registry ADD COLUMN revision_number integer NOT NULL DEFAULT 0;
+ALTER TABLE skills_registry ADD COLUMN tombstoned_at text;
+ALTER TABLE skills_registry ADD COLUMN tombstone_purge_after text;

package/migrations/sqlite/0005_tag_projection.sql

@@ -0,0 +1,25 @@
+-- The hosted tag surface (T7) queries tag membership from this relational
+-- projection of skills_registry.tags_json, in both dialects with one identical
+-- shape. SQLite cannot index json_each() over the JSON column, so the tag
+-- lookup becomes an indexed read here: the PRIMARY KEY serves (org_id, slug)
+-- maintenance and the org_tag index serves (org_id, tag) filters. The write
+-- paths keep it in step; the backfill below covers rows that predate it.
+-- No composite FK to skills_registry: the schema-parity parser cannot
+-- represent a multi-column FK identically in both dialects, and every write
+-- path here maintains the projection explicitly (publish/update replace its
+-- rows, the tombstone purge removes them with the row), so the constraint
+-- would be redundancy.
+CREATE TABLE skills_tags (
+  org_id text NOT NULL REFERENCES organizations(id) ON DELETE CASCADE,
+  slug text NOT NULL,
+  tag text NOT NULL,
+  PRIMARY KEY (org_id, slug, tag)
+);
+
+CREATE INDEX skills_tags_org_tag_idx ON skills_tags (org_id, tag);
+
+-- Backfill every existing row's tags from the stored JSON array.
+INSERT INTO skills_tags (org_id, slug, tag)
+SELECT DISTINCT r.org_id, r.slug, je.value
+FROM skills_registry r, json_each(r.tags_json) AS je
+WHERE je.value <> '';

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hasna/skills",
-  "version": "0.1.63",
+  "version": "0.1.66",
   "description": "Skills library for AI coding agents",
   "type": "module",
   "bin": {
@@ -74,6 +74,7 @@
   "license": "Apache-2.0",
   "devDependencies": {
     "@types/bun": "latest",
+    "@types/node": "25.2.3",
     "@types/react": "^18.2.0",
     "bun-types": "1.3.14",
     "react-devtools-core": "^7.0.1",
@@ -82,7 +83,7 @@
   "dependencies": {
     "@aws-sdk/client-ecs": "^3.1079.0",
     "@aws-sdk/client-s3": "^3.1079.0",
-    "@hasna/events": "0.1.7",
+    "@hasna/events": "0.1.16",
     "@modelcontextprotocol/sdk": "^1.26.0",
     "chalk": "^5.3.0",
     "commander": "^12.1.0",