Skip to content

Reject duplicate JSON keys in native worker results - #113

Merged
kudama merged 1 commit into
mainfrom
fix/native-worker-json-112
Nov 18, 2026
Merged

kudama merged 1 commit into
mainfrom
fix/native-worker-json-112

Conversation

@kudama

@kudama kudama commented Nov 18, 2026

Copy link
Copy Markdown
Owner

Native work orders currently accept repeated JSON keys because ordinary parsing silently keeps the last value. A worker result can therefore pass source/schema validation after part of its raw output has been discarded.

Reuse the existing strict JSON parser for native result admission and execution-result correspondence, while retaining bounded file loading. Duplicate keys at any nesting depth and nonstandard constants are rejected; source, tool and review boundaries are unchanged.

Validation:95 work-order, native handoff and receipt-recovery checks pass in an isolated controller copy. Restoring both legacy worker parsing calls makes both new native duplicate-key cases fail, confirming they reproduce the original defect. No deployed controller or model routing changed.

Fixes #112. Found during the Qwen3.8 handoff evaluation in #111; draft for review.

@kudama
kudama marked this pull request as ready for review November 18, 2026 19:09
@kudama
kudama merged commit ea5af8a into main Nov 18, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Reject duplicate JSON keys in native worker results instead of silently accepting the last value

1 participant