Previous run produced "The system cannot find the path specified."
with exit 2 right after ISCC's banner — ISPP loaded fine (Martijn Laan
copyright printed) but then 200ms of work and silent path failure.
Three changes to isolate/fix:
- Sync `[System.IO.Directory]::SetCurrentDirectory` alongside
Push-Location. PowerShell's Push-Location updates the PSDrive
location but not the .NET process cwd that native exes inherit, so
ISCC may have been resolving `..\dist` against the wrong dir.
- Bake AppVersion into a temp `.gen.iss` instead of passing
`/DAppVersion=...`, removing /D from the equation.
- Pass `/O<absolute path>` so OutputDir resolution doesn't depend on
cwd at all.
Also dumps the iscc log file contents and prints PS-vs-.NET cwd before
and after Push-Location so the next run shows whether the divergence
was real.