Expand description
Deterministic scripted traces for adapter cutover and dogfooding.
Protocol adapters are compared only after they have emitted the shared
AgentEvent vocabulary. This keeps trace-corpus checks independent of
ACP/native process details and makes failures replayable in CI or locally.
Structs§
- Scripted
Trace - A named, serializable normalized trace fixture.
- Trace
Comparison - Comparison result includes both event and replay-state equality. A pair of traces can reach equal state while still differing in protocol behavior; that distinction is useful during adapter cutover.
- Trace
Difference - The first event mismatch, if two normalized traces are not identical.