fix(docs): repair 64 broken links in the Beryl/B20 spec - #1814
Open
pucedoteth wants to merge 1 commit into
Open
Conversation
Every generated B20 interface reference page renders a "Related concept"
link pointing into `.../b20/specification/concepts/` or
`.../b20/specification/implementation/`. Neither directory exists, so all
58 + 4 of those links 404 in production. The pages are reachable (the
spec index links into the reference tree), so the path is:
spec -> reference -> method page -> click -> 404.
The concept material does exist, as sections of `specification/index.mdx`,
so repoint each link at the matching anchor:
concepts/roles-and-access-control -> #roles-model
concepts/policies-and-scopes -> #policy-registry
concepts/variants-asset-vs-stablecoin -> #variants
concepts/architecture-and-precompiles -> #precompile-addresses
implementation/deployment-and-... -> #factory
concepts/token-lifecycle -> the page itself, since it
spans the Mint / Burn / Seize / Supply Cap / Pause sections
Separately, the Beryl overview links twice to
`/base-chain/specs/upgrades/beryl/eip-8130`, which 404s; that page lives
at `/base-chain/specs/upgrades/cobalt/eip-8130`.
All targets and anchors verified against docs.base.org.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Collaborator
🟡 Heimdall Review Status
|
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
3 participants
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.
Problem
Every generated B20 interface reference page renders a
[Related concept](…)link on line 7 that points into.../b20/specification/concepts/or.../b20/specification/implementation/. Neither directory exists in this repo, so all 62 of those links 404 in production.These pages are reachable by users —
specification/index.mdxlinks into the generated reference tree — so the path is: spec → reference → method page → click "Related concept" → 404.Verified live:
…/specification/concepts/token-lifecycle…/specification/concepts/policies-and-scopes…/specification/concepts/variants-asset-vs-stablecoin…/specification/concepts/roles-and-access-control…/specification/concepts/architecture-and-precompiles…/specification/implementation/deployment-and-initcalls-encoding/base-chain/specs/upgrades/beryl/eip-8130Fix
The concept material does exist — as sections of
specification/index.mdx— so each link is repointed at the matching anchor:concepts/roles-and-access-controlspecification#roles-modelconcepts/policies-and-scopesspecification#policy-registryconcepts/variants-asset-vs-stablecoinspecification#variantsconcepts/architecture-and-precompilesspecification#precompile-addressesimplementation/deployment-and-initcalls-encodingspecification#factoryconcepts/token-lifecyclespecification(spans Mint / Burn / Seize / Supply Cap / Pause, so no single anchor fits)Separately,
beryl/overview.mdxlinks twice to/base-chain/specs/upgrades/beryl/eip-8130, which 404s — that page lives at/base-chain/specs/upgrades/**cobalt**/eip-8130("Native Account Abstraction").Every destination and anchor id was checked against the rendered pages on docs.base.org. One line changed per link; no prose edits.
Notes for maintainers
description: "Generated B20 reference for …"). If so, the durable fix belongs in whatever generates them, or this will regress on the next run. Happy to adjust if you can point me at the generator.beryl/overview.mdxstill describes EIP-8130 as "upcoming in a later Beryl phase" while the page now lives under Cobalt. I only corrected the link — the prose seemed like a maintainer call.concepts/andimplementation/pages are planned rather than dropped, the alternative fix is to publish them and revert this. Either way the links shouldn't 404 in the meantime.