todo: urgent — per-feature server routing, due tomorrow for reclip

Adds priority/due to the item format and an Urgent section to the generated index.

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

todo/README.md

@@ -45,6 +45,11 @@ process everywhere, report which host is behind…
   `assumed` (unknown, floored at 2026-08-20, the day before the split — a bounded "before today"
   rather than an invented day).
 - **`order`** — position within the theme, preserved from the original list. What a board reorders.
+- **`priority`** _(optional)_ — `urgent` when the owner says so, absent otherwise. There is no scale of
+  five: an item is either something he named as urgent or it is not, and a scale would only invite
+  everything to drift upward. Urgent items are listed first in the generated index.
+- **`due`** _(optional)_ — a date the owner named. Only ever written because he said one; never inferred
+  from tone or from how the item is worded.
 - **The body is prose, and it is the point.** These entries carry the reasoning, what was verified
   versus assumed, and what was already tried. An item stripped to a title loses the thing that made
   this list worth keeping.

todo/fleet/settings-to-choose-which-server-each-feature.md

@@ -0,0 +1,37 @@
+---
+id: fleet/settings-to-choose-which-server-each-feature
+title: "Settings to choose which server each feature uses"
+theme: fleet
+status: open
+priority: urgent
+due: 2026-08-22
+created: 2026-08-21
+date_source: stated
+order: 0
+---
+
+**Settings to choose which server each feature uses.** Wanted 2026-08-21, **needed 2026-08-22** — the
+owner named it urgent and named the case: **ReClip, for saving videos.** Now that there are several
+servers, each functionality needs to be pointed at one deliberately, from Officer's settings, rather
+than always resolving to whatever is local.
+
+**The blocker is concrete and small.** `api/file-browser/router.ts:1271` reads
+
+```ts
+const RECLIP_BASE = process.env.RECLIP_URL ?? 'http://localhost:8899';
+```
+
+— a module-level constant, read once at import, from an environment variable. So every install can only
+ever reach its OWN ReClip, there is no way to say "download this on `omega`", and changing it means
+editing `.env` and restarting rather than a setting. Five hosts hold a platform checkout
+(`docs/servers.md`); three run it.
+
+The generalisation the owner asked for is the setting being **per feature**, not one global "which
+server am I". Different functions belong on different machines — the box with the disks is not the box
+with the GPU is not the box on the fast line — so this is a routing table, one row per capability.
+
+Worth knowing before designing it: the platform already has per-server registries for a plugin
+(Jellyfin keeps servers with write-only access tokens; offscale keeps a server picker), so there is a
+shape to copy rather than invent. And `docs/multi-server-push.md` is the same question arriving from the
+other direction — a payload that does not say which server sent it — so whatever names a server here
+should be the identifier that design settles on.