Add the admin page (phase 3)

services/admin is a client of the content service's HTTP API, served on
the tailnet only. It renders on the server with plain forms and no client
scripts, and holds the admin token so the browser never sees it.

- Review queue: reasons, line diff against the live version, accept,
  reject, and reject with the live version put back into Obsidian
- Notes and drafts: search, preview, fields, backlinks, publish toggle
- History with compare and roll back
- Quick capture for a status or a Library item (optionally both)
- Store: orders open or closed per category, open slots and stock
- Overview: counts, last scan and error, scan now, sync job health
- Same-origin check on every post, strict CSP, sanitized previews

The content service gains /api/status, sync run reports (/api/syncs) and
lookup of a note by name.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012aSbo2D1qP8cMFQCykf7kx

README.md

@@ -13,11 +13,12 @@ with the decisions behind it, is the
 | `packages/schema` | The one definition of every note type: fields, folders, file names, and the checks for one note and for the whole folder. The migration, the content service, the MCP server, the site and any later editing tool all use it. |
 | `vault-kit` | What goes into the vault: the Obsidian templates (generated from the schema) and the Site guide. |
 | `services/content` | The content service: watches the Site folder, runs the rules, keeps the last good version and its history, and serves the one write API. The MCP server for agents is part of it. See [docs/content-service.md](docs/content-service.md). |
+| `services/admin` | The admin page: the review queue with diffs, history and rollback, quick capture, store orders, draft previews and sync health. A client of the content service, on the tailnet only. See [docs/admin.md](docs/admin.md). |
 | `tools/migrate` | The one-time migration from the old site's data into Site folder notes. |
 | `docs` | How the pieces fit. Start with [docs/content-model.md](docs/content-model.md). |
 | `legacy` | The old site, kept for reference only. Nothing outside it imports from it except the migration. |
 
-Coming in later phases: the admin page, the component library, and the new site.
+Coming in later phases: the component library and the new site.
 
 ## Commands
 
@@ -33,6 +34,9 @@ npm run schema:json  # writes a JSON Schema per note type to packages/schema/jso
 # the content service, against a copy of the Site folder
 SITE_DIR=out/24.01_PersonalWebsite/Site DATA_DIR=data \
 CONTENT_TOKENS="reader:<24+ chars>,admin:<24+ chars>" npm run content
+
+# the admin page, in a second terminal
+ADMIN_TOKEN=<the admin token> npm run admin   # http://localhost:4320
 ```
 
 ## The old site