From 88eecb1c71899b861614f110a4de5d0ce9b0bb18 Mon Sep 17 00:00:00 2001 From: Marcos Paulo Date: Sat, 5 Sep 2026 01:22:00 +0000 Subject: [PATCH] fix: gate the launcher's npm ci on a lockfile, not package.json The pre-existing root package.json has two scripts and no dependencies, and there is no package-lock.json until task 01 scaffolds Astro, so every launch died on `npm ci` before reaching the agent. Co-Authored-By: Claude Opus 5 --- .agents/scripts/launch.sh | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/.agents/scripts/launch.sh b/.agents/scripts/launch.sh index bf51c11..61612da 100755 --- a/.agents/scripts/launch.sh +++ b/.agents/scripts/launch.sh @@ -56,9 +56,10 @@ else git worktree add "$dir" -b "$branch" "$base" fi -# npm ci only once task 01 has produced a package.json. Before that there is no -# toolchain to install, and no hooks to verify. -if [ -f "$dir/package.json" ]; then +# npm ci only once task 01 has produced a lockfile. The pre-existing root +# package.json carries two scripts and no dependencies, so before task 01 there +# is no toolchain to install and no hooks to verify. +if [ -f "$dir/package-lock.json" ]; then ( cd "$dir" && npm ci --prefer-offline && .agents/scripts/verify-hooks.sh ) fi