@tangle-network/agent-interface 0.46.1 → 0.47.0

package/dist/agent-execution-preparation.d.ts

@@ -81,7 +81,9 @@ export interface AgentExecutionPreparationReceipt {
     schemaVersion: 1;
     preparationId: string;
     requestDigest: Sha256Digest;
+    /** Canonical identity before executor overrides. */
     authoredProfileDigest: Sha256Digest;
+    /** Canonical identity after executor overrides. */
     effectiveProfileDigest: Sha256Digest;
     backend: string;
     harness: HarnessType;

package/dist/agent-profile.d.ts

@@ -339,13 +339,12 @@ export interface AgentProfile {
      * Preferred execution harness for this profile — the coding-CLI runtime that
      * materializes and runs it (`claude-code`, `codex`, `opencode`, `pi`, …).
      *
-     * This is an optional PREFERENCE, not part of profile IDENTITY: the same
-     * profile still runs on any harness, and an executor MAY override it (e.g. the
-     * leaderboard's `harness × model` axis sweeps a profile across every harness,
-     * and a supervisor spawning a worker may pick a harness per subtask). When
-     * unset, the caller/executor chooses. Formalizes what runtimes already read as
-     * `profile.harness`; making it typed also lets an improvement loop optimize
-     * harness routing as a first-class lever.
+     * This optional authored preference participates in canonical profile
+     * identity. An executor MAY override it for one run; the effective profile and
+     * execution receipt then bind that override without changing what was
+     * authored. When unset, the caller/executor chooses. Formalizes what runtimes
+     * already read as `profile.harness`; making it typed also lets an improvement
+     * loop optimize harness routing as a first-class lever.
      */
     harness?: HarnessType;
     permissions?: Record<string, AgentProfilePermission>;

package/dist/harness.d.ts

@@ -2,13 +2,12 @@ import { z } from "zod";
 /**
  * The execution runner for an agent — WHICH runtime materializes and runs an `AgentProfile`.
  *
- * Harness is an EXECUTION concern, not part of profile IDENTITY: the same `AgentProfile`
- * (prompt/model/skills/tools/mcp/subagents) runs on any harness. A profile MAY carry an optional
- * `harness` PREFERENCE (`AgentProfile.harness`), but the caller/executor can always override it per
- * run — the leaderboard's `harness × model` axis sweeps one profile across every harness, and a
- * supervisor may pick a harness per spawned worker. This is the single shared enum every layer
- * references instead of keeping its own copy (session control, the profile materializer, the
- * cli-bridge backends, VB profile specs).
+ * This enum describes an EXECUTION concern. When an `AgentProfile` authors a `harness`
+ * preference, that field participates in its canonical identity like every other parsed profile
+ * field. A caller or executor may override the preference for one run, but the execution receipt
+ * preserves the authored identity, effective identity, and selected harness separately. This is
+ * the single shared enum every layer references instead of keeping its own copy (session control,
+ * the profile materializer, the cli-bridge backends, VB profile specs).
  *
  * `cli-base` is the router-backed mode — a plain multi-turn router call (a reviewer, a cheap judge,
  * a one-shot) with no full coding-agent harness. The rest are full agentic harnesses run in a

package/dist/profile-schema.d.ts

@@ -490,6 +490,18 @@ export declare const agentProfileSchema: z.ZodObject<{
     metadata: z.ZodOptional<z.ZodType<Record<string, unknown>, unknown, z.core.$ZodTypeInternals<Record<string, unknown>, unknown>>>;
     extensions: z.ZodOptional<z.ZodType<Record<string, Record<string, unknown> | undefined>, unknown, z.core.$ZodTypeInternals<Record<string, Record<string, unknown> | undefined>, unknown>>>;
 }, z.core.$strict>;
+/**
+ * Model-facing JSON Schema for an authored {@link AgentProfile}.
+ *
+ * This is generated from {@link agentProfileSchema}'s input contract rather
+ * than restating the profile shape. Zod sees encoded record keys at its
+ * preprocessing boundary, so the generated `propertyNames` constraints for
+ * that internal encoding are removed before exposing the schema to callers.
+ * The root dialect declaration is also omitted because tool APIs embed this
+ * value as a subschema rather than serving it as a standalone document.
+ * Runtime admission remains the canonical Zod validator above.
+ */
+export declare const agentProfileJsonSchema: z.core.JSONSchema.JSONSchema;
 export declare const agentProfileDiffSchema: z.ZodType<AgentProfileDiff>;
 /**
  * A registered capability: a stable id paired with its canonical

package/dist/profile-schema.js

@@ -315,6 +315,50 @@ export const agentProfileSchema = z
     .superRefine((profile, context) => {
     validateNestedRecordKeys(profile, context, [], new Set());
 });
+const encodedRecordKeyPattern = "^u(?:[0-9a-f]{4})*$";
+function isEncodedRecordKeyPropertyNames(value) {
+    if (value === null || typeof value !== "object" || Array.isArray(value)) {
+        return false;
+    }
+    const propertyNames = value;
+    return (propertyNames.type === "string" &&
+        propertyNames.pattern === encodedRecordKeyPattern);
+}
+function removeModelInputSchemaArtifacts(value) {
+    if (Array.isArray(value)) {
+        return value.map(removeModelInputSchemaArtifacts);
+    }
+    if (value === null || typeof value !== "object") {
+        return value;
+    }
+    const result = {};
+    for (const [key, entry] of Object.entries(value)) {
+        if (key === "$schema") {
+            continue;
+        }
+        if (key === "propertyNames" && isEncodedRecordKeyPropertyNames(entry)) {
+            continue;
+        }
+        result[key] = removeModelInputSchemaArtifacts(entry);
+    }
+    return result;
+}
+/**
+ * Model-facing JSON Schema for an authored {@link AgentProfile}.
+ *
+ * This is generated from {@link agentProfileSchema}'s input contract rather
+ * than restating the profile shape. Zod sees encoded record keys at its
+ * preprocessing boundary, so the generated `propertyNames` constraints for
+ * that internal encoding are removed before exposing the schema to callers.
+ * The root dialect declaration is also omitted because tool APIs embed this
+ * value as a subschema rather than serving it as a standalone document.
+ * Runtime admission remains the canonical Zod validator above.
+ */
+export const agentProfileJsonSchema = removeModelInputSchemaArtifacts(z.toJSONSchema(agentProfileSchema, {
+    target: "draft-2020-12",
+    io: "input",
+    unrepresentable: "any",
+}));
 function validateNestedRecordKeys(value, context, path, seen) {
     if (value === null || typeof value !== "object" || seen.has(value))
         return;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tangle-network/agent-interface",
-  "version": "0.46.1",
+  "version": "0.47.0",
   "type": "module",
   "sideEffects": false,
   "license": "MIT",