Add reproducible randomized test order

docs/json-event-protocol.mdmodified+4-2

Changes to docs/json-event-protocol.md

		⋯34 linesShow the 34 lines above this hunk@@ -35,8 +35,8 @@ events are emitted in attempt order immediately before their `test_end`.
35	35
36	36	| Type | Data fields |
37	37	| --- | --- |
38		-| `run_start` | `total` |
39		-| `run_end` | `total`, `passed`, `flaky`, `failed`, `skipped`, `duration_ns` |
	38	+| `run_start` | `total`, optional `random_seed` |
	39	+| `run_end` | `total`, `passed`, `flaky`, `failed`, `skipped`, `duration_ns`, optional `random_seed` |
40	40	| `suite_start`, `suite_end` | `name` |
41	41	| `test_start` | `name`, optional `suite` |
42	42	| `test_end` | `name`, optional `suite`, `status`, `duration_ns`, optional `error_message` |
		⋯8 linesShow the 8 lines above this hunk@@ -51,6 +51,8 @@ Output streams are `stdout` or `stderr`.
51	51
52	52	Optional fields are serialized as `null` when no value is available. Durations
53	53	are unsigned integer nanoseconds. Percentages are numbers from 0 through 100.
	54	+When randomized ordering is enabled, both run events carry the reproducible
	55	+unsigned integer seed.
54	56
55	57	## Compatibility policy
56	58