@oracle-agent/oracle 0.3.3 → 0.3.5

package/bin/oracle-init.mjs

@@ -176,71 +176,6 @@ function record(kind, detail) {
   log(`${APPLY ? "  ✔" : "  ·"} ${kind}: ${detail}`);
 }
 
-// Write Hermes mcp_servers.oracle-data directly into the profile config.
-// Prefer this over `hermes mcp add`: current Hermes takes --command and --args
-// as separate tokens, prompts interactively for tool enablement, and the old
-// installer form `--command "node <path>"` silently no-ops under execFileSync.
-function yamlScalar(value) {
-  if (
-    value === "" ||
-    /[:#\[\]{},&*!|>'"%@`\s]/.test(value) ||
-    /^(?:null|true|false|\d+)$/i.test(value)
-  ) {
-    return JSON.stringify(value);
-  }
-  return value;
-}
-
-function mcpServerBlock(serverName, scriptPath) {
-  return [
-    `  ${serverName}:`,
-    "    command: node",
-    "    args:",
-    `      - ${yamlScalar(scriptPath)}`,
-    "    enabled: true",
-  ].join("\n");
-}
-
-function wireMcpIntoConfig(configPath, serverName, scriptPath) {
-  const entry = mcpServerBlock(serverName, scriptPath);
-  if (!fs.existsSync(configPath)) {
-    fs.writeFileSync(configPath, `mcp_servers:\n${entry}\n`, "utf8");
-    return "created";
-  }
-
-  let txt = fs.readFileSync(configPath, "utf8");
-  if (
-    txt.includes(scriptPath) &&
-    new RegExp(`^\\s*${serverName}:\\s*$`, "m").test(txt)
-  ) {
-    return "present";
-  }
-
-  // Replace an existing server block of the same name (simple indented map).
-  const serverRe = new RegExp(
-    `^([ \\t]*)${serverName}:\\s*\\n(?:\\1[ \\t]+.*\\n)*`,
-    "m",
-  );
-  if (serverRe.test(txt)) {
-    txt = txt.replace(serverRe, `${entry}\n`);
-    fs.writeFileSync(configPath, txt, "utf8");
-    return "updated";
-  }
-
-  if (/^mcp_servers:\s*$/m.test(txt) || /^mcp_servers:\s*\n/m.test(txt)) {
-    txt = txt.replace(/^(mcp_servers:\s*\n)/m, `$1${entry}\n`);
-  } else if (/^_config_version:.*$/m.test(txt)) {
-    txt = txt.replace(
-      /^(_config_version:.*\n)/m,
-      `$1mcp_servers:\n${entry}\n`,
-    );
-  } else {
-    txt = `mcp_servers:\n${entry}\n${txt}`;
-  }
-  fs.writeFileSync(configPath, txt, "utf8");
-  return "wired";
-}
-
 // ---------------------------------------------------------------- main
 
 const schema = loadSchema();
@@ -428,40 +363,35 @@ for (const def of profiles) {
     }
   }
 
-  // MCP: write Hermes config directly. CLI is optional convenience only.
-    for (const m of def.mcp || []) {
-      const scriptPath = path.join(ROOT, "bin", "oracle-data-mcp.mjs");
-      const configPath = path.join(laneDir, "config.yaml");
-      const manual = `hermes -p ${def.id} mcp add ${m} --command node --args ${scriptPath}`;
-
-      if (m !== "oracle-data") {
-        record("mcp manual", manual);
-        mcpManual.push({ lane: def.id, server: m, command: manual });
-        continue;
-      }
-
-      record(
-        "wire mcp",
-        `${m} (${def.id}) -> ${path.relative(os.homedir(), configPath)}`,
-      );
-      if (APPLY) {
-        try {
-          fs.mkdirSync(laneDir, { recursive: true });
-          const how = wireMcpIntoConfig(configPath, m, scriptPath);
-          record(
-            "mcp config",
-            `${how}: ${path.relative(os.homedir(), configPath)}`,
-          );
-        } catch (err) {
-          record("mcp note", `could not write ${configPath}: ${err.message}`);
-          mcpManual.push({ lane: def.id, server: m, command: manual });
-        }
+  // MCP: the read plane. This is the one step that genuinely needs the CLI, since
+  // it edits the profile's own config. Without it, print the command instead.
+  for (const m of def.mcp || []) {
+    const cmd = path.join(ROOT, "bin", "oracle-data-mcp.mjs");
+    if (!hermes) {
+      record("mcp manual", `hermes -p ${def.id} mcp add ${m} --command "node ${cmd}"`);
+      mcpManual.push({ lane: def.id, server: m, command: `hermes -p ${def.id} mcp add ${m} --command "node ${cmd}"` });
+      continue;
+    }
+    record("wire mcp", `${m} (${def.id})`);
+    if (APPLY && m === "oracle-data") {
+      try {
+        execFileSync(
+          "hermes",
+          ["-p", def.id, "mcp", "add", "oracle-data", "--command", `node ${cmd}`],
+          { stdio: "pipe", timeout: 60_000 },
+        );
+      } catch {
+        // Already registered, or this Hermes build wants different flags. Not fatal:
+        // the profile is usable, it just needs the MCP wired by hand.
+        record("mcp note", `could not auto-wire ${m} for ${def.id}; add it manually`);
+        mcpManual.push({ lane: def.id, server: m, command: `hermes -p ${def.id} mcp add ${m} --command "node ${cmd}"` });
       }
     }
-
-    record("posture", `DISARMED (${(def.posture.grantActions || []).join(", ")})`);
   }
 
+  record("posture", `DISARMED (${(def.posture.grantActions || []).join(", ")})`);
+}
+
 const summary = {
   ok: true,
   applied: APPLY,
@@ -484,13 +414,10 @@ if (JSON_OUT) {
     log("pass --force to overwrite (a timestamped .bak is written first).");
   }
   if (mcpManual.length) {
-    log("\nMCP wiring needed a manual follow-up:");
+    log("\nMCP wiring needs the hermes CLI. Run these when it is available:");
     for (const m of mcpManual) log(`  ${m.command}`);
   }
   if (!APPLY) log("re-run with --apply to make changes.");
-  log("\nEvery lane is DISARMED. Start the read plane, then chat a lane:");
-  log("  npx oracle-data                 # 127.0.0.1:8787 — MCP tools need this");
-  log("  hermes -p oracle chat");
-  log("\nSet each lane's model in:");
+  log("\nEvery lane is DISARMED. Set each lane's model in:");
   log(`  ${path.join(hermesRoot(), "profiles", "<lane>", "config.yaml")}`);
 }

package/docs/profiles.md

@@ -34,28 +34,19 @@ Three practical reasons, learned the hard way:
 
 | Profile | Owns | Typical grant |
 |---|---|---|
-| `oracle` | routing, synthesis, multi-chain comparison, `/balance` portfolio aggregation | read + simulate only |
+| `oracle` | routing, synthesis, multi-chain comparison | read + simulate only |
 | `polymarket-agent` | prediction markets, event odds, CLOB cards/API-key order intents | read, quote, prepare |
 | `hyperliquid-agent` | perps, spot, HIP-3 builder dexs, HIP-4 outcomes | read, quote, prepare |
 | `robinhood-agent` | Robinhood Chain (4663) tokens, NFTs, tokenized Robinhood-style assets, capped NFT mints | read, quote, prepare |
 | `solana-agent` | Solana swaps, research, Jupiter routes | read, quote, prepare |
 | `bitcoin-agent` | Bitcoin L1, Ordinals/runes, inscriptions | read, prepare:inscription |
 | `stable-agent` | Stable (988), USDT-native gas quirks | read, quote, prepare |
-| `protocol-builder` | scaffold, review, prepare chain-family token/NFT collections, gacha, DEX, and protocol deploys | prepare:deploy, prepare:mint, simulate |
+| `protocol-builder` | scaffold, review, prepare protocol/NFT/gacha/DEX deploys and mint bots | prepare:deploy, prepare:mint, simulate |
 | `_template` | your new lane | you decide |
 
-`protocol-builder` classifies each launch by chain family, then designs and
-prepares unsigned token, NFT collection, protocol, or mint-bot transactions. It
-fails closed when no verified adapter exists, never house-signs, and keeps deploy,
-metadata, liquidity, mint, and authority actions as separate user approvals.
-
-The root `oracle` lane owns `/balance`, natural-language balance, and portfolio
-history requests. Its `balance` skill calls the read-only
-`portfolio_snapshot` MCP tool once, records a compact profile-local observation,
-reports partial coverage and unavailable providers, and labels `knownUsd` as
-incomplete instead of inventing a full portfolio total. `portfolio_history`
-reads those observations and `portfolio_value_graph` renders the known-value
-series while omitting unavailable values rather than plotting fake zeroes.
+`protocol-builder` can design a protocol and prepare an unsigned deploy or mint
+bot transaction. It never house-signs, and its destinations and gas-war caps are
+allowlisted like any other lane.
 
 ## Model choice is yours
 
@@ -110,21 +101,10 @@ hermes profile create polymarket-agent
 ```
 
 Then give it a `SOUL.md` (who it is, what it owns, what it must refuse) and a
-`config.yaml` (model + provider). Point it at Oracle's MCP read plane.
-
-`oracle-init --apply` writes this for you. Manual form (Hermes wants command and
-args as separate tokens):
+`config.yaml` (model + provider). Point it at Oracle's MCP read plane:
 
 ```bash
-# terminal 1 — local read plane the MCP tools call
-npx oracle-data
-
-# terminal 2 — wire MCP into a lane
-hermes -p polymarket-agent mcp add oracle-data \
-  --command node \
-  --args "$(node -p "require.resolve('@oracle-agent/oracle/package.json').replace(/package\\.json$/, 'bin/oracle-data-mcp.mjs')")"
-# or after npm link / PATH has the bin:
-# hermes -p polymarket-agent mcp add oracle-data --command oracle-data-mcp
+hermes mcp add oracle-data --command "oracle-data-mcp"
 ```
 
 Now that lane can read 30+ providers across 11 chains, quote real routes, and

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@oracle-agent/oracle",
-  "version": "0.3.3",
+  "version": "0.3.5",
   "description": "Oracle: prepare-only multichain agent control plane. Policy-bounded intents for a user-signed wallet. Self-custody by default — the public package never takes your key. Built for Hermes; no model key required.",
   "license": "Apache-2.0",
   "type": "module",

package/profiles/_template/SOUL.md

@@ -38,15 +38,8 @@ Terse. Answer first, evidence second. State confidence: `high` / `moderate` /
 ## Wiring it up
 
 ```bash
-# preferred: installer writes SOUL, skills, and MCP config
-npx oracle-init --apply
-
-# or by hand
 hermes profile create my-lane
-npx oracle-data   # keep running — MCP tools call 127.0.0.1:8787
-hermes -p my-lane mcp add oracle-data --command oracle-data-mcp
-# if the bin is not on PATH:
-# hermes -p my-lane mcp add oracle-data --command node --args /abs/path/to/oracle-data-mcp.mjs
+hermes mcp add oracle-data --command "oracle-data-mcp"
 ```
 
 Then copy this `SOUL.md` into `~/.hermes/profiles/my-lane/SOUL.md` and set the

package/profiles/oracle/SOUL.md

@@ -20,11 +20,9 @@ value yourself.
 | Stable (988), USDT-native gas | `stable-agent` |
 | tokenized Robinhood-style assets / stock tokens | exact home-chain lane + `oracle-rfq-tokenized-assets` |
 | meme-token launches, sniping, liquidity/pool watches | token's home-chain lane + `oracle-meme-token-sniper` |
-| create a fungible token or NFT collection | home-chain specialist for chain facts + `protocol-builder` using the matching multichain launch skill |
-| deploy/review custom contracts, gacha, DEX, launchpad, or capped NFT mint bot | `protocol-builder` + `oracle-nft-mint-gas-war` |
+| deploy/review a contract, NFT/gacha launch, DEX, or capped NFT mint bot | `protocol-builder` + `oracle-nft-mint-gas-war` |
 | RFQ / solver-intent route comparison across chains | `oracle` + `oracle-rfq-tokenized-assets` |
 | graph/card alert rendering | token's home-chain lane + `oracle-chain-graphs-telegram-cards` |
-| `/balance`, balance, holdings, wallet portfolio | `oracle` + `balance`; one deterministic `portfolio_snapshot` read plus profile-local observation |
 | compare chains, "which is cheaper" | you, using the data plane |
 
 If the chain is ambiguous, resolve the token's home chain first (DexScreener via
@@ -55,11 +53,6 @@ the data plane). If it stays ambiguous, ask. Do not guess a chain.
    delta → the action did not succeed. Say so plainly.
 7. **Never invent chain facts.** If it did not come from a live read, label it
    `unknown`.
-8. **Balance uses one source of truth.** `/balance` and plain-language balance
-   requests call `portfolio_snapshot`; use `portfolio_history` and
-   `portfolio_value_graph` for historical requests. Report `knownUsd` as
-   incomplete whenever a provider, address, price, token/NFT indexer, or chain
-   adapter is missing. Never turn an unavailable historical value into zero.
 
 ## Confidence
 

package/profiles/oracle/profile.json

@@ -4,7 +4,7 @@
   "label": "oracle",
   "role": "router",
   "color": "#7CC4FF",
-  "description": "Router for multichain trading, building, analysis, wallet/NFT inventory and value history, scanners, RFQ, tokenized-asset buys, NFT mint gas limits, meme-token sniping, and chain-family token/NFT launches.",
+  "description": "Router for multichain trading, building, analysis, scanners, RFQ, tokenized-asset buys, NFT mint gas limits, meme-token sniping, Solana, Bitcoin, and protocol launches.",
   "model": {
     "note": "Wants the strongest reasoner available: routing and synthesis are judgment calls.",
     "suggested": "strong-reasoner"
@@ -18,10 +18,7 @@
     "oracle-meme-token-sniper",
     "oracle-chain-graphs-telegram-cards",
     "oracle-rfq-tokenized-assets",
-    "oracle-nft-mint-gas-war",
-    "oracle-multichain-token-launch",
-    "oracle-multichain-nft-launch",
-    "balance"
+    "oracle-nft-mint-gas-war"
   ],
   "mcp": [
     "oracle-data"

package/profiles/protocol-builder/SOUL.md

@@ -1,16 +1,13 @@
 # protocol builder
 
-You classify by chain family, then design, review, and prepare deploys for fungible
-tokens, NFT collections, protocols, gacha products, DEX surfaces, launchpads, mint
-pages, and scanner-backed on-chain apps. You never sign one. Unsupported chain
-adapters fail closed.
+You design, review, and prepare deploys for protocols, NFT/gacha products, DEX
+surfaces, launchpads, mint pages, and scanner-backed on-chain apps. You never sign one.
 
 ## What you own
 
-Chain-family token/NFT launch manifests, contract and program scaffolding,
-NFT/gacha mint mechanics, DEX/pool/launchpad design, security review, deploy and
-verify scripts, and **unsigned** deploy transactions. Research of existing
-protocols before cloning them.
+Contract scaffolding, NFT/gacha mint mechanics, DEX/pool/launchpad design,
+security review, deploy and verify scripts, and **unsigned** deploy transactions.
+Research of existing protocols before cloning them.
 
 ## Deployment is permanent
 
@@ -45,11 +42,7 @@ what an attacker gains from each privileged function.
 3. **Simulate before preparing.** An unsimulated deploy is a guess.
 4. **State the authority model before the code.** A user who doesn't know who owns
    the contract cannot consent to deploying it.
-5. **Receipts or it didn't happen.** Deployed address, receipt, verified source.
-6. **Chain-family support is explicit.** Use `TEMPLATE_READY`, `ADAPTER_READY`,
-   `GUIDED_BUILD`, `RESEARCH_ONLY`, or `UNSUPPORTED`. RPC reachability is not deploy support.
-7. **One approval per side effect.** Deploy, metadata upload, mint, liquidity,
-   authority transfer/revoke, reveal, and verification remain separate.
+5. **Receipts or it didn't happen** — deployed address, receipt, verified source.
 
 ## Voice
 

package/profiles/protocol-builder/profile.json

@@ -4,7 +4,7 @@
   "label": "protocol builder",
   "role": "builder",
   "color": "#ff8c5a",
-  "description": "Builder lane for protocol, chain-family token/NFT collections, gacha, DEX, scanner, and mint-bot surfaces with unsigned deploy/mint preparation.",
+  "description": "Builder lane for protocol, NFT/gacha, DEX, scanner, and mint-bot surfaces with unsigned deploy/mint preparation.",
   "model": {
     "note": "Contract review is unforgiving and mistakes are permanent; wants the strongest reasoner available.",
     "suggested": "strong-reasoner"
@@ -13,8 +13,6 @@
     "oracle-protocol-builder",
     "oracle-contract-research",
     "oracle-protocol-security",
-    "oracle-multichain-token-launch",
-    "oracle-multichain-nft-launch",
     "oracle-nft-gacha-launch",
     "oracle-dex-launch",
     "oracle-receipts",