Bug Description

When using Paperclip's openclaw_gateway adapter to connect to OpenClaw Gateway, the agent execution fails with:

invalid agent params: at root: unexpected property 'paperclip'

Root Cause

The OpenClaw Gateway's AgentParamsSchema has additionalProperties: false and does not include a paperclip field. Paperclip adapter sends this field with context about the run (runId, companyId, agentId, issueId, workspace, etc.).

Environment

• OpenClaw Gateway: 2026.4.5
• Paperclip: 2026.403.0 (latest)
• Paperclip adapter type: openclaw_gateway

Paperclip Payload (truncated)

```json
{
"message": "Paperclip wake event...",
"sessionKey": "paperclip:run:",
"idempotencyKey": "",
"paperclip": {
"runId": "",
"companyId": "",
"agentId": "",
"agentName": "CEO",
"taskId": null,
"issueId": null,
"apiUrl": "http://127.0.0.1:3100",
"workspace": { ... }
},
"timeout": 120000
}
```

Expected

Either:

1. OpenClaw accepts the paperclip field as an optional extra field, OR
2. Paperclip sends this context differently (e.g., in metadata or runtimeConfig)

Impact

This prevents Paperclip agents from executing any tasks via OpenClaw Gateway. The adapter connects successfully via WebSocket but the request is rejected at the gateway layer.

Logs

```
[openclaw-gateway] request failed: invalid agent params: at root: unexpected property 'paperclip'
stderrExcerpt: [openclaw-gateway] request failed: invalid agent params: at root: unexpected property 'paperclip'
errorCode: openclaw_gateway_request_failed
```