todo: one file per item, grouped by theme, with a generated index

TODO.md had reached 1050 lines and 72 open items across 28 sections, read mostly
on a phone. It is now a directory: todo/<theme>/<item>.md, one card per file, with
frontmatter carrying id, status, created date and order, and the prose body copied
across verbatim. TODO.md becomes a generated index (bun run todo:index).

Dates: where an item's prose stated one it is used; otherwise its old section's;
otherwise 2026-08-20, floored at the day before the split rather than invented.
date_source records which.

Shaped for a two-way Kanban board, filed as todo/tooling — a card is a file, id is
the identity, frontmatter is the machine's half and the body is the owner's.

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

todo/transmission/container-host-path-mapping.md

@@ -0,0 +1,15 @@
+---
+id: transmission/container-host-path-mapping
+title: "Container→host path mapping"
+theme: transmission
+status: open
+created: 2026-08-20
+date_source: assumed
+order: 4
+---
+
+**Container→host path mapping.** The daemon reports its own namespace (`/downloads/complete`),
+which is not a path on this host. A mapping table (`/downloads` → `~/hdds/08_TB_01/Torrents`,
+`/downloadsTV` → `14_TB_02/Torrents`) would make locations clickable through to `/files` and
+make "Set location" offer real destinations. Deliberately dropped from phase 1: the reference
+app has no such feature, so it would have been config nothing read.