aw-sync README: documents the non-working daemon path and claims Android is unsupported

[ErikBjare]

Two things in aw-sync/README.md are actively misleading, and both point users at broken or non-existent behaviour.

1. It recommends the path that does not work

The Usage section opens with:

This will start a daemon which pulls and pushes events with the sync directory (~/ActivityWatchSync by default) every 5 minutes:

aw-sync
aw-sync daemon

Per #682, bare aw-sync / aw-sync daemon never pulls anything — it scans two directory levels while real peers live three levels down. The command that actually works today is aw-sync sync, which the README presents further down as the lesser "sync all buckets once and exit" option.

Once #685 merges this section becomes correct, so the fix is either to land alongside it or to carry an interim note. It should not be left as-is in a release where the daemon still no-ops.

2. It says Android is unsupported

Under Limitations:

• It doesn't support Android, yet.

Android sync shipped. aw-android drives this same crate over JNI (syncPull, syncPullAll, syncPush, syncBoth in aw-sync/src/android.rs), and aw-android v0.14.1 is on the Play Store with a sync settings screen. The limitation immediately above it —

• It only syncs afk and window buckets by default

— also no longer matches the code: SyncSpec.buckets: None means all buckets, and --buckets is opt-in filtering rather than the default.

Also worth refreshing

• The "Setting up sync" section does not mention that the sync directory must be shared by a file syncer before aw-sync is useful, or what the resulting {hostname}/{device_id}/test.db layout looks like. aw-sync: sync failures are silent — add aw-sync status, loud diagnostics, per-device manifest, and surface peers in Raw Data #684 covers making this discoverable in the tool; the README is the cheaper half.
• The FAQ's "What are the limitations?" list is the first thing a new user reads to decide whether sync is worth setting up, so stale entries there cost more than elsewhere.

Small and self-contained — reasonable good first issue if nobody picks it up with #685.

cc @TimeToBuildBob

[TimeToBuildBob]

Two separate lies, two different clocks.

1. Daemon docs: fix(aw-sync): make default daemon use host-layout pull/push #685 is parked for v0.14.0, so aw-sync / aw-sync daemon still no-ops on the 3-level layout. Until that switch lands, the README should lead with aw-sync sync (the command that actually works) and mark the daemon path as broken, not recommended. Landing the current text "alongside fix(aw-sync): make default daemon use host-layout pull/push #685" would leave a release that still ships the no-op.

2. Android + default buckets: those two lines are just false today. Android drives this crate over JNI and aw-android v0.14.1 is on the Play Store; SyncSpec.buckets: None means all buckets. They can ship as a docs-only change without waiting on fix(aw-sync): make default daemon use host-layout pull/push #685.

Parked as not-in-v0.14.0 on ActivityWatch/activitywatch#1445. (2) is the cheap half and does not need the daemon switch; (1) should not pretend the daemon works in the meantime.

[TimeToBuildBob]

Docs PR: #701

Interim README for the parked-#685 world: Usage leads with aw-sync sync, daemon marked broken for the 3-level layout, Android / default-buckets claims removed, setup documents {hostname}/{device_id}/test.db and "share the folder first".