* Fix Windows ConPTY probe failures by removing startup control bytes
Avoid prepending terminal probes with interrupt (`\x03`) or line-kill
(`\x15`) control characters on fresh shell launches. In Windows ConPTY,
echoing a startup Ctrl+C can print a literal "^C" and corrupt the subsequent
PowerShell commands.
- Extract probe command sequence generation to a dedicated helper
- Include E2E unit tests in the Vitest test suite config
* Rename terminal probe E2E test to match unit test pattern
Update the Vitest configuration glob pattern to target only E2E tests
ending in `.unit.test.ts`, and rename the terminal probe input sequence
test to match. This ensures only unit-like E2E tests are picked up
by Vitest.
Ensure terminal E2E probes run reliably on Windows CI, where the shell
does not always inherit setup-node's PATH.
- Add `nodeTerminalCommand` helper to resolve and quote `process.execPath`
for either POSIX shells or PowerShell depending on the platform.
- Update terminal tests and probes to use the new helper instead of
hardcoded `node` invocations.
Jinjing
Brennan Benson
