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>

crates/feed/src/lib.rs

@@ -1140,6 +1140,9 @@ pub fn category_path(name: &str) -> (String, Option<String>) {
     (name.to_string(), None)
 }
 
+/// TypeSafe's System One endpoint, where Jev answers questions about a piece of state.
+pub const JEV_URL: &str = "https://api.typesafe.ai/v1/systemone";
+
 /// A Directory category for a feed that names none of its own, which most blogs do not (#117):
 /// TypeSafe's Jev picks one of Apple's categories or subcategories from the feed's title and
 /// latest items, the subcategory being what a podcast's own category is stored as. The likeliest
@@ -1164,7 +1167,7 @@ pub async fn classify(client: &reqwest::Client, key: &str, feed: &ParsedFeed) ->
         }},
     });
     let answer: serde_json::Value = client
-        .post("https://api.typesafe.ai/v1/systemone")
+        .post(JEV_URL)
         .bearer_auth(key)
         .json(&body)
         .timeout(FEED_TIMEOUT)