0xbyt4 eeda18a9b7 chore(tui): record gateway exit reason in crash log ... Gateway exits weren't reaching the panic hook because entry.py calls sys.exit(0) on broken stdout — clean termination, no exception. That left "gateway exited" in the TUI with zero forensic trail when pipe breaks happened mid-turn. Entry.py now tags each exit path — startup-write failure, parse-error- response write failure, per-method response write failure, stdin EOF — with a one-line entry in ~/.hermes/logs/tui_gateway_crash.log and a gateway.stderr breadcrumb. Includes the JSON-RPC method name on the dispatch path, which is the only way to tell "died right after handling voice.toggle on" from "died emitting the second message.complete".		2026-04-23 16:18:15 -07:00
..
__init__.py	feat: new tui based on ink	2026-04-02 19:07:53 -05:00
entry.py	chore(tui): record gateway exit reason in crash log	2026-04-23 16:18:15 -07:00
render.py	tui: inherit Python-side rendering via gateway bridge	2026-04-05 18:50:41 -05:00
server.py	chore(tui): dump gateway crash traces to ~/.hermes/logs/tui_gateway_crash.log	2026-04-23 16:18:15 -07:00
slash_worker.py	feat: personality	2026-04-08 00:15:15 -04:00