docs: clarify macOS release-specific support guidance

[TimeToBuildBob]

Summary

• remove the homepage FAQ claim that all macOS support is 10.15+
• update the schema markup to stop advertising a single hard-coded macOS floor
• add a downloads-page note telling users to verify macOS architecture/version requirements per release

Why

ActivityWatch/activitywatch#1294 surfaced that the public site was overpromising a single macOS minimum version. The current release lines do not share one universal macOS floor, so the old copy was misleading.

Impact

Users looking for Catalina/Intel compatibility get pointed at the release assets instead of a wrong blanket claim.

Validation

• confirmed the stale 10.15+ copy in this repo 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 removes the stale blanket macOS 10.15+ minimum-version claim from four locations (homepage FAQ, downloads page, and both Schema.org structured-data blocks), replacing it with language that tells users the actual floor varies by release and points them to the GitHub release assets for confirmation.

• _includes/schema-faq.html / _includes/schema-index.html: Both JSON-LD structured-data blocks drop the hard-coded macOS 10.15 floor from softwareRequirements and the FAQ answer; the new copy defers to the downloads page.
• index.pug: The visible FAQ section removes (10.15+) from the macOS bullet and adds an inline link to /downloads/ for per-release details.
• downloads.pug: A new p.mt-2 paragraph is added below the "older releases" line, advising users to check GitHub release assets for architecture/version-specific builds before installing.

Confidence Score: 5/5

Safe to merge — all four changes are copy-only edits that remove a now-incorrect macOS version claim and consistently redirect users to the release assets for accurate build information.

Every changed line is documentation or schema text; no logic, routing, or data-handling code is touched. The author validated the change against actual binary metadata, and a repo-wide grep confirms no residual 10.15 strings remain.

No files require special attention. All four files carry straightforward text replacements with no side-effects.

Important Files Changed

Filename	Overview
_includes/schema-faq.html	FAQ JSON-LD schema updated to remove hard-coded "10.15+" macOS floor; replaced with a note pointing users to the downloads page.
_includes/schema-index.html	SoftwareApplication schema softwareRequirements field updated to drop the macOS 10.15 floor and defer to the downloads page instead.
downloads.pug	Added a p.mt-2 paragraph advising users to check GitHub release assets for macOS-specific builds; placed after the existing "older releases" line.
index.pug	Homepage FAQ answer updated to drop the "(10.15+)" qualifier and link to /downloads/ for per-release macOS details.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[User visits activitywatch.net] --> B{Needs macOS build?}
    B -- No --> C[Download latest stable build]
    B -- Yes --> D[Reads updated copy: 'macOS support varies by release']
    D --> E[Homepage FAQ link to /downloads/]
    D --> F[Downloads page note]
    E --> G[GitHub release assets]
    F --> G
    G --> H{Find matching arch + macOS version}
    H -- x86_64 / Intel --> I[v0.13.2 · min macOS 10.13]
    H -- arm64 / Apple Silicon --> J[v0.14.0b1 · min macOS 11.0]

Loading

_{Reviews (1): Last reviewed commit: "docs: clarify macOS release-specific gui..." | Re-trigger Greptile}