-
released this
2026-08-31 22:18:16 -05:00 | 518 commits to main since this releaseInstrumentation only — how undos are applied is unchanged.
The crawl's window line now logs
undosbesideunmatchedUndos.unmatchedUndosis the tripwire on the oneITEM_UNDOassumption this service cannot verify: that an undone purchase carries the bought item inbeforeIdwithafterId: 0. It was never checked against a captured payload, because the key available when the parser was written returned 403.Until now only the numerator was logged. The window of 2026-08-31 closed with
unmatchedUndos=271over 200 timelines — which is either a handful of edge cases out of thousands of undos, or every undo in the window with the convention the other way round and undone purchases being published as real ones. Nothing in the line could tell those apart.TimelineStatsalready countedundosper timeline; the crawl summed only the unmatched half and dropped it. It now carries both, so the next window answers a question that has been open since the parser shipped. Read them as a pair: an undone sale lands inunmatchedUndoslegitimately, so a small non-zero floor is expected — what matters is whether the two counts track each other.Downloads
-
Source code (ZIP)
0 downloads
-
Source code (TAR.GZ)
0 downloads
-
Source code (ZIP)