Phase 16 — UI / operator implications

How the UI should render each actuation class (no green for REALRUN unless authority lands):

• PREVIEW_READY (show "Preview" action, ai or human): the 7 safe-triage action types; 132 AI-handleable orphans. Outcome = triage disposition, audit-only.
• DRYRUN_READY: same set (preview=true path). Safe to expose a "Dry-run" button that writes only an audit row.
• OWNER_BLOCKED (show "Needs owner", disabled): ASSIGN_OWNER, RECONCILE_TO_DOT; 15 owner-needed queue items; candidate-discovery automation; cron-35 / fs-101 reconcile; trigger_registry refresh.
• AUTHORITY_BLOCKED (show "Needs president", disabled): CREATE_BIRTH_REQUEST, SEND_TO_GOVERNANCE; 5 PROC-OWN; AX-TRIGGER registration; official process RP.
• OPERATOR_BLOCKED (show "Operator action", disabled): UI deploy (feat/rp-current-supervision), event activation/emit flip, REAL_RUN flips.
• REALRUN: must render NO_GO / red while v_rp_realrun_no_go_guard holds 8/8. Never green without live authority.

Scanner freshness in the UI: read from wf_scanner_run_log / workflow_scanner_registry is now valid (wired); still cross-checkable against wf_adapter_run_log. The v_rp_scanner_automation_reality view now labels them REAL_AUTOMATION_WIRED.