email-cmd: RETIRED 4 October 2026 (kept, never deleted)

What it was. The email command route: mail to [email protected] went by Cloudflare Email Routing to this worker, which stored each instruction in R2 under salus-mind/email-cmd/ and served it at https://cmd.salus-mind.com to the Mac daemon tools/email-daemon.py, which ran Claude Code on it and replied through Resend.

Why it went. Unused: its only client, the daemon, was retired on 13 June 2026 on Scott's words "get rid of it"; no instruction was stored after 13 April 2026 (358 files); no email reached it in the 7 days before retirement; its 2,930 calls in the 31 days before were internet scanners. An internet-facing worker holding four secrets and write access to the live media bucket, with no user, and needing three sender-gate repairs on 4 Oct 2026, is attack surface with no benefit. Retired on the Boss's decision (window ca3461cf, 4 Oct 2026, about 16:42 BST) by Elsie's design: salus-brain reports/design_email-command-route-retirement_2026-10-04.md.

What was done, and what was kept.

Email Routing rule a0f80192e5b3459d8ea634150000381d (to = [email protected], action worker email-cmd) set enabled: false, kept.
Custom domain cmd.salus-mind.com detached from the worker (its AAAA 100:: record went with it). workers.dev was already off.
The worker script email-cmd, its bytes (etag 4cb67280..., module sha256 12a95067...), its four secrets and its R2 binding are left in place, unreachable. The 358 R2 files are kept.
Banked before the change and read back by hash: salus-brain reports/evidence/elsie7-ca34-2026-10-04/email-cmd-bank/.

What replaced it. Nothing: Scott retired remote command by email on 13 June 2026. Outbound mail from [email protected] through Resend (for example MASTERdrive/Tools/debrief_email.py) is a different route and is unaffected. Stale text still naming the address as a reply target: tools/salus-produce.py line 5002 ("Email PASS or faults to [email protected]"), Bob's pipeline file, not changed here.

How it comes back, one command each (Cloudflare API, keys from api-keys.json cloudflare):

Domain: PUT /accounts/<account>/workers/domains with {"hostname":"cmd.salus-mind.com","service":"email-cmd","environment":"production","zone_id":"<salus-mind.com zone>"}.
Email: PUT /zones/<salus-mind.com zone>/email/routing/rules/a0f80192e5b3459d8ea634150000381d with the rule's matchers and actions and "enabled": true. The worker needs no redeploy; its bytes and secrets were never touched.