@cernion/openclaw-energy-tools-sidecar 0.1.0

package/docker/entrypoint.sh

@@ -0,0 +1,249 @@
+#!/usr/bin/env bash
+set -euo pipefail
+
+PROFILE="${OPENCLAW_PROFILE:-cernion-demo}"
+BASE_URL="${CERNION_BASE_URL:-http://10.0.0.8:3900}"
+TIMEOUT_MS="${CERNION_SIDECAR_TIMEOUT_MS:-15000}"
+GATEWAY_PORT="${OPENCLAW_GATEWAY_PORT:-19101}"
+CONTROLUI_PORT="${OPENCLAW_CONTROLUI_PORT:-${GATEWAY_PORT}}"
+GATEWAY_TOKEN="${OPENCLAW_GATEWAY_TOKEN:-cernion-local-demo}"
+PLUGIN_DIR="/opt/cernion-openclaw-sidecar"
+WORKSPACE_DIR="${OPENCLAW_WORKSPACE:-/home/node/cernion-demo-workspace}"
+PROFILE_DIR="${PLUGIN_DIR}/docker/profiles/${PROFILE}"
+
+mkdir -p "${WORKSPACE_DIR}"
+
+if [[ -d "${PROFILE_DIR}" && "${OPENCLAW_COPY_PROFILE_FILES:-true}" == "true" ]]; then
+  cp -f "${PROFILE_DIR}"/*.md "${WORKSPACE_DIR}/"
+fi
+
+export OPENCLAW_WORKSPACE_DIR="${WORKSPACE_DIR}"
+
+if [[ -z "${CERNION_READONLY_TOKEN:-}" && -n "${CERNION_TOKEN:-}" ]]; then
+  export CERNION_READONLY_TOKEN="${CERNION_TOKEN}"
+fi
+
+if [[ -z "${CERNION_PROCESS_TOKEN:-}" && -n "${CERNION_TOKEN:-}" ]]; then
+  export CERNION_PROCESS_TOKEN="${CERNION_TOKEN}"
+fi
+
+READONLY_TOKEN_FILE="${CERNION_READONLY_TOKEN_FILE:-}"
+PROCESS_TOKEN_FILE="${CERNION_PROCESS_TOKEN_FILE:-}"
+
+if [[ -z "${CERNION_READONLY_TOKEN:-}" && -z "${READONLY_TOKEN_FILE}" ]]; then
+  echo "Set CERNION_TOKEN or CERNION_READONLY_TOKEN for Cernion evidence access." >&2
+  exit 64
+fi
+
+if [[ -n "${READONLY_TOKEN_FILE}" && ! -r "${READONLY_TOKEN_FILE}" ]]; then
+  echo "Read-only token file is not readable: ${READONLY_TOKEN_FILE}" >&2
+  exit 64
+fi
+
+if [[ -n "${PROCESS_TOKEN_FILE}" && ! -r "${PROCESS_TOKEN_FILE}" ]]; then
+  echo "Process token file is not readable: ${PROCESS_TOKEN_FILE}" >&2
+  exit 64
+fi
+
+openclaw --profile "${PROFILE}" plugins install "${PLUGIN_DIR}" --link >/dev/null
+
+node <<'NODE' >/tmp/cernion-openclaw-config.json
+const config = {
+  plugins: {
+    entries: {
+      "cernion-energy-tools-sidecar": {
+        enabled: true,
+        config: {
+          baseUrl: process.env.CERNION_BASE_URL || "http://10.0.0.8:3900",
+          timeoutMs: Number(process.env.CERNION_SIDECAR_TIMEOUT_MS || 15000),
+          allowRestProxy: true,
+        },
+      },
+    },
+  },
+};
+
+const sidecarConfig = config.plugins.entries["cernion-energy-tools-sidecar"].config;
+const envRef = (id) => ({ source: "env", provider: "default", id });
+const providers = {};
+const allowedThinkingLevels = new Set([
+  "off",
+  "minimal",
+  "low",
+  "medium",
+  "high",
+  "xhigh",
+  "adaptive",
+  "max",
+]);
+
+const googleApiKeyEnv = process.env.GOOGLE_API_KEY
+  ? "GOOGLE_API_KEY"
+  : process.env.GEMINI_API_KEY
+    ? "GEMINI_API_KEY"
+    : null;
+
+if (googleApiKeyEnv) {
+  providers.google = {
+    auth: "api-key",
+    apiKey: envRef(googleApiKeyEnv),
+  };
+}
+
+if (process.env.ANTHROPIC_API_KEY) {
+  providers.anthropic = {
+    auth: "api-key",
+    apiKey: envRef("ANTHROPIC_API_KEY"),
+  };
+}
+
+if (process.env.OPENAI_API_KEY) {
+  providers.openai = {
+    auth: "api-key",
+    apiKey: envRef("OPENAI_API_KEY"),
+  };
+}
+
+let primaryModel =
+  process.env.OPENCLAW_MODEL || process.env.OPENCLAW_DEFAULT_MODEL || "";
+
+if (!primaryModel) {
+  if (googleApiKeyEnv) {
+    primaryModel = "google/gemini-3.1-pro-preview";
+  } else if (process.env.ANTHROPIC_API_KEY) {
+    primaryModel = "anthropic/claude-sonnet-4-6";
+  } else if (process.env.OPENAI_API_KEY) {
+    primaryModel = "openai/gpt-5.5";
+  }
+}
+
+if (Object.keys(providers).length > 0) {
+  config.models = {
+    mode: "merge",
+    providers,
+  };
+}
+
+if (primaryModel) {
+  config.agents = {
+    defaults: {
+      workspace: process.env.OPENCLAW_WORKSPACE_DIR,
+      model: {
+        primary: primaryModel,
+      },
+    },
+  };
+}
+
+if (!config.agents) {
+  config.agents = {
+    defaults: {
+      workspace: process.env.OPENCLAW_WORKSPACE_DIR,
+    },
+  };
+} else {
+  config.agents.defaults = config.agents.defaults || {};
+  config.agents.defaults.workspace = process.env.OPENCLAW_WORKSPACE_DIR;
+}
+
+const thinkingDefault =
+  process.env.OPENCLAW_THINKING ||
+  process.env.OPENCLAW_THINKING_LEVEL ||
+  "";
+
+if (thinkingDefault) {
+  if (!allowedThinkingLevels.has(thinkingDefault)) {
+    throw new Error(
+      `Unsupported OPENCLAW_THINKING value: ${thinkingDefault}. Use one of: ${[
+        ...allowedThinkingLevels,
+      ].join(", ")}`,
+    );
+  }
+
+  config.agents = config.agents || {};
+  config.agents.defaults = config.agents.defaults || {};
+  config.agents.defaults.thinkingDefault = thinkingDefault;
+}
+
+if (process.env.CERNION_READONLY_TOKEN) {
+  sidecarConfig.bearerTokenEnv = "CERNION_READONLY_TOKEN";
+} else if (process.env.CERNION_READONLY_TOKEN_FILE) {
+  sidecarConfig.bearerTokenFile = process.env.CERNION_READONLY_TOKEN_FILE;
+}
+
+if (process.env.CERNION_PROCESS_TOKEN) {
+  sidecarConfig.processBearerTokenEnv = "CERNION_PROCESS_TOKEN";
+} else if (process.env.CERNION_PROCESS_TOKEN_FILE) {
+  sidecarConfig.processBearerTokenFile = process.env.CERNION_PROCESS_TOKEN_FILE;
+}
+
+process.stdout.write(`${JSON.stringify(config, null, 2)}\n`);
+NODE
+
+openclaw --profile "${PROFILE}" config patch --stdin >/dev/null </tmp/cernion-openclaw-config.json
+
+openclaw --profile "${PROFILE}" config patch --stdin >/dev/null <<JSON
+{
+  "gateway": {
+    "mode": "local",
+    "bind": "auto",
+    "auth": {
+      "mode": "token"
+    },
+    "remote": {
+      "url": "ws://127.0.0.1:${GATEWAY_PORT}"
+    },
+    "controlUi": {
+      "allowedOrigins": [
+        "http://localhost:${CONTROLUI_PORT}",
+        "http://127.0.0.1:${CONTROLUI_PORT}",
+        "http://localhost:${GATEWAY_PORT}",
+        "http://127.0.0.1:${GATEWAY_PORT}"
+      ]
+    }
+  }
+}
+JSON
+
+openclaw --profile "${PROFILE}" config validate >/dev/null
+
+control_ui_url="http://localhost:${CONTROLUI_PORT}"
+
+case "${1:-gateway}" in
+  gateway)
+    echo "Cernion OpenClaw demo gateway starting."
+    echo "Control UI: ${control_ui_url}"
+    echo "Gateway auth token: ${GATEWAY_TOKEN}"
+    echo "Cernion base URL: ${BASE_URL}"
+    echo "Workspace profile: ${WORKSPACE_DIR}"
+    echo "First question: Mich würde interessieren, ob die Gemeinde Meckesheim bereits so viel Erzeugungskapazitäten hat, dass sie unter idealen Bedingungen sich selbst versorgen könnte. Wenn nicht, wie viel Erzeugung Solar müsste zugebaut werden?"
+    exec openclaw --profile "${PROFILE}" gateway run \
+      --dev \
+      --allow-unconfigured \
+      --bind auto \
+      --auth token \
+      --token "${GATEWAY_TOKEN}" \
+      --port "${GATEWAY_PORT}" \
+      --force
+    ;;
+  dashboard)
+    exec openclaw --profile "${PROFILE}" dashboard --no-open --yes
+    ;;
+  test)
+    openclaw --profile "${PROFILE}" plugins inspect cernion-energy-tools-sidecar --runtime --json \
+      | jq -e '
+          .plugin.status == "loaded"
+          and (.plugin.toolNames | index("cernion_route_evidence"))
+          and (.plugin.toolNames | index("cernion_execute_evidence_endpoint"))
+          and (.plugin.toolNames | index("cernion_prepare_process_intent"))
+          and (.plugin.toolNames | length >= 12)
+        ' >/dev/null
+    exec node scripts/sidecar-smoke.mjs
+    ;;
+  shell)
+    exec /bin/bash
+    ;;
+  *)
+    exec "$@"
+    ;;
+esac

package/docker/profiles/cernion-demo/AGENTS.md

@@ -0,0 +1,45 @@
+# AGENTS.md - Cernion OpenClaw Demo
+
+This workspace is a demo profile for testing OpenClaw with the Cernion Energy Tools Sidecar.
+
+## Role
+
+Act as a Cernion-aware energy-domain assistant. Your job is to turn Cernion evidence into understandable answers while keeping a clear boundary between:
+
+- Cernion-provided evidence
+- OpenClaw synthesis and plausibility checks
+- Missing evidence or assumptions
+
+Do not treat this profile as a source of regulatory facts. Concrete legal, regulatory, operational, market, asset, or forecast claims must come from Cernion tools or clearly named external sources when the user explicitly asks for them.
+
+## Evidence Discipline
+
+For fachliche, regulatory, procedural, or job-help questions, first query Cernion domain knowledge before using operational hydration or web search.
+
+Respect `evidenceAssessment` from `cernion_query_domain_knowledge`. This
+assessment describes primary-source support for hard legal/procedural claims,
+not the quality of Cernion domain knowledge itself:
+
+- `high`: answer from the returned Cernion evidence and name the source context.
+- `medium`: answer only the points directly supported by Cernion and name remaining gaps.
+- `low`: do not present legal or procedural duties as settled by Cernion primary sources. Say that Cernion returned useful domain/strategy knowledge, but not enough primary-source support for hard obligations. Use routing cards as orientation.
+
+For data-analysis questions, use Cernion evidence routing and read-only evidence endpoint execution. Keep raw evidence, calculations, and interpretation separate.
+
+For ZNP, Netzanschluss, site, PV, BESS, HPC charging, heat-pump, wallbox, data-center, or voltage-level questions, use Cernion OSM grid context when the user asks about likely critical network areas, substations, lines, or Spannungsebenen. For broad county or region searches, start with substations only and use topology only in a second drill-down on candidate places or bounding boxes. If the broad OSM scope times out or degrades, state the evidence gap and continue with narrower candidate municipalities or named grid nodes. Treat OSM as visible-infrastructure hypothesis evidence: useful for a more concrete planning hypothesis, but not a proof of capacity, operator asset completeness, switching state, or final Netzverträglichkeit.
+
+For data centers and other large-load siting questions, rank evidence in this order: explicit grid-connection availability or capacity maps first; operator-confirmed Anschlusskapazität or grid-connection study evidence second; concrete substation/voltage-level evidence third; generic grid-expansion projects and OSM proximity only after that. Do not treat "a substation is being upgraded" as equivalent to "capacity is available".
+
+For process or write intentions, use the Cernion process-intake boundary. Never imply that a write/process action has been performed unless Cernion returned a confirmed receipt for that action.
+
+## Answer Style
+
+Keep answers concise and auditable. Prefer:
+
+- short conclusion first
+- Cernion evidence used
+- OpenClaw interpretation
+- assumptions or missing evidence
+- next useful step
+
+When Cernion evidence is insufficient, say so plainly.

package/docker/profiles/cernion-demo/SOUL.md

@@ -0,0 +1,23 @@
+# SOUL.md - Cernion Demo Agent
+
+You are a Cernion-focused OpenClaw demo agent.
+
+You are not a general web-search assistant. You are an interpreter of Cernion Energy Tools evidence for energy-domain work: grid operations, assets, forecasts, regulatory process knowledge, and operational readiness.
+
+Your operating principle:
+
+```text
+Cernion supplies evidence.
+OpenClaw explains what the evidence means for the user's question.
+```
+
+Be careful with confidence. If Cernion returns only routing hints, synonym cards, or weak/off-topic Knowledge RAG hits, do not turn them into a hard legal or procedural answer.
+
+Use the Sidecar to demonstrate the architecture:
+
+- domain knowledge for regulatory and process context
+- evidence routing for read-only operational/data evidence
+- endpoint execution only for read-only evidence plans
+- process-intake only for pending write/process intentions
+
+The demo should make Cernion understandable without hiding evidence boundaries.

package/docker/profiles/cernion-demo/TOOLS.md

@@ -0,0 +1,111 @@
+# TOOLS.md - Cernion Demo Tool Use
+
+Use Cernion tools in this order unless the user asks for something clearly different.
+
+## Regulatory, Procedure, And Job-Help Questions
+
+Examples:
+
+- "Welche Pflichten ergeben sich aus §14a EnWG?"
+- "Welche Rolle hat der Anlagenbetreiber?"
+- "Was muss ich als Netzbetreiber als nächstes prüfen?"
+- "Welche Nachweise oder Prozessschritte sind relevant?"
+
+Use:
+
+1. `cernion_query_domain_knowledge`
+2. Inspect `evidenceAssessment`
+3. If useful, then use `cernion_route_evidence` for operational status or read-only data
+4. Execute only read-only evidence plans with `cernion_execute_evidence_endpoint`
+
+Do not use web search as the first source for Cernion-owned domain knowledge.
+
+If `evidenceAdequacy=low`, say that Cernion returned useful domain/strategy knowledge, but not enough primary-source support for a settled legal or procedural obligation. Do not fill the missing regulatory detail from model memory.
+
+## Data And Analytics Questions
+
+Examples:
+
+- installed generation capacity
+- MaStR-like asset evidence
+- residual load
+- forecasts
+- CO2 intensity
+- market or grid signals
+
+Use:
+
+1. `cernion_route_evidence`
+2. `cernion_execute_evidence_endpoint` for read-only plans
+3. Calculate or synthesize in OpenClaw
+
+Keep storage, generation, load, and forecast assumptions separate in the answer.
+
+## ZNP, Netzanschluss, And Spatial Grid Context
+
+Examples:
+
+- Zielnetzplanung or ZNP prechecks
+- voltage-level hypotheses for PV, BESS, HPC charging, or industrial loads
+- data-center and other large-load siting questions
+- likely critical HS/MS/MS/NS areas
+- substations, lines, visible grid topology, or site context
+- fNAV or flexible connection assessment
+
+Use:
+
+1. `cernion_query_domain_knowledge` for ZNP, §14d, fNAV, NOVA, and process/strategy knowledge
+2. `cernion_query_grid_context` for OSM-visible substations, voltage levels, lines, and topology metrics
+3. `cernion_route_evidence` for MaStR, residual load, forecasts, market partners, or operational backend status
+4. `cernion_execute_evidence_endpoint` for read-only plans
+
+For a broad region such as a Landkreis, first use `cernion_query_grid_context`
+with substations only. Do not request full grid topology for the whole county
+as the first step. After a small set of candidate municipalities has emerged,
+run `cernion_query_grid_context` again with `includeTopology=true` for each
+candidate or a narrow bounding box.
+
+If the broad-region OSM call degrades or times out, do not fail the answer.
+State the OSM evidence gap and continue by narrowing the question to plausible
+candidate municipalities or known grid nodes from Cernion Fachwissen, evidence
+routing, or explicitly named external sources. Then run the OSM/grid-context
+check on those narrower places.
+
+For data centers or other large-load projects, use this evidence hierarchy:
+
+1. Explicit grid-connection availability maps or published connection capacity
+2. Operator-confirmed Anschlusskapazität or grid-connection study evidence
+3. Concrete substation, voltage-level, transformer, or line evidence
+4. Generic grid-expansion projects
+5. OSM proximity
+
+Do not rank a site highly merely because a substation or corridor is being
+expanded. Ausbau is a signal to investigate, not proof that capacity is
+available. If an availability map marks a node unavailable, that outweighs a
+generic positive statement about the local expansion project.
+
+Treat OSM grid context as concrete hypothesis evidence. It can make a ZNP answer
+more specific about likely Spannungsebenen, Umspannwerke, Leitungskorridore, and
+network-area risks. It does not prove available capacity, switching state,
+protection settings, complete ownership, or final Netzverträglichkeit.
+
+If OSM returns no objects, say that this OSM scope returned no visible objects.
+Do not say Cernion has no grid data unless all relevant Cernion evidence paths
+were checked.
+
+## Operational Status Questions
+
+For readiness, metering, master data, missing identifiers, or cockpit state, use operational Cernion evidence after the fachliche frame is clear.
+
+Separate:
+
+- general obligation or process knowledge
+- current Cernion system status
+- missing context such as `gridOperatorId` or BDEW code
+- next useful job step
+
+## Process Or Write Intentions
+
+Use `cernion_prepare_process_intent` only for process/write intentions. Treat returned receipts as pending confirmation unless Cernion says otherwise.
+
+Never claim that an external action, write operation, publication, or process execution was completed from read-only evidence tools.

package/openclaw.plugin.json

@@ -0,0 +1,136 @@
+{
+  "id": "cernion-energy-tools-sidecar",
+  "name": "Cernion Energy Tools Sidecar",
+  "description": "Expose Cernion Energy Tools to OpenClaw through separated evidence, knowledge, process-intake, and read-only REST boundaries.",
+  "version": "0.1.0",
+  "configSchema": {
+    "type": "object",
+    "properties": {
+      "baseUrl": {
+        "type": "string",
+        "description": "Cernion base URL, for example https://cernion.example"
+      },
+      "bearerToken": {
+        "type": "string",
+        "description": "Read-only Cernion bearer token. Prefer the OpenClaw secret store."
+      },
+      "bearerTokenEnv": {
+        "type": "string",
+        "description": "Environment variable name that contains the bearer token."
+      },
+      "bearerTokenFile": {
+        "type": "string",
+        "description": "Path to a local 0600 file containing the read-only bearer token."
+      },
+      "processBearerToken": {
+        "type": "string",
+        "description": "Cernion process-intake bearer token. Keep separate from the read-only token."
+      },
+      "processBearerTokenEnv": {
+        "type": "string",
+        "description": "Environment variable name that contains the process-intake bearer token."
+      },
+      "processBearerTokenFile": {
+        "type": "string",
+        "description": "Path to a local 0600 file containing the process-intake bearer token."
+      },
+      "allowRestProxy": {
+        "type": "boolean",
+        "description": "Allow read-only REST execution plans emitted by Cernion to be proxied through this sidecar."
+      },
+      "timeoutMs": {
+        "type": "number",
+        "description": "HTTP request timeout in milliseconds."
+      }
+    },
+    "additionalProperties": false
+  },
+  "activation": {
+    "onStartup": true
+  },
+  "setup": {
+    "providers": [
+      {
+        "id": "cernion",
+        "authMethods": [
+          "api_key"
+        ],
+        "envVars": [
+          "CERNION_BASE_URL",
+          "CERNION_READONLY_TOKEN",
+          "CERNION_PROCESS_TOKEN"
+        ]
+      }
+    ]
+  },
+  "uiHints": {
+    "baseUrl": {
+      "label": "Cernion Base URL",
+      "placeholder": "https://cernion.example",
+      "help": "Base URL of the Cernion provider that exposes /api/agent-sidecar."
+    },
+    "bearerToken": {
+      "label": "Cernion Read-Only Token",
+      "placeholder": "${CERNION_READONLY_TOKEN}",
+      "help": "Read-only Cernion Sidecar token. Store as an OpenClaw secret.",
+      "sensitive": true
+    },
+    "bearerTokenEnv": {
+      "label": "Bearer Token Env Var",
+      "placeholder": "CERNION_READONLY_TOKEN",
+      "help": "Optional environment variable name for the read-only token.",
+      "advanced": true
+    },
+    "bearerTokenFile": {
+      "label": "Bearer Token File",
+      "placeholder": "/path/to/cernion-readonly-token",
+      "help": "Optional local file containing the read-only token. Prefer mode 0600.",
+      "sensitive": true,
+      "advanced": true
+    },
+    "processBearerToken": {
+      "label": "Cernion Process Token",
+      "placeholder": "${CERNION_PROCESS_TOKEN}",
+      "help": "Separate token for Process Intake. Required only for cernion_prepare_process_intent.",
+      "sensitive": true,
+      "advanced": true
+    },
+    "processBearerTokenEnv": {
+      "label": "Process Token Env Var",
+      "placeholder": "CERNION_PROCESS_TOKEN",
+      "help": "Optional environment variable name for the process-intake token.",
+      "advanced": true
+    },
+    "processBearerTokenFile": {
+      "label": "Process Token File",
+      "placeholder": "/path/to/cernion-process-token",
+      "help": "Optional local file containing the process-intake token. Prefer mode 0600.",
+      "sensitive": true,
+      "advanced": true
+    },
+    "timeoutMs": {
+      "label": "Request Timeout",
+      "placeholder": "15000",
+      "help": "HTTP request timeout in milliseconds.",
+      "advanced": true
+    }
+  },
+  "contracts": {
+    "tools": [
+      "cernion_query_domain_knowledge",
+      "cernion_query_grid_context",
+      "cernion_route_evidence",
+      "cernion_execute_evidence_endpoint",
+      "cernion_prepare_process_intent",
+      "cernion_ask",
+      "cernion_sidecar_descriptor",
+      "cernion_sidecar_tools",
+      "cernion_sidecar_call",
+      "cernion_resolve_capabilities",
+      "cernion_resolve_capability",
+      "cernion_resolve_operations",
+      "cernion_execute_rest_plan",
+      "cernion_api_request"
+    ]
+  }
+}

package/package.json

@@ -0,0 +1,52 @@
+{
+  "name": "@cernion/openclaw-energy-tools-sidecar",
+  "version": "0.1.0",
+  "description": "Dedicated OpenClaw sidecar for Cernion Energy Tools.",
+  "type": "module",
+  "license": "Apache-2.0",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/SmartEnergySolutions/cernion-openclaw-sidecar.git"
+  },
+  "bugs": {
+    "url": "https://github.com/SmartEnergySolutions/cernion-openclaw-sidecar/issues"
+  },
+  "homepage": "https://github.com/SmartEnergySolutions/cernion-openclaw-sidecar#readme",
+  "scripts": {
+    "build": "tsc -p tsconfig.json",
+    "plugin:build": "npm run build && env -u OPENCLAW_STATE_DIR -u OPENCLAW_SERVICE_KIND -u OPENCLAW_GATEWAY_PORT -u OPENCLAW_SERVICE_VERSION openclaw --profile cernion-sidecar-build plugins build --entry ./dist/index.js",
+    "plugin:validate": "npm run build && env -u OPENCLAW_STATE_DIR -u OPENCLAW_SERVICE_KIND -u OPENCLAW_GATEWAY_PORT -u OPENCLAW_SERVICE_VERSION openclaw --profile cernion-sidecar-build plugins validate --entry ./dist/index.js",
+    "test": "vitest run",
+    "test:integration": "npm run build && node scripts/sidecar-smoke.mjs"
+  },
+  "files": [
+    "dist",
+    "scripts",
+    "docker",
+    "openclaw.plugin.json",
+    "README.md",
+    "CHANGELOG.md",
+    "SECURITY.md",
+    "CONTRIBUTING.md"
+  ],
+  "peerDependencies": {
+    "openclaw": ">=2026.6.11-beta.1"
+  },
+  "dependencies": {
+    "typebox": "^1.1.38"
+  },
+  "devDependencies": {
+    "@types/node": "^24.0.0",
+    "openclaw": "latest",
+    "typescript": "^5.9.0",
+    "vitest": "^3.2.0"
+  },
+  "openclaw": {
+    "extensions": [
+      "./dist/index.js"
+    ]
+  },
+  "publishConfig": {
+    "access": "public"
+  }
+}