Grok plugin validate reports hooks without opening hooks.json
The mode on hooks.json was 000. grok plugin validate still printed hooks at the end of the component line and exited 0. The line above that suffix was Plugin manifest is valid. The file was not opened. A later install of a different copy, twelve bytes and not JSON, also exited 0 and left those twelve bytes in the installed plugin.
That is what Grok 1.0.67 did on 18 November 2026. grok --version printed grok 1.0.67 (2fe064390d07). The host was Linux x86_64. No login was run. No model call was made. No TUI session was started. Each home under test was a new directory passed as HOME. The operator Grok home was not one of those directories, and its timestamp did not move during the run.