Bilal Godil a9c22da3bd fix(cli): don't fall back when npx is killed by a signal; harden tests ... Review follow-ups: - A Ctrl-C forwarded to the npx child surfaced as exit code null (-> 1), which the fallback logic misread as an npx failure and relaunched dev on the installed CLI instead of aborting. Capture the terminating signal in runReexec and propagate (128+signum) instead of falling back. - Scrub STACK_CLI_REEXEC_MARKER from the wrapped user command's env so the internal handshake var doesn't leak into arbitrary child processes. - Add wiring tests (marker present -> propagate; absent -> fall back without process.exit) and a signal-abort case, so a regression in the glue between createReexecMarker/spawn/decidePostReexec is caught.		2026-06-16 14:46:58 -07:00
..
scripts	feat(hexclave): PR 5 — internal symbol/path/package renames + brand strings (#1547)	2026-06-03 18:57:09 -07:00
src	fix(cli): don't fall back when npx is killed by a signal; harden tests	2026-06-16 14:46:58 -07:00
.eslintrc.cjs	feat(hexclave): PR 5 — internal symbol/path/package renames + brand strings (#1547)	2026-06-03 18:57:09 -07:00
package.json	chore: update package versions	2026-06-16 19:32:53 +00:00
tsconfig.json	feat(hexclave): PR 5 — internal symbol/path/package renames + brand strings (#1547)	2026-06-03 18:57:09 -07:00
tsdown.config.ts	feat(hexclave): PR 5 — internal symbol/path/package renames + brand strings (#1547)	2026-06-03 18:57:09 -07:00
vitest.config.ts	feat(hexclave): PR 5 — internal symbol/path/package renames + brand strings (#1547)	2026-06-03 18:57:09 -07:00