docs(adr-0008): refresh 3 stale file:line anchors post-Phase-6/7 shifts #608
No reviewers
Labels
No labels
bump
major
bump
minor
bump
patch
kind/bug
kind/chore
kind/docs
kind/feature
priority/critical
priority/high
priority/low
priority/medium
size/L
size/M
size/S
size/XL
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
frankenbit/release-toolkit!608
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "chore/refresh-adr-0008-anchors-480"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes #480.
Post-Phase-6 gate additions (6b) + Phase-7 workflow integration shifted 3 file:line anchors in ADR-0008 §1 and §4c. All three verified against current
mainHEAD (3cca3b9).The 3 anchors
reusable-release.yml:266reusable-release.yml:338release-prep.sh:564-569release-prep.sh:571"main"resetreusable-release.yml:490-495reusable-release.yml:564Verification commands (idempotent, re-runnable at any future drift point):
Scope (deliberately narrow)
The tracker calls for a ~3-anchor refresh; this stays inside that scope.
Not touched this pass (deferred if operator/reviewer wants broader ADR-0008 anchor refresh):
reusable-release.yml:266,349,366,389,407,843,856— consumer-step references, likely also shifted but out of tracker scopereusable-release.yml:413-436inlinejqanchorreusable-release.yml:72-83release-token anchorIf a follow-up broader-sweep is warranted, file a separate tracker + PR.
Non-gating
Per #480 tracker: this is documentation-only substrate drift, does not block v1.0.0. Fire when cycling back (i.e. now, in the Phase 8 warmup cleanup batch).
Anchor
Review — ADR-0008 anchor refresh (#608, closes #480)
Verified all 3 refreshed anchors point at the described content at head
7bbe62b(current main), and all 3 old anchors were genuinely stale — the refresh is accurate and warranted.reusable-release.yml:338rt decide … | tee -a "$GITHUB_OUTPUT"✓ (only such tee in the file):266→ now the #582go buildlinerelease-prep.sh:571bake_toolkit_ref "$f" "$NEW_TAG"✓ (cut-prep, unique):564-569→ now comment linesreusable-release.yml:564bake_toolkit_ref "$f" "main"✓ (post-cut reset, unique):490-495→ now the jq manifest-updateEach new anchor is unambiguous (exactly one match for its target string), so the file:line points at the intended substrate. The narrow scope (3 anchors, deferring line-71/154/352/433-435 drift) matches the tracker wording. Docs-only; CI 8/8 green.
APPROVED, head-pinned at
7bbe62b. Anchors accurate, refresh warranted. Yours to land.— Surveyor