feat(intel): per-character system tracking from Local logs

[AreteDriver]

Stacked on #64 → #63 → #62. Merge order: #62 → #63 → #64 → this. Each PR auto-retargets to `main` as its base merges.

Summary

EVE writes a separate `Local_*.txt` chat log per character session. The header has a `Listener:` line naming the character; the body has `Channel changed to Local : ` lines whenever that character jumps. We parse both into a per-character current-system map.

What's new

• `intel/character_location.py` — `CharacterLocationTracker(QObject)`:
  • Polls `Local_*.txt` files (UTF-16-LE) in the EVE chat log directory
  • Parses `Listener:` header once per file (4KB scan, regex)
  • Tails for `Channel changed to Local : X` and emits `character_system_changed(char_name, system)` only on real changes
  • File rotation/truncation handling, garbage-line rejection, idempotent start/stop
• `StatusDock.set_character_system` — updates every chip for a character (multibox-aware: same character in multiple windows all sync together)
• `WindowManager._character_systems` — persistent per-character map that survives window add/remove cycles
• `MainWindowV21._init_location_tracker` + `_on_character_system_changed` slot — forwards updates to dock + manager
• `MainTab._sync_status_dock` seeds chip systems from cached state so newly-imported windows populate without waiting

Why this matters

This is the architectural unlock for chip-level / frame-level threat differentiation. Previously the parser tracked one global `current_system` (`intel/parser.py:326`) — every chip and frame shared it. Now each character has independent location state, so a future PR can tint only the frames whose character is in (or near) the affected system.

Phase A — explicit scope

This PR ships the tracker + UI sync of system labels only. Smart per-character threat fan-out (filter `apply_threat_state` by character system) is deliberately a follow-up. The storage map exists; the fan-out semantics decision is parked until per-char tracking is observed in production.

Test plan

• 33 new tests in `tests/test_character_location.py` (header parsing, channel-changed line parsing, multi-character, file truncation, lifecycle, parametrized garbage-line rejection, dock + manager setters, MainWindowV21 wiring, MainTab seeding)
• 1 existing test patched (`test_init_creates_core_modules` now also patches `_init_location_tracker`)
• Full suite: 2289 passed, 5 skipped, 0 failures
• `ruff check` + `ruff format --check` clean
• Manual smoke: run with `intel.track_character_locations=true` while EVE is running, jump systems on multiple characters, verify each chip's system label updates independently

Settings

• `intel.track_character_locations` — default `true`. Tracker idles if false or if no EVE log directory is found.

Follow-ups (future PRs)

• Smart fan-out: `apply_threat_state(level, system)` → only tint frames whose character is in `system`, with a fallback for unknown locations
• Jumps-from: integrate `JumpCalculator` per-character so danger pulses on chips in adjacent systems too
• Per-character accent border: frame inherits chip's accent color when threat is clear

🤖 Generated with Claude Code

[gemini-code-assist]

Code Review

This pull request introduces a CharacterLocationTracker to monitor EVE Online chat logs for character system changes and update the UI. Feedback points out a performance risk in scanning the entire log directory on the GUI thread and a potential bug where advancing the file cursor during partial reads could cause missed events.

[gemini-code-assist]

Scanning the entire chat log directory every 2 seconds is a significant performance risk. EVE Online players often accumulate thousands of log files over time. Since glob("Local_*.txt") returns all historical logs and this method runs on the GUI thread, it can cause the application to hang or stutter as it iterates and stats every file. It is recommended to limit the search to files modified recently (e.g., today and yesterday) using a more specific glob pattern based on the date strings in the filenames.

Suggested change

	files = list(self._log_directory.glob(_LOCAL_FILE_GLOB))
	import time
	today = time.strftime("%Y%m%d", time.localtime())
	yesterday = time.strftime("%Y%m%d", time.localtime(time.time() - 86400))
	try:
	files = list(self._log_directory.glob(f"Local_{today}_*.txt"))
	files.extend(self._log_directory.glob(f"Local_{yesterday}_*.txt"))

[gemini-code-assist]

Updating state.position to fb.tell() immediately after reading to EOF can lead to missed events if a log line is partially written at the moment of polling. The partial line will be read, fail to match the regex (because it is incomplete), and then be skipped in subsequent polls because the cursor has moved past it. To ensure robustness, the tracker should only advance the position to the end of the last complete line (ending in a newline) found in the buffer, or buffer the remainder for the next poll.