@hasna/skills 0.1.63 → 0.1.64

package/dist/lib/remote-registry.d.ts

@@ -19,4 +19,30 @@ export declare function buildSkillsApiUrl(apiUrl: string, endpoint?: string): st
 export declare function parseRemoteRegistryPayload(payload: unknown): SkillMeta[];
 export declare function parseRemoteSkillPayload(payload: unknown): SkillMeta;
 export declare function loadRemoteRegistry(options?: RemoteRegistryOptions): Promise<SkillMeta[]>;
+/**
+ * Merge the authenticated remote registry into a local listing, whenever the
+ * install is pointed at a hosted instance.
+ *
+ * This is the fail-closed (R1) default-read merge: a client configured with an
+ * origin sees the folder UNION cloud in the plain `list`/`search` path, while
+ * every other install keeps today's exact local behavior.
+ *
+ *   - No origin configured  -> the local list is returned unchanged and no
+ *     request is attempted. An unconfigured install must stay byte-identical
+ *     to the pre-merge output.
+ *   - Origin configured but no credential -> the local list is returned
+ *     unchanged and nothing throws. Auth-missing must never crash a read.
+ *   - Origin + credential -> the remote registry is fetched and merged under
+ *     the precedence in registry-merge.ts (custom > extension > private >
+ *     private-hosted > remote > upstream > official), remote rows tagged
+ *     `source: "remote"`.
+ *   - A configured, authenticated read that FAILS (auth rejection, HTTP
+ *     error, network failure) throws a clear error rather than silently
+ *     returning the local half — a silent partial listing would report
+ *     success for a union the caller asked to include.
+ *
+ * The explicit `--remote` path stays on loadRemoteRegistry(): an explicit
+ * request has always been fatal on failure, and that contract is unchanged.
+ */
+export declare function mergeRemoteRegistry(local: SkillMeta[], options?: RemoteRegistryOptions): Promise<SkillMeta[]>;
 export declare function loadRemoteSkill(name: string, options?: RemoteRegistryOptions): Promise<SkillMeta>;

package/dist/lib/revision.d.ts

@@ -0,0 +1,29 @@
+/** The row's content-addressed revision identity: a lowercase hex sha-256. */
+export declare const REVISION_ID_PATTERN: RegExp;
+export interface RevisionContent {
+    slug: string;
+    displayName: string;
+    description: string;
+    category: string;
+    tags: string[];
+    source: string;
+    kind: "executable" | "instruction";
+    version?: string;
+    skillMd?: string;
+    bundleSha256?: string;
+    bundleByteSize?: number;
+}
+export declare function revisionIdOf(content: RevisionContent): string;
+export declare function revisionIdOfRecord(record: RevisionContent): string;
+/**
+ * The legacy-row marker the 0004 migration leaves behind.
+ *
+ * Migration 0004 adds revision_id with DEFAULT '', so rows written before the migration
+ * carry an empty id. An empty id would make the If-Match guard vacuous for those rows:
+ * two clients that both read '' would both "match" and both land, silently overwriting
+ * each other. The stores replace the marker with a real content sha on first open
+ * (idempotent: new code always writes a full id, so the marker never reappears).
+ */
+export declare const LEGACY_REVISION_ID = "";
+/** True when a revision id is the empty legacy marker (needs backfill). */
+export declare function isLegacyRevisionId(value: string): boolean;