Julian lechnerandClaude Sonnet 5 6314b408b3 fix(build): add explicit exit 0 on success (PowerShell) ...

Without it, a stale $LASTEXITCODE left over from an earlier native
command in the same PowerShell session could cause a CI step to be
reported as failed even though the script itself completed successfully.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

2026-09-11 16:06:42 +02:00

..

lib

fix: mark shell scripts executable in git

2026-09-11 16:06:37 +02:00

build.ps1

fix(build): add explicit exit 0 on success (PowerShell)

2026-09-11 16:06:42 +02:00

build.sh

fix: mark shell scripts executable in git

2026-09-11 16:06:37 +02:00

doctor.ps1

feat(doctor): validate managed files, counts, and config syntax (PowerShell)

2026-09-11 15:43:10 +02:00

doctor.sh

fix: mark shell scripts executable in git

2026-09-11 16:06:37 +02:00

install.ps1

feat(installer): install via managed manifest with non-interactive params (PowerShell)

2026-09-11 15:42:59 +02:00

install.sh

fix: mark shell scripts executable in git

2026-09-11 16:06:37 +02:00

test-build-validation.ps1

test: add build-time validation regression tests (PowerShell)

2026-09-11 15:43:31 +02:00

test-build-validation.sh

fix: mark shell scripts executable in git

2026-09-11 16:06:37 +02:00

test-managed-install.ps1

test: add managed-manifest installer scenarios (PowerShell)

2026-09-11 15:43:21 +02:00

test-managed-install.sh

fix: mark shell scripts executable in git

2026-09-11 16:06:37 +02:00

test-platform-packages.ps1

test: derive expected agent and skill counts from source (PowerShell)

2026-09-11 15:42:36 +02:00

test-platform-packages.sh

fix: mark shell scripts executable in git

2026-09-11 16:06:37 +02:00