3 Commits

Include renames

Author	SHA1	Message	Date
bvandeusenandClaude Opus 5.5	7aa074d1a9	feat: the unified card shows referenced images, their text, and an undo (4402) ... The linked drop's images and the piece's variants join the teaser's rail, after its own images, each with a corner badge. The meta line counts them apart ("+N from Discord"), so a Patreon card never reads as though the creator posted Discord's files there. The text of each referenced post sits under the teaser's body. If FC made the link, the card says so, names the matching working name and offers Undo. If a person accepted it, it offers Unlink and makes no claim about FC. Both dismiss the pair. The kept row then stops the next sweep from linking it straight back. The announcement settings card gets the two windows: how close a drop must be before its own card is left out of the feed, and how far to reach for variants. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LVjrnpQjRgHdvq95rASoiR	2026-09-24 11:25:52 -04:00
bvandeusenandClaude Opus 5	b3e4491b0a	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	2026-09-24 08:16:07 -04:00
bvandeusenandClaude Opus 5	d0b0458d27	feat: the announcement link, on the card and in a review queue (388 E5) ... Rule 27 — E5's other half. The matcher can propose; this is where the operator decides, and where an accepted link actually shows up. **The review queue** (Settings → Ingestion & filters). Each proposal shows the per-signal breakdown, not just the total: "why did it suggest this" is the question the operator actually has, and a lone percentage cannot answer it. So a row reads "72% · timing 95% · says so 60%", and the copy states outright that a pair always needs two reasons — which is the property that stops a busy posting day from producing false pairs. The empty state says so explicitly. Nothing proposed is the EXPECTED state most of the time, and an empty queue that looks like a failure invites turning the threshold down until it produces noise. **On the card**, both directions, and accepted links only: the teaser gets "The full set is in Discord", the drop gets "Announced on Patreon". A pending proposal is a question for the review queue, never a claim to render beside the artwork — that distinction is the whole confirm-only design, so it is asserted in the backend (only `linked` rows reach the payload) and again here. One detail worth the comment it carries: the link's target is `{ query: { post_id } }` with no name or path. In vue-router that means "the current route with these query params", so it works identically from Latest and from Browse — and, more usefully, the card never reaches for `useRoute()`, which it has no other reason to know about and which is not available when it is mounted in a test without a router. Backend CI on 235393c was green: all 13 E5 tests and migration 0094. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LNXXULQDjVZmbuNa2G9mD9	2026-09-10 11:53:17 -04:00