Surface sustained CPU incidents

[heznpc]

What changed

• elevate sustained full-core CPU observations above storage and browser-automation findings on the main diagnosis screen
• correlate the observation PID with the process snapshot so the owning app and executable path are shown
• route the recovery action to Activity while keeping process termination manual
• exclude Modore's own scan process from this incident class

Why

Modore already captured Taxi's Node runtime at 102.7% sustained CPU, but the trust-safe process classification and incident priority ladder buried that evidence. A legitimate executable can still be stuck and causing heat, battery drain, and UI latency.

Verification

• swift test --package-path macos/Modore — 488 passed
• python3 -I -B -m pytest tests/test_rule_engine.py -q — 45 passed
• release app built, installed, and launched
• existing real Taxi scan renders Taxi가 CPU 한 코어 이상을 계속 사용합니다, 102.7%, and the Taxi executable path on the first screen