Promote hero_office_server (and hero_office_ui, hero_office_bridge) to hero_proc-managed services #4

New issue

Closed

opened 2026-04-26 07:47:40 +00:00 by zaelgohary · 0 comments

zaelgohary commented

2026-04-26 07:47:40 +00:00

Member

hero_office_server, hero_office_ui, and the hero_office_bridge UDS->TCP shim currently run under screen -dmS on dev machines. They are not registered as hero_proc services and do not survive a reboot — start commands live only in shell history.

Acceptance

Each binary registers itself with hero_proc on --start (matching the pattern in the hero_proc_service_singlebin / hero_proc_service_selfstart skills).
hero_proc service.list shows hero_office, hero_office_ui, hero_office_bridge (or a single composite hero_office action that starts all three).
hero_proc service.restart hero_office cleanly restarts the stack.
Reboot survival: services come back up automatically without manual screen sessions.

hero_office_server, hero_office_ui, and the hero_office_bridge UDS->TCP shim currently run under `screen -dmS` on dev machines. They are not registered as hero_proc services and do not survive a reboot — start commands live only in shell history. ## Acceptance - Each binary registers itself with hero_proc on `--start` (matching the pattern in the hero_proc_service_singlebin / hero_proc_service_selfstart skills). - `hero_proc service.list` shows `hero_office`, `hero_office_ui`, `hero_office_bridge` (or a single composite `hero_office` action that starts all three). - `hero_proc service.restart hero_office` cleanly restarts the stack. - Reboot survival: services come back up automatically without manual screen sessions.