todo: directory watchers with attached actions

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

TODO.md

@@ -36,6 +36,27 @@ the owner's OS user and can never be granted. Indirection there really is accide
       generating" was once treated as permission and started a second agent in a repository another was
       building in. Whatever shape this takes, it inherits those three refusals.
 
+## File watchers
+
+- [ ] **Watch a directory, and attach actions to what lands in it.** Wanted 2026-08-21. The owner sets a
+      watcher on a path and configures what happens when a file appears there — the general mechanism,
+      not one hard-coded flow.
+
+      **The driving use case, end to end:** instead of opening a chat, record an audio note; it lands in
+      a watched directory; the existing transcription path turns it into a text file; and on the watch,
+      an agent picks the new files up and files them as todos. So the owner can capture an idea with no
+      session open and no phone unlocked into the right screen.
+
+      What it needs, in rough order: a watcher registry (path + what to do), a trigger that fires on
+      file arrival rather than on a clock, and a way to hand the file to an agent turn. Note the second
+      and third are the **same two gaps the Nudger item names** — the platform has no periodic/event
+      trigger, and `pushTurn` has one caller, so nothing server-side can speak into a session. Build
+      them once.
+
+      Open, not decided: whether the watcher is a plugin or core; whether "action" is a task, a
+      prompt from the prompt library, or a chat message; and how a file is marked consumed so it is not
+      picked up twice.
+
 ## Prompt library
 
 - [ ] **A store of ready-made prompts, versioned, categorized and tagged.** Wanted 2026-08-21. The owner