links_resolve can miss a real broken link on a line that carries a backslash-escaped backtick: stripInlineCode (internal/core/lint/lint.go) pairs every backtick it meets, so an escaped backtick, which CommonMark reads as a literal character and never as a code-span delimiter, opens a span that the next backtick closes, and a link between them is blanked before the link pattern runs. A line reading a literal backtick, then text with a link to a missing file, then another literal backtick reports no finding, so the records gate passes a broken link. Found by the tier1 review (review-tier1 finding 4).

links_resolve can miss a real broken link on a line that carries a backslash-escaped backtick: stripInlineCode (internal/core/lint/lint.go) pairs every backtick it meets, so an escaped backtick, which CommonMark reads as a literal character and never as a code-span delimiter, opens a span that the next backtick closes, and a link between them is blanked before the link pattern runs. A line reading a literal backtick, then text with a link to a missing file, then another literal backtick reports no finding, so the records gate passes a broken link. Found by the tier1 review (review-tier1 finding 4).

Grounds

• pursued: links_resolve reports a broken link on a line carrying escaped backticks and still blanks real code spans; shown wrong if a link inside a real code span is reported, or a broken link beside an escaped backtick is not