Skip to content

v0.1.1 - one answer for the same window

Latest

Choose a tag to compare

@acrot0 acrot0 released this 14 Nov 18:16

The prose review found a real defect: two tools were reporting different totals for the
same window.

Fixed

Three tools, one answer. cf-cost summed per file, so a resumed session was charged
once per replay — $3,566 / 37 sessions against cf-analyze's $3,562 / 34. The page counted a
fork's replayed boundary records again, so it said 120 boundaries / 19.4M dropped where the CLI
said 119 / 19.2M; its error table was inflated the same way. One question — what counts as one
session?
— was answered in three places. dedupeResumed now lives in lib/transcript.mjs and
all three import it; the atlas also dedupes at the record level, because a fork carries a new
session id and the id-level rule cannot see the replay.

Verified on one machine's logs, 30-day window:

tool total boundaries dropped errors
cf-analyze $3,562.19 119 19,247,822 106
cf-cost $3,562.19 — — —
cf-atlas $3,562 119 19.2M 106

The README quoted the wrong numbers — including one this changelog calls a bug. It said
399.6M dropped tokens, which is the figure the cumulative-counter defect produced. The same
wrong figure shipped inside read-sessions.zip. Restated with a measurement window.

Both READMEs said "four skills" after build-atlas shipped in v0.1.0; skills/README.md
omitted it from the table entirely. A test now fails if a skills/ directory is missing from
either README.

The test badge claimed a count nobody maintained — 149 when the suite was 169, then 170,
then 177. Replaced with the live CI badge.

Added

docs/release.md — how a zip is built, why CreateFromDirectory needs absolute paths (a
relative call silently produced five identical 22-byte empty zips), and the check that catches
a fix landing in only one tool: compare the packed copy's numbers, not just that it starts.

Assets

Five skill zips, SKILL.md at each archive root. Every entry was diffed byte-for-byte against
this tag before upload. The zips embed file mtimes, so they are not reproducible byte-for-byte —
what is reproducible is the content.

177 unit tests, green on 3 OSes × Node 20/22/24.

MIT · acrot0