VFX-E-1006¶

Title¶

InvalidToolArgument

Explanation¶

A tool argument failed validation before anything was spawned. One code shared across run_suite, plan_coverage, and scaffold_suite, because it is one condition in each case: the call as written cannot be performed and the caller must change an argument. The fix is always a different call, so this code is never retryable.

Common causes¶

• A path or tags value on run_suite beginning with - (e.g. --version), rejected outright rather than risking it being misread as a command-line flag by the spawned vouchfx process.
• An out-of-range timeoutSeconds on run_suite (must be 1-3600).
• An empty steps array on scaffold_suite — there is nothing to scaffold.
• An out-of-range threshold override on plan_coverage (staleDays, flakyMinRuns, fragileMinEnvErrors, inconclusiveMin), or a bad/missing/empty suite path.
• An out-of-range maxFindings on plan_coverage (must be 1-150). It is refused, not clamped, so that a host cannot believe it asked for 500 findings and received all of them.

Fixes¶

• Re-check the failing argument against the tool's own input schema and the constraint named in the error message.
• Never build a path/tags value by concatenating untrusted input that could begin with -.
• For scaffold_suite, supply at least one entry in steps.
• For plan_coverage, keep threshold overrides within their documented ranges, and point path at an existing suite file or a directory containing at least one .e2e.yaml file.
• For plan_coverage's maxFindings, pass a value in 1-150 or omit it entirely. Omitting it is usually right: the response is size-budgeted regardless, and maxFindings only ever asks for fewer findings than that budget allows — it cannot raise the ceiling. If you are omitting findings you wanted, narrow path instead and check responseTruncated / omittedFindingCount on the result.