@hasna/skills 0.10.47 → 0.10.49

package/dist/server/index.d.ts

@@ -1,2 +1,2 @@
 #!/usr/bin/env bun
-export {};
+import "../lib/launch-cwd-apply.js";

package/dist/server/maintenance.d.ts

@@ -1,2 +1,2 @@
 #!/usr/bin/env bun
-export {};
+import "../lib/launch-cwd-apply.js";

package/dist/server/migrate.d.ts

@@ -1,4 +1,21 @@
 #!/usr/bin/env bun
+/**
+ * Schema migration for whichever backend is configured.
+ *
+ * Migrations are per-dialect files, not one file rewritten at runtime. Both approaches
+ * were on the table; the parallel set won because a runtime translator would have to
+ * turn `jsonb`, `timestamptz`, `bigserial`, `::jsonb` casts, `now()` defaults, and
+ * `CREATE EXTENSION` into SQLite as a text transformation, and would silently mistranslate
+ * the first construct a future migration used that the translator had never seen - on
+ * the operator's machine, at migrate time, against their real data. Two hand-written
+ * files fail at review time instead, and src/server/schema-parity.test.ts executes the
+ * SQLite one and diffs its real introspected shape against the Postgres DDL so the pair
+ * cannot drift.
+ *
+ * Applied-version keys are file basenames, so migrations/0001_*.sql moving into
+ * migrations/postgres/ did not orphan databases that had already applied it.
+ */
+import "../lib/launch-cwd-apply.js";
 import { type DatabaseTarget } from "./database-url.js";
 export interface MigrationResult {
     backend: DatabaseTarget["kind"];

package/dist/server/worker.d.ts

@@ -1,4 +1,5 @@
 #!/usr/bin/env bun
+import "../lib/launch-cwd-apply.js";
 import { ArtifactStorage } from "../sdk/storage.js";
 import type { SkillsProductStore } from "../sdk/storage.js";
 export declare function runWorkerOnce(store: SkillsProductStore, workerId?: string, storage?: ArtifactStorage): Promise<boolean>;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hasna/skills",
-  "version": "0.10.47",
+  "version": "0.10.49",
   "description": "Skills library for AI coding agents",
   "type": "module",
   "bin": {