docs: record the 2026-07-26 baseline, both releases, and the pending checkpoints#97
Merged
Merged
Conversation
…checkpoints Captures the snapshot taken immediately before the v0.7.2 posts: 4 stars, 0 forks, 0 watchers, 195 views from 25 unique visitors, 634 clones from 204 unique cloners, 677 npm downloads over seven days and 0 today. The 204 unique cloners against 25 unique visitors, and the 516-then-0 download pattern around release days, continue to indicate automation rather than people. Recorded as such rather than counted as adoption. Notes what changed in the log's own terms: the binding constraint through 2026-07-25 was correctness, since promoting a tool that could not find chalk's own colour detection would have converted qualified visitors into permanent non-users. That is fixed and measured. What remains is that nobody outside this repository has run FixMap and said anything about it, and no further ranking work changes that number. Also records the two figures deleted this release — a token proxy measured against reading an entire repository, and a minutes-saved comparison against an unmeasured baseline — and the six passages of ready-to-paste post copy in the growth kit that quoted a hit rate which was never reproducible. The X and LinkedIn rows are entered with pending URLs rather than omitted, so the 24- and 72-hour checkpoints stay honest if either post produces nothing. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Snapshot taken immediately before the v0.7.2 posts, so the rolling 14-day GitHub window is preserved rather than reconstructed later.
204 unique cloners against 25 unique visitors, and 516 downloads on one release day followed by 0 today, continue to read as automation rather than people. Recorded as such.
The interpretation section states the thing the log exists to track: through 07-25 the binding constraint was correctness, and promoting a tool that could not find chalk's own colour-detection code would have converted qualified visitors into permanent non-users. That is now fixed and measured across three suites. What remains is that nobody outside this repository has run FixMap and said anything about it — and no further ranking work moves that number. The next milestone worth recording is one issue opened by a stranger.
Also records what v0.7.1 and v0.7.2 changed for evidence rather than features: the held-out suite, the confidence intervals, the two deleted figures, and the six passages of ready-to-paste growth-kit copy that quoted a hit rate which was never reproducible.
X and LinkedIn rows are entered with pending URLs rather than omitted, so the 24- and 72-hour checkpoints stay honest if either post produces nothing.
🤖 Generated with Claude Code