docs: stop asserting which machine the agent is on

CLAUDE.md said "there is usually no Chronicle stack on this workstation" and
AGENTS.md said the deployment is "not on the machine containing this workspace".
Both files are checked in, so they read identically on Kraken — which has this
checkout at ~/workspaces/friend-lite and runs the stack locally. An agent there
was told to go find a remote Kraken while running on it. Both now start by
resolving `hostname`.

Kraken runs under WSL2, so two Tailscale peers answer to that hostname; the
resolution order now requires OS == linux, since the Windows host responds but
serves no Chronicle.

Separately, the docs described the desktop app as macOS-specific on every machine:
docs/screenpipe.md claimed extras/vault-sync/main.py "selects the macOS menu bar or
Linux system tray adapter" with desktop_core.py holding shared state. Neither file
exists. The entry point is extras/chronicle-tray/app.py — a single QSystemTrayIcon
that renders in both — and vault-sync is now a library plus legacy pre-tray service
management. Three other "macOS menu bar app" references updated to match.

Author: AnkushMalaker

AGENTS.md

@@ -15,16 +15,20 @@ This supports a comprehensive web dashboard for management.
 
 ## Live Deployment Location
 
-The normal live Chronicle deployment is hosted on the Tailnet machine **`kraken`**, not
-on the machine containing this workspace. A stopped or unconfigured local stack does
+The normal live Chronicle deployment is hosted on the Tailnet machine **`kraken`**. Run
+`hostname` before acting on this section — this file is checked in and reads the same on
+every machine, including Kraken itself, where the deployment is *local* and there is no
+remote host to reach. On any other machine a stopped or unconfigured local stack does
 not mean Chronicle is unavailable.
 
 For read-only checks of the running application (health checks, API inspection, or
 browser/screenshot verification):
 
 1. Try `https://kraken.parrot-census.ts.net` first. Use HTTPS; plain HTTP redirects.
 2. If that name is unavailable, inspect the current Tailscale mesh with
-   `tailscale status --json` and resolve the online peer whose `HostName` is `Kraken`.
+   `tailscale status --json` and resolve the online peer whose `HostName` is `Kraken`
+   **and whose `OS` is `linux`** — Kraken runs under WSL2, so the Windows host
+   advertises the same hostname and answers pings while serving no Chronicle.
    Prefer its returned `DNSName`; use its current Tailscale IP only as a temporary
    fallback. Do not persist a `100.x` address because it may change.
 3. If the host is reachable but the Chronicle endpoint is unclear, use the repository's

CLAUDE.md

@@ -4,9 +4,20 @@
 
 ## Verifying against a running backend
 
-There is usually **no** Chronicle stack on this workstation — but that does not mean
-you cannot verify your work. The live deployment runs on **`kraken`** and is reachable
-from here without any tunnel:
+**First work out which machine you are on — this file is checked in, so it reads the
+same on every one of them.** Run `hostname`:
+
+| hostname | what it is | how to verify |
+|---|---|---|
+| `rainbow` | Ankush's dev workstation (CachyOS). Usually **no** Chronicle stack running. | Reach Kraken over the network, as below. |
+| `Kraken` | The live deployment (Ubuntu 24.04 under WSL2). The stack is running **locally**. | Check it locally — `podman ps`, `curl localhost:8000/health`. Do **not** go looking for a remote Kraken; you are it. |
+
+Anything below about reaching Kraken applies when you are *not* on Kraken. Do not
+describe a machine as macOS unless `uname -s` actually says `Darwin`.
+
+If there is no Chronicle stack on the machine you are on, that does not mean you
+cannot verify your work. The live deployment runs on **`kraken`** and is reachable
+from `rainbow` without any tunnel:
 
 - `https://kraken.parrot-census.ts.net` (Tailnet, preferred)
 - `https://192.168.0.110/` over LAN — self-signed cert, so use `curl -k`. Caddy on
@@ -16,6 +27,10 @@ Before reporting something as "not verified because nothing is running locally",
 check Kraken first. See AGENTS.md → "Live Deployment Location" for the full
 resolution order.
 
+Note that Kraken runs in WSL2, so **two** Tailscale peers answer to the hostname
+`Kraken` — the Linux guest (which runs Chronicle) and the Windows host. When
+resolving it from `tailscale status --json`, take the one whose `OS` is `linux`.
+
 Kraken runs *deployed* code from `~/workspaces/friend-lite` on that host, so it will
 not have uncommitted local changes. To exercise new backend code end-to-end, stand up
 the pieces you need locally (a `podman run` Mongo plus the FastAPI app is usually

docs/backend/memories.md

@@ -98,7 +98,7 @@ Chat is always **agentic / tool-calling**. The chat LLM is given a `search_memor
 
 ## Vault sync to Obsidian (separate feature)
 
-The vault is designed to be edited and viewed directly. The optional **vault-sync** feature (`extras/vault-sync/`, macOS menu bar app) syncs `data/conversation_docs/` to an Obsidian vault via Syncthing, so you can browse and hand-edit your memory notes in Obsidian. Human edits made in Obsidian sync back into the vault. This sync is independent of the memory provider itself — the vault on the backend remains the source of truth.
+The vault is designed to be edited and viewed directly. The optional **vault sync** feature (in the cross-platform desktop tray, `extras/chronicle-tray/`) syncs `data/conversation_docs/` to an Obsidian vault via Syncthing, so you can browse and hand-edit your memory notes in Obsidian. Human edits made in Obsidian sync back into the vault. This sync is independent of the memory provider itself — the vault on the backend remains the source of truth.
 
 ## What was removed
 

docs/overview.md

@@ -73,7 +73,7 @@ Audio/Images/Data  →  Ingestion  →  Processing  →  Memories
 | **ASR Services** | `extras/asr-services/` | Local speech-to-text (Parakeet) |
 | **TTS Services** | `extras/tts/` | Text-to-speech (TADA, Fish Speech, KittenTTS) |
 | **HAVPE Relay** | `extras/havpe-relay/` | ESP32 audio bridge |
-| **Vault Sync** | `extras/vault-sync/` | macOS menu bar app — syncs your conversation_docs vault to Obsidian via Syncthing |
+| **Desktop tray** | `extras/chronicle-tray/` | Cross-platform tray/menu-bar app (Linux + macOS): vault sync, ScreenPipe controls, pendant |
 
 ### Pluggable Providers
 
@@ -99,7 +99,8 @@ chronicle/
 │   ├── asr-services/        # Local ASR (Parakeet)
 │   ├── tts/                 # Text-to-speech (TADA, Fish Speech, KittenTTS)
 │   ├── havpe-relay/         # ESP32 audio bridge
-│   └── vault-sync/          # macOS menu bar app: vault ⇄ Obsidian via Syncthing
+│   ├── chronicle-tray/      # cross-platform desktop tray (Linux + macOS)
+│   └── vault-sync/          # vault ⇄ Obsidian sync core used by the tray
 ├── config/                  # Central configuration
 ├── docs/                    # Documentation
 ├── tests/                   # Integration tests (Robot Framework)

docs/screenpipe.md

@@ -13,9 +13,12 @@ the timeline and memory curator.
   observation lifecycle, checkpoints progress, and answers bounded media requests.
 - Chronicle's backend stores timeline activity and only the media selected for a
   durable Chronicle view or memory.
-- `extras/vault-sync/` is the single Chronicle desktop entry point. `main.py` selects
-  the macOS menu bar or Linux system tray adapter; `desktop_core.py` contains their
-  shared state, logging, and vault synchronization.
+- `extras/chronicle-tray/` is the single Chronicle desktop entry point, on every
+  platform. `app.py` is one `QSystemTrayIcon` that renders in the Linux system tray
+  and the macOS menu bar alike; the menu is assembled from `sections/`. It imports
+  the vault-sync core (`extras/vault-sync/chronicle_vault_sync/core.py`) in place —
+  that package is now a library plus its legacy pre-tray service management, not a
+  desktop app of its own.
 - ScreenPipe's own desktop UI is an optional, on-demand local timeline viewer. It is
   not the recorder and should not autostart or launch a second recording process.
 
@@ -240,7 +243,10 @@ systemctl --user status screenpipe.service chronicle-screenpipe.service chronicl
 journalctl --user -u screenpipe.service -u chronicle-screenpipe.service -u chronicle-desktop.service
 ```
 
-On macOS, use `extras/vault-sync/start.sh logs` for the installed desktop service.
+On macOS the same services are launchd agents rather than systemd units, so use
+`launchctl print gui/$(id -u)/<label>` and the logs under `~/Library/Logs/Chronicle/`
+(labels are in `clients.py`). `extras/vault-sync/start.sh logs` only covers a legacy
+pre-tray install.
 
 The Linux ScreenPipe UI launcher may set rendering/onboarding environment required by
 the locally installed build, but its desktop autostart entry should remain disabled.