bot docs: CI no longer runs the test suites; they run locally before a push

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

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.