@tangle-network/agent-app 0.44.58 → 0.44.59

package/dist/{chunk-OO4DROKM.js → chunk-DMYCGXBP.js}

@@ -11,4 +11,4 @@ export {
   DesignCanvasLazy,
   DesignCanvasChromeLazy
 };
-//# sourceMappingURL=chunk-OO4DROKM.js.map
+//# sourceMappingURL=chunk-DMYCGXBP.js.map

package/dist/design-canvas-react/index.js

@@ -91,7 +91,7 @@ import {
 import {
   DesignCanvasChromeLazy,
   DesignCanvasLazy
-} from "../chunk-OO4DROKM.js";
+} from "../chunk-DMYCGXBP.js";
 import "../chunk-J25RST7G.js";
 
 // src/design-canvas-react/components/CanvasInsertPanel.tsx

package/dist/design-canvas-react/lazy.js

@@ -1,7 +1,7 @@
 import {
   DesignCanvasChromeLazy,
   DesignCanvasLazy
-} from "../chunk-OO4DROKM.js";
+} from "../chunk-DMYCGXBP.js";
 export {
   DesignCanvasChromeLazy,
   DesignCanvasLazy

package/dist/vault/server.d.ts

@@ -0,0 +1,130 @@
+/**
+ * Server-only policy sibling of the React `./vault` client surface. Pure
+ * decision logic — no I/O, no logging, ZERO imports — extracted from
+ * gtm-agent's local guard (gtm#612) after it lost 48 production vault files:
+ * a half-mounted sandbox scanned cleanly and reconciliation derived a
+ * mass-deletion batch from an empty manifest. The #265/#332 audit ruled both
+ * checks here universal shell mechanism, not gtm-specific, so they live here
+ * once instead of being re-forked per product.
+ *
+ * Two independent checks:
+ *  - `assessVaultDeletionBatch` — blast-radius refusal. Given the live
+ *    baseline and what a reconciliation pass proposes to delete, decide
+ *    whether the batch is safe to apply or must be refused. Refusal is a
+ *    SUCCESSFUL outcome, not a thrown error: content changes still apply,
+ *    only the deletions are withheld. What to do with a refusal (log, alert,
+ *    retry the scan) stays the caller's job.
+ *  - `compareIncarnationBaseline` — filesystem-incarnation comparison. Given
+ *    a recorded baseline incarnation id and the sandbox's current identity
+ *    fields, decide whether the sandbox filesystem is the same one the
+ *    baseline was captured against, fail-closed on anything not clearly
+ *    identified and ready.
+ *
+ * Both are pure functions over caller-supplied data: no manifest reads, no
+ * sandbox calls, no console output. The caller pre-filters tombstoned
+ * entries (this module only ever sees the LIVE path set) and owns everything
+ * that happens after a verdict comes back.
+ */
+/** Refuse a deletion batch once it would remove at least this fraction of the
+ *  live baseline (both this and `VAULT_DELETION_REFUSAL_MIN_LIVE_FILES` must
+ *  hold — a tiny vault can lose all its files without tripping this ratio
+ *  gate; `refusesAllFiles` catches that case separately). */
+declare const VAULT_DELETION_REFUSAL_RATIO = 0.75;
+/** The blast-radius ratio gate only engages once the live baseline is at
+ *  least this large, so a 2-file vault losing 1 file (50%) is not refused on
+ *  ratio alone. */
+declare const VAULT_DELETION_REFUSAL_MIN_LIVE_FILES = 10;
+/** Overrides for `assessVaultDeletionBatch`'s two thresholds. Both default to
+ *  the exported constants above. Values are validated fail-loud:
+ *  `refusalRatio` must be finite and in (0, 1] — `NaN` (a config parse
+ *  failure) would make `deletionRatio >= refusalRatio` always false and silently
+ *  disable the guard, and `0` would refuse a zero-deletion batch; and
+ *  `minLiveFiles` must be finite and >= 0. Invalid values throw `RangeError`
+ *  instead of running with a guard that cannot fire (or cannot pass). */
+interface VaultDeletionPolicy {
+    refusalRatio?: number;
+    minLiveFiles?: number;
+}
+interface VaultDeletionAssessment {
+    /** True when no refusal reason fired. */
+    allowed: boolean;
+    /** Precedence when multiple reasons would fire: `empty-manifest` beats
+     *  `all-files` beats `ratio-exceeded` (most specific first — an empty scan
+     *  IS an all-files deletion, but the diagnostic that matters is "the scan
+     *  came back empty", not "it deleted everything"). Undefined when allowed. */
+    reason?: 'empty-manifest' | 'all-files' | 'ratio-exceeded';
+    /** wouldDelete / baselineLive, or 0 when the baseline is itself empty. */
+    deletionRatio: number;
+    wouldDelete: number;
+    /** The paths that would be deleted, sorted — mirrors gtm's `.sort()` so log
+     *  output and any snapshot fixture are byte-stable. */
+    wouldDeletePaths: string[];
+    baselineLive: number;
+}
+/**
+ * Decide whether a reconciliation pass's proposed deletions are safe to
+ * apply against the live baseline.
+ *
+ * `manifestEmpty: true` means the filesystem scan that produced
+ * `proposedDeletions` came back with nothing — the caller could not have
+ * derived a meaningful proposed-deletions list, so this treats the FULL live
+ * baseline as would-delete regardless of what `proposedDeletions` contains.
+ * That is what distinguishes `'empty-manifest'` from `'all-files'`: an empty
+ * scan structurally implies every baseline path would be deleted, but the
+ * diagnostic that matters to a caller is "the scan was empty", not merely
+ * "everything would go".
+ */
+declare function assessVaultDeletionBatch(input: {
+    /** LIVE (non-tombstoned) baseline path set — the caller pre-filters, as gtm does. */
+    baselinePaths: readonly string[];
+    /** Paths a reconciliation pass proposes to delete; intersected with `baselinePaths` internally. */
+    proposedDeletions: readonly string[];
+    manifestEmpty?: boolean;
+    policy?: VaultDeletionPolicy;
+}): VaultDeletionAssessment;
+/** The subset of a sandbox's filesystem-incarnation identity this module
+ *  needs. A product's real incarnation type is structurally compatible —
+ *  no import required. */
+interface FilesystemIncarnationLike {
+    filesystemIncarnationId?: string;
+    filesystemIncarnationProvenance?: 'fresh' | 'restored' | 'unknown';
+    filesystemIncarnationReadiness?: 'transitioning' | 'ready';
+}
+/**
+ * Result of comparing a recorded baseline incarnation id against the
+ * sandbox's current identity. A discriminated union over `verdict` so a
+ * caller's `switch` gets compile-time coverage instead of a stringly-typed
+ * status it can forget to branch on.
+ */
+type IncarnationComparison = {
+    verdict: 'match';
+} | {
+    verdict: 'mismatch';
+    baselineId: string;
+    currentId: string;
+} | {
+    verdict: 'not-ready';
+    readiness: string | undefined;
+} | {
+    verdict: 'unidentified';
+} | {
+    verdict: 'no-baseline';
+};
+/**
+ * Compare a recorded baseline filesystem-incarnation id against a sandbox's
+ * current incarnation fields. Check order mirrors gtm's gate sequence and is
+ * itself a tested fail-closed property — each earlier check short-circuits
+ * the ones after it, so a box with BOTH bad readiness and a mismatched id
+ * resolves `'not-ready'`, never `'mismatch'`:
+ *
+ *  1. `unidentified` — the current id is missing/empty, or the provenance is
+ *     not one of `fresh`/`restored`/`unknown`.
+ *  2. `not-ready` — readiness is anything other than the literal string
+ *     `'ready'` (this also catches `undefined`).
+ *  3. `no-baseline` — no baseline id was ever recorded to compare against.
+ *  4. `mismatch` — the baseline id and current id disagree.
+ *  5. `match` — same incarnation.
+ */
+declare function compareIncarnationBaseline(baselineId: string | undefined, current: FilesystemIncarnationLike): IncarnationComparison;
+
+export { type FilesystemIncarnationLike, type IncarnationComparison, VAULT_DELETION_REFUSAL_MIN_LIVE_FILES, VAULT_DELETION_REFUSAL_RATIO, type VaultDeletionAssessment, type VaultDeletionPolicy, assessVaultDeletionBatch, compareIncarnationBaseline };

package/dist/vault/server.js

@@ -0,0 +1,60 @@
+// src/vault/server.ts
+var VAULT_DELETION_REFUSAL_RATIO = 0.75;
+var VAULT_DELETION_REFUSAL_MIN_LIVE_FILES = 10;
+function assessVaultDeletionBatch(input) {
+  const refusalRatio = input.policy?.refusalRatio ?? VAULT_DELETION_REFUSAL_RATIO;
+  const minLiveFiles = input.policy?.minLiveFiles ?? VAULT_DELETION_REFUSAL_MIN_LIVE_FILES;
+  if (!Number.isFinite(refusalRatio) || refusalRatio <= 0 || refusalRatio > 1) {
+    throw new RangeError(
+      `vault deletion policy refusalRatio must be a finite number in (0, 1], got ${refusalRatio}`
+    );
+  }
+  if (!Number.isFinite(minLiveFiles) || minLiveFiles < 0) {
+    throw new RangeError(
+      `vault deletion policy minLiveFiles must be a finite number >= 0, got ${minLiveFiles}`
+    );
+  }
+  const manifestEmpty = input.manifestEmpty ?? false;
+  const baselineLive = input.baselinePaths.length;
+  const proposedSet = new Set(input.proposedDeletions);
+  const wouldDeletePaths = manifestEmpty ? [...input.baselinePaths].sort() : input.baselinePaths.filter((p) => proposedSet.has(p)).sort();
+  const wouldDelete = wouldDeletePaths.length;
+  const deletionRatio = baselineLive > 0 ? wouldDelete / baselineLive : 0;
+  const refusesEmptyManifest = manifestEmpty && baselineLive > 0;
+  const refusesAllFiles = wouldDelete > 0 && wouldDelete === baselineLive;
+  const refusesBlastRadius = wouldDelete > 0 && baselineLive >= minLiveFiles && deletionRatio >= refusalRatio;
+  const reason = refusesEmptyManifest ? "empty-manifest" : refusesAllFiles ? "all-files" : refusesBlastRadius ? "ratio-exceeded" : void 0;
+  return {
+    allowed: reason === void 0,
+    reason,
+    deletionRatio,
+    wouldDelete,
+    wouldDeletePaths,
+    baselineLive
+  };
+}
+function compareIncarnationBaseline(baselineId, current) {
+  const currentId = current.filesystemIncarnationId;
+  const provenance = current.filesystemIncarnationProvenance;
+  const isValidProvenance = provenance === "fresh" || provenance === "restored" || provenance === "unknown";
+  if (typeof currentId !== "string" || currentId.length === 0 || !isValidProvenance) {
+    return { verdict: "unidentified" };
+  }
+  if (current.filesystemIncarnationReadiness !== "ready") {
+    return { verdict: "not-ready", readiness: current.filesystemIncarnationReadiness };
+  }
+  if (baselineId === void 0) {
+    return { verdict: "no-baseline" };
+  }
+  if (baselineId !== currentId) {
+    return { verdict: "mismatch", baselineId, currentId };
+  }
+  return { verdict: "match" };
+}
+export {
+  VAULT_DELETION_REFUSAL_MIN_LIVE_FILES,
+  VAULT_DELETION_REFUSAL_RATIO,
+  assessVaultDeletionBatch,
+  compareIncarnationBaseline
+};
+//# sourceMappingURL=server.js.map

package/dist/vault/server.js.map

@@ -0,0 +1 @@
+{"version":3,"sources":["../../src/vault/server.ts"],"sourcesContent":["/**\n * Server-only policy sibling of the React `./vault` client surface. Pure\n * decision logic — no I/O, no logging, ZERO imports — extracted from\n * gtm-agent's local guard (gtm#612) after it lost 48 production vault files:\n * a half-mounted sandbox scanned cleanly and reconciliation derived a\n * mass-deletion batch from an empty manifest. The #265/#332 audit ruled both\n * checks here universal shell mechanism, not gtm-specific, so they live here\n * once instead of being re-forked per product.\n *\n * Two independent checks:\n *  - `assessVaultDeletionBatch` — blast-radius refusal. Given the live\n *    baseline and what a reconciliation pass proposes to delete, decide\n *    whether the batch is safe to apply or must be refused. Refusal is a\n *    SUCCESSFUL outcome, not a thrown error: content changes still apply,\n *    only the deletions are withheld. What to do with a refusal (log, alert,\n *    retry the scan) stays the caller's job.\n *  - `compareIncarnationBaseline` — filesystem-incarnation comparison. Given\n *    a recorded baseline incarnation id and the sandbox's current identity\n *    fields, decide whether the sandbox filesystem is the same one the\n *    baseline was captured against, fail-closed on anything not clearly\n *    identified and ready.\n *\n * Both are pure functions over caller-supplied data: no manifest reads, no\n * sandbox calls, no console output. The caller pre-filters tombstoned\n * entries (this module only ever sees the LIVE path set) and owns everything\n * that happens after a verdict comes back.\n */\n\n/** Refuse a deletion batch once it would remove at least this fraction of the\n *  live baseline (both this and `VAULT_DELETION_REFUSAL_MIN_LIVE_FILES` must\n *  hold — a tiny vault can lose all its files without tripping this ratio\n *  gate; `refusesAllFiles` catches that case separately). */\nexport const VAULT_DELETION_REFUSAL_RATIO = 0.75\n\n/** The blast-radius ratio gate only engages once the live baseline is at\n *  least this large, so a 2-file vault losing 1 file (50%) is not refused on\n *  ratio alone. */\nexport const VAULT_DELETION_REFUSAL_MIN_LIVE_FILES = 10\n\n/** Overrides for `assessVaultDeletionBatch`'s two thresholds. Both default to\n *  the exported constants above. Values are validated fail-loud:\n *  `refusalRatio` must be finite and in (0, 1] — `NaN` (a config parse\n *  failure) would make `deletionRatio >= refusalRatio` always false and silently\n *  disable the guard, and `0` would refuse a zero-deletion batch; and\n *  `minLiveFiles` must be finite and >= 0. Invalid values throw `RangeError`\n *  instead of running with a guard that cannot fire (or cannot pass). */\nexport interface VaultDeletionPolicy {\n  refusalRatio?: number\n  minLiveFiles?: number\n}\n\nexport interface VaultDeletionAssessment {\n  /** True when no refusal reason fired. */\n  allowed: boolean\n  /** Precedence when multiple reasons would fire: `empty-manifest` beats\n   *  `all-files` beats `ratio-exceeded` (most specific first — an empty scan\n   *  IS an all-files deletion, but the diagnostic that matters is \"the scan\n   *  came back empty\", not \"it deleted everything\"). Undefined when allowed. */\n  reason?: 'empty-manifest' | 'all-files' | 'ratio-exceeded'\n  /** wouldDelete / baselineLive, or 0 when the baseline is itself empty. */\n  deletionRatio: number\n  wouldDelete: number\n  /** The paths that would be deleted, sorted — mirrors gtm's `.sort()` so log\n   *  output and any snapshot fixture are byte-stable. */\n  wouldDeletePaths: string[]\n  baselineLive: number\n}\n\n/**\n * Decide whether a reconciliation pass's proposed deletions are safe to\n * apply against the live baseline.\n *\n * `manifestEmpty: true` means the filesystem scan that produced\n * `proposedDeletions` came back with nothing — the caller could not have\n * derived a meaningful proposed-deletions list, so this treats the FULL live\n * baseline as would-delete regardless of what `proposedDeletions` contains.\n * That is what distinguishes `'empty-manifest'` from `'all-files'`: an empty\n * scan structurally implies every baseline path would be deleted, but the\n * diagnostic that matters to a caller is \"the scan was empty\", not merely\n * \"everything would go\".\n */\nexport function assessVaultDeletionBatch(input: {\n  /** LIVE (non-tombstoned) baseline path set — the caller pre-filters, as gtm does. */\n  baselinePaths: readonly string[]\n  /** Paths a reconciliation pass proposes to delete; intersected with `baselinePaths` internally. */\n  proposedDeletions: readonly string[]\n  manifestEmpty?: boolean\n  policy?: VaultDeletionPolicy\n}): VaultDeletionAssessment {\n  const refusalRatio = input.policy?.refusalRatio ?? VAULT_DELETION_REFUSAL_RATIO\n  const minLiveFiles = input.policy?.minLiveFiles ?? VAULT_DELETION_REFUSAL_MIN_LIVE_FILES\n  if (!Number.isFinite(refusalRatio) || refusalRatio <= 0 || refusalRatio > 1) {\n    throw new RangeError(\n      `vault deletion policy refusalRatio must be a finite number in (0, 1], got ${refusalRatio}`,\n    )\n  }\n  if (!Number.isFinite(minLiveFiles) || minLiveFiles < 0) {\n    throw new RangeError(\n      `vault deletion policy minLiveFiles must be a finite number >= 0, got ${minLiveFiles}`,\n    )\n  }\n  const manifestEmpty = input.manifestEmpty ?? false\n\n  const baselineLive = input.baselinePaths.length\n  const proposedSet = new Set(input.proposedDeletions)\n  const wouldDeletePaths = manifestEmpty\n    ? [...input.baselinePaths].sort()\n    : input.baselinePaths.filter((p) => proposedSet.has(p)).sort()\n  const wouldDelete = wouldDeletePaths.length\n  const deletionRatio = baselineLive > 0 ? wouldDelete / baselineLive : 0\n\n  const refusesEmptyManifest = manifestEmpty && baselineLive > 0\n  const refusesAllFiles = wouldDelete > 0 && wouldDelete === baselineLive\n  // `wouldDelete > 0` is unreachable-false under the validated policy domain\n  // (a positive refusalRatio can never be met by a 0 ratio) — it is here so\n  // the ratio branch stays safe on its own terms, independent of the\n  // validation above ever being relaxed.\n  const refusesBlastRadius = wouldDelete > 0\n    && baselineLive >= minLiveFiles\n    && deletionRatio >= refusalRatio\n\n  const reason = refusesEmptyManifest\n    ? ('empty-manifest' as const)\n    : refusesAllFiles\n      ? ('all-files' as const)\n      : refusesBlastRadius\n        ? ('ratio-exceeded' as const)\n        : undefined\n\n  return {\n    allowed: reason === undefined,\n    reason,\n    deletionRatio,\n    wouldDelete,\n    wouldDeletePaths,\n    baselineLive,\n  }\n}\n\n/** The subset of a sandbox's filesystem-incarnation identity this module\n *  needs. A product's real incarnation type is structurally compatible —\n *  no import required. */\nexport interface FilesystemIncarnationLike {\n  filesystemIncarnationId?: string\n  filesystemIncarnationProvenance?: 'fresh' | 'restored' | 'unknown'\n  filesystemIncarnationReadiness?: 'transitioning' | 'ready'\n}\n\n/**\n * Result of comparing a recorded baseline incarnation id against the\n * sandbox's current identity. A discriminated union over `verdict` so a\n * caller's `switch` gets compile-time coverage instead of a stringly-typed\n * status it can forget to branch on.\n */\nexport type IncarnationComparison =\n  | { verdict: 'match' }\n  | { verdict: 'mismatch'; baselineId: string; currentId: string }\n  | { verdict: 'not-ready'; readiness: string | undefined }\n  | { verdict: 'unidentified' }\n  | { verdict: 'no-baseline' }\n\n/**\n * Compare a recorded baseline filesystem-incarnation id against a sandbox's\n * current incarnation fields. Check order mirrors gtm's gate sequence and is\n * itself a tested fail-closed property — each earlier check short-circuits\n * the ones after it, so a box with BOTH bad readiness and a mismatched id\n * resolves `'not-ready'`, never `'mismatch'`:\n *\n *  1. `unidentified` — the current id is missing/empty, or the provenance is\n *     not one of `fresh`/`restored`/`unknown`.\n *  2. `not-ready` — readiness is anything other than the literal string\n *     `'ready'` (this also catches `undefined`).\n *  3. `no-baseline` — no baseline id was ever recorded to compare against.\n *  4. `mismatch` — the baseline id and current id disagree.\n *  5. `match` — same incarnation.\n */\nexport function compareIncarnationBaseline(\n  baselineId: string | undefined,\n  current: FilesystemIncarnationLike,\n): IncarnationComparison {\n  const currentId = current.filesystemIncarnationId\n  const provenance = current.filesystemIncarnationProvenance\n  const isValidProvenance = provenance === 'fresh' || provenance === 'restored' || provenance === 'unknown'\n\n  if (typeof currentId !== 'string' || currentId.length === 0 || !isValidProvenance) {\n    return { verdict: 'unidentified' }\n  }\n\n  if (current.filesystemIncarnationReadiness !== 'ready') {\n    return { verdict: 'not-ready', readiness: current.filesystemIncarnationReadiness }\n  }\n\n  if (baselineId === undefined) {\n    return { verdict: 'no-baseline' }\n  }\n\n  if (baselineId !== currentId) {\n    return { verdict: 'mismatch', baselineId, currentId }\n  }\n\n  return { verdict: 'match' }\n}\n"],"mappings":";AAgCO,IAAM,+BAA+B;AAKrC,IAAM,wCAAwC;AA4C9C,SAAS,yBAAyB,OAOb;AAC1B,QAAM,eAAe,MAAM,QAAQ,gBAAgB;AACnD,QAAM,eAAe,MAAM,QAAQ,gBAAgB;AACnD,MAAI,CAAC,OAAO,SAAS,YAAY,KAAK,gBAAgB,KAAK,eAAe,GAAG;AAC3E,UAAM,IAAI;AAAA,MACR,6EAA6E,YAAY;AAAA,IAC3F;AAAA,EACF;AACA,MAAI,CAAC,OAAO,SAAS,YAAY,KAAK,eAAe,GAAG;AACtD,UAAM,IAAI;AAAA,MACR,wEAAwE,YAAY;AAAA,IACtF;AAAA,EACF;AACA,QAAM,gBAAgB,MAAM,iBAAiB;AAE7C,QAAM,eAAe,MAAM,cAAc;AACzC,QAAM,cAAc,IAAI,IAAI,MAAM,iBAAiB;AACnD,QAAM,mBAAmB,gBACrB,CAAC,GAAG,MAAM,aAAa,EAAE,KAAK,IAC9B,MAAM,cAAc,OAAO,CAAC,MAAM,YAAY,IAAI,CAAC,CAAC,EAAE,KAAK;AAC/D,QAAM,cAAc,iBAAiB;AACrC,QAAM,gBAAgB,eAAe,IAAI,cAAc,eAAe;AAEtE,QAAM,uBAAuB,iBAAiB,eAAe;AAC7D,QAAM,kBAAkB,cAAc,KAAK,gBAAgB;AAK3D,QAAM,qBAAqB,cAAc,KACpC,gBAAgB,gBAChB,iBAAiB;AAEtB,QAAM,SAAS,uBACV,mBACD,kBACG,cACD,qBACG,mBACD;AAER,SAAO;AAAA,IACL,SAAS,WAAW;AAAA,IACpB;AAAA,IACA;AAAA,IACA;AAAA,IACA;AAAA,IACA;AAAA,EACF;AACF;AAuCO,SAAS,2BACd,YACA,SACuB;AACvB,QAAM,YAAY,QAAQ;AAC1B,QAAM,aAAa,QAAQ;AAC3B,QAAM,oBAAoB,eAAe,WAAW,eAAe,cAAc,eAAe;AAEhG,MAAI,OAAO,cAAc,YAAY,UAAU,WAAW,KAAK,CAAC,mBAAmB;AACjF,WAAO,EAAE,SAAS,eAAe;AAAA,EACnC;AAEA,MAAI,QAAQ,mCAAmC,SAAS;AACtD,WAAO,EAAE,SAAS,aAAa,WAAW,QAAQ,+BAA+B;AAAA,EACnF;AAEA,MAAI,eAAe,QAAW;AAC5B,WAAO,EAAE,SAAS,cAAc;AAAA,EAClC;AAEA,MAAI,eAAe,WAAW;AAC5B,WAAO,EAAE,SAAS,YAAY,YAAY,UAAU;AAAA,EACtD;AAEA,SAAO,EAAE,SAAS,QAAQ;AAC5B;","names":[]}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tangle-network/agent-app",
-  "version": "0.44.58",
+  "version": "0.44.59",
   "packageManager": "pnpm@11.17.0",
   "description": "Build agent applications with typed chat, tools, sandboxes, integrations, billing, and evaluation.",
   "keywords": [
@@ -393,6 +393,11 @@
       "import": "./dist/vault/lazy.js",
       "default": "./dist/vault/lazy.js"
     },
+    "./vault/server": {
+      "types": "./dist/vault/server.d.ts",
+      "import": "./dist/vault/server.js",
+      "default": "./dist/vault/server.js"
+    },
     "./brand": {
       "types": "./dist/brand/index.d.ts",
       "import": "./dist/brand/index.js",