Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For the non-Windows
select --json --initial <64KiB+1>path, discarding stdout makes this smoke test pass for any exit-2 failure, including a host/argument-parser failure that never reaches clet validation and emits no JSON. That is the exact regression this process-level case used to catch, and the comment’s claimed unit coverage does not exist in this repo (rg Alias_InitialExceeds64KiBonly finds this comment), while the smoke-test/release-gate docs still require validating stdout JSON/envelope shape.Useful? React with 👍 / 👎.