hyperhive/hive-c0re
müde 891223219e server: notify manager on admin-socket Rebuild outcomes
HostRequest::Rebuild was the only rebuild path that bypassed
notify_manager. dashboard / auto_update / actions::approve
already emit Rebuilt events on both success + failure, but a
'hive-c0re rebuild <name>' from the host CLI (and the recent
matrix-flake build failure that surfaced in journald) left the
manager in the dark.

mirror auto_update::rebuild_agent's pattern: on success →
Rebuilt{ok:true}, on failure → Rebuilt{ok:false, note=
format!('{e:#}')}. note carries the stderr tail lifecycle::run
collected (the actual nix error: missing prompt file, dep
build failure, etc.), so the manager has enough context to
adjust the agent's agent.nix without ssh-ing to the host.
2026-05-16 03:30:02 +02:00
..
assets dashboard: approval history tab on P3NDING APPR0VALS 2026-05-16 03:07:50 +02:00
src server: notify manager on admin-socket Rebuild outcomes 2026-05-16 03:30:02 +02:00
Cargo.toml dashboard: diff against applied/proposal/<id>, prefer fetched_sha 2026-05-15 23:18:17 +02:00