@jinn-network/client 0.1.2 → 0.1.3-canary.24b69ea4

package/plugins/network-tools/.claude-plugin/plugin.json

@@ -0,0 +1,12 @@
+{
+  "name": "network-tools",
+  "version": "0.1.0",
+  "description": "Network Tools for agent Harnesses. Exposes the Jinn client MCP tools as a Claude Code plugin.",
+  "mcpServers": {
+    "jinn-client": {
+      "command": "node",
+      "args": ["${CLAUDE_PLUGIN_ROOT}/mcp/jinn-client-server.mjs"],
+      "cwd": "${CLAUDE_PLUGIN_ROOT}"
+    }
+  }
+}

package/plugins/network-tools/.codex-plugin/plugin.json

@@ -0,0 +1,39 @@
+{
+  "name": "network-tools",
+  "version": "0.1.0",
+  "description": "Network Tools for agent harnesses. Exposes the Jinn client MCP tools as a Codex plugin.",
+  "author": {
+    "name": "Jinn Network",
+    "url": "https://github.com/Jinn-Network/mono"
+  },
+  "homepage": "https://github.com/Jinn-Network/mono",
+  "repository": "https://github.com/Jinn-Network/mono",
+  "license": "MIT",
+  "keywords": [
+    "jinn",
+    "mcp",
+    "codex",
+    "tools"
+  ],
+  "mcpServers": "./.mcp.json",
+  "interface": {
+    "displayName": "Network Tools",
+    "shortDescription": "Jinn client MCP tools for runtime agents",
+    "longDescription": "Exposes the Jinn client MCP tool surface to Codex-backed harness sessions.",
+    "developerName": "Jinn Network",
+    "category": "Coding",
+    "capabilities": [
+      "Interactive",
+      "Read",
+      "Write"
+    ],
+    "websiteURL": "https://github.com/Jinn-Network/mono",
+    "privacyPolicyURL": "https://github.com/Jinn-Network/mono",
+    "termsOfServiceURL": "https://github.com/Jinn-Network/mono",
+    "defaultPrompt": [
+      "Use Jinn network tools."
+    ],
+    "brandColor": "#0F766E",
+    "screenshots": []
+  }
+}

package/plugins/network-tools/.mcp.json

@@ -0,0 +1,11 @@
+{
+  "mcpServers": {
+    "jinn-client": {
+      "command": "node",
+      "args": [
+        "mcp/jinn-client-server.mjs"
+      ],
+      "cwd": "."
+    }
+  }
+}

package/plugins/network-tools/jinn.plugin.json

@@ -0,0 +1,29 @@
+{
+  "name": "@jinn-network/network-tools",
+  "version": "0.1.0",
+  "description": "Network Tools for agent Harnesses. Declares shared runtime MCP tooling provided by the client runtime; SolverNet contracts remain the canonical protocol and schema authority.",
+  "jinn": {
+    "supports": ["jinn.runtime"],
+    "capabilities": {
+      "tools": {
+        "jinn-runtime": [
+          "search_records",
+          "inspect_record",
+          "acquire_artifact",
+          "get_task"
+        ]
+      }
+    },
+    "mcpServers": {
+      "jinn-runtime": {
+        "providedBy": "jinn-client-runtime",
+        "tools": [
+          "search_records",
+          "inspect_record",
+          "acquire_artifact",
+          "get_task"
+        ]
+      }
+    }
+  }
+}

package/plugins/network-tools/mcp/jinn-client-server.mjs

@@ -0,0 +1,110 @@
+#!/usr/bin/env node
+import { spawn } from 'node:child_process';
+import { existsSync } from 'node:fs';
+import { dirname, isAbsolute, join, resolve } from 'node:path';
+import { fileURLToPath, pathToFileURL } from 'node:url';
+
+const here = dirname(fileURLToPath(import.meta.url));
+const pluginRoot = resolve(here, '..');
+
+function envPath(name, env) {
+  const value = env[name];
+  return value && value.trim() ? value.trim() : undefined;
+}
+
+function absolutePath(path, base = process.cwd()) {
+  return isAbsolute(path) ? path : resolve(base, path);
+}
+
+function launcherForServerPath(serverPath, cwd) {
+  const args = serverPath.endsWith('.ts')
+    ? ['--import', 'tsx', serverPath]
+    : [serverPath];
+  return { command: process.execPath, args, cwd };
+}
+
+function firstExistingServer(root) {
+  const distServer = join(root, 'dist', 'mcp', 'server.js');
+  if (existsSync(distServer)) return distServer;
+
+  const sourceServer = join(root, 'src', 'mcp', 'server.ts');
+  if (existsSync(sourceServer)) return sourceServer;
+
+  return undefined;
+}
+
+export function resolveJinnClientMcpLauncher(env = process.env, root = pluginRoot) {
+  const explicitServerPath =
+    envPath('JINN_NETWORK_TOOLS_MCP_SERVER_PATH', env) ??
+    envPath('JINN_CLIENT_MCP_SERVER_PATH', env);
+  const explicitClientRoot =
+    envPath('JINN_NETWORK_TOOLS_CLIENT_ROOT', env) ??
+    envPath('JINN_CLIENT_ROOT', env);
+
+  if (explicitServerPath) {
+    const cwd = explicitClientRoot
+      ? absolutePath(explicitClientRoot, root)
+      : dirname(absolutePath(explicitServerPath, root));
+    return launcherForServerPath(absolutePath(explicitServerPath, cwd), cwd);
+  }
+
+  const candidateRoots = [
+    explicitClientRoot ? absolutePath(explicitClientRoot, root) : undefined,
+    // Normal source/package layout: <client>/plugins/network-tools.
+    resolve(root, '..', '..'),
+    // Allow launching from an unpacked client root or a caller-provided cwd.
+    absolutePath(envPath('PWD', env) ?? process.cwd(), root),
+  ].filter(Boolean);
+
+  for (const candidateRoot of candidateRoots) {
+    const serverPath = firstExistingServer(candidateRoot);
+    if (serverPath) return launcherForServerPath(serverPath, candidateRoot);
+  }
+
+  const searched = candidateRoots.join(', ');
+  throw new Error(
+    `Unable to find the Jinn client MCP server. Set JINN_NETWORK_TOOLS_MCP_SERVER_PATH or JINN_NETWORK_TOOLS_CLIENT_ROOT. Searched: ${searched}`,
+  );
+}
+
+export function startJinnClientMcpServer(env = process.env, root = pluginRoot) {
+  const launcher = resolveJinnClientMcpLauncher(env, root);
+  const child = spawn(launcher.command, launcher.args, {
+    cwd: launcher.cwd,
+    env,
+    stdio: 'inherit',
+  });
+
+  const forwardSignal = (signal) => {
+    if (!child.killed) child.kill(signal);
+  };
+  const forwardSigint = () => forwardSignal('SIGINT');
+  const forwardSigterm = () => forwardSignal('SIGTERM');
+  process.once('SIGINT', forwardSigint);
+  process.once('SIGTERM', forwardSigterm);
+
+  child.on('exit', (code, signal) => {
+    process.off('SIGINT', forwardSigint);
+    process.off('SIGTERM', forwardSigterm);
+    if (signal) {
+      process.kill(process.pid, signal);
+      return;
+    }
+    process.exit(code ?? 1);
+  });
+
+  child.on('error', (err) => {
+    console.error(`[network-tools] Failed to launch Jinn client MCP server: ${err.message}`);
+    process.exit(1);
+  });
+}
+
+if (process.argv[1] && import.meta.url === pathToFileURL(process.argv[1]).href) {
+  try {
+    startJinnClientMcpServer();
+  } catch (err) {
+    const message = err instanceof Error ? err.message : String(err);
+    console.error(`[network-tools] ${message}`);
+    process.exit(1);
+  }
+}

package/plugins/swe-rebench-v2-runtime/.claude-plugin/plugin.json

@@ -0,0 +1,5 @@
+{
+  "name": "swe-rebench-v2-runtime",
+  "version": "0.1.0",
+  "description": "Runtime plugin for the swe-rebench-v2.v1 SolverNet — provides Solver-side orientation skills for code-issue resolution tasks."
+}

package/plugins/swe-rebench-v2-runtime/.codex-plugin/plugin.json

@@ -0,0 +1,39 @@
+{
+  "name": "swe-rebench-v2-runtime",
+  "version": "0.1.0",
+  "description": "Runtime plugin for the swe-rebench-v2.v1 SolverNet - provides orientation and planning skills for code-issue resolution tasks.",
+  "author": {
+    "name": "Jinn Network",
+    "url": "https://github.com/Jinn-Network/mono"
+  },
+  "homepage": "https://github.com/Jinn-Network/mono",
+  "repository": "https://github.com/Jinn-Network/mono",
+  "license": "MIT",
+  "keywords": [
+    "jinn",
+    "swe-rebench",
+    "codex",
+    "skills"
+  ],
+  "skills": "./skills/",
+  "interface": {
+    "displayName": "SWE-rebench v2 Runtime",
+    "shortDescription": "SWE-rebench v2 orient and plan skills",
+    "longDescription": "Provides Solver-side orientation and planning skills for SWE-rebench v2 code-issue tasks.",
+    "developerName": "Jinn Network",
+    "category": "Coding",
+    "capabilities": [
+      "Interactive",
+      "Read",
+      "Write"
+    ],
+    "websiteURL": "https://github.com/Jinn-Network/mono",
+    "privacyPolicyURL": "https://github.com/Jinn-Network/mono",
+    "termsOfServiceURL": "https://github.com/Jinn-Network/mono",
+    "defaultPrompt": [
+      "Solve this SWE-rebench v2 task."
+    ],
+    "brandColor": "#0F766E",
+    "screenshots": []
+  }
+}

package/plugins/swe-rebench-v2-runtime/README.md

@@ -0,0 +1,11 @@
+# SWE-rebench v2 runtime plugin
+
+Provides Solver-side orientation + planning skills for the `swe-rebench-v2.v1` SolverNet.
+
+This plugin bundles two skills:
+- `swe-rebench-v2-orient` — read the task, identify FAIL_TO_PASS tests, plan the bug hypothesis.
+- `swe-rebench-v2-plan` — sketch the minimal diff that satisfies FAIL_TO_PASS without breaking PASS_TO_PASS.
+
+The plugin is loaded automatically when an operator's daemon has the `swe-rebench-v2.v1` SolverNet enabled, per the SDK's `defaultRuntimePlugins: ['bundled:swe-rebench-v2-runtime']`.
+
+License: MIT.

package/plugins/swe-rebench-v2-runtime/jinn.plugin.json

@@ -0,0 +1,12 @@
+{
+  "name": "swe-rebench-v2-runtime",
+  "version": "0.1.0",
+  "jinn": {
+    "supports": ["swe-rebench-v2.v1"],
+    "skills": [
+      "skills/orient/SKILL.md",
+      "skills/plan/SKILL.md"
+    ],
+    "description": "Provides Solver-side orientation + planning skills for SWE-rebench v2 code-issue Tasks."
+  }
+}

package/plugins/swe-rebench-v2-runtime/skills/orient/SKILL.md

@@ -0,0 +1,25 @@
+---
+name: swe-rebench-v2-orient
+description: Orient on a SWE-rebench v2 task — read the problem statement, repo, base commit, and auxiliary interface info; identify the test files in FAIL_TO_PASS; understand what change the issue requires.
+---
+
+# Orient on a SWE-rebench v2 task
+
+Inputs you receive under `goal.spec` in the full task body:
+
+- `goal.spec.instance_id` — e.g. `unidata__netcdf-c-1925`
+- `goal.spec.repo` — `org/repo`
+- `goal.spec.base_commit` — git SHA
+- `goal.spec.language` — `python | javascript | typescript | go | c | cpp | cs | java | rust | dart`
+- `goal.spec.problem_statement` — the issue description
+- `goal.spec.interface` — auxiliary interface info (function names, signatures, descriptions). May be empty.
+
+Steps:
+
+1. Read the problem statement carefully. Note the symptom, the expected behaviour, and any hints about which files / symbols are involved.
+2. If `task.interface` is non-empty, treat it as authoritative for function names + signatures of the API you must implement / fix.
+3. Use Network Tools to look for prior execution data from similar SWE-rebench v2 work. Call `search_records` with `solverType: "swe-rebench-v2.v1"`, `role: "restoration"`, and `artifactType: "swe-rebench-v2_v1_solution"`; use `inspect_record` on promising refs. Call `acquire_artifact` only when the inspected record has donated IPFS sources and the full execution data is likely to help this task.
+4. Check the `FAIL_TO_PASS` test names from the HF row — these define the success criterion. Find them in the codebase via grep / fs search.
+5. Output a brief Orient summary (3-5 sentences): your hypothesis about the bug, the files you intend to touch, the test you intend to satisfy, and any donated execution data that affected the plan.
+
+Pass this summary forward to the Plan phase.

package/plugins/swe-rebench-v2-runtime/skills/plan/SKILL.md

@@ -0,0 +1,64 @@
+---
+name: swe-rebench-v2-plan
+description: Plan the patch for a SWE-rebench v2 task — given the Orient summary, sketch the minimal diff that resolves the issue without breaking existing PASS_TO_PASS tests, then submit the final patch via the `submit_typed_payload` MCP tool.
+---
+
+# Plan the patch
+
+Inputs:
+- The Orient summary from the previous phase.
+- The repo at `goal.spec.base_commit`.
+- The `FAIL_TO_PASS` test names (must pass after your patch).
+- The `PASS_TO_PASS` test names (must continue passing — don't break them).
+
+Steps:
+
+1. Read the failing test(s). Understand exactly what behaviour they assert.
+2. Locate the source file(s) that need editing. Use grep, AST tools, or filesystem search.
+3. Sketch the minimal diff:
+   - What lines change in which files?
+   - What does the new code do?
+   - Which existing tests must continue to pass (briefly justify why they will)?
+4. Output the plan as a list of file-level edits.
+
+Pass this plan forward to the Execute phase, which produces the actual patch.
+
+## Submitting the final patch
+
+Once Execute has produced the unified diff, call the **`submit_typed_payload`** MCP tool exposed by the daemon to register the Solution. The daemon validates the payload against the SolverNet contract's solution schema before persisting it; if validation fails, the tool returns the Zod error tree under `error.issues` and you can retry.
+
+If `submit_typed_payload` is not available in the current harness, write the same payload object directly to `<workingDir>/.execute/solution-payload.json`. Create the `.execute` directory if needed. The daemon's harvester reads that file after the harness exits and applies the same SolverNet payload schema during envelope assembly.
+
+Required payload shape for `swe-rebench-v2.v1`:
+
+```json
+{
+  "schemaVersion": "swe-rebench-v2-solution.v1",
+  "patch": "<unified diff, git-format>"
+}
+```
+
+Optional fields:
+
+- `cost.totalUsd: number` — operator-self-reported cost in USD for producing this Solution. Include if you can compute it from your LLM/tool usage; omit otherwise.
+
+Do **not** include daemon-derived fields (e.g. trajectory CIDs) — the daemon attaches trajectory provenance to the envelope automatically. The Solution payload is purely solver-known fields.
+
+Example call:
+
+```
+submit_typed_payload({
+  payload: {
+    schemaVersion: "swe-rebench-v2-solution.v1",
+    patch: "--- a/src/foo.c\n+++ b/src/foo.c\n@@ -1 +1 @@\n-old\n+new\n"
+  }
+})
+```
+
+A successful response looks like:
+
+```json
+{ "accepted": true, "solverType": "swe-rebench-v2.v1", "role": "restoration", "persistedTo": "<workingDir>/.execute/solution-payload.json" }
+```
+
+After a successful submission, this Plan/Execute cycle is complete — the daemon's harness picks up the persisted payload post-execution and assembles the on-chain envelope.