fix(weave): resolve recursive LiteralOperation schema to fix Mintlify warnings

[rajkumar-prog]

Problem

Fixes #5619

The LiteralOperation schema in sdks/node/weave.openapi.json contains recursive self-references:

"additionalProperties": { "$ref": "#/components/schemas/LiteralOperation" }
"items": { "$ref": "#/components/schemas/LiteralOperation" }

Static OpenAPI tooling (including Mintlify) cannot resolve infinite recursive schemas and emits warnings during documentation builds.

Root cause

LiteralOperation represents a JSON literal — a value that can be a string, number, boolean, object, array, or null. Objects and arrays within a literal can themselves contain arbitrary values, but the schema modelled this as a recursive reference to LiteralOperation. Static tools cannot follow infinite recursion, unlike a runtime parser.

Fix

Replaced the recursive $ref entries with open schemas that are semantically equivalent for a JSON literal:

• "additionalProperties": true — object values are unconstrained
• "items": {} — array elements are unconstrained

This matches the runtime behaviour (any JSON value is valid) while remaining resolvable by static tooling.

Note: This change only affects the generated OpenAPI schema used for documentation. It does not touch any runtime validation logic.

Changes

• sdks/node/weave.openapi.json — 2 lines changed

[wandbot-3000]

This PR requires manual approval from a wandb user to run all CI checks.

To see the current diff, click here.

To approve CI for this PR as of this commit, comment:

/approve 5416f1ccef5fbe496078c96ebbb040b334818cd2

[rajkumar-prog]

/approve be45200

[wandbot-3000]

Preview this PR with FeatureBee: https://beta.wandb.ai/?betaVersion=5c00326293e674804efc84c4aaf335a1bfc59c3e