- Add 🔑 Critical Context section with project structure table
- Document key configuration (PostgreSQL container name, ports)
- Add i18n completeness trap warning (check-i18n doesn't check zh-Hant.json)
- Add Language-Specific Notes for TypeScript/React and Go
- Add 🚫 Code Change Boundaries section with 4 workflow patterns
- Update freshness status to v0.93.2 (2026-02-08)

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

- Standardize field alignment in deltaStats, DeltaStats, TracingContext structs
- Improve i18n validation script with complete zh-Hant.json check
- Add cross-reference to DEBUG_LESSONS.md for migration notes
- Refine terminology: GraphQL/Proto → Proto/Schema
- Update code-reviewer agent description format

All tests pass, build successful.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

- Remove unused Database import from ProgressIndicator
- Fix Navigation i18n key path to ai.knowledge-graph.title
- Merge duplicate ai.progress keys into first ai key (en.json, zh-Hans.json)
- Apply auto-formatting fixes

Refs #120

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

- Fix matchPool.Get() type assertion in sensitive.go
- Add slog error handling in analyzer.go async save
- Fix defer close error handling in exporter.go
- Fix http.NewRequest nil to http.NoBody in prometheus_test.go
- Rename testErr to errTest for staticcheck compliance
- Remove unused matchPool.Put to avoid SA6002
- Simplify regex pattern using \S* instead of [^\s]*
- Remove unused fields and imports

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Add "Go Lint 常见陷阱" section with:
- Type assertion must use comma-ok pattern
- Defer error checking requirements
- Error comparison with errors.Is
- HTTP nil body should use http.NoBody
- error variable naming convention
- Regex simplification patterns
- sync.Pool usage restrictions

This section captures lessons learned from fixing 18 golangci-lint issues
in commit 14900ad, preventing future repetitions.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

…prompts

- Update document.documentElement.lang in applyLocaleEarly()
- Update document.documentElement.lang in loadLocale()
- Map zh-Hans → zh-CN, zh-Hant → zh-TW for BCP 47 compliance

This prevents Chrome/Google from offering to translate the page when
the user's browser language matches the content language.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

This commit fixes two issues with AI chat streaming:

1. **Tool call metadata fix**: tool_use events were incorrectly using
   response.eventData (JSON parameters) as toolName instead of
   eventMeta.toolName. Now correctly displays tool names like
   "schedule_query" instead of JSON strings.

2. **Optimistic block recreation fix**: Added blockAlreadyExists check
   to prevent recreating blocks on every SSE event, which was
   clearing the accumulated eventStream.

3. **Simplification**: Removed FIFO queue infrastructure (~250 lines)
   as SSE events are serial by nature - no concurrent updates occur.

Root causes:
- tool_use handler: toolName: response.eventData → toolMeta?.toolName
- Every SSE event triggered block recreation, resetting eventStream
- FIFO queue was over-engineering for serial SSE stream

Refs streaming UI debugging session

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Adds two new debug lessons:
1. Tool call metadata error - using eventData instead of eventMeta.toolName
2. Over-engineering: FIFO queue - SSE is serial, queue was always empty

Key takeaways:
- Diagnose before treating - add logs to confirm assumptions
- SSE doesn't need queuing - events are inherently serial
- Simplify over complexity - React Query has internal batching

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

- Remove console.log from eventTransformers.ts (extractToolCalls)
- Remove console.log from ChatMessages.tsx (eventStream debugging)
- Keep critical error logging in useAIQueries.ts

These debug logs were added during the streaming UI fix investigation
and are no longer needed now that the issue is resolved.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Add comprehensive technical specification for implementing full streaming
tool calls (Solution A) in AI chat system.

Key decisions:
- Adopt complete streaming mode (DeepSeek native support)
- Progressive enhancement strategy with backward compatibility
- New ChatStreamWithTools interface

Expected improvements:
- First tool call latency: ~800ms → ~200ms (75% reduction)
- Perceived latency: 3-5s → <1s (60% reduction)

Refs #125

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>