v0.0.6
LatestLocal crash capture, reviewable bug reporting without telemetry, unified version stamping, and download resilience.
Offline crash capture
Crashes and unhandled exceptions write to local storage whether reporting is on or off. The fatal crash handler runs without network calls. On the next launch, a banner offers the option to inspect and send the report, backed by a three-day cooldown.
Reviewable report queue
Reports live in an atomic local queue capped at three items, with fingerprint deduplication across seven days and a 64 KB body limit. Submission uses a prefilled GitHub issue form for manual review or a token-free draft. The application never stores a GitHub write credential.
Python engine exit capture
Unexpected Python exits are recorded directly from the process exit code, preserving failure details even when stdout closes before process termination.
Exit-point redaction
Stored summaries, report bodies, issue URLs, and network payloads scrub tokens, cookie headers, and sensitive parameters independently.
Length-guarded issue URLs
When a report body exceeds GitHub query-string URL length limits, Grablytic copies the full issue markdown to the clipboard and keeps the queue entry instead of losing the text.
Unified version stamping
The About screen, bug reports, and diagnostic logs now read the exact build version stamped from pubspec.yaml (0.0.6+6).
Engine controls and title safety
The engine logging level forwards properly to yt-dlp. Long video titles clamp in bytes to prevent filesystem errors, and resume scans search both download roots recursively.