{# -*- CUI // SP-CTI -*-
Reusable partial — Autonomous Recovery panel.
Shows the failure_triage + autofix + recent-failures stream so the
operator can see what the autonomous system is doing. Auto-hides
entirely when nothing is happening (no triage markers in the last 24h,
no autofix branches, no unresolved failures in the last hour).
Include on any page that wants this view:
{% include "_autonomy_status.html" %}
Host page must call refreshAutonomyStatus() AND refreshMergeReadiness()
on load and in its auto-refresh loop. The functions + window.ICDEV_AUTO
namespace are guarded against double-include.
Two sections, two visibility rules, on purpose (kpr-watch-03):
* Autonomous Recovery hides when nothing is being recovered.
* Awaiting Merge hides only when NOTHING IS OPEN, and stays visible and
says so when the report cannot be produced -- a panel that disappears
when it breaks is indistinguishable from a clean board. #}
Autonomous Recovery
active
{# ── Awaiting Merge (kpr-watch-03) ──────────────────────────────────────────
The kpr-watch-01 classification, on the page instead of in a report nobody
opens. Read-only by construction: there is no merge button and no un-draft
action here, and the API behind it (/api/merge-readiness) is GET with no
sibling POST. The point is to SEE what the automation is doing.
Its OWN section with its OWN visibility, deliberately NOT folded into the
Autonomous Recovery body above: that panel hides when nothing is being
recovered, which is precisely when a PR quietly stuck in awaiting_ci needs
looking at. #}