Fix Engaging sort to rank by reaction count

[soyalejolopez]

Problem

Sorting the catalog by Engaging never surfaced highly-reacted resources. PowerClaw — the only resource with a reaction — stayed near the bottom instead of the top.

Two root causes:

1. Rate-based sort buried high-traffic resources. "Engaging" used a smoothed upvotes-per-view rate (upvotes + 2) / (views + 40). With 1,632 views, a single reaction produces a microscopic rate, so PowerClaw sank below low-traffic resources that had zero reactions.
2. Only 👍 counted. build-stats.js counted only THUMBS_UP reactions as upvotes, so any other reaction (❤️ 🚀 🎉 👀 …) was ignored entirely.

Changes

• index.html — "Engaging" now ranks by raw reaction/upvote count descending, with views as a tiebreaker, then name.
• tools/catalog-build/build-stats.js — mapDiscussions now sums reactors across all reaction groups, not just THUMBS_UP. The upvotes field name is unchanged (now represents total reactions), so nothing downstream changes.

Notes

resource-stats.json still needs a fresh traffic-stats workflow run to pick up the new reaction totals; after that, reacted resources will sort to the top of Engaging.

Co-authored-by: Copilot App 223556219+Copilot@users.noreply.github.com

[github-actions]

🛰️ PR Sweeper report

Risk: 🟢 LOW · Security gate: ✅ passing · Files: 2

🔒 Automated guardrails (authoritative)

	Category	Location	Finding
ℹ️	scope	—	Change(s) outside known content roots: index.html.

🤖 Dual-model AI review (advisory)

Deep-reasoning reviewer — openai/o3 · verdict: comment · risk: low

No hard-coded secrets, data exfiltration, or dangerous patterns observed. Changes are logic-only and pose negligible security risk. One quality concern: the new reaction count may include negative reactions unintentionally.

Quality notes:

• tools/catalog-build/build-stats.js — The new summation counts every reaction group, including potentially negative or neutral ones (e.g., THUMBS_DOWN, CONFUSED). If the intent is to capture only positive signals you may want to filter by content === 'THUMBS_UP' (or a positive-reaction allow-list) before adding.
• index.html — Sort order for the 'engaging' tab changed from a weighted engagement rate to a simple upvotes→views→name sort. If this is intentional, consider updating any UI/help text that still references the previous “engagement rate” concept.

✅ Suggested next steps

• Confirm that counting all reaction groups (not just THUMBS_UP) is expected; otherwise filter accordingly.
• If the sorting philosophy for the 'engaging' view has changed, update accompanying documentation or UI hints so users understand the new behavior.

---

The automated guardrails are authoritative and gate the security status. The AI review is advisory and never auto-merges. Thanks for contributing to FastTrack! 🛩️

[gemini-code-assist]

Caution

The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased.