docs(self-host): add backup-restore doc (#1795)

* docs: update URLs and simplify bun commands in documentation

* docs: improve backup-and-restore guide with verification and rehearsal steps

Author: tyler-dane

AGENTS.md

@@ -2,7 +2,7 @@
 
 ## Defaults
 
-- Frontend-only work usually starts with `bun run dev:web`; it does not require
+- Frontend-only work usually starts with `bun dev:web`; it does not require
   backend services.
 - Backend, auth, MongoDB, Google sync, and SSE work require
   a `compass.yaml` at the repo root. Bootstrap with:
@@ -13,33 +13,33 @@ cp compass.example.yaml compass.yaml
 
 - `compass.yaml` contains secrets. Do not commit it.
 
-- Avoid defaulting to `bun run test`; use the focused package test first.
+- Avoid defaulting to `bun test`; use the focused package test first.
 - Formatting is handled by the repo-local Codex Stop hook after each agent turn.
-- Use `bun run lint` and relevant verification before push or handoff.
+- Use `bun lint` and relevant verification before push or handoff.
 
 ## Commands
 
 ```bash
 bun install
-bun run dev:web
-bun run dev:backend
-bun run test:core
-bun run test:web
-bun run test:backend
-bun run test:scripts
-bun run type-check
-bun run lint
-bun run lint:fix
+bun dev:web
+bun dev:backend
+bun test:core
+bun test:web
+bun test:backend
+bun test:scripts
+bun type-check
+bun lint
+bun lint:fix
 ```
 
 Validation defaults:
 
-- Core: `bun run test:core`
-- Web: `bun run test:web`
-- Backend: `bun run test:backend`
-- Scripts: `bun run test:scripts`
+- Core: `bun test:core`
+- Web: `bun test:web`
+- Backend: `bun test:backend`
+- Scripts: `bun test:scripts`
 - Shared contracts/cross-package behavior: affected package tests plus
-  `bun run type-check`
+  `bun type-check`
 - Keep regression tests that protect real behavior. Remove temporary tests,
   scripts, debug hooks, or code added only to confirm a one-time hypothesis once
   that verification is complete.

docs/development/hosting-modes.md

@@ -20,8 +20,8 @@ When you are debugging anything storage-, auth-, or sync-related, the first ques
 
 | Hosting context | Account state | Calendar/event data location |
 | ---------------- | ------------- | ---------------------------- |
-| Compass Cloud (`app.compasscalendar.com`) | Anonymous | Browser IndexedDB |
-| Compass Cloud (`app.compasscalendar.com`) | Signed in | Compass backend -> Compass MongoDB |
+| Compass Cloud (`compasscalendar.com`) | Anonymous | Browser IndexedDB |
+| Compass Cloud (`compasscalendar.com`) | Signed in | Compass backend -> Compass MongoDB |
 | Self-hosted | Anonymous | Browser IndexedDB |
 | Self-hosted | Signed in | Operator backend -> configured MongoDB |
 
@@ -35,7 +35,7 @@ The lightest state. Useful for trying Compass without creating an account.
 - events and tasks live in the browser's IndexedDB
 - calendar and task data never leave the browser
 
-This is the same story everywhere: on [app.compasscalendar.com](https://app.compasscalendar.com) and on a self-hosted install before the user signs up. The web app might be served from Compass Cloud or from a self-hosted server, but either way, anonymous calendar and task data stay in the browser.
+This is the same story everywhere: on [compasscalendar.com](https://compasscalendar.com) and on a self-hosted install before the user signs up. The web app might be served from Compass Cloud or from a self-hosted server, but either way, anonymous calendar and task data stay in the browser.
 
 ## Self-Hosted Account Mode
 
@@ -51,7 +51,7 @@ For the runtime env and required variables, see [Local Development](./local-deve
 
 ## Hosted Compass Cloud Account Mode
 
-The signed-in state on the managed product at [app.compasscalendar.com](https://app.compasscalendar.com).
+The signed-in state on the managed product at [compasscalendar.com](https://compasscalendar.com).
 
 - Compass-operated backend
 - Compass-owned MongoDB and SuperTokens configuration

docs/self-hosting/README.md

@@ -1,10 +1,10 @@
 # Self-Hosting
 
-Self-hosting Compass means running it on a server you control instead of using `app.compasscalendar.com`.
+You can run Compass on infrastructure you control instead of using the hosted version on `compasscalendar.com`
 
-Start with [Run Compass on a server](./server-guide.md). It walks through a small VPS setup with your own domain, HTTPS, and the Compass services running behind Caddy.
+Start with [Run Compass on a server](./server-guide.md). It walks through a small VPS setup with your own domain, HTTPS, and the Compass services running behind a reverse proxy.
 
-If you only want to run Compass on your own computer, use the normal local development flow with Bun instead of the self-host installer. See [Run Compass without the installer](./advanced-manual.md).
+If you only want to run Compass on your own computer, use the normal local development flow with Bun instead of the self-host installer.
 
 ## What Compass is made of
 
@@ -33,7 +33,7 @@ flowchart TD
 ## Start here
 
 - New self-host install: [Run Compass on a server](./server-guide.md)
-- Backups and restore: [Back up and restore your data](./backups-and-restore.md)
+- Backups and restore: [Back up and restore your data](./backup-and-restore.md)
 - Google Calendar: [Add Google Calendar](./google-calendar.md)
 - Manual Bun setup: [Run Compass without the installer](./advanced-manual.md)
 - Monitoring: [Monitoring](./monitoring.md)