devops agent: fleet control-panel buildout (tracks devops#9-13)

[vybe]

Summary

Tracks the devops agent's fleet control-panel buildout — a 5-issue, ~7-day plan to ship a password-gated UI for fleet oversight: fleet overview → per-instance detail (Agents/Telemetry) → backlog/monitor tabs → Uptime Kuma health badges + live execution SSE → deployment to the monitoring-stack instance.

Sub-issues (devops agent repo)

• devops#9 — Scaffold control/ + fleet overview page (Day 1-2, in-progress)
• devops#10 — Instance detail page: Agents + Telemetry tabs (Day 3)
• devops#11 — Backlog + Monitor tabs and fleet /backlog page (Day 4)
• devops#12 — Health badges + Uptime Kuma overlay + live exec SSE (Day 5)
• devops#13 — Deploy to monitoring-stack + admin password gate (Day 6-7)

Context

Centralizes oversight of the Trinity fleet behind one UI instead of jumping between per-instance dashboards. The buildout lives in the devops agent's own repository; this Trinity issue exists purely as a fleet-level tracker so the work is visible on the roadmap board.

Acceptance Criteria

• devops#9 closed — control/ scaffold + fleet overview reachable
• devops#10 closed — instance detail page renders Agents + Telemetry tabs
• devops#11 closed — Backlog + Monitor tabs and fleet /backlog page live
• devops#12 closed — health badges driven by Uptime Kuma, executions streamed via SSE
• devops#13 closed — deployed to monitoring-stack instance behind admin password

Technical Notes

Implementation lives in the devops agent's repository, not in abilityai/trinity. Update this tracker when sub-issue status changes; close it once devops#13 ships.

[obasilakis]

Final sub-issue devops#13 (admin password gate + monitoring-stack deploy) is up as Abilityai/trinity-ops-agent#37 — deployed and verified live on monitoring-stack (:3002, both containers healthy, full auth flow passing). That completes this tracker's last acceptance box.

Cross-repo Closes won't fire from the ops-repo PR, so this tracker will be closed manually once #37 merges.