docs: blog post: aw-tauri and ActivityWatch v0.14 (supersedes #34)

[TimeToBuildBob]

The Tauri story for ActivityWatch v0.14.0, superseding #34. The release tag now exists; the post is dated for launch and this PR is ready to merge together with #84.

This branch preserves 0xbrayo's original #34 commits and authorship, then updates the post for the v0.14.0 release. The filename _posts/2024-05-13-introducing-tauri.md remains unchanged, as Erik requested, so the permalink slug stays introducing-tauri.

Credit: original post and most of aw-tauri by 0xbrayo (Brian Vuku); the author front matter is unchanged. Wording from Erik's review on #34 is kept, including the caveat that ActivityWatch still runs an HTTP server and therefore still needs the same network precautions.

Final launch state

• v0.14.0 stable is tagged at 99259fec (annotated tag created 2026-10-06 12:10 UTC); GitHub release publication is still pending.
• Front matter date is 2026-10-06 14:00 +0200.
• Copy and links now target v0.14.0 stable, including the exact release tag URL.
• Updater copy reflects the stable behavior: built-in updates on macOS/Linux, manual install on Windows.
• Tauri remains explicitly experimental and ships beside the classic aw-qt distribution.
• Linux packaging copy distinguishes self-contained AppImage/deb/rpm bundles from the zip's optional Python watchers and installer helper.
• The screenshot shows the actual Tauri Activity view with demo data, per Erik's review.
• Greptile reviewed the substantive post at 5/5; its two findings and Erik's screenshot request were addressed.

Verified against primary sources

• ActivityWatch v0.14.0 annotated tag points to release commit 99259fec3315746e16ff99d5f7337d8f7c16e618.
• Tauri assets exist for Windows x86_64, macOS arm64/Intel, and Linux x86_64/aarch64 in the release build outputs.
• aw-tauri sources document the own-webview/tray process, restart behavior, autostart, opt-in sync, native notifications, Linux awatcher, and updater behavior.
• v0.14.0b8 assets were used for the installer-size comparison; the post labels those figures accordingly.
• The final markdown front matter and screenshot paths are valid. The companion posts: ActivityWatch v0.14.0 release announcement #84 site build passes.

Deliberate boundaries

• Windows and macOS bundle contents are not generalized beyond verified installer formats.
• Download-size figures are not presented as runtime-memory measurements.
• The downloads page is described honestly as linking the classic build by default; Tauri users are sent to the exact release assets.

[greptile-apps]

Confidence Score: 5/5

[Low risk] Blog post and screenshot for a new release.

The changes appear safe to merge from a review standpoint, subject to the post’s stated hold until the stable release and its publish-date update.

Findings

1.  Tauri builds missing from downloads ▶
2.  Opening will be outdated ▶

Summary

The post introduces aw-tauri for ActivityWatch v0.14.0. Since the previous review, it has replaced the opening’s “upcoming” wording, directed readers seeking Tauri builds to GitHub release assets, and swapped in an Activity-view screenshot.

_{Reviews (2) · Last reviewed commit: "docs: swap aw-tauri post screenshot to A..."}

[TimeToBuildBob]

Pushed 513fc701 addressing the review. Still held for ActivityWatch v0.14.0 stable (the date placeholder stays 2099-12-31); bump it at merge time.

Erik's screenshot note — replaced the Welcome capture with a windowed capture of the Activity view (7-day aggregate) with demo/fake data, so the image now shows the actual aw-tauri window and meaningful activity bars/applications/categories rather than a bare webui page. See the inline reply.

Greptile P1 (Tauri builds missing from downloads) — confirmed: scripts/update-downloads.py's _matches() sorts Tauri assets last and _pick() takes the first match, so the downloads page surfaces the classic aw-qt asset only. The post now points readers at the GitHub release assets and notes the downloads page links the classic build by default, instead of promising Tauri builds there.

Greptile P2 (opening outdated) — the first line no longer calls the release "upcoming"; it reads correctly once the post is published after stable.

[TimeToBuildBob]

@greptileai review