feat: the announcement card offers the auto-link switch and says why (4392)

The card's copy had gone stale against its own backend in three places, which
matters more than usual here because every line of it is a claim about what FC
will do with the operator's library:

  * "nothing is linked until you accept one" is no longer true for a pair the
    creator's own file name settles. The switch that governs that is now on the
    card rather than only in the database.
  * "always needs two reasons — close in time and the post mentioning Discord"
    left out the shared-marker signal, and named 0.55 as the number below which
    no single signal can carry a pair. That number is 0.45 now.
  * "pairs only appear when a post lands near a drop and says it is about
    Discord" described the empty state as if the identity route did not exist.

A queued row now shows the working name behind it when there is one, and says
in the same breath why that name was not enough on its own. A review queue
that cannot explain itself is one the operator learns to click through without
reading, and this is the only signal that claims the two posts are the SAME
piece rather than that they happened near each other.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01LVjrnpQjRgHdvq95rASoiR

frontend/src/stores/postAssociations.js

@@ -6,14 +6,18 @@ import { useAsyncAction } from '../composables/useAsyncAction.js'
 import { toast } from '../utils/toast.js'
 
 // Backs the announcement review queue (#388 E5): "this Patreon post announced
-// that Discord drop". Confirm-only, deliberately — a wrongly-asserted link
-// tells the operator two different pieces are one, which is worse than no link
-// at all, so accept is the ONLY thing that makes a link real. Mirrors
-// seriesSuggestions (FC-6.3), which is the same shape for the same reason.
+// that Discord drop". A wrongly-asserted link tells the operator two different
+// pieces are one, which is worse than no link at all — so what reaches this
+// queue is everything FC is NOT sure enough about to act on by itself.
+//
+// A pair the creator's own working name identifies, where that name is on
+// these two posts and nowhere else in their library, is linked without asking
+// (`auto`). Mirrors seriesSuggestions (FC-6.3) in shape.
 export const usePostAssociationsStore = defineStore('postAssociations', () => {
   const api = useApi()
   const proposals = ref([])
   const enabled = ref(true)
+  const auto = ref(true)
   const threshold = ref(0.6)
   const windowHours = ref(24)
   const { loading, error, run } = useAsyncAction({ errorAs: 'message' })
@@ -28,6 +32,7 @@ export const usePostAssociationsStore = defineStore('postAssociations', () => {
   async function loadSettings () {
     const s = await api.get('/api/settings/import')
     enabled.value = s.discord_link_enabled
+    auto.value = s.discord_link_auto
     threshold.value = s.discord_link_threshold
     windowHours.value = s.discord_link_window_hours
   }
@@ -41,6 +46,11 @@ export const usePostAssociationsStore = defineStore('postAssociations', () => {
     await saveSettings({ discord_link_enabled: v })
   }
 
+  async function setAuto (v) {
+    auto.value = v
+    await saveSettings({ discord_link_auto: v })
+  }
+
   async function setThreshold (v) {
     threshold.value = v
     await saveSettings({ discord_link_threshold: v })
@@ -76,8 +86,8 @@ export const usePostAssociationsStore = defineStore('postAssociations', () => {
   }
 
   return {
-    proposals, enabled, threshold, windowHours, loading, error,
-    load, loadSettings, setEnabled, setThreshold, setWindowHours,
+    proposals, enabled, auto, threshold, windowHours, loading, error,
+    load, loadSettings, setEnabled, setAuto, setThreshold, setWindowHours,
     accept, dismiss, rescan
   }
 })