Structured KASAN/oops console-report parser and symbolizer

## Problem

Boot-outcome classification is literal substring matching (`readiness.py` / `crash_signatures`); an agent must eyeball the raw KASAN/oops report in the console artifact.

## Proposed work

A tool that parses a KASAN/oops report into `{bug_type, fault_address, access, call_stack[]}` and symbolizes bare addresses against the staged vmlinux.

**Scope:** new parser over the redacted console/dmesg + the debuginfo resolver.

## Acceptance

Given a Run whose console contains a KASAN report, one call returns the structured report with a symbolized call stack.

---
*Source: OPUS_REVIEW.md §5, item I-10 (Tier 4, nice-to-have). Would speed every test case.*

Start by reading readiness.py and crash_signatures to understand the current literal boot-outcome matching, then trace how redacted console/dmesg content and the staged vmlinux debuginfo resolver are exposed. The work is done when a Run containing a KASAN report yields bug_type, fault_address, access, and a symbolized call_stack in one call.

Written by the indexing model from the issue text.