3 commits

Author	SHA1	Message	Date
A	b62dc1af33	feat: ban as type assertions, add runtime schema validation with valibot (#1775) ... * fix: resolve all biome lint warnings across the codebase - Replace all noExplicitAny with proper types (unknown, Record<string, unknown>) - Fix useBlockStatements in picker.ts (braceless if) - Fix useNumberNamespace in picker.ts (parseInt → Number.parseInt) - Codebase now passes biome lint with 0 errors and 0 warnings Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * feat: ban `as` type assertions, add runtime schema validation with valibot Replace all ~170 unsafe `as` type assertions across the entire codebase (production + tests) with runtime-validated alternatives: - Add GritQL biome plugin (`no-type-assertion.grit`) that bans all `as` casts except `as const` - Add valibot for schema-validated JSON parsing (`parseJsonWith`) - Add shared utilities: `parse.ts` (schema parsing), `type-guards.ts` - Replace `as` casts in all 5 cloud modules (aws, daytona, hetzner, digitalocean, fly) with valibot schemas + type guards - Replace `as` casts in shared modules (manifest, update-check, oauth, commands, history, ui) - Replace `as any` in all 26 test files with proper `new Response()` mocks and typed variables - Add 13 tests for parseJsonWith/parseJsonRaw - Add "Embrace Bold Changes" culture rule to CLAUDE.md - Bump version 0.6.19 → 0.7.0 1859 tests pass, 0 lint errors across 95 files, bundle +6KB from valibot. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * refactor: move GritQL plugin into cli/lint/ directory Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> --------- Co-authored-by: lab <6723574+louisgv@users.noreply.github.com> Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-02-22 18:50:53 -08:00
L	eea43adcad	fix: re-exec with new binary after auto-update for all invocations (#1526) ... Two bugs in reExecWithArgs(): 1. args.length === 0 early exit: Running bare `spawn` (interactive picker) after an auto-update would print "Run your spawn command again" and exit, requiring the user to manually re-invoke. Now always re-exec so the new flow triggers immediately. 2. process.argv[1] stale binary path: If the installer places the updated binary in a different directory than the currently running binary (e.g. old: ~/.local/bin, new: /usr/local/bin), re-exec would run the old stale binary. Fix: add findUpdatedBinary() which resolves via `which spawn` (PATH lookup) first, falling back to process.argv[1] only if which fails. Bump CLI version 0.5.17 → 0.5.18. Co-authored-by: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>	2026-02-20 10:26:02 -05:00
B	462cd367e0	chore: Switch from npm lockfile to bun lockfile ... Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-02-10 06:16:19 +00:00