Windows Agent Shell Pack

Six execution-layer recoveries

• Node on Windows: 'Assertion failed: !(handle->flags & UV_HANDLE_CLOSING)' at exitAssertion failed: !(handle->flags & UV_HANDLE_CLOSING), file src\win\async.c
• node --test with a bare directory argument fails with a nameless failing 'test'test at test:1:1 ... 'test failed' with zero real tests run
• PowerShell 5.1: '&&' and '||' are parser errorsThe token '&&' is not a valid statement separator in this version
• curl -w format strings mangled into C:/Program Files/Git/ paths on git-bashC:/Program Files/Git/ prefixed onto strings that started with a forward slash
• PowerShell Read-Host: secret pasted into the prompt string yields an empty variable$t = Read-Host "<the secret itself>" ... later auth fails with ENEEDAUTH / empty credential
• Windows: an env var set with setx is missing in the shell that set itenvironment variable appears unset immediately after setx reported success

Free decision preview

1. Identify the process that parses the failing line before rewriting its syntax.
2. Separate PowerShell 5.1 grammar from PowerShell 7 features, especially pipeline chaining.
3. Treat Git Bash path conversion as an argument-boundary problem, not a curl problem.
4. Keep secret prompts out of command history and model-visible arguments.
5. Distinguish persistent setx writes from the environment inherited by the current process.
6. Let Node providers and handles close cleanly before process exit on Windows.

The paid body supplies exact commands, version branches, failure-layer checks, secret-handling constraints, and verification procedures for all six cases.