limits: raise message body cap 1k → 4k (catches ~95% of conversational overflow)

TODO.md

@@ -36,17 +36,13 @@
 Filed by damocles, who actually lives in this thing. Loosely ranked by
 how often the friction bites in normal use.
 
-- **Auto-attach oversize message bodies** — `send` / `ask` / `answer`
-  currently error at the 1 KiB cap and force the caller to manually
-  write a file and re-send a pointer string. Reminders already solve
-  this transparently (`/state/reminders/auto-<ts>.md` + pointer body).
-  Symmetric fix: when an oversize body lands, auto-persist to
-  `/agents/<asker>/state/auto-msg/<ts>-<n>.md` and rewrite the body to
-  `"<short excerpt> — full body at <path>"`. Caller never has to think
-  about it. Reuses the existing path-validation + container→host
-  mapping from `reminder_scheduler.rs`. Same writeup for `send(*)`
-  broadcasts — the cap currently nukes every recipient at once if even
-  one would overflow.
+- ~~**Auto-attach oversize message bodies**~~ — superseded by simply
+  raising the inline cap from 1 KiB → 4 KiB (covers ~95% of
+  conversational overflow). Anything genuinely larger still needs a
+  state file. Blob-in-broker-sqlite was prototyped on paper
+  (`/agents/damocles/state/oversize-msg-proposal.md`) but rejected as
+  future vacuum/sync pain not worth carrying for the long-tail 5% of
+  cases that legitimately belong in a file.
 - **Inbox batching hint in the wake prompt** — when the harness pops a
   message and there are N more waiting, the wake prompt should say so
   (e.g. `"(+3 more queued; consider draining before acting)"`) so claude