also looking at this
Define stable JSON event protocol
#27
11 files
+442
-177
| @@ -43,9 +43,10 @@ New plan producers should append `PlanItem` values. New executors should emit | ||
| 43 | 43 | implement `Reporter.VTable`; `EventStream` adapts the typed lifecycle to that |
| 44 | 44 | stable callback interface. |
| 45 | 45 | |
| 46 | The event types are intentionally internal Zig structures. The separately | |
| 47 | versioned JSON wire protocol is built on this layer rather than making this API | |
| 48 | depend on one serialization format. | |
| 46 | The lifecycle structures remain format-independent. The JSON reporter, live UI, | |
| 47 | and test history adapt them to the public, versioned | |
| 48 | [JSON event protocol](json-event-protocol.md), so integrations share one wire | |
| 49 | model without coupling the execution API to JSON. | |
| 49 | 50 | |
| 50 | 51 | ## Migration |
| 51 | 52 | |