claude-hdb 8729c3e522 fix(grok): read the actual installer instead of guessing — the binary is 'grok' ... Fetched https://x.ai/cli/install.sh and read it, rather than inferring the layout from docs. Three facts, every one of which the template had wrong: · the CLI installs as 'grok' (with an 'agent' alias) — NOT 'grok-build'. So the drill was checking a command that never existed. · BIN_DIR defaults to $HOME/.grok/bin, and what lands there is a SYMLINK into the versioned download dir — which is exactly why the template's 'find -type f' found nothing. · GROK_BIN_DIR can override the directory. The install was almost certainly succeeding the whole time; the template was hunting for the wrong name, as the wrong file type, in the wrong place. Now it links the known path onto the system PATH, asserts 'grok --version' answers, and dumps what the installer actually left if the upstream layout ever moves. Also corrected: the drill's version check (grok, not grok-build), the agent briefing ('grok login'), the template description, and the README row. The lesson is the repo's oldest one — read the thing, don't reason about it.		2026-07-14 20:04:10 +00:00
..
box.env	fix(grok): read the actual installer instead of guessing — the binary is 'grok'	2026-07-14 20:04:10 +00:00
user-data.yaml	fix(grok): read the actual installer instead of guessing — the binary is 'grok'	2026-07-14 20:04:10 +00:00