fix hover on keywords returning wrong content

When hovering over control flow keywords (if, else, range, end), the LSP
incorrectly returned the next sibling keyword instead of empty content.
For example, hovering on 'if' would show 'else'.

Fixed by returning nil early from FindSourceDefinitionFromPosition when
IsKeyword is true. Added test to verify keywords return empty hover.

Also updated CLAUDE.md to reflect the actual project (Go template LSP).

Author: Jason-Abbott

.beans/gozer-45gq--hover-on-keywords-returns-wrongunexpected-content.md

@@ -0,0 +1,23 @@
+---
+# gozer-45gq
+title: Hover on keywords returns wrong/unexpected content
+status: completed
+type: bug
+created_at: 2026-01-19T17:18:47Z
+updated_at: 2026-01-19T17:18:47Z
+---
+
+When hovering over control flow keywords like `if`, `else`, `range`, `end`, the hover handler returns incorrect content (e.g., showing 'else' when hovering on 'if').
+
+## Root Cause
+In `analyzer_lsp.go`, `FindSourceDefinitionFromPosition` sets `IsKeyword = true` when the cursor is on a keyword (lines 303-308), but then doesn't check this flag - it proceeds to try matching the keyword as a variable/template definition, producing wrong results.
+
+## Expected Behavior
+Keywords should either:
+1. Return no hover content (preferred - they're not identifiers with type info)
+2. Return documentation about the keyword
+
+## Checklist
+- [x] Create failing test demonstrating the bug
+- [x] Fix `FindSourceDefinitionFromPosition` to return nil when `IsKeyword` is true
+- [x] Run tests and linter

CLAUDE.md

@@ -1,45 +1,11 @@
-# CLAUDE.md
+# Gozer
 
-This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
-
-## Overview
-
-HTML linter written in Go. Validates HTML for accessibility, best practices, and common mistakes. Implements rules from html-validate.org.
+Go HTML template LSP and Zed extension
 
 ## Guidelines
 
 - Be concise
+- When fixing or investigating code issues, ALWAYS create a failing test FIRST to demonstrate understanding of the problem THEN change code and confirm the test passes
 - Run `golangci-lint run --fix` after modifying Go code
 - Run `go test ./...` after changes
 - **NEVER commit without explicit user request**
-- Use external test packages (`package foo_test`)
-
-## Commands
-
-```bash
-go build ./...                        # Build
-go test ./...                         # Test all
-go test ./linter -run TestLintContent # Run single test
-golangci-lint run                     # Lint
-go install .                          # Install to $GOBIN
-go-html-validate --help               # Usage
-```
-
-## Architecture
-
-**Data flow:** `main.go` → `linter.Linter` → `parser.ParseFragment` → `rules.Rule.Check()` → `reporter.Reporter`
-
-**Key types:**
-- `parser.Document` - parsed HTML tree with `Walk(func(*Node) bool)` for traversal
-- `parser.Node` - wraps `html.Node` with `HasAttr()`, `GetAttr()`, `TextContent()`, `IsElement()` helpers
-- `rules.Rule` interface - `Name()`, `Description()`, `Check(*parser.Document) []Result`
-- `rules.Result` - lint finding with `Rule`, `Message`, `Filename`, `Line`, `Col`, `Severity`
-
-**Template handling:** The parser preprocesses Go template syntax (`{{...}}`) before parsing. Files starting with `{{define` are marked as template fragments.
-
-## Adding Rules
-
-1. Create `rules/rule_name.go` implementing `rules.Rule` interface
-2. Add rule name constant to `rules/rule.go`
-3. Register in `NewRegistry()` in `rules/rule.go`
-4. Add tests in `linter/linter_*_test.go` (grouped by category: accessibility, validation, deprecated, etc.)

internal/template/analyzer/analyzer_lsp.go

@@ -32,6 +32,11 @@ func FindSourceDefinitionFromPosition(
 		return nil
 	}
 
+	// Keywords (if, else, range, end, etc.) don't have hover content
+	if seeker.IsKeyword {
+		return nil
+	}
+
 	//
 	// 2. From the node and token found, find the appropriate 'Source Definition'
 	//

internal/template/template_test.go

@@ -710,3 +710,68 @@ func TestHover_MultipleInstancesSameLine(t *testing.T) {
 		})
 	}
 }
+
+// TestHover_KeywordsReturnEmpty verifies that hovering over control flow keywords
+// (if, else, range, end, etc.) returns empty hover content, not incorrect values.
+func TestHover_KeywordsReturnEmpty(t *testing.T) {
+	// Template with various control flow keywords
+	// Line 0: {{if .Cond}}yes{{else}}no{{end}}
+	//           ^^ if at char 2
+	//                          ^^^^ else at char 16
+	//                                    ^^^ end at char 25
+	source := `{{if .Cond}}yes{{else}}no{{end}}`
+
+	root, parseErrs := template.ParseSingleFile([]byte(source))
+	if len(parseErrs) != 0 {
+		t.Fatalf("Parse errors: %v", parseErrs)
+	}
+
+	workspace := map[string]*parser.GroupStatementNode{
+		"test.html": root,
+	}
+
+	file, _ := template.DefinitionAnalysisSingleFile("test.html", workspace)
+	if file == nil {
+		t.Fatal("Expected non-nil file definition")
+	}
+
+	testCases := []struct {
+		name string
+		pos  lexer.Position
+	}{
+		{
+			name: "if keyword",
+			pos:  lexer.Position{Line: 0, Character: 3}, // on "if"
+		},
+		{
+			name: "else keyword",
+			pos:  lexer.Position{Line: 0, Character: 17}, // on "else"
+		},
+		{
+			name: "end keyword",
+			pos:  lexer.Position{Line: 0, Character: 26}, // on "end"
+		},
+	}
+
+	for _, tc := range testCases {
+		t.Run(tc.name, func(t *testing.T) {
+			hoverText, hoverRange := template.Hover(file, tc.pos)
+
+			if hoverText != "" {
+				t.Errorf(
+					"Expected empty hover text for %s, but got %q",
+					tc.name,
+					hoverText,
+				)
+			}
+
+			if !hoverRange.IsEmpty() {
+				t.Errorf(
+					"Expected empty hover range for %s, but got %v",
+					tc.name,
+					hoverRange,
+				)
+			}
+		})
+	}
+}