• v0.27.1 08dbbfa197

    v0.27.1 — the undo denominator
    All checks were successful
    CI / gate (push) Successful in 2m16s
    CI / image (push) Successful in 1m54s
    Stable

    joeyr released this 2026-08-31 22:18:16 -05:00 | 518 commits to main since this release

    Instrumentation only — how undos are applied is unchanged.

    The crawl's window line now logs undos beside unmatchedUndos.

    unmatchedUndos is the tripwire on the one ITEM_UNDO assumption this service cannot verify: that an undone purchase carries the bought item in beforeId with afterId: 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=271 over 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.

    TimelineStats already counted undos per 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 in unmatchedUndos legitimately, so a small non-zero floor is expected — what matters is whether the two counts track each other.

    Downloads