nip71: default ingest OFF until feed pipeline can absorb it

Ingest's data path is verified working (subscribe -> fetch -> adapt ->
inject -> survives the whitelist filter), but surfacing a burst of
ingested authors pushes bitvid's moderation/WoT stage to hydrate trust +
report data (kind 30000 / 1984) for many cold authors at once, storming
relays and stalling the feed render ("nothing loads"). The native feed
avoids this only because it trickles authors in gradually.

Flip FEATURE_NIP71_INGEST default to false to restore a stable feed for
launch. All ingest code stays in place behind the admin toggle; re-enable
once moderation/WoT hydration is bounded/non-blocking for an author
influx, or whitelisted authors are treated as pre-trusted (skipping the
WoT fetch). Tracked as the next NIP-71 increment.

Co-Authored-By: Claude Opus 4.8 <[email protected]>

config/instance-config.js

@@ -246,8 +246,14 @@ export const ALLOW_NSFW_CONTENT = false;
  *
  * Set to `false` to disable all inbound NIP-71 ingest with a single switch if it
  * ever causes problems (spam, low-quality content, performance).
+ *
+ * NOTE: currently OFF by default. Ingest's data pipeline works, but surfacing a
+ * burst of ingested authors pushes bitvid's moderation/WoT stage to hydrate
+ * trust + report data for many cold authors at once, which storms relays and
+ * stalls the feed render. Re-enable once that hydration is bounded/non-blocking
+ * (or whitelisted authors are treated as pre-trusted). See the NIP-71 plan doc.
  */
-export const FEATURE_NIP71_INGEST = true;
+export const FEATURE_NIP71_INGEST = false;
 
 /**
  * Emergency fallback accounts for seeding the moderation graph.