---
name: v084-published
description: v0.8.4 published 2026-06-17 (counter 20); Windows script-command launch fix (PATHEXT resolve)
metadata: 
  node_type: memory
  type: project
  originSessionId: 291b3f47-b265-4a38-867f-ac3d798281c0
---

v0.8.4 PUBLIC 2026-06-17 (counter 20); PATCH 0.8.3→0.8.4; Windows script-command launch fix. A start command resolving to a `.cmd`/`.bat` batch file or an extensionless CLI shim (e.g. node `ccs` launcher) failed with CreateProcessW os error 193 ("not a valid Win32 application") — daemon tried to exec the non-PE file directly. spt-core now PATHEXT-resolves the program (real exes preferred) + runs script targets via interpreter (cmd.exe/PowerShell). No change macOS/Linux. See [[ccs-win-pty-program-resolve]].

doyle merged PR#20 (6cbb11a) before handoff; deployah self-drive: bump c9ff19f (Cargo.toml 0.8.3→0.8.4 + AUTHORED CHANGELOG [0.8.4] from doyle's vetted body — [Unreleased] was empty, PR#20 added no entry + Cargo.lock 11 first-party only) → CI green BOTH → tag v0.8.4 @ c9ff19f → sign+publish (update-set v20). Hashes: linux `3ba0e390c6831455…` / win `183df369ce0edc85…`. doyle hash-check ✓. Spared third-party @ 0.8.3: filedescriptor, tinystr, yoke. Publisher leg 14× clean (counter 7-20).

GOTCHA: doyle pings for hashes can land WHILE publish still mid-flight (build ~1min) — finish publish, read output, then send; not a delay concern (doyle confirmed). See [[v083-published]] (same revive session), [[v090-published]].