diff --git a/bot/AGENT.md b/bot/AGENT.md
index 1817cca..521f51e 100644
--- a/bot/AGENT.md
+++ b/bot/AGENT.md
@@ -134,10 +134,12 @@ message content; Message Content is a privileged intent, enable it only if you n
 
 ## 6. Working with the admin
 
-- **Source**: push to the community Gitea. CI runs on the `python312` runner label (CPython 3.12 plus node),
-  builds the release bundle (§1a), and on `main` installs it on the server. Keep `main` deployable: a failing
-  **pytest** run stops the build and the deploy, and a bundle that fails its checksum check is refused. The
-  website's **node tests are advisory** — a failure is annotated as a warning and blocks nothing.
+- **Source**: push to the community Gitea. CI builds the release bundle on the `python312` runner label
+  (CPython 3.12 plus node) and, on `main`, installs it on the server. **The test jobs are commented out: run
+  the suites locally before you push** (`python -m pytest -q` and `node --test app/tests/*.test.js`). What CI
+  still enforces: the bundle must import cleanly with only its own `vendor/` on the path, every file must
+  match `BUILD.json`, and the bot must answer on its port within 45 s of the swap or the deploy fails and the
+  previous release stays rollback-ready.
 - **Need infra?** Open a Gitea issue titled `infra: …` stating the exact change: a new env var and why,
   a mount, a Caddy path that should skip login (e.g. a public webhook endpoint), a new database.
   Don't work around the proxy or the firewall.
diff --git a/bot/README.md b/bot/README.md
index d55cfbf..bef45c4 100644
--- a/bot/README.md
+++ b/bot/README.md
@@ -10,8 +10,10 @@ Your repo's Gitea Actions workflow builds a **release bundle**: one tar.gz holdi
 checks its signature and every checksum, swaps it into `/srv/bot/app` (bind-mounted at `/app`, previous
 release kept for `--rollback`) and restarts the container. The install log comes back in the CI job.
 
-A branch or pull request runs the tests and builds the artifact, and deploys nothing. The python tests gate the
-build; the website's node tests are advisory and only add a warning when they fail.
+A branch or pull request builds the artifact and deploys nothing. The test jobs are commented out in the
+workflow — run `python -m pytest -q` and `node --test app/tests/*.test.js` locally before pushing. CI still
+refuses a bundle that cannot import from its own `vendor/`, or whose files do not match `BUILD.json`, and the
+deploy fails if the bot does not answer on its port after the swap.
 
 ## Your secrets live in Gitea