@skaile/workspaces 6.0.0 → 6.1.0

package/dist/chunk-PUK7TQT4.js

@@ -1,13 +0,0 @@
-import { isValidAssetName } from './chunk-WDXZA7QW.js';
-
-// cli/src/store-addable.ts
-function storeNotInstallableReason(a) {
-  if (!isValidAssetName(a.name)) {
-    return `the name "${a.name}" is not a canonical asset name, so no ref names it`;
-  }
-  return void 0;
-}
-
-export { storeNotInstallableReason };
-//# sourceMappingURL=chunk-PUK7TQT4.js.map
-//# sourceMappingURL=chunk-PUK7TQT4.js.map

package/dist/chunk-PUK7TQT4.js.map

@@ -1 +0,0 @@
-{"version":3,"sources":["../cli/src/store-addable.ts"],"names":[],"mappings":";;;AAkBO,SAAS,0BACd,CAAA,EACoB;AACpB,EAAA,IAAI,CAAC,gBAAA,CAAiB,CAAA,CAAE,IAAI,CAAA,EAAG;AAC7B,IAAA,OAAO,CAAA,UAAA,EAAa,EAAE,IAAI,CAAA,mDAAA,CAAA;AAAA,EAC5B;AACA,EAAA,OAAO,MAAA;AACT","file":"chunk-PUK7TQT4.js","sourcesContent":["/**\n * Which store entries `skaile add` can take. The store lists only what `add` can install\n * (owner decision, RCV p385): one rule for `search`, `store search`, `store show` and the\n * `manage` store feed, so a listing never offers a ref that then fails.\n *\n * Every store kind is installable (owner decision, RCW p610): `add` stages the pointer's files\n * into the store cache and deploys them (skills, agents, contracts) or composes them at session\n * start (mcp-server). Only a name that is no canonical asset name cannot be added.\n */\n\nimport { isValidAssetName } from \"@skaile/workspaces/core\";\nimport type { CatalogAsset } from \"@skaile/workspaces/plugins\";\n\n/**\n * Why `skaile add` cannot take a store row as printed, or `undefined` when it can: a name that\n * is not a canonical asset name (`UI Rendering` copied from a listing is two shell arguments\n * and no ref).\n */\nexport function storeNotInstallableReason(\n  a: Pick<CatalogAsset, \"kind\" | \"name\">,\n): string | undefined {\n  if (!isValidAssetName(a.name)) {\n    return `the name \"${a.name}\" is not a canonical asset name, so no ref names it`;\n  }\n  return undefined;\n}\n"]}