Repository navigation
Runner: append role lifecycle events to events.jsonl for GUI v1 #175
Description
From the approved GUI v1 decision (~/.cache/ntg-gui/decision-v1.ko.md): the runner should append one JSON line per role invocation start/end to an events.jsonl next to the ledger, so the GUI Office tab can show per-role states (start=working, end DONE/GO=done, end BLOCKED/NO_GO/FAILED=blocked, absent=idle).\n\nRequirements:\n- Line shapes: {"ts","role","milestone","event":"start"} and {"ts","role","milestone","event":"end","status","duration_ms"}\n- All string fields pass through the existing telemetry.mjs redaction\n- Ledger stays the source of truth; events.jsonl is a display-only append log\n- A failed events append must not fail the milestone; it logs a warning (never fully silent)\n- Unit + integration tests with stubbed invocations\n- No new dependencies
Activity
Merge pull request #176 from sleegme/feat/gui-events
sleegme commentedon Oct 28, 2026
Implemented by PR #176 (73b839e, merged). Live evidence from the 2026-10-28 #167 NTG run: events.jsonl lines match the required shapes, e.g. {"role":"bulldozer","milestone":"m1","event":"start"} / {"event":"end","status":"DONE","duration_ms":1013725}. tests/test_events.mjs and tests/test_runner_events.mjs pass on main. Closing. — 벨로나냥