Once #101's branch material is renamed by the anchors → criteria change, the relative links in PR #101's own description point at paths that no longer exist on main:
complexity_assessments/calibration/proposed-anchors.md → now proposed-criteria.mdcomplexity_assessments/calibration/proposed-anchors.py → now proposed-criteria.py
GitHub resolves relative links in a PR body against the repo, so both 404 after the rename merges. #101 is the reference people will follow to understand where revision 2's five new criteria came from, so the links are worth keeping alive.
Fix: edit #101's description, replacing proposed-anchors with proposed-criteria in the two links (the body also references complexity_assessments/calibration/README.md, which is unaffected). The body still says "anchors" throughout its prose — that's an accurate record of the terminology at the time and should be left as written.
Do this after the rename PR merges, not before.
Once #101's branch material is renamed by the anchors → criteria change, the relative links in PR #101's own description point at paths that no longer exist on
main:complexity_assessments/calibration/proposed-anchors.md→ nowproposed-criteria.mdcomplexity_assessments/calibration/proposed-anchors.py→ nowproposed-criteria.pyGitHub resolves relative links in a PR body against the repo, so both 404 after the rename merges. #101 is the reference people will follow to understand where revision 2's five new criteria came from, so the links are worth keeping alive.
Fix: edit #101's description, replacing
proposed-anchorswithproposed-criteriain the two links (the body also referencescomplexity_assessments/calibration/README.md, which is unaffected). The body still says "anchors" throughout its prose — that's an accurate record of the terminology at the time and should be left as written.Do this after the rename PR merges, not before.