dev 6bf5687aca session: a snapshot publishes the telemetry of the transition that just ended ... AgentSlot.telemetry was written only by the Agent.Initialize handler, so every CommittedSnapshot carried warm-up telemetry labelled as boundary k while each AgentCommitResult.telemetry was validated and dropped. The commit result is now stored on the slot beside the committed step, and the media test asserts that published telemetry advances across boundaries instead of merely being nonzero. A refused snapshot is recorded and sequenced like a refused descriptor revision, because the repair path exists for the consumer that did not receive it; the sequence advances with the value rather than with the delivery, so two snapshots can never share one. The query service counts an answer it could not deliver rather than discarding the result, and an unreadable event batch is distinct from the end of the stream.		2026-09-22 20:18:49 +00:00
..
common	session: parallel processes, a launcher and the fault behaviour	2026-09-22 14:33:25 +00:00
failures.rs	session: resolve uncertain calls, and measure each mode in its own process	2026-09-22 15:41:42 +00:00
media.rs	session: an unknown launch option is an error, not a no-op	2026-09-22 16:28:59 +00:00
processes.rs	session: name the two ways a durable wait ends without an acknowledgment	2026-09-22 18:45:51 +00:00
publishing.rs	session: a snapshot publishes the telemetry of the transition that just ended	2026-09-22 20:18:49 +00:00
session.rs	Merge main: the per-fly processes, the launcher and the thread budgets	2026-09-22 16:07:30 +00:00
state.rs	session: name the two ways a durable wait ends without an acknowledgment	2026-09-22 18:45:51 +00:00