docs(chaos): add the intermittency datum the new capture's second run produced

The Chaos lane ran twice on the same branch, separated only by two documentation commits -
no Java, no pom, no workflow. First run red on the BLOCKED-on-monitor discriminator, second
run green: 1 of 2, different seeds, on a tree that is identical for every purpose this
failure could care about.

That is the closest-together same-tree pass/fail pair this file has, and it says what the
looser pair already cited says - the trigger is the schedule, not the tree. Recorded as
intermittency, NOT as a clearance: a green run has never been read as one here, and the seed
above is still unreplayed.

Author: astubbs

docs/inflight/bug-857-family.md

@@ -1817,6 +1817,18 @@ waiting to acquire a monitor**, on an `AtomicBoolean` held by `pc-control-PC-12`
 `commitOffsetsThatAreReady` reached from `onPartitionsRevoked`. The instrumentation states the
 disjunction it was written to settle: contention or a lock-ordering defect, **not** a slow broker.
 
+<!-- post-merge: checked-begin -->
+**It did not reproduce on the next run of the same tree, which is an intermittency datum rather
+than a clearance.** The two `Chaos Pain Suite` runs on astubbs/parallel-consumer#379 are separated
+only by two documentation commits - no Java, no pom, no workflow - so the tree the second run
+scheduled is the first run's tree for every purpose this failure could care about. One red, one
+green: **1 of 2**, with different seeds each time, since the lane seeds per run. That is the same
+shape as the pair of runs one commit apart already cited above, and it says the same thing - the
+trigger is the schedule, not the tree - on a pair whose two halves are closer together than any
+previous one. It is not evidence the capture was noise, and a green run has never been treated as
+one here.
+<!-- post-merge: checked-end -->
+
 <!-- post-merge: checked-begin -->
 **Not the observing PR's defect.** It was seen on astubbs/parallel-consumer#379, which adds an
 unpublished Kafka Streams build-machinery module and touches no core Java, no locking, no rebalance