@tangle-network/agent-profile-materialize 1.1.6 → 1.1.8

package/dist/harness.d.ts

@@ -1,131 +0,0 @@
-export declare const MATERIALIZER_HARNESSES: readonly ["claude-code", "nanoclaw", "codex", "opencode", "kimi-code", "pi", "prime", "gemini", "hermes", "openclaw"];
-export type HarnessId = (typeof MATERIALIZER_HARNESSES)[number];
-export declare function isMaterializerHarness(harness: string): harness is HarnessId;
-export declare function assertMaterializerHarness(harness: string): asserts harness is HarnessId;
-export declare const CODEX_SYSTEM_PROMPT_FILE = ".codex/system-prompt.md";
-export declare const OPENCODE_APPEND_SYSTEM_PROMPT_FILE = ".opencode/agent-system-prompt.md";
-export declare const OPENCODE_CONFIG_FILE = "opencode.json";
-export declare const OPENCODE_CONFIG_SCHEMA = "https://opencode.ai/config.json";
-export declare const OPENCODE_PRIMARY_AGENT_PREFIX = "tangle-profile-";
-export declare const CLAUDE_SETTINGS_PATH = ".tangle/claude-settings.json";
-/** Whether the shared materializer may place its context file in the harness agent directory. */
-export declare function harnessAutoLoadsAgentContextFile(harness: HarnessId): boolean;
-/**
- * Why a harness refuses a system-prompt REPLACEMENT.
- *
- * The reason names the control that does exist, so the refusal is actionable
- * without a capability-matrix lookup — a bare "unsupported" sends the caller
- * looking for a flag that was never there.
- */
-export declare function systemPromptRefusal(harness: HarnessId): string;
-/**
- * Why a harness refuses an ADDITION to the system prompt.
- *
- * gemini puts its context file in the system-prompt position, so the temptation
- * is to lower an addition there. That is refused because GEMINI.md is the ONE
- * file it auto-loads: an addition written there is byte-identical to the same
- * text under `prompt.instructions`, and no consumer could tell which intent the
- * caller expressed. opencode is not refused for the same situation, because it
- * loads exactly the files its config names and can therefore carry the two
- * intents in separate, separately-ordered files.
- */
-export declare function appendSystemPromptRefusal(harness: HarnessId): string;
-/** Project context file each harness actually reads from cwd. NEVER a constant. */
-export declare const CONTEXT_FILE: Record<HarnessId, string>;
-/**
- * The paths a profile resource may never mount.
- *
- * Codex names no system-prompt file of its own — `model_instructions_file`
- * takes whatever path it is given — and opencode names none either, since it
- * reads exactly the files its config lists. All three names below were chosen
- * here, so a file already at one of them is this materializer's own output from
- * an earlier application into the same workspace, and a mount there could not
- * survive the next application.
- *
- * That is an inference from the path name, not verified provenance: nothing
- * checks the existing bytes are prior materializer output, so a workspace that
- * carried a foreign file at one of these invented names is overwritten on the
- * first application. Accepted cost of stateless multi-turn re-application,
- * bounded by the names being ones no harness or user convention uses.
- */
-export declare const MATERIALIZER_RESERVED_PATHS: ReadonlySet<string>;
-/**
- * The context files this package owns by MARKER rather than by name:
- * `AGENTS.md`, `CLAUDE.md`, `GEMINI.md`, `HERMES.md`.
- *
- * Each is a documented name a repository can already carry, so the name proves
- * nothing. A generated one carries the line {@link markMaterializerContextFile}
- * writes, and only that line lets the next materialization replace it.
- *
- * opencode's context file is absent because it is a RESERVED name this package
- * invented, already owned by the name alone.
- */
-export declare const MATERIALIZER_CONTEXT_PATHS: ReadonlySet<string>;
-/** Mark one generated native agent file without changing its harness meaning. */
-export declare function markMaterializerSubagent(relPath: string, content: string): string;
-/**
- * Mark one generated context file so the NEXT materialization can prove this
- * package wrote the bytes it is about to replace.
- *
- * The marker is an HTML comment on line 1. CommonMark closes an HTML block at
- * the line holding `-->`, so every instruction below it parses exactly as it
- * did without the line, and the line itself states no instruction. It is one
- * more line this package composes into a file it already composes: it goes on
- * a context file, which carries `prompt.instructions`, and NEVER on a
- * system-prompt REPLACEMENT, whose bytes are the caller's exact text
- * (`.gemini/system.md`; `.codex/system-prompt.md` is a reserved name this
- * package invented and needs no marker to be owned).
- *
- * It carries the digest of the generated body below it, which the subagent
- * marker does not need. `CLAUDE.md` is claude-code's own memory file and the
- * agent appends to it mid-session, so a bare marker would still sit on line 1
- * of a file the agent has since rewritten. The digest tells which leading bytes
- * are still this package's own: the next materialization replaces exactly
- * those and keeps what the agent appended below them
- * ({@link generatedContextAppendix}). The marker's wording is part of every
- * marker already written into live workspaces, so it stays as it is.
- *
- * A reserved context path — opencode's invented instruction file — is returned
- * unchanged: its NAME already proves the provenance, and nothing else may mount
- * there.
- */
-export declare function markMaterializerContextFile(relPath: string, content: string): string;
-/**
- * Whether a generated file occupies a path that the profile materializer owns.
- *
- * Generated native agent files and generated context files come from the active
- * profile.
- * The active profile must replace the prior profile version at the same path.
- * Otherwise, a profile update stops every resumed session before launch.
- * Explicit resources at these paths stay shared.
- * The plan builder applies ownership only when the source is `generated`.
- * An output marker proves ownership before replacement.
- */
-export declare function isMaterializerOwnedPath(relPath: string): boolean;
-/**
- * The bytes to publish at owned path `relPath` over the file already there, or
- * `undefined` when that file is not this package's earlier output and must be
- * refused (`undefined` content: no regular file there). For a context file the
- * replacement is the planned file followed by whatever the agent appended
- * below the generated body (claude-code appends its memory to `CLAUDE.md`). A
- * body written before the marker existed is adopted once, only when it is
- * byte-identical to the body this plan writes.
- */
-export declare function materializerReplacement(relPath: string, content: () => string | undefined, plannedContent: string): string | undefined;
-/**
- * cwd-relative native skill dir per harness, or null if the harness has no
- * cwd skill primitive (skills live in a user/global dir the workspace plan
- * cannot reach). Public so consumers composing a profile can (a) render the
- * exact path the platform will mount a skill at into their prompts instead
- * of hardcoding `~/.claude/skills/...`, and (b) branch on skill support
- * ahead of materialization instead of catching the materialize-time throw.
- */
-export declare const HARNESS_SKILL_DIRS: Readonly<Record<HarnessId, string | null>>;
-/**
- * Resolve the cwd-relative directory `resources.skills` refs materialize
- * into on `harness`. `null` means the harness cannot receive cwd skills, the
- * same condition that surfaces as an `unsupported`
- * "skills" entry (and an {@link assertWorkspacePlanSupported} throw) at
- * materialize time, exposed here as branchable data.
- */
-export declare function skillDirForHarness(harness: HarnessId): string | null;

package/dist/harness.js

@@ -1,416 +0,0 @@
-export const MATERIALIZER_HARNESSES = [
-    "claude-code",
-    "nanoclaw",
-    "codex",
-    "opencode",
-    "kimi-code",
-    "pi",
-    "prime",
-    "gemini",
-    "hermes",
-    "openclaw",
-];
-const MATERIALIZER_HARNESS_SET = new Set(MATERIALIZER_HARNESSES);
-export function isMaterializerHarness(harness) {
-    return MATERIALIZER_HARNESS_SET.has(harness);
-}
-export function assertMaterializerHarness(harness) {
-    if (!isMaterializerHarness(harness)) {
-        throw new Error(`Unsupported profile materialization harness "${harness}"`);
-    }
-}
-export const CODEX_SYSTEM_PROMPT_FILE = ".codex/system-prompt.md";
-export const OPENCODE_APPEND_SYSTEM_PROMPT_FILE = ".opencode/agent-system-prompt.md";
-export const OPENCODE_CONFIG_FILE = "opencode.json";
-export const OPENCODE_CONFIG_SCHEMA = "https://opencode.ai/config.json";
-export const OPENCODE_PRIMARY_AGENT_PREFIX = "tangle-profile-";
-export const CLAUDE_SETTINGS_PATH = ".tangle/claude-settings.json";
-/** Whether the shared materializer may place its context file in the harness agent directory. */
-export function harnessAutoLoadsAgentContextFile(harness) {
-    assertMaterializerHarness(harness);
-    // Prime uses the fork-specific materializePrimeProfileControls path. It
-    // does not consume the shared agent-root plan produced by this predicate.
-    return harness === "pi";
-}
-/**
- * Why a harness refuses a system-prompt REPLACEMENT.
- *
- * The reason names the control that does exist, so the refusal is actionable
- * without a capability-matrix lookup — a bare "unsupported" sends the caller
- * looking for a flag that was never there.
- */
-export function systemPromptRefusal(harness) {
-    switch (harness) {
-        case "opencode":
-            // The control exists, so the reason names the two declarations that reach
-            // it rather than claiming opencode has none.
-            return 'opencode: the only system-prompt replacement is per-agent (`agent.<name>.prompt`), which binds to the agent selected at launch and a workspace plan cannot guarantee; an executor that applies the plan\'s "--agent" flag to its own spawn declares binds: ["systemPrompt"], and one that composes opencode\'s config itself declares binds: ["opencode.agent-prompt"]';
-        default:
-            return `${harness}: no verified exact system-prompt replacement control`;
-    }
-}
-/**
- * Why a harness refuses an ADDITION to the system prompt.
- *
- * gemini puts its context file in the system-prompt position, so the temptation
- * is to lower an addition there. That is refused because GEMINI.md is the ONE
- * file it auto-loads: an addition written there is byte-identical to the same
- * text under `prompt.instructions`, and no consumer could tell which intent the
- * caller expressed. opencode is not refused for the same situation, because it
- * loads exactly the files its config names and can therefore carry the two
- * intents in separate, separately-ordered files.
- */
-export function appendSystemPromptRefusal(harness) {
-    switch (harness) {
-        case "gemini":
-            return "gemini: the only additive system-prompt channel is GEMINI.md memory, the single context file it auto-loads, which `prompt.instructions` already materializes — use it instead";
-        case "codex":
-            return "codex: no verified additive system-prompt control — its AGENTS.md lands in a developer/user message, not the system channel";
-        default:
-            return `${harness}: no verified additive system-prompt control`;
-    }
-}
-/** Project context file each harness actually reads from cwd. NEVER a constant. */
-export const CONTEXT_FILE = {
-    "claude-code": "CLAUDE.md",
-    nanoclaw: "CLAUDE.md",
-    codex: "AGENTS.md",
-    opencode: ".opencode/profile-instructions.md",
-    "kimi-code": "AGENTS.md",
-    pi: "AGENTS.md",
-    // prime (PrimeIntellect-ai/prime-agent v0.7.0, be9e2fa0) walks cwd and its
-    // ancestors for AGENTS.md/CLAUDE.md, cwd first (fork resource-loader.ts:59
-    // candidates, :94-109 walk from cwd inside loadProjectContextFiles).
-    prime: "AGENTS.md",
-    gemini: "GEMINI.md", // current default; AGENTS.md only via .gemini/settings.json context.fileName
-    hermes: "HERMES.md", // highest-priority native name; only ONE context loads (first match)
-    openclaw: "AGENTS.md",
-};
-/**
- * The paths a profile resource may never mount.
- *
- * Codex names no system-prompt file of its own — `model_instructions_file`
- * takes whatever path it is given — and opencode names none either, since it
- * reads exactly the files its config lists. All three names below were chosen
- * here, so a file already at one of them is this materializer's own output from
- * an earlier application into the same workspace, and a mount there could not
- * survive the next application.
- *
- * That is an inference from the path name, not verified provenance: nothing
- * checks the existing bytes are prior materializer output, so a workspace that
- * carried a foreign file at one of these invented names is overwritten on the
- * first application. Accepted cost of stateless multi-turn re-application,
- * bounded by the names being ones no harness or user convention uses.
- */
-export const MATERIALIZER_RESERVED_PATHS = new Set([
-    CODEX_SYSTEM_PROMPT_FILE,
-    OPENCODE_APPEND_SYSTEM_PROMPT_FILE,
-    CONTEXT_FILE.opencode,
-]);
-/** Every path any harness reads as its project context file. */
-const CONTEXT_FILE_PATHS = new Set(Object.values(CONTEXT_FILE));
-/**
- * The context files this package owns by MARKER rather than by name:
- * `AGENTS.md`, `CLAUDE.md`, `GEMINI.md`, `HERMES.md`.
- *
- * Each is a documented name a repository can already carry, so the name proves
- * nothing. A generated one carries the line {@link markMaterializerContextFile}
- * writes, and only that line lets the next materialization replace it.
- *
- * opencode's context file is absent because it is a RESERVED name this package
- * invented, already owned by the name alone.
- */
-export const MATERIALIZER_CONTEXT_PATHS = new Set([...CONTEXT_FILE_PATHS].filter((path) => !MATERIALIZER_RESERVED_PATHS.has(path)));
-/**
- * The paths whose generated content is wholly this package's output, per
- * {@link PlanFile.ownership}: the reserved names, the context files, and
- * `opencode.json`, which carries only the registrations this package generates
- * from the profile.
- *
- * `opencode.json` and every context file is a documented name a user repository
- * can carry, so the name alone proves nothing and a profile resource may still
- * mount one. An existing file there is replaced only when
- * {@link materializerReplacement} recognizes its bytes as this package's own
- * earlier output.
- *
- * Deliberately absent: `.gemini/system.md`, the file `prompt.systemPrompt`
- * lowers to. The line a marker would have to add is the reason. A REPLACEMENT
- * is the caller's exact bytes and this package may add none of its own, so that
- * path keeps refusing. A context file carries `prompt.instructions`, which this
- * package already composes — it joins the blocks and appends the final newline
- * — so one more composed line is inside the same authority.
- *
- * That line, not "which channel the harness reads it on", is what separates the
- * two. `GEMINI.md` is owned even though gemini lowers its context file into the
- * system-prompt position as an ADDITION ({@link appendSystemPromptRefusal}),
- * because the intent it carries is still instructions this package composed.
- */
-const MATERIALIZER_OWNED_PATHS = new Set([
-    ...MATERIALIZER_RESERVED_PATHS,
-    ...MATERIALIZER_CONTEXT_PATHS,
-    OPENCODE_CONFIG_FILE,
-]);
-const MATERIALIZER_SUBAGENT_PATH = /^(?:(?:\.claude|\.opencode|\.gemini)\/agents\/[a-z0-9][a-z0-9_-]*\.md|\.codex\/agents\/[a-z0-9][a-z0-9_-]*\.toml)$/u;
-/** The one provenance token every generated-file marker carries. */
-const MATERIALIZER_MARKER = "tangle-agent-profile-materialize: generated";
-const MATERIALIZER_SUBAGENT_MARKER = `# ${MATERIALIZER_MARKER}`;
-const MATERIALIZER_CONTEXT_MARKER_NOTE = "do not edit; the next profile materialization replaces this file";
-function materializerSubagentMarkerPrefix(relPath) {
-    return relPath.endsWith(".toml")
-        ? `${MATERIALIZER_SUBAGENT_MARKER}\n`
-        : `---\n${MATERIALIZER_SUBAGENT_MARKER}\n`;
-}
-/** Mark one generated native agent file without changing its harness meaning. */
-export function markMaterializerSubagent(relPath, content) {
-    if (!MATERIALIZER_SUBAGENT_PATH.test(relPath)) {
-        throw new Error(`Not a native agent path: ${relPath}`);
-    }
-    if (relPath.endsWith(".toml")) {
-        return `${materializerSubagentMarkerPrefix(relPath)}${content}`;
-    }
-    if (!content.startsWith("---\n")) {
-        throw new Error(`Native Markdown agent has no frontmatter: ${relPath}`);
-    }
-    return `${materializerSubagentMarkerPrefix(relPath)}${content.slice(4)}`;
-}
-/** The marker line a generated context file whose body is `body` carries. */
-function materializerContextMarker(body) {
-    const digest = createHash("sha256").update(body, "utf8").digest("hex");
-    return `<!-- ${MATERIALIZER_MARKER} sha256:${digest}; ${MATERIALIZER_CONTEXT_MARKER_NOTE} -->`;
-}
-/**
- * Mark one generated context file so the NEXT materialization can prove this
- * package wrote the bytes it is about to replace.
- *
- * The marker is an HTML comment on line 1. CommonMark closes an HTML block at
- * the line holding `-->`, so every instruction below it parses exactly as it
- * did without the line, and the line itself states no instruction. It is one
- * more line this package composes into a file it already composes: it goes on
- * a context file, which carries `prompt.instructions`, and NEVER on a
- * system-prompt REPLACEMENT, whose bytes are the caller's exact text
- * (`.gemini/system.md`; `.codex/system-prompt.md` is a reserved name this
- * package invented and needs no marker to be owned).
- *
- * It carries the digest of the generated body below it, which the subagent
- * marker does not need. `CLAUDE.md` is claude-code's own memory file and the
- * agent appends to it mid-session, so a bare marker would still sit on line 1
- * of a file the agent has since rewritten. The digest tells which leading bytes
- * are still this package's own: the next materialization replaces exactly
- * those and keeps what the agent appended below them
- * ({@link generatedContextAppendix}). The marker's wording is part of every
- * marker already written into live workspaces, so it stays as it is.
- *
- * A reserved context path — opencode's invented instruction file — is returned
- * unchanged: its NAME already proves the provenance, and nothing else may mount
- * there.
- */
-export function markMaterializerContextFile(relPath, content) {
-    if (!CONTEXT_FILE_PATHS.has(relPath)) {
-        throw new Error(`Not a harness context file: ${relPath}`);
-    }
-    if (!MATERIALIZER_CONTEXT_PATHS.has(relPath))
-        return content;
-    return `${materializerContextMarker(content)}\n${content}`;
-}
-const MATERIALIZER_CONTEXT_MARKER_HEAD = `<!-- ${MATERIALIZER_MARKER} sha256:`;
-const MATERIALIZER_CONTEXT_MARKER_TAIL = `; ${MATERIALIZER_CONTEXT_MARKER_NOTE} -->`;
-const SHA256_HEX = /^[0-9a-f]{64}$/u;
-/**
- * Text an agent appended below this package's generated context body: `""`
- * for exact output, `undefined` when no marker is on line 1 or no leading part
- * of the body matches its digest (an edit inside the generated part). Each
- * line boundary is a candidate end; one incremental hash walks the body once.
- */
-function generatedContextAppendix(existing) {
-    const lineEnd = existing.indexOf("\n");
-    if (lineEnd === -1)
-        return undefined;
-    const marker = existing.slice(0, lineEnd);
-    if (!marker.startsWith(MATERIALIZER_CONTEXT_MARKER_HEAD) ||
-        !marker.endsWith(MATERIALIZER_CONTEXT_MARKER_TAIL)) {
-        return undefined;
-    }
-    const digest = marker.slice(MATERIALIZER_CONTEXT_MARKER_HEAD.length, marker.length - MATERIALIZER_CONTEXT_MARKER_TAIL.length);
-    if (!SHA256_HEX.test(digest))
-        return undefined;
-    const body = existing.slice(lineEnd + 1);
-    // No cut at 0: a generated body is never empty, so it never adopts a whole file.
-    const boundaries = [];
-    for (let newline = body.indexOf("\n"); newline !== -1; newline = body.indexOf("\n", newline + 1)) {
-        boundaries.push(newline, newline + 1);
-    }
-    if (boundaries.length === 0 ||
-        boundaries[boundaries.length - 1] !== body.length) {
-        boundaries.push(body.length);
-    }
-    const hash = createHash("sha256");
-    let hashed = 0;
-    for (const end of boundaries) {
-        hash.update(body.slice(hashed, end), "utf8");
-        hashed = end;
-        if (hash.copy().digest("hex") === digest)
-            return body.slice(end);
-    }
-    return undefined;
-}
-/** The planned context file, then the agent's appended text on its own line. */
-function withContextAppendix(plannedContent, appendix) {
-    if (appendix === "" ||
-        plannedContent.endsWith("\n") ||
-        appendix.startsWith("\n")) {
-        return `${plannedContent}${appendix}`;
-    }
-    return `${plannedContent}\n${appendix}`;
-}
-/**
- * Whether a generated file occupies a path that the profile materializer owns.
- *
- * Generated native agent files and generated context files come from the active
- * profile.
- * The active profile must replace the prior profile version at the same path.
- * Otherwise, a profile update stops every resumed session before launch.
- * Explicit resources at these paths stay shared.
- * The plan builder applies ownership only when the source is `generated`.
- * An output marker proves ownership before replacement.
- */
-export function isMaterializerOwnedPath(relPath) {
-    return (MATERIALIZER_OWNED_PATHS.has(relPath) ||
-        MATERIALIZER_SUBAGENT_PATH.test(relPath));
-}
-/** The top-level keys this package writes into `opencode.json`. */
-const OPENCODE_CONFIG_KEYS = new Set([
-    "$schema",
-    "instructions",
-    "mcp",
-    "tools",
-    "permission",
-]);
-/**
- * The bytes to publish at owned path `relPath` over the file already there, or
- * `undefined` when that file is not this package's earlier output and must be
- * refused (`undefined` content: no regular file there). For a context file the
- * replacement is the planned file followed by whatever the agent appended
- * below the generated body (claude-code appends its memory to `CLAUDE.md`). A
- * body written before the marker existed is adopted once, only when it is
- * byte-identical to the body this plan writes.
- */
-export function materializerReplacement(relPath, content, plannedContent) {
-    if (!MATERIALIZER_CONTEXT_PATHS.has(relPath)) {
-        return isMaterializerOutput(relPath, content, plannedContent)
-            ? plannedContent
-            : undefined;
-    }
-    const existing = content();
-    if (existing === undefined)
-        return undefined;
-    const appendix = generatedContextAppendix(existing);
-    if (appendix === "")
-        return plannedContent;
-    // Appended text rides only on a marked plan, which the next version recognizes.
-    if (generatedContextAppendix(plannedContent) !== "")
-        return undefined;
-    if (appendix !== undefined) {
-        return withContextAppendix(plannedContent, appendix);
-    }
-    return existing === plannedContent.slice(plannedContent.indexOf("\n") + 1)
-        ? plannedContent
-        : undefined;
-}
-/**
- * Whether the file already at owned path `relPath`, other than a context file,
- * is this package's own earlier output. A reserved name proves that by itself.
- * Native agent files require the generated marker. An exact unmarked copy of
- * the planned native agent file is adopted once for upgrades from materializer
- * versions without that marker. `undefined` content means no regular file is
- * there.
- *
- * An `opencode.json` this package wrote holds the opencode schema id, only the
- * keys this package writes, and only instruction paths this package invented;
- * a user config holding nothing else is replaced too, any other key or own
- * instruction path is refused.
- */
-function isMaterializerOutput(relPath, content, plannedContent) {
-    if (MATERIALIZER_RESERVED_PATHS.has(relPath))
-        return true;
-    if (relPath === ".pi/mcp.json" || relPath === ".kimi-code/mcp.json")
-        return isMaterializerMcpConfig(relPath, content);
-    if (MATERIALIZER_SUBAGENT_PATH.test(relPath)) {
-        const existing = content();
-        if (existing === undefined)
-            return false;
-        const markerPrefix = materializerSubagentMarkerPrefix(relPath);
-        if (existing.startsWith(markerPrefix))
-            return true;
-        if (!plannedContent.startsWith(markerPrefix))
-            return false;
-        const legacyContent = relPath.endsWith(".toml")
-            ? plannedContent.slice(markerPrefix.length)
-            : `---\n${plannedContent.slice(markerPrefix.length)}`;
-        return existing === legacyContent;
-    }
-    if (relPath !== OPENCODE_CONFIG_FILE)
-        return false;
-    const bytes = content();
-    if (bytes === undefined)
-        return false;
-    let parsed;
-    try {
-        parsed = JSON.parse(bytes);
-    }
-    catch {
-        return false;
-    }
-    if (parsed === null || typeof parsed !== "object" || Array.isArray(parsed)) {
-        return false;
-    }
-    const config = parsed;
-    if (config.$schema !== OPENCODE_CONFIG_SCHEMA)
-        return false;
-    if (!Object.keys(config).every((key) => OPENCODE_CONFIG_KEYS.has(key))) {
-        return false;
-    }
-    const instructions = config.instructions;
-    if (instructions === undefined)
-        return true;
-    return (Array.isArray(instructions) &&
-        instructions.every((entry) => entry === OPENCODE_APPEND_SYSTEM_PROMPT_FILE ||
-            entry === CONTEXT_FILE.opencode));
-}
-/**
- * cwd-relative native skill dir per harness, or null if the harness has no
- * cwd skill primitive (skills live in a user/global dir the workspace plan
- * cannot reach). Public so consumers composing a profile can (a) render the
- * exact path the platform will mount a skill at into their prompts instead
- * of hardcoding `~/.claude/skills/...`, and (b) branch on skill support
- * ahead of materialization instead of catching the materialize-time throw.
- */
-export const HARNESS_SKILL_DIRS = {
-    "claude-code": ".claude/skills",
-    nanoclaw: ".claude/skills",
-    codex: ".codex/skills",
-    opencode: ".opencode/skills",
-    "kimi-code": ".kimi/skills",
-    pi: ".pi/skills",
-    // prime auto-discovers project skills from <cwd>/<configDir>/skills where the
-    // fork ships configDir ".prime/agent" (fork package.json piConfig, config.ts:494;
-    // package-manager.ts:885 projectBaseDir, :2175-2180 projectDirs.skills,
-    // :2209-2213 collectAutoSkillEntries). The loader recurses into
-    // <name>/SKILL.md subdirs (skills.ts:328-372).
-    prime: ".prime/agent/skills",
-    gemini: ".gemini/skills",
-    hermes: null, // skills are ~/.hermes/skills (user) only — no cwd discovery
-    openclaw: "skills", // <workspace>/skills/<name>/SKILL.md
-};
-/**
- * Resolve the cwd-relative directory `resources.skills` refs materialize
- * into on `harness`. `null` means the harness cannot receive cwd skills, the
- * same condition that surfaces as an `unsupported`
- * "skills" entry (and an {@link assertWorkspacePlanSupported} throw) at
- * materialize time, exposed here as branchable data.
- */
-export function skillDirForHarness(harness) {
-    assertMaterializerHarness(harness);
-    return HARNESS_SKILL_DIRS[harness];
-}
-import { createHash } from "node:crypto";
-import { isMaterializerMcpConfig } from "./mcp-config-ownership.js";

package/dist/hooks.d.ts

@@ -1,6 +0,0 @@
-export declare function materializeHooks(h: HarnessId, hooks: Record<string, AgentProfileHookCommand[]>, add: AddPlanFile, unsupported: (d: Unsupported["dimension"], r: string) => void, plan: WorkspacePlan): void;
-export declare function registerClaudeSettings(plan: WorkspacePlan): void;
-export declare function hookWrapperSource(executable: string, args: string[], extraEnv: Record<string, string>, envSources?: Record<string, string>): string;
-import type { AgentProfileHookCommand } from "@tangle-network/agent-interface";
-import type { AddPlanFile } from "./plan-json.js";
-import type { HarnessId, Unsupported, WorkspacePlan } from "./plan-types.js";