Reliable delivery checks on Windows
Isolated agent work can now complete its delivery checks reliably on Windows. Pekan previously tried to launch the npm command shim as if it were a native executable. Newer Node.js releases reject that process launch with an EINVAL error, so a clean branch could be retained as undelivered even when its translation catalog check passed. Pekan now routes that fixed verification command through the Windows command interpreter while keeping the worktree path outside the command string. This preserves safe handling for project paths that contain spaces or shell metacharacters.
The verifier still captures the check's exit status, standard output, standard error, and timeout diagnostics, and non-Windows systems continue to invoke npm directly. New process-level coverage runs the actual launcher from a deliberately awkward temporary path, supplementing the existing mocked success and failure cases. This specifically unblocks automatic run telemetry work completed in an isolated worktree and prevents the delivery status from misrepresenting a Windows launcher problem as an internationalization failure.
Highlights
- Windows delivery checks no longer fail with spawn EINVAL.
- Worktree paths with spaces and shell metacharacters remain safe.
- Real process-level tests cover the Windows npm launcher.
- Non-Windows verification behavior remains unchanged.