Connect an OpenClaw Agent

Set up BenchGen tracing in this OpenClaw gateway.

Follow these steps exactly. Do not invent configuration keys: every name below
is read verbatim by the plugin.

## 1. Install the plugin

    openclaw plugins install @benchgen/benchgen-openclaw

## 2. Get the secret key from me

Four values are needed. Three are here; the fourth is a secret and is NOT in this
prompt:

  publicKey: pk-lf-YOUR-PUBLIC-KEY
  baseUrl:   https://traces.benchgen.com
  chatUrl:   wss://benchgen.com/api/public/openclaw/chat
  secretKey: ASK ME FOR IT. It is on the BenchGen agent page I copied this from,
             in the Observability card. Do not guess it, do not invent a
             placeholder, and do not continue without it.

## 3. Write the configuration

Merge this into the gateway's `openclaw.json`, keeping any other entries that
are already under `plugins.entries`:

    {
      "plugins": {
        "entries": {
          "benchgen": {
            "enabled": true,
            "config": {
              "enabled": true,
              "publicKey": "pk-lf-YOUR-PUBLIC-KEY",
              "secretKey": "<the key I give you>",
              "baseUrl": "https://traces.benchgen.com",
              "chat": { "url": "wss://benchgen.com/api/public/openclaw/chat" }
            }
          }
        }
      }
    }

Both `enabled` flags have to be true: the outer one turns the plugin entry on,
the inner one turns tracing on, and the plugin checks both.

The `chat.url` is where the plugin dials in so BenchGen can chat with the agent
(the Runtime card connects itself once the gateway is up). It is on by default;
set `"chat": { "enabled": false }` to opt out.

`benchgen` is the plugin's manifest id, which is not its npm package name. An
unknown id under `plugins.entries` is a configuration error the gateway refuses
to start on, so do not change that string.

Instead of putting the keys in the file, you may set `BENCHGEN_PUBLIC_KEY`,
`BENCHGEN_SECRET_KEY`, `BENCHGEN_BASE_URL` and `BENCHGEN_CHAT_URL` in the gateway's environment; the
plugin falls back to those when the config omits them.

## 4. Restart the gateway

The configuration is only read at startup, so nothing happens until you restart
the gateway. This is the most common reason setup appears to fail.

## 5. Verify

On every start the plugin sends a trace named `benchgen.plugin.connected`,
tagged `benchgen-setup`. Tell me to look for it on the Traces tab. That trace
is the gateway confirming it reached BenchGen, and it is the only real proof
this worked.

If nothing arrives, check the credentials themselves:

    curl -s -o /dev/null -w '%{http_code}\n' \
      -u 'pk-lf-YOUR-PUBLIC-KEY:<the key I give you>' \
      'https://traces.benchgen.com/api/public/health'

200 means the keys are good and the problem is the config or the restart. 401
means the keys are wrong.

## Do not

- Do not run `openclaw benchgen configure`. It prompts interactively and cannot be
  driven from this conversation; the JSON in step 3 is its exact equivalent.
- Do not print the secret key back to me, and do not write it anywhere except
  the gateway configuration or its environment.