commit b7b88a56bb42860a3ab031f40dbbd63f9f109086
parent a21a7592179d5b31871e52b16fbf27c5e41aaa71
Author: I Mean I'm Just Saying <imeanimjustsaying@kiwifarms.st>
Date: Fri, 9 Oct 2026 12:40:05 -0400
homepage: the Running an archive doc says how to run one from a shell or an agent
A section, "From a shell or an agent": `pnpm ops` (the running editor's actions over HTTP), `pnpm archilyzer`
(the core's command line) and the MCP server, three example commands, and links to the source's OPERATING.md and
COMMANDS.md. Gates: `pnpm --filter homepage test` 23/23; `build:nodata` ok (45 s, 5 GB scope).
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Diffstat:
2 files changed, 29 insertions(+), 0 deletions(-)
diff --git a/homepage/CHANGELOG.md b/homepage/CHANGELOG.md
@@ -1,6 +1,7 @@
# Homepage Changelog
## [Unreleased]
+- **The *Running an archive* doc says how to run one from a shell or an agent.** A new section, *From a shell or an agent*, names the three surfaces — `pnpm ops` (the running editor's actions over HTTP, with `ARCHILYZER_EDITOR_URL` and `WORKER_TOKEN`), `pnpm archilyzer` (the core's command line) and the MCP server — with three example commands, and links the source's OPERATING.md (recipes) and COMMANDS.md (every command and action).
- **The homepage builds and deploys from the Docker image too.** It is a publish stage like a site's: `archilyzer publish homepage [--deploy]` (or its row on /sites → Publish) builds it — the `/source` mirror included, from the repository `docker-compose.source.yml` mounts read-only — into `homepage/out`, stamps it, and deploys that build to its Pages project, or with `--to local` into the volume the container's `homepage` service serves. The image has the pinned git-filter-repo; it has no gitleaks or stagit, so a container build skips the secret scan with a warning and ships no history pages.
- **A site that publishes only its reports is not on the homepage.** A site with `publish: "cited"` has no Official Instances card, chart series, `/stats` entry or recent item, is not in `channel-sites.json`, and the channels only it carries count in no total — as an unlisted site, whatever its listing setting says. A site with reports that publishes its full corpus is listed as before.
- **The AI and MCP doc has a Ten-minute setup.** Right after the MCP server's introduction, one block runs Claude Code against a published archive, the Jeralyzer as the example: clone the source (or unpack the tarball on Downloads), `pnpm install`, `claude mcp add archilyzer`, start `claude` and try `/ask`; then what it needs, why the server must be registered as `archilyzer` (the shipped `/ask` and `/sweep` call `mcp__archilyzer__…`), the two optional editor lines for `fetch_clip`, `TRANSCRIPT_HUB_URL`, where the `mcp.json` form for other clients is, and WSL2 on Windows. "What it can do" is a heading of its own after it. Every archive's **Use with AI** link now lands on this page.
diff --git a/homepage/content/docs/operate.md b/homepage/content/docs/operate.md
@@ -107,4 +107,32 @@ Audio for recordings that have disappeared upstream is protected from cleanup, o
the reasoning that a local copy of something no longer available anywhere is the
one thing you cannot re-fetch.
+## From a shell or an agent
+
+Everything above can be run without a browser, three ways:
+
+- **`pnpm ops <action>`** sends the editor the same action a click does — add a
+ channel, sync, download, import, transcribe, tag, fetch posts, prepare reports,
+ publish — over HTTP. It needs the running editor's address
+ (`ARCHILYZER_EDITOR_URL`) and its `WORKER_TOKEN`. A job-starting action returns
+ once the job is queued; `--wait` follows it to the end.
+- **`pnpm archilyzer <command>`** is the core's own command line: the index,
+ publish stages (`publish now`, `publish build <id>`, `publish deploy <id>`),
+ reports, offline refreshes, and `doctor`, which says what the machine can do.
+- **The MCP server** lets an AI assistant read a published archive — search,
+ transcripts, reports — and ask the editor for the media behind a cited moment.
+ See [Use with AI](/docs/ai-and-mcp/).
+
+```sh
+pnpm ops create-channel --json '{"fields":{"name":"Example","handling":"youtube","url":"https://www.youtube.com/@example"}}'
+pnpm ops sync --json '{"slug":"example"}' --wait
+pnpm ops publish --json '{"verb":"now"}' --wait
+```
+
+Every fetch still goes through the editor's paced, per-platform queues; nothing
+here downloads around them. Recipes for each task are in
+[OPERATING.md](https://archilyzer.pages.dev/source/tree/OPERATING.md), and every
+command and action in
+[COMMANDS.md](https://archilyzer.pages.dev/source/tree/COMMANDS.md).
+
Next: [Deploy to Cloudflare](/docs/deploy-cloudflare/).
