Skip to content

fix(audit): semantic bugs, null cards, OI labels, citation direction - #2033

Merged
Flotapponnier merged 2 commits into
mainfrom
dev
Aug 21, 2026
Merged

fix(audit): semantic bugs, null cards, OI labels, citation direction#2033
Flotapponnier merged 2 commits into
mainfrom
dev

Conversation

@Flotapponnier

Copy link
Copy Markdown
Collaborator

Summary

  • Bug fixes from audit review:

    • alternatives/[slug]: filter null perp bench cards (section hidden when no metrics measured)
    • products/[slug]: remove hardcoded "refreshed every minute" from fallback description
    • answers/[slug]: remove hardcoded ", refreshed every minute." footnote
    • perp-venue-external.ts: rename "Open Interest" → "OI (all markets)" in extraKpis to distinguish from benchmark KPI strip (resolves $9B vs $64B Hyperliquid OI confusion)
    • citation.ts: headlineSentence() now uses "posts the lowest" for lower-is-better metrics instead of "leads" — affects /api/citable, /api/llm-context, MCP, JSON-LD
    • benchmarks/perp-amm-volume-share.yml: fix duplicate bench number 043 → 233
  • 7 answer YAMLs with inverted directional language for lower-is-better metrics:

    • which-l2-has-the-fastest-block-time, which-gas-oracle-is-the-most-accurate, best-rpc-for-indexer, which-bridge-has-the-fastest-quote-api, which-evm-aggregator-has-the-fastest-quote, which-stablecoin-is-the-most-stable, how-much-does-it-cost-to-bridge-usdc-to-arbitrum

…on direction, bench 233

* fix(audit): answer leads semantics, freshness copy, null bench cards, OI label

* fix(audit): stablecoin/bridge leads semantics, drop hardcoded refresh cadence on answers page

* fix: perp-amm-volume-share duplicate bench number 043 -> 233

* fix(citation): direction-aware headlineSentence for lower-is-better metrics
@Flotapponnier
Flotapponnier merged commit 5365bec into main Aug 21, 2026
1 of 2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant