[#86]: Add effort and terminalSequence fields for Claude Code v2.1.133+/v2.1.141+ compat

[delexw]

Summary

Fixes #86 — Claude Code v2.1.133 and v2.1.141 introduced new fields in hook-related JSONL entries that the parser should handle explicitly.

Changes in Claude Code:

• v2.1.133: Hook input JSON now includes effort: {level: "low"|"normal"|"high"} at the top level.
• v2.1.141: Hook output entries may include terminalSequence at the top level (for desktop notifications, window titles, bells).

What changed

src-tauri/src/parser/entry.rs — two new fields added to the Entry struct:

// v2.1.133+: effort:{level} injected into hook input JSON
pub effort: Option<Value>,

// v2.1.141+: hooks may emit this to trigger desktop notifications/bells
pub terminal_sequence: Option<String>,

The parser already used serde defaults (no #[serde(deny_unknown_fields)] anywhere), so these fields were silently ignored before — no crash risk existed. This PR makes the capture explicit so callers can inspect the values.

Tests added (5 new)

• parse_entry_captures_effort_field_v2_1_133 — verifies effort.level is captured from hook progress entries
• parse_entry_effort_defaults_to_none_when_absent — pre-v2.1.133 entries have effort: None
• parse_entry_captures_terminal_sequence_field_v2_1_141 — verifies terminalSequence is captured from hook output entries
• parse_entry_terminal_sequence_defaults_to_none_when_absent — older hook entries have terminal_sequence: None
• parse_entry_unknown_fields_are_silently_ignored — documents and verifies future unknown fields don't crash the parser

Verification

test result: ok. 386 passed; 0 failed (cargo test)
Test Files  27 passed (vitest)
Tests       352 passed (vitest)
cargo clippy -- -D warnings: no warnings