Signals: feeds made from your subscriptions, picked by Jev (#254)

A Signal is a name and keywords. A task beside DeadAir's asks TypeSafe's Jev, on the owner's own
key, about each item of their subscribed feeds from the last 30 days and every new one: one call
an item, one noul question for each of their Signals still to hear about it, 0.5 or more a fit.
Every verdict is kept, fitting or not, in signal_verdicts, so nothing is asked twice, and new
keywords drop a Signal's verdicts to be judged afresh. A key TypeSafe refuses (401/402/403) is
passed over until its owner saves another, so a bad key is not sent the whole queue.

A Signal's items come through entries_where with an EXISTS on its hits, so filters, search, sort
and read state are an ordinary list's, and reading an item in a Signal reads it in its feed.

The page shows Signals under the places, with New signal, and Settings takes the TypeSafe key,
which is never sent back. The browser suite stubs Jev in the fixture server (IPX_TYPESAFE_URL).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

web/src/types.ts

@@ -82,6 +82,16 @@ interface Me {
   deadair_saved: number;
   theme: {name: string, mode: string} | null;
   version: string;
+  /// A TypeSafe key is saved for Signals; the key itself never comes back.
+  typesafe_key_set: boolean;
+}
+
+/// A Signal in your sidebar, `/api/signals` (db.rs SignalRow).
+interface Signal {
+  id: number;
+  name: string;
+  keywords: string[];
+  unread: number;
 }
 
 /// A feed as the Directory lists it (web.rs PopularRow): never its address.
@@ -101,6 +111,7 @@ interface DirFeed {
 /// The page's own state (util.ts `S`).
 interface State {
   feeds: Feed[];
+  signals: Signal[];
   /// The feed or place open: a feed's id, or a view such as ':all'.
   feed: string | null;
   entries: Entry[];