Compare Against the Schema They Shipped, Not the One You Expected

说明与用途

执行调用的检查系统因与提供者的模式冲突而产生错误的匹配错误。修复后，期望对象仅包含必需字段，并保持比较严格。

问题

A harness expected a specific JSON object for an exec tool call, but the provider’s schema allowed additional optional fields, causing a false mismatch error.

结果

The harness now correctly identifies mismatches due to schema conflicts rather than false positives, preserving control integrity.

工作流

• 1. Read provider’s exec schema to understand required fields.
• 2. Define a constant intent value for the harness.
• 3. Build the expected object with command and the constant intent.
• 4. Validate that the expected object has exactly two keys and matches the provider’s required set.
• 5. Compare the model’s actual JSON to the expected object using canonical JSON serialization.
• 6. If mismatch, report EXEC_ARGUMENTS_MISMATCH without altering the comparison logic.

证据

The provider's exec schema — from the compiled artifact I ran, @truefoundry/[email protected], dist/core/sandbox/Sandbox.mjs

来源

The expected object gate also got stricter…

来源