Surface the per-field Elo leaderboards everywhere they are useful: as an
embeddable JSON+HTML widget that wiki pages, dashboards, and the per-field
/science/<field> landing pages can fetch by field tag. Today the data is
queryable via field_leaderboard() in
scidex/agora/open_question_tournament.py:600 but there is no public widget
endpoint or reusable HTML component that other surfaces can embed without
rewriting query+render logic.
GET /api/widget/open_questions/top?field=<slug>&limit=10{field, generated_at, items:[{id, question_text,
importance_elo, rd, sub_field, source_kind, age_days, n_matches}]},field_leaderboard() under the hood, applies thestatus IN ('open','active') filter from the decay task.
GET /widget/open_questions/top.html?field=<slug>&limit=10<iframe>-able from wiki pages and from aq-live-embed-dashboard-in-wiki).
[[openq:top10:neurodegeneration]] macro in wikicontent_md is rendered server-side to the widget HTML duringwiki_quality_pipeline.py post-process. Macro syntax is documenteddocs/atlas/openq_widget.md (≤2 pages).
Cache-Control: public, max-age=300.
api.py:56167 field-router) gains aAlzheimer's disease shows the widget after theapi.py:56167-56270 towiki_quality_pipeline.py and bulk_mermaid.py to learn theproject_scidex_mermaid_fence_incident).
<style scoped> and a single <table>; no47ee9103-ccc0 — Elo tournament populates importance_eloq-openq-decay-and-retire-answered — supplies the status filterq-live-embed-dashboard-in-wiki (sibling) — shares the wiki macro