feat(lang): rename concept_comparison to definition (v0.3.2)

Renames the `concept_comparison` keyword to `definition` across the
entire codebase for better readability and conciseness.

Changes:
- Tree-sitter grammar: `concept_comparison` node → `definition`
- Tree-sitter queries: highlights, outline, and indents updated
- Zed extension highlights.scm updated to match
- Lexer: `Token::ConceptComparison` → `Token::Definition`
- Parser: `ConceptComparisonDecl` rule → `DefinitionDecl`
- AST: `Declaration::ConceptComparison` → `Declaration::Definition`,
  `ConceptComparisonDecl` struct → `DefinitionDecl`
- All Rust source files updated (validate, names, convert, references,
  semantic_tokens, symbols, code_actions, hover, completion)
- `validate_concept_comparison_patterns` → `validate_definition_patterns`
- Example file and test corpus updated
- Spec docs: created SBIR-v0.3.2-SPEC.md, updated TYPE-SYSTEM.md,
  README.md, SBIR-CHANGELOG.md, SBIR-v0.3.1-SPEC.md

.claude/CLAUDE.md

@@ -76,7 +76,7 @@ feat(lexer): add type system keywords
 Added four keywords for new type system:
 - concept: Base type definition
 - sub_concept: Enum/record sub-type definition
-- concept_comparison: Compile-time enum mapping
+- definition: Compile-time enum mapping
 - any: Universal type for dynamic contexts
 ```
 
@@ -90,6 +90,14 @@ Added four keywords for new type system:
   - `SBIR-v0.2.0-SPEC.md` - Storybook Intermediate Representation binary format
 - `.claude/tmp` - Unlimited storage for temporary files. Use this for plans, reports, and other temporary data that is not part of the repository.
 
+## Debugging Protocol
+
+When debugging fails after 2 attempts, stop and enter plan mode. Explain your current hypothesis, what you've tried, and propose next steps before making more changes. Do not blame caching or environment without evidence.
+
+## Project-Specific: Zed Extension
+
+For Zed extension work: the compiled grammar is cached and `highlights.scm` must be bundled correctly. Never delete local query files assuming Zed will fall back to fetched ones. Always verify the extension builds and loads before declaring success.
+
 ## Testing Philosophy
 
 - Every feature needs tests