1.1.0: reach nntmux over its Newznab API (search + getnzb, metamesh key) with a per-release .nzb cache; drop the MariaDB/storage coupling

feeder-plugin/usenet-feeder/src/lib.rs

@@ -1,8 +1,9 @@
 //! `usenet-feeder` library surface. The binary (`main.rs`) wraps the plugin in
 //! [`meta_feeder_sdk::serve_feeders`].
 //!
-//! This feeder owns the **metadata half** of Usenet: it reads an nntmux header-
-//! scan catalog we run ourselves and mints a portable `nzb-posting` (`0x1003`)
+//! This feeder owns the **metadata half** of Usenet: it searches an nntmux
+//! header-scan indexer we run ourselves (the separate NNTmux app, over its
+//! Newznab API) and mints a portable `nzb-posting` (`0x1003`)
 //! cid from each release's article Message-IDs. Unlike `meta-feeder-indexer`'s
 //! `0x1005` locator, that cid embeds no indexer host, so any peer with a plain
 //! NNTP provider can redeem it — no indexer credential anywhere in the path.
@@ -20,10 +21,12 @@
 //!
 //! See `meta-gateway/docs/others/self-hosted-usenet-indexer-study.md`.
 
-/// Read-only access to the nntmux sidecar: its MariaDB release catalog and the
-/// on-disk gzip NZBs that are the *only* durable home of the Message-IDs.
+/// Our own nntmux, reached only over its Newznab HTTP API: the client, the
+/// per-release `.nzb` cache, the release type and the Message-ID extraction.
 pub mod nntmux {
-    pub mod db;
+    pub mod api;
+    pub mod cache;
+    pub mod catalog;
     pub mod nzb;
 }