Files
pad/docs
xarmian 76aa111e53 docs(metrics,deployment): finish the undecodable wording and answer the label question in the artifact (BUG-2739, codex round 6)
Round 6's end-to-end failover trace matched the comments step for step, so
both findings were prose again.

The struct comment above WatchSequenceResetsTotal still grouped
undecodable_message with subscription_resumed as 'we simply lost part of
it'. Only the second is demonstrable: for the first, the instance knows an
unreadable message arrived and cannot tell whether it was ours. Round 5
corrected the exported Help string and the docs but not this one — the same
claim in a fourth place, which is what a class-wide sweep is supposed to
prevent.

The counter_backward rename has now been raised three rounds running, each
time because the answer lives in a commit message and a reviewer reads
artifacts. It is answered where an operator with a broken dashboard would
look: no tagged release emitted the plural, so there is nothing to migrate.
Re-derived at 40b0db06 rather than restated.

Claude-Session: https://claude.ai/code/session_01JVDBKbgn3Xt7ndW1YoYd8X
2026-08-23 13:33:58 +00:00
..