mqtt section: spell out that webhooks also auto-ingest new jellyfin items

the existing handler already inserts fresh media_items when an Item
Added arrives for a jellyfin id we haven't seen (upsertJellyfinItem
runs insert-or-update). nothing code-wise to change — just make the
ui copy describe both directions of the channel: ingest new adds,
and confirm post-ffmpeg state.

package.json

@@ -1,6 +1,6 @@
 {
 	"name": "netfelix-audio-fix",
-	"version": "2026.04.14.8",
+	"version": "2026.04.14.9",
 	"scripts": {
 		"dev:server": "NODE_ENV=development bun --hot server/index.tsx",
 		"dev:client": "vite",

src/features/settings/MqttSection.tsx

@@ -212,8 +212,10 @@ export function MqttSection({ cfg, locked }: { cfg: Record<string, string>; lock
 				{enabled && <span className={`text-xs px-2 py-0.5 rounded border ${statusColor}`}>MQTT: {status.status}</span>}
 			</div>
 			<p className="text-gray-500 text-sm mb-3 mt-0">
-				Close the loop: once Jellyfin finishes its post-ffmpeg rescan, it publishes an event to your MQTT broker. We
-				re-analyze the item, confirming it as done or flipping it back to pending if something didn't stick.
+				Two jobs over one channel: when Jellyfin's library picks up a brand-new or modified file, we analyze it
+				immediately and drop it into the Review column — no manual Scan needed. And when we finish an ffmpeg job,
+				Jellyfin's post-rescan event confirms the plan as done (or flips it back to pending if the on-disk streams
+				don't actually match).
 			</p>
 
 			<label className="flex items-center gap-2 text-sm text-gray-700 mb-3">