docs: note A2 code drift from merged link-scanner fixes - #178
Merged
Merged
Conversation
Record that PRs #174 and #176 changed the broken-links heading/block branch after this plan was authored: A2.2's patch instructions no longer match the code structure, A2.1's block case is partially satisfied but still lacks the metadata-unavailable distinction, and the A2.3 comparison-version comment must cover both semantics changes. Documentation only.
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
Adds an execution note to the A2 section of
2026-09-13-v1-core-reliability.mdrecording that the link-scanner fixes merged after the plan was authored (#174 for issue #170, #176 for issue #173) changed the exact code area A2 targets.The note covers the three practical consequences for the future executor:
isBlock/foundbranches unchanged" instruction no longer matches the two-branch structure; adapt rather than apply verbatim.^block-idregression is partially satisfied by fix: stop flagging unverifiable and hashless block links as broken #174, but a null target cache is still misdescribed as "not found among explicit block ids" — the metadata-unavailable distinction and the heading null-cache case remain open A2 work.COMPARISON_VERSIONcomment must cover both semantics changes per the master plan's increment-once rule for the unreleased series.Documentation only; no behavior change.
Validation
npm run lint && npm run lint:obsidian-warnings && npm run build && npm test— 929 tests pass.