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 THUMBS_UP counted. build-stats.js counted only THUMBS_UP reactions as upvotes, so any other reaction (heart, rocket, tada, eyes ...) 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.

[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 security, privacy, or licensing issues detected. Changes adjust sorting heuristics and broaden reaction counting logic. Implementation is straightforward and unobfuscated. Only minor quality concerns: editing generated HTML and potential behaviour change in reaction counting.

Quality notes:

• index.html — Directly editing the built HTML bundle can make future maintenance harder and diverge from source-of-truth templates or scripts. Consider applying this sorting-logic change in the source JS/TS file and regenerate the bundle.
• tools/catalog-build/build-stats.js — New logic now sums all reaction groups, not only THUMBS_UP. Confirm this is intentional; it will count all emoji reactions equally (e.g., laugh, hooray) and may inflate 'upvotes'.

✅ Suggested next steps

• Verify that the repository’s build workflow regenerates index.html from a source file; if so, move the change to the appropriate source to avoid manual bundle edits.
• Confirm that including all reaction types (not just THUMBS_UP) in upvote counts is the desired behaviour; otherwise, refine the filter.
• Add/update unit tests (if available) to cover the new engaging-sort criteria and the revised reaction-count aggregation.

---

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