Events

Events are Hexi's primary observability contract.

Event fields

• type: progress | question | review | artifact | error | done
• one_line_summary: concise operator-facing summary
• blocking: whether user input/action is required
• payload: structured machine-readable details

Where events go

• Rich console output for live operator feedback
• .hexi/runlog.jsonl for durable run history

Typical event sequence

1. progress (run started)
2. progress (plan parsed)
3. action-level events (artifact, question, or error)
4. review (git status/diff summary)
5. done (terminal status)

Event quality rules

• Keep summaries short and specific.
• Put parsable details in payload keys.
• Include actionable error causes, not generic messages.