📖About

Today the escalation message reads 'last exec 412 failed; no recovery in flight' — that's queue metadata, not analysis. Albus has already investigated by the time Orion sees the escalation (every escalation = Albus could not self-recover); his rationale + verdict already exist in his last handshake payload. Surface that. Fix: in the Monitor's escalation card builder, after pulling needs_attention_reason, look up the latest al-auto-01 handshake whose payload references the failed exec_id, extract verdict + rationale, append/include them in the failure_reason output. Add an albus_diagnosis field on the response too so future UIs can render it as a structured block.