Boundaries that were supposed to hold

The security pass. Six findings, none reachable by visiting the site and
every one a boundary this codebase says it keeps.

A subagent is pinned to a list of read-only commands, in every mode,
unattended, with no card anybody could approve -- and `find *` was on it.
find writes files with -fprintf, runs programs with -exec and removes them
with -delete, and none of that needs a character the metacharacter guard
refuses. A page the model had just read could ask for a helper and get a
key into authorized_keys, from Plan mode, which promises to change
nothing. Refused in `subject()` rather than trimmed from the list: a
pattern cannot say "and no dangerous flags", and "this one looks
read-only" is exactly what put find there.

The loopback guard missed `0.0.0.0`, which is not is_loopback but does
connect to localhost -- so it answered a *decided* False and skipped the
DNS half too. The one spelling of "this machine" that walked past a guard
whose whole job is that sentence.

Twice in the update helper, which is the one place this deliberately
crosses a privilege boundary: root ran a script the service account owns,
and root sourced a file that account can replace. Either turns a
compromise of the web application into root. The first needed no
compromise at all -- a pull happens as the service user and root runs
whatever it fetched, so control of the branch was control of root. The
old test asserted that exact ExecStart line and had pinned it in place.

Push endpoints skipped check_url, the only outbound request that did. And
a chat could be filed in another account's folder, which hands over its
system prompt -- `_new_chat` resolved the folder, discarded it when it was
not the caller's, and stored the raw id anyway.

An existing helper install keeps the old wiring until install.sh is
re-run; update.sh now says so when it finds itself inside the checkout.

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

README.md

@@ -427,6 +427,18 @@ run by hand.
 Release notes come out of the annotated tag itself, so no forge API is involved
 anywhere.
 
+Root runs a **copy** of `deploy/update.sh` that the installer places outside the
+checkout and root owns. It must not run the one in the checkout: that file
+belongs to the unprivileged service account, so anything able to write as that
+account could rewrite it and become root — and so could whoever controls the
+branch, since a pull happens as that account and root would run whatever it
+fetched. The cost is that changing `update.sh` needs the installer re-run, and
+it tells you when your copy has fallen behind.
+
+**If you installed the helper before this changed, re-run the installer.** The
+old wiring points systemd at the checkout, and the update script now says so
+loudly when it notices it is running from there.
+
 ## How it fits together
 
 ```