feat(quality): GOAT synthesis improvements - hybrid cross-source linking, YouTube synonyms, human-readable xref tags

Ran 15-way blinded comparison (5 topics x 3 versions). CROSS won all 5 topics
(4.74/5.0 avg vs HN 4.10, Base 3.73). Then improved CROSS further:

- dedupe.py: hybrid similarity (token+trigram Jaccard) at 0.40 threshold,
  cross-source links went from 3 to 13 items across 5 topics
- render.py: [xref: HN5, HN4] -> [also on: HN, Reddit] for human-readable tags
- youtube_yt.py: SYNONYMS dict so "hip hop" matches "rap" (0.33 -> 0.71 score)
- SKILL.md: instruction #7 tells Claude to lead with cross-platform signals

Validation: improved CROSS scores 4.38/5.0 vs original 3.98 (+0.40), wins 4/5
topics. Biggest gains in specificity (+0.8) and format compliance (+1.0).

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

docs/comparison-results/synthesis/cross-5-react-svelte-improved.md

@@ -0,0 +1,38 @@
+## What I learned:
+
+The React-vs-Svelte debate in early 2026 has shifted from "which is better" to "when does each one make sense" - and the answer increasingly depends on what you're optimizing for. A viral comparison by Beyond Fireship (697K views) captures the mood with the line "life is more fun when unreasonable," suggesting that Svelte's appeal is partly philosophical. Meanwhile on Reddit, a startup migration post in r/webdev details real performance gains after moving from React to Svelte 5, grounding the conversation in production evidence rather than benchmark theater.
+
+**Svelte 5 runes reset the learning curve - and the narrative.** Fireship's "Did runes just ruin Svelte?" crystallized a tension the community is still processing. The old dollar-sign reactivity was Svelte's signature trick; runes replaced it with something more explicit but less magical. Reddit threads in r/sveltejs reflect this split: newcomers find runes intuitive, while long-time users mourn the simplicity that drew them in. The net effect is that Svelte now feels closer to React's mental model (explicit state declarations), which paradoxically makes it easier to compare - and harder to differentiate.
+
+**React's dominance is increasingly described as inertia, not enthusiasm.** @nicobaogim on X argues React in 2026 "only makes sense for ecosystem maturity and team habits," while @Chubbi_Stephen satirizes the discourse with "Meanwhile React: still powering 80%..." A CityJS conference talk by @erikras uses the phrase "late-stage React," treating it like an incumbent that everyone depends on but few champion. The Reddit thread in r/react comparing hooks/useEffect to runes reads less like advocacy and more like a support group. React is not losing users - it is losing evangelists.
+
+**Job market pragmatism still favors React, but the gap is narrowing.** The r/sveltejs thread "How is going svelte?" surfaces a recurring tension: developers love writing Svelte but worry about employability. @singhprateek_25's X post listing 2026 fresher requirements includes both React and Svelte side by side, signaling that hiring managers are at least aware. The government portal evaluation in r/sveltejs - a developer coming from .NET and React, seriously weighing Svelte for accessibility, SEO, and forms - suggests Svelte is crossing the threshold from "side project framework" to "enterprise candidate."
+
+**Post-framework thinking is emerging.** @cityjsconf announced a talk on Ripple that cherry-picks from React, Svelte, and Solid, while @dennydotio predicted frameworks themselves become obsolete once AI handles code generation. The Japanese developer community is exploring WebF, which compiles React/Vue/Svelte directly to native apps, per @QiitaTrend. The React-vs-Svelte framing may have a shorter shelf life than either community expects.
+
+### CONTRADICTIONS
+
+The biggest contradiction sits at the center of the Svelte community itself. Runes were supposed to make Svelte more approachable and scalable, but Fireship's video questioning whether runes "ruined" Svelte shows genuine anxiety. Reddit threads where newcomers say "Svelte is easier than React" coexist with experienced Svelte developers saying the migration to runes introduced friction they did not expect.
+
+**KEY PATTERNS:**
+
+1. **Decision-making threads outnumber opinion threads** - developers are asking "when should I use Svelte" not "is Svelte good," signaling market maturation, per r/sveltejs
+2. **Svelte wins the greenfield argument, React wins the hiring argument** - the tradeoff is consistently framed around team composition, not technology, per @nicobaogim
+3. **Svelte 5 runes narrowed the gap in both directions** - Svelte gained explicitness but lost some of its simplicity advantage over React, per Fireship on YouTube
+4. **Real-world constraint discussions favor nuanced choices** - the government portal thread showed that SSR support, a11y tooling, and i18n readiness matter more than DX benchmarks, per r/sveltejs
+5. **Cross-compilation and hybrid approaches are gaining traction** - WebF and Ripple both treat React and Svelte as source material rather than competing endpoints, per @QiitaTrend
+
+---
+All agents reported back!
+├─ 🟠 Reddit: 6 threads │ 339 upvotes
+├─ 🔵 X: 9 posts │ 76 likes │ 4 reposts
+├─ 🔴 YouTube: 10 videos │ 2,085,183 views │ 3 with transcripts
+├─ 🟡 HN: 0 stories (no results this cycle)
+├─ 🌐 Web: supplementary
+└─ 🗣️ Top voices: @FabianHiller (61 likes), @cityjsconf │ r/sveltejs, r/webdev, r/react
+---
+
+I'm now an expert on React vs Svelte 2026. Some things I can help with:
+- Evaluate whether Svelte fits a specific project with constraints like a11y, i18n, or SSR requirements
+- Compare the hiring and ecosystem implications of choosing Svelte over React for a new team
+- Analyze how Svelte 5 runes changed the developer experience compared to Svelte 4's dollar-sign syntax