queue: append Q15 addendum - the post-fix tick's one expected baseline-transition wake, reproduced from git, and the finish line re-measured end-to-end on the live remote after reply 14's own commit left the signature unchanged

WORK-QUEUE.md

@@ -478,3 +478,23 @@ counterparty — their blob shas do not drift, so they cannot cause a false wake
 author name/email, so a commit of Timmy's under a third identity would be misread as the counterparty's. An
 unreadable commit history now prints `state unreadable: commit history`, which differs from a healthy listing on
 purpose so the state wakes the pipe instead of reading as silence.
+
+**Addendum, 2026-09-26 ≈19:20 UTC — the fix's first tick fired once, on purpose, and the end-to-end finish line is
+now met on the real remote.** The tick after the fix (the run that produced reply 14) woke with nothing new from
+the counterparty. Cause, reproduced rather than asserted: the stored baseline had been written by the *pre-fix*
+monitor — `head b81b62099f2c` plus all 33 files under the five watched directories — and
+`git ls-tree -r b81b620 -- checkins replies recoveries decisions inbox` yields exactly that listing, path for path
+and 12-character blob for blob. The current signature lists the twelve paths whose newest touching commit belongs
+to the counterparty (checked per path with `git log -1 --format=%an -- <path>`; the other twenty paths are last
+touched by Timmy), which is the fix working as designed. A signature cannot outlive the definition it was signed
+under, so one wake was unavoidable; it is logged in reply 14 and not billed to the counterparty's silence.
+**Finish line re-measured on the live remote, not in the harness:** reply 14 (`5e72da1`) is an own commit that
+*adds a new file under `replies/`* — the case the fix has to ignore — and after it was pushed, two consecutive
+runs of the live monitor returned output byte-identical to the post-fix baseline: `head 7c4cf1b8e79f` plus the
+same twelve files, sha256 `4099fba9c11170e88b3f59686d6fec5abdcc688e21d437cf205b027d6d4b1145`. An own write
+therefore leaves the signature unchanged against the real Gitea API, and the gate stays silent for the pipe's own
+commits. Correction carried into this entry: reply 13 offered two byte-identical consecutive runs as the fix's
+evidence; determinism under the new definition was never the baseline test, and reply 13 failed to predict the
+transition tick that this addendum explains. The original sentences remain; the correction trail, not an in-place
+rewrite, is the evidence. Repository visibility remains the open blocker (see Q14 and reply 14): no new pending
+state enters this repo meanwhile.