geo: fix cross-surface cache inconsistency and non-responsive answer pages - #1611
Closed
Flotapponnier wants to merge 1 commit into
Closed
Flotapponnier wants to merge 1 commit into
Flotapponnier wants to merge 1 commit into
Conversation
Flotapponnier
force-pushed
the
hotfix/geo-consistency-main
branch
from
September 11, 2026 15:56
a0af092 to
ea26957
Compare
Collaborator
Author
|
Closing during a branch cleanup: this has sat open since its creation date and the work has either shipped another way or gone stale. The diff stays readable on this page if any of it is wanted again. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Cherry-pick of #1610 onto main.
revalidate-aggregate/route.ts: also invalidates"benchmarks"tag so per-bench caches refresh atomically with the aggregate on each worker publish (fixes /answers/[slug] serving stale values vs the hub)llms.txt:groundingTraceLineinstead ofheadlineSentence— date-anchored claims so crawlers know the measurement timestampanswers/which-prediction-market-has-the-strictest-rate-limits.yml: rewrote short_answer to answer rate-limit strictness (Myriad 30 req/10s), not latencyanswers/which-prediction-market-data-api-is-the-freshest.yml: removed circular{{best_name}}(always resolved to Polymarket T0), now names Codex via{{p50:codex}}answers/drpc-vs-publicnode-vs-1rpc.yml: lead with the dRPC/PublicNode comparison before contextualizing with the wider board