docs(blog): publish reading a falling crash count - #43
Merged
Conversation
Git-Session-Id: fb6c
Owner
Author
🤖 AI code reviewAdds a blog post about building durable Android error reports for ActivityWatch, describing the Play Console API query approach, interpretation caveats, snapshot/disposition strategy, and results from a live read-only verification. Safe to merge — no P0/P1 findingsConfidence 5/5 ✅ No findings. The diff looks correct to me on this pass. Reviewed Maintainer commands
|
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
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.
Publish “Reading a Falling Crash Count,” a concrete account of the Android error-report work in ActivityWatch/stats#28. It explains rolling-window count changes, top-N disappearance, issue identity, and the limits of the two live validation collections. The implementation's pending merge and production verification are explicit.
Includes the scoped OG card. Full website build, scoped prek hooks, source frontmatter/public-URL/redaction checks, and the PR quality gate (100/100) passed. Independent fact review verified the saved observations and exact implementation revision; a separate editorial review checked the card and full-build HTML metadata, table, and code rendering.