Hot-reload content on a NATS trigger instead of requiring a restart

questions is now Arc<ArcSwap<HashMap<...>>> - readers do a lock-free
atomic load (state.questions.load().get(&id).cloned()), never blocking
on or blocked by a reload. content::watch_for_reload subscribes to
portal.content.reload (published by the questions repo's own CI after
it lints a push - see that repo's lint-and-reload.yml) and swaps in a
freshly re-fetched HashMap on each message. A fetch/parse failure logs
and keeps serving the last-good content rather than clearing it.

src/resource.rs

@@ -22,7 +22,9 @@ pub async fn get_resource(
     let state = expect_context::<AppState>();
     let question = state
         .questions
+        .load()
         .get(&question_id)
+        .cloned()
         .ok_or_else(|| ServerFnError::new("unknown question"))?;
     let feature = question
         .alternatives