hooks.json: unknown keys (name, description, conditions) trigger a Claude Code load warning

Start with hooks/hooks.json and compare both matcher entries with Claude Code's accepted hook schema. Check hooks-config.json and lsp-hooks.sh to confirm extension filtering remains covered, then verify the warning is gone on plugin load and /reload-plugins without changing hook behavior.

Claude Code 2.1.274 warns at plugin load:

lsp-tools: hooks.json: unknown keys "name" in hooks.PostToolUse[0], "description" in hooks.PostToolUse[0], "conditions" in hooks.PostToolUse[0], "name" in hooks.PreToolUse[0], "description" in hooks.PreToolUse[0] ignored

Plugin: lsp-tools 0.4.0 (via zircote/lsp-marketplace), macOS.

Cause: hooks/hooks.json puts name, description and conditions on the matcher entries. Claude Code's hook schema only accepts matcher and hooks there, so the three keys are dropped and the warning prints on every session start and /reload-plugins.

Impact: cosmetic. The hooks still register and run. conditions.fileExtensions never took effect, but lsp-hooks.sh already filters by extension through hooks-config.json, so behaviour is unchanged.

Suggested fix: remove the three keys from both entries. The extension list is already covered by hooks-config.json; the descriptions can live in the README or a top-level comment field. Removing them locally clears the warning with no change in hook behaviour.