Closes #80. MonitorToDiagnosticHandoff.anomaly_context was a raw prose string, the #1 context-passing anti-pattern: the Diagnostic sub-agent had to re-parse a narrative to recover what breached, by how much, and where. The downstream DiagnosisReport already uses structured claim-source records, so the first handoff now matches. - New DetectedAnomaly model (anomaly_type, summary, detected_at, plus optional metric / observed_value / baseline / threshold / breach_direction / affected_component / source_signal_ids) carries typed context. - MonitorToDiagnosticHandoff.anomaly: DetectedAnomaly replaces the string; the size-guard now truncates the only unbounded field (summary) so an over-long narrative can never overflow the diagnostic prompt. - _detect_anomalies returns DetectedAnomaly | None: it injects the schema into the detection prompt and parses the conclusion via _parse_detection, which falls back to wrapping prose in summary so detection always yields a typed object (no crash, no extra LLM call, detection stays one response). - _spawn_diagnostic_agent takes the typed anomaly and injects its JSON; runbook resolution runs off anomaly.summary (keeps _resolve_runbooks' string contract, so steering/runbook tests are untouched). Single-agent extractor uses the typed fields. Tests: DetectedAnomaly required/optional/round-trip, handoff typed + summary truncation + round-trip, _parse_detection JSON + prose fallback, and _detect_anomalies returns typed anomaly / None. Full suite 229 passed; ruff + mypy clean.

Commits

Commits on Jul 9, 2026

feat(agent): structured Monitor->Diagnostic handoff (typed, not prose)