Treat image labels as Markdown alternative text

docs/config.md

@@ -59,7 +59,9 @@ submodule contents remain out of scope under either setting.
 
 The parser recognizes inline links, images, reference links, and CommonMark
 autolinks; link-like text in code is ignored, and raw HTML destinations are
-outside this check. Relative paths resolve from the source document in the
+outside this check. For linked images, the image source and enclosing link
+target are checked. Image labels supply alternative text.
+Relative paths resolve from the source document in the
 captured commit. Query components are ignored for file existence, and percent
 escapes in local paths and fragments are decoded once. Fragments are compared
 in lowercase with anchors derived from visible ATX or Setext heading text.

docs/roadmap/remediation.md

@@ -1,6 +1,6 @@
 # ReleaseKit implementation remediation
 
-Status: Two open v0.2.0 findings (8–9). Findings 1–7 are addressed.
+Status: One open v0.2.0 finding (9). Findings 1–8 are addressed.
 
 The v0.2.0 review covers committed state `edd670e` and the implementation
 commits after `89981ab`, against the [implementation plan](implementation.md),
@@ -330,6 +330,13 @@ Keep external destination availability outside this offline capability.
 
 ## 8. P2: Image alternative text creates additional release requirements
 
+**Resolution:** Addressed. Destination extraction records an image source and
+skips its alternative-text children. Regression coverage exercises nested
+images/links, missing anchors, and outside-checkout label syntax under both
+boundary settings. Real linked images still report missing sources and link
+targets. The regression failed before the fix, and
+`go test ./internal/validation` passed afterward.
+
 **Owner:** [Markdown link extraction](../../internal/validation/markdown.go),
 `parseMarkdown`, especially the image branch and AST traversal at lines 65–110.