[appdevelopsk]

User impact

All four editorial guides currently send readers directly to Google Play but provide no per-app link to their existing first-party feature, privacy and FAQ pages. This makes comparison/reassurance difficult before install. Add a clearly labeled Features & FAQs internal link to each of 17 existing editorial guide cards while keeping the existing Google Play CTA unchanged.

Scope

• Quick games: Blur, Instant Judge, Dotchi, Nodo, BrainBurst (5).

• Daily habits: True Me, FutureMe, Water Reminder, Gratitude Log (4).

• Decision helpers: Food Roulette, Movie Roulette, What To Do, Chore Roulette (4).

• AI tools: Debate Me, Voice Memo, Pantry AI, Name Maker (4).

• All destination /support/<slug>/index.html files verified to exist in main before editing.

• Add app-specific accessible labels, shared understated link styling, and a privacy-safe app_detail_click with app_slug, guide and placement=guide_card (reusing homepage event). Keep guide_store_click unchanged.

Verification

• Directly audited all four changed GitHub HTML blobs: 17/17 distinct matching store IDs, support path slugs, data-guide-detail, and app-specific aria-labels, with unchanged Play card count and exactly one new click listener per guide.

• Added scripts/test_guide_detail_links.py with 3 regression methods covering per-card ID/path equivalence and real support source files, event wiring, and first-party vs external store links.

• Executed the exact GitHub test-source blob be3036515588621f4640e206fcedbd402399c7c3 against representative 17-card fixture HTML locally: 3/3 PASS. The fixture is synthetic; not a full-browser test of the actual four GitHub HTML pages.

• No GitHub Actions, no deployment, GA4 DebugView or measured install uplift. Production release still owner-controlled.