Best possible solution:

Close this duplicate PR and consolidate review on one canonical implementation, preferably an additive adapter metadata contract or an explicitly approved Paperclip compatibility field with tests, generated protocol artifacts, and follow-up closure of duplicate reports after merge.

Do we have a high-confidence way to reproduce the issue?

Yes. Sending a Gateway agent request with a root-level paperclip field against current main follows a deterministic validation path: AgentParamsSchema has no such field, the object is closed, and the handler rejects before dispatch.

Is this the best way to solve the issue?

No. This PR fixes the immediate validation failure in principle, but it is not the best current path because older open PRs already cover the same work with tests and maintainer context, and this branch leaves protocol tests/generated artifacts out of sync.

Security review:

Security review cleared: The diff only adds an optional ignored schema field and does not touch workflows, dependencies, lockfiles, scripts, secrets, or package publishing surfaces.

What I checked:

• Current schema rejects the field: AgentParamsSchema on current main lists allowed agent params and closes the object with { additionalProperties: false }; there is no paperclip, adapterMeta, or adapterContext field. (src/gateway/protocol/schema/agent.ts:132, 9cb71f767242)
• Validation happens before dispatch: The Gateway agent handler calls validateAgentParams(p) before building the runtime request and returns INVALID_REQUEST with invalid agent params on schema failure. (src/gateway/server-methods/agent.ts:494, 9cb71f767242)
• Unknown fields are not stripped: The protocol Ajv instance uses removeAdditional: false, so unknown root fields on strict schemas fail validation instead of being silently removed. (src/gateway/protocol/index.ts:337, 9cb71f767242)
• This PR is schema-only: The PR file list shows only src/gateway/protocol/schema/agent.ts changed, adding paperclip: Type.Optional(Type.Unknown()) with no tests or generated protocol artifacts. (src/gateway/protocol/schema/agent.ts:176, 9406acc1a3b2)
• Older open PR covers the same fix with handler coverage: Open PR fix(gateway): accept Paperclip adapter root-level paperclip metadata in agent params #69139 adds an optional paperclip field for the same Paperclip agent-param failure and includes a Gateway agent-handler acceptance test. (997b76a1dcee)
• Another older open PR covers the same fix with schema coverage: Open PR fix: AgentParamsSchema must accept paperclip property in wake payload #72565 also adds the same optional paperclip field and adds focused schema tests for minimal params, Paperclip-shaped metadata, arbitrary nested metadata, and strict rejection of other unknown fields. (3f4d6012632a)

Likely related people:

• vincentkoc: Recent history on the central Gateway protocol/agent paths includes input-provenance schema sharing and spawned workspace/agent-param boundary work, which are adjacent to the strict AgentParamsSchema validation surface. (role: recent gateway protocol and agent-param boundary maintainer; confidence: high; commits: 7c889e71136a, 46a332385d11, 985000026e35; files: src/gateway/protocol/schema/agent.ts, src/gateway/protocol/index.ts, src/gateway/server-methods/agent.ts)
• steipete: Recent commits and merges touch Gateway protocol generated models and the Gateway agent handler, and related PR discussion routes maintainer review for this surface to steipete alongside vincentkoc. (role: recent adjacent Gateway/protocol maintainer; confidence: medium; commits: bdba90a20b2b, e035300d8ed3, ac0fa474f831; files: apps/shared/OpenClawKit/Sources/OpenClawProtocol/GatewayModels.swift, apps/macos/Sources/OpenClawProtocol/GatewayModels.swift, src/gateway/server-methods/agent.ts)

Codex review notes: model gpt-5.5, reasoning high; reviewed against 9cb71f767242.