@tangle-network/agent-profile-materialize 0.20.7 → 0.20.9

package/dist/harness-prompt.d.ts

@@ -10,12 +10,8 @@ import type { HarnessId } from "./harness.js";
  * harness prompt to stay in force: that is what `appendSystemPrompt` means.
  * A host that replaced it with its own template would delete exactly what the
  * profile kept. On 2026-10-03 every Discovery research director ran under the
- * sandbox's app-builder template this way.
- *
- * Only a harness whose addition is a launch argument can carry the host's
- * context as an addition. claude-code is the one wired end to end through the
- * sidecar and the CLI adapter, so it is the only one listed. Every other
- * harness keeps the host's replacement, unchanged.
+ * sandbox's app-builder template this way: claude-code through
+ * `--system-prompt`, opencode through a generated primary agent.
  */
 export declare function keepsHarnessSystemPrompt(profile: AgentProfile | undefined, harness: HarnessId | string | undefined): boolean;
 /** Join prompt additions in order, skipping empty ones. */

package/dist/harness-prompt.js

@@ -1,3 +1,17 @@
+/**
+ * Harnesses whose adapter can carry a host's environment context as an
+ * ADDITION to the harness's own system prompt:
+ *
+ * - claude-code and pi: `--append-system-prompt`.
+ * - opencode: the addition file that opencode.json names in `instructions`
+ *   (OPENCODE_APPEND_SYSTEM_PROMPT_FILE). OpenCode's own prompt stays because
+ *   no profile primary agent replaces it.
+ * - codex: `developer_instructions`, which codex sends after its own base
+ *   instructions.
+ *
+ * Every other harness keeps the host's replacement, unchanged.
+ */
+const HARNESSES_WITH_ADDITIVE_HOST_PROMPT = new Set(["claude-code", "pi", "opencode", "codex"]);
 /**
  * Whether a run keeps the harness's own system prompt, so that a host's
  * environment context joins the profile's addition instead of replacing the
@@ -8,12 +22,8 @@
  * harness prompt to stay in force: that is what `appendSystemPrompt` means.
  * A host that replaced it with its own template would delete exactly what the
  * profile kept. On 2026-10-03 every Discovery research director ran under the
- * sandbox's app-builder template this way.
- *
- * Only a harness whose addition is a launch argument can carry the host's
- * context as an addition. claude-code is the one wired end to end through the
- * sidecar and the CLI adapter, so it is the only one listed. Every other
- * harness keeps the host's replacement, unchanged.
+ * sandbox's app-builder template this way: claude-code through
+ * `--system-prompt`, opencode through a generated primary agent.
  */
 export function keepsHarnessSystemPrompt(profile, harness) {
     const prompt = profile?.prompt;
@@ -21,7 +31,9 @@ export function keepsHarnessSystemPrompt(profile, harness) {
         return false;
     const declaresIntent = (prompt.instructions?.length ?? 0) > 0 ||
         prompt.appendSystemPrompt !== undefined;
-    return declaresIntent && harness === "claude-code";
+    return (declaresIntent &&
+        harness !== undefined &&
+        HARNESSES_WITH_ADDITIVE_HOST_PROMPT.has(harness));
 }
 /** Join prompt additions in order, skipping empty ones. */
 export function joinSystemPromptAdditions(...additions) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tangle-network/agent-profile-materialize",
-  "version": "0.20.7",
+  "version": "0.20.9",
   "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",
   "repository": {
@@ -25,8 +25,8 @@
     "dist"
   ],
   "devDependencies": {
-    "@tangle-network/agent-interface": "2.13.0",
-    "@tangle-network/agent-interface-current": "npm:@tangle-network/agent-interface@2.13.0",
+    "@tangle-network/agent-interface": "2.17.0",
+    "@tangle-network/agent-interface-current": "npm:@tangle-network/agent-interface@2.17.0",
     "@types/node": "25.6.0",
     "typescript": "^6.0.3",
     "vitest": "^4.1.11"