A eec83898e4 fix(kilocode): add binary verification after npm install to recover from silent postinstall failures (#2707) ... @kilocode/cli v7+ uses a native binary postinstall that downloads a platform-specific binary. On some clouds (notably GCP with cloudInitTier "node"), this postinstall can fail silently, leaving the npm bin symlink pointing to a JS wrapper with no actual native binary to exec. The fix adds a KILOCODE_BINARY_VERIFY shell snippet that runs after npm install and: 1. Checks if kilocode is already working (fast path) 2. If not, finds the npm package dir and re-runs the postinstall 3. If still not found, searches for the native binary in the package dir and symlinks it into a PATH-accessible location Fixes #2706 Agent: code-health Co-authored-by: B <6723574+louisgv@users.noreply.github.com> Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>		2026-03-17 08:30:00 -07:00
..
cli	fix(kilocode): add binary verification after npm install to recover from silent postinstall failures (#2707)	2026-03-17 08:30:00 -07:00
shared	feat: add downloadFile to CloudRunner + local OpenClaw config merge (#2636)	2026-03-14 15:47:32 -07:00