docs: clarify macOS release-specific support guidance

[TimeToBuildBob]

Summary

• update the FAQ platform-support answer to stop claiming a single macOS 10.15+ floor
• point readers at the downloads page and release assets for exact macOS build compatibility

Why

ActivityWatch/activitywatch#1294 surfaced that the public docs still promised macOS 10.15+, but current macOS support varies across release lines.

Impact

The FAQ no longer gives Catalina/Intel users a false expectation about every current macOS build.

Validation

• confirmed the stale 10.15+ copy in src/faq.rst before editing
• inspected release assets for ActivityWatch/activitywatch
• verified the stable v0.13.2 macOS x86_64 binary advertises LC_VERSION_MIN_MACOSX 10.13.0
• verified the prerelease v0.14.0b1 macOS arm64 binary advertises LC_BUILD_VERSION minos 11.0.0

Related to ActivityWatch/activitywatch#1294.

[greptile-apps]

Greptile Summary

This PR updates the platform-support FAQ entry to remove the stale macOS 10.15+ floor and instead direct users to the downloads page and GitHub release assets for release-specific macOS compatibility information.

• The macOS-specific sentence now includes one-click hyperlinks to both the downloads page and the GitHub releases page, addressing the prior thread concern about plain-text references.
• As a side effect, the Windows (10 and later) and Linux (most distributions) qualifiers were also silently dropped from the sentence, which appears consistent with the PR's intent of avoiding version claims that can go stale.

Confidence Score: 5/5

Documentation-only change with no code execution paths affected; safe to merge.

The change is a single-sentence edit to a documentation file. The stale version claim is removed, both destination links are live and correct, and the new wording accurately reflects that macOS build compatibility varies per release. No logic, configuration, or API surface is touched.

No files require special attention.

Important Files Changed

Filename	Overview
src/faq.rst	Replaces specific macOS version floor with a release-dependent guidance note and adds hyperlinks to the downloads page and GitHub releases; also quietly drops the Windows and Linux version qualifiers.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[User reads platform support FAQ] --> B{Needs macOS-specific build?}
    B -- No --> C[Proceed with installation]
    B -- Yes --> D[Check downloads page\nor GitHub release assets]
    D --> E[Find exact macOS version\nand architecture support\nfor target release]
    E --> C

Loading

_{Reviews (2): Last reviewed commit: "docs: link GitHub release assets in macO..." | Re-trigger Greptile}

[greptile-apps]

The "GitHub release assets" reference is plain text while the downloads page next to it is a proper hyperlink. Readers following the macOS-specific path will need to navigate to GitHub on their own; linking directly to the releases page gives them a one-click path to the same information.

Suggested change

ActivityWatch runs on **Windows**, **macOS**, **Linux**, and **Android**. Browser extensions are available for Chrome, Firefox, and Edge to track your web activity. macOS version and architecture support varies by release, so if you need a specific macOS build check the `downloads page <https://activitywatch.net/downloads/>`_ or the GitHub release assets.

ActivityWatch runs on **Windows**, **macOS**, **Linux**, and **Android**. Browser extensions are available for Chrome, Firefox, and Edge to track your web activity. macOS version and architecture support varies by release, so if you need a specific macOS build check the `downloads page <https://activitywatch.net/downloads/>`_ or the `GitHub release assets <https://github.com/ActivityWatch/activitywatch/releases>`_.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

[TimeToBuildBob]

Linked the GitHub release assets directly in fb32551, so the macOS guidance now has one-click links for both destinations.

[TimeToBuildBob]

Build is green on fb32551, the Greptile thread is already handled, and I attempted to squash-merge this PR. GitHub rejected the merge because TimeToBuildBob does not have MergePullRequest permission on ActivityWatch/docs, so this is ready and just waiting on a maintainer merge.