You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
sync-starlight.mjs maps only ##-level USER_GUIDE.md anchors when rewriting cross-links for the Starlight mirrors. A ###-level heading falls through the mapping, and the mirror rewrites the cross-link to a page that does not contain that anchor. The result is a silent 404: the page loads, the anchor jump fails, and astro check cannot detect it because the link target page exists.
Why this is a design issue, not a per-link fix
This is the third instance of the anchor/route-mapping bug class in this stack:
Three instances of the same class point at the mapping design rather than the individual links. Candidate directions:
Map anchors at all heading levels, not just ##
Add a post-sync link-check step that resolves every rewritten anchor against the generated pages and fails the sync on a miss (closing the gap astro check leaves)
Origin
Found during self-review of PR #763 — see the merge-guidance comment: #763 (comment)
Problem
sync-starlight.mjsmaps only##-levelUSER_GUIDE.mdanchors when rewriting cross-links for the Starlight mirrors. A###-level heading falls through the mapping, and the mirror rewrites the cross-link to a page that does not contain that anchor. The result is a silent 404: the page loads, the anchor jump fails, andastro checkcannot detect it because the link target page exists.Why this is a design issue, not a per-link fix
This is the third instance of the anchor/route-mapping bug class in this stack:
COST_ATTRIBUTIONlink mapping#repository-onboardinganchor###heading caught in self-review on docs(cost): document every max_budget_usd surface and reconcile the Blueprint gap #763 (relinked to#per-repo-overridesas a workaround)Three instances of the same class point at the mapping design rather than the individual links. Candidate directions:
##astro checkleaves)Origin
Found during self-review of PR #763 — see the merge-guidance comment: #763 (comment)