docs(internal): correct ARL per-tier enforcement findings in debug-ratelimit chapter#30
Merged
Merged
Conversation
…telimit chapter md-CLAUDE-chapters/debug-ratelimit-tester.md still asserted the earlier, since-retracted conclusion that Cloudflare's response-header score counting is "empirically imprecise" and that business-tier was "effectively unlimited." A clean controlled A/B on rpc.near.red showed both requests_per_period and score_per_period enforce accurately (~1.0x), and per-tier requests_per_period caps every tier including business (50,028/50,000) -- so the prod-path 2x is path-specific and confounded (grandfathered skip rules + a rate floor), not an intrinsic score defect. Retract the old claim, record the rpc.near.red validation, and add the companion /api/debug route note. This correction was authored on the (now-merged) browser-keys-docs branch but only ever lived in a local stash; committing it here so main stops carrying the wrong conclusion. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01H8DjaLbA7Ed63XuSAENrJ7
Deploying builder-docs with
|
| Latest commit: |
3c83ae3
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://da4d850b.builder-docs.pages.dev |
| Branch Preview URL: | https://docs-debug-ratelimit-finding.builder-docs.pages.dev |
mikedotexe
added a commit
that referenced
this pull request
Jul 21, 2026
…an older build) No content change. Four PRs merged within ~3 minutes (#32, #33, #30, #31) and their Cloudflare Pages deployments finished out of order: #33 fe452e4 14:01:28 #31 f914d2f 14:02:13 <- newest commit (contains the RPC endpoint-URL fix) #30 99a2520 14:02:56 <- finished LAST CF Pages points the production alias at the last deployment to *finish*, not the newest commit, so docs.fastnear.com got pinned to #30's build (main.6e03125c.js), which predates the RPC fix. Result: the live docs still rendered a fabricated `https://rpc.mainnet.fastnear.com/account/view_account` instead of the real base endpoint. This empty commit forces a fresh production deployment of current main, which already contains the fix. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01H8DjaLbA7Ed63XuSAENrJ7
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.
What
md-CLAUDE-chapters/debug-ratelimit-tester.md(an internal continuity chapter) still asserted an earlier conclusion that has since been retracted: that Cloudflare's response-header score counting is "empirically imprecise" and that business-tier was "effectively unlimited."Why
A clean controlled A/B on
rpc.near.redshowed bothrequests_per_periodandscore_per_periodenforce accurately (~1.0×), and per-tierrequests_per_periodcaps every tier including business (50,028 / 50,000). The prod-path 2× was path-specific and confounded (≈142 grandfathered skip rules bypassing ARL + a rate floor), not an intrinsic score defect.Change
rpc.near.redvalidation./api/debugroute note (server-side off-origin probing).Docs-only, internal chapter — no runtime, RU-content, or page-surface changes. The correction was authored on the (now-merged)
browser-keys-docsbranch but only ever lived in a local stash.🤖 Generated with Claude Code
https://claude.ai/code/session_01H8DjaLbA7Ed63XuSAENrJ7