Improve ARVIO discovery guides, collection examples and attribution

[ProdigyV21]

Summary

• Improve existing Jellyfin, Plex/Emby/Jellyfin and compatible-addon guides with concrete decision sections, testing checklists and honest limits; preserve URLs, screenshots and free Android pricing.
• Add three public-safe Collection Studio starters, deterministic JSON generation and read-only preview/fork links; keep Studio network-free and fix normal anchor handling.
• Add bounded guide-landing measurements and landing-page reporting to the existing first-party conversion funnel, preserving opt-outs, write budgets and server-only payment confirmation.
• Add a reviewer testing brief and researched, unsent outreach drafts. No advertising spend, public messages or directory resubmission.

Verification

• 86 focused website tests passed; localized guide validation passed (22 pages, 40 sitemap URLs).
• 131 backend tests passed.
• Full web suite passed (947 tests) and TypeScript passed; additional starter-import integration test passed through the actual app parser (18 Studio tests).
• Desktop and 390px mobile browser checks: starter preview, fork editing, preserved original draft, gallery navigation and no horizontal overflow.
• Production backend deployment precedes marketing publication; verify live pages after merge.

Scope

No Android or hosted web runtime changes. Existing dependency audit warnings are outside this incremental marketing task. This includes a web test change, so the existing hosted-web deploy workflow may rerun without a runtime change.

[ProdigyV21]

Release complete: PR merged and both marketing/auth production deployments verified ready on main commit 1bd7a1e. All required checks passed before merge. Approved reviewer pitches were sent to AFTVnews (Gmail SENT) and AndroidTVNews (contact-form success confirmation). The research document's draft statuses refer to preparation time. Updated 40-URL sitemap is live, but Google individual indexing returned a submission error and refreshed sitemap submission has no confirmed receipt; Search Console still shows the prior 4 October submission. No indexing, traffic or subscriber gains claimed. One source=qa journey was used for backend verification and must be excluded from business results. No paid ads or scheduled monitoring created.