Closes #104469

What Problem This Solves

Fixes an issue where tool schemas containing non-finite numeric values could be projected into provider-facing schemas with those values silently changed to null.

The trigger is a runtime/custom tool schema that contains a JavaScript-only numeric value such as Number.POSITIVE_INFINITY or Number.NaN in a JSON Schema numeric constraint/default. The shared projector serialized the schema with JSON.stringify() before validating the projected JSON value, so those values could become explicit null fields while reporting no schema violation.

Why This Change Was Made

The shared runtime tool schema projector now detects non-finite numbers before JSON serialization and reports the exact offending schema path as non-JSON-serializable.

This keeps the existing quarantine behavior narrow: the invalid tool is dropped with diagnostics, healthy sibling tools remain available, and provider-specific schema cleanup is left unchanged. The changed shared path is used by OpenAI and Anthropic tool projection; sibling provider paths such as Google/Gemini and Mistral use separate schema handling and are not changed by this PR.

User Impact

Plugin/tool authors and operators get safer tool schema handling. Invalid non-finite numeric schema values now produce a clear projection violation instead of being silently rewritten into materially different provider payloads.

For example, a bad bad_limits tool with maximum: Number.POSITIVE_INFINITY is quarantined, while a healthy sibling lookup tool remains available for provider use.

Evidence

Behavior proof:

JSON.stringify({
  type: object,
  properties: {
    amount: { type: number, maximum: Number.POSITIVE_INFINITY },
    score: { type: number, default: Number.NaN },
  },
})

// Before this PR, JSON serialization could turn both values into null:
// {type:object,properties:{amount:{type:number,maximum:null},score:{type:number,default:null}}}

Focused regression coverage added:

• src/agents/tool-schema-projection.test.ts covers Number.NaN at the shared runtime schema projection layer and expects parameters.properties.score.default is not JSON-serializable.
• packages/ai/src/providers/openai-tool-projection.test.ts covers OpenAI tool projection quarantining a bad maximum: Number.POSITIVE_INFINITY tool while preserving a healthy sibling.
• packages/ai/src/providers/anthropic-tool-projection.test.ts covers Anthropic tool projection quarantining the bad original tool while preserving a healthy sibling.

Validation run:

git diff --check
node scripts/run-vitest.mjs run packages/ai/src/providers/openai-tool-projection.test.ts packages/ai/src/providers/openai-tool-schema.test.ts packages/ai/src/providers/anthropic-tool-projection.test.ts src/agents/tool-schema-projection.test.ts

[test] passed 2 Vitest shards in 7.22s
Test Files  1 passed (1), 3 passed (3)
Tests       11 passed (11), 26 passed (26)

Additional local validation note:

pnpm check:test-types

was attempted separately but did not reach useful typechecking in this checkout because workspace package resolution reports @openclaw/gateway-protocol@workspace:* from packages/gateway-client while no @openclaw/gateway-protocol package is present in the local workspace. That appears unrelated to the four files changed here.