@tangle-network/agent-profile-materialize 0.10.3 → 0.12.0

package/dist/model-id.d.ts

@@ -0,0 +1,42 @@
+/**
+ * The one canonicalization of a model id, shared by everything that writes a
+ * model id into an {@link AgentProfile} and everything that later compares one
+ * against it.
+ *
+ * A model id is qualified by prepending provider segments, and the same model
+ * is legitimately spelled at more than one qualification level as it travels:
+ * the caller sends `{ provider: "openai-compat", model: "deepseek/deepseek-v4-flash" }`,
+ * the profile records the qualified `openai-compat/deepseek/deepseek-v4-flash`,
+ * and the CLI is spawned with that qualified form. Two spellings, one model.
+ *
+ * Every writer and every reader must run both sides through here, so a
+ * comparison cannot mistake two spellings of one model for a conflict. Two
+ * independent copies of this rule are exactly how that bug arises.
+ */
+/**
+ * Qualify `modelId` with `provider` — the canonical form of a model id.
+ *
+ * The already-qualified check is prefix-SPECIFIC rather than "already contains
+ * a slash": a router slug legitimately carries an upstream segment of its own
+ * (`deepseek/deepseek-v4-flash`, `zai/glm-4.7`), so a generic slash test would
+ * leave those unqualified, while an unconditional prefix would double-qualify
+ * an id that has already been through here.
+ *
+ * Idempotent by construction:
+ * `qualifyModelId(p, qualifyModelId(p, m)) === qualifyModelId(p, m)`.
+ */
+export declare function qualifyModelId<T extends string | undefined>(provider: string | undefined, modelId: T): T;
+/**
+ * Do two model ids name the same model?
+ *
+ * Both operands are qualified by `provider` before comparison, so the
+ * qualification level a caller happened to use is not a difference. Two
+ * different model names are still different — this narrows a comparison to the
+ * model's identity, it does not make the comparison permissive.
+ *
+ * `provider` is optional because a profile may carry a `model.default` that was
+ * qualified by a writer which did not also record `model.provider`. With no
+ * provider to qualify by, a bare id and its single-segment-qualified spelling
+ * are still the same model, which is the only tolerance the undeclared case gets.
+ */
+export declare function modelIdsMatch(a: string | undefined, b: string | undefined, provider?: string): boolean;

package/dist/model-id.js

@@ -0,0 +1,59 @@
+/**
+ * The one canonicalization of a model id, shared by everything that writes a
+ * model id into an {@link AgentProfile} and everything that later compares one
+ * against it.
+ *
+ * A model id is qualified by prepending provider segments, and the same model
+ * is legitimately spelled at more than one qualification level as it travels:
+ * the caller sends `{ provider: "openai-compat", model: "deepseek/deepseek-v4-flash" }`,
+ * the profile records the qualified `openai-compat/deepseek/deepseek-v4-flash`,
+ * and the CLI is spawned with that qualified form. Two spellings, one model.
+ *
+ * Every writer and every reader must run both sides through here, so a
+ * comparison cannot mistake two spellings of one model for a conflict. Two
+ * independent copies of this rule are exactly how that bug arises.
+ */
+/**
+ * Qualify `modelId` with `provider` — the canonical form of a model id.
+ *
+ * The already-qualified check is prefix-SPECIFIC rather than "already contains
+ * a slash": a router slug legitimately carries an upstream segment of its own
+ * (`deepseek/deepseek-v4-flash`, `zai/glm-4.7`), so a generic slash test would
+ * leave those unqualified, while an unconditional prefix would double-qualify
+ * an id that has already been through here.
+ *
+ * Idempotent by construction:
+ * `qualifyModelId(p, qualifyModelId(p, m)) === qualifyModelId(p, m)`.
+ */
+export function qualifyModelId(provider, modelId) {
+    if (!provider || !modelId)
+        return modelId;
+    if (modelId === provider || modelId.startsWith(`${provider}/`))
+        return modelId;
+    return `${provider}/${modelId}`;
+}
+/**
+ * Do two model ids name the same model?
+ *
+ * Both operands are qualified by `provider` before comparison, so the
+ * qualification level a caller happened to use is not a difference. Two
+ * different model names are still different — this narrows a comparison to the
+ * model's identity, it does not make the comparison permissive.
+ *
+ * `provider` is optional because a profile may carry a `model.default` that was
+ * qualified by a writer which did not also record `model.provider`. With no
+ * provider to qualify by, a bare id and its single-segment-qualified spelling
+ * are still the same model, which is the only tolerance the undeclared case gets.
+ */
+export function modelIdsMatch(a, b, provider) {
+    if (a === b)
+        return true;
+    if (a === undefined || b === undefined)
+        return false;
+    if (qualifyModelId(provider, a) === qualifyModelId(provider, b))
+        return true;
+    if (provider)
+        return false;
+    return ((!a.includes("/") && b.endsWith(`/${a}`)) ||
+        (!b.includes("/") && a.endsWith(`/${b}`)));
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tangle-network/agent-profile-materialize",
-  "version": "0.10.3",
+  "version": "0.12.0",
   "description": "Materialize an AgentProfile into the native per-harness workspace files (the one shared materializer for cli-bridge, agent-dev-container, and VB).",
   "type": "module",
   "main": "./dist/index.js",
@@ -20,13 +20,13 @@
     "dist"
   ],
   "devDependencies": {
-    "@tangle-network/agent-interface": "0.43.1",
+    "@tangle-network/agent-interface": "0.45.0",
     "@types/node": "25.6.0",
     "typescript": "^6.0.3",
     "vitest": "^4.1.10"
   },
   "peerDependencies": {
-    "@tangle-network/agent-interface": ">=0.38.0 <0.44.0"
+    "@tangle-network/agent-interface": ">=0.45.0 <0.46.0"
   },
   "scripts": {
     "build": "tsc -p tsconfig.json",