fix(agents): parse prose and rendered HTML anchors

docs/development/agent-workflow.md

@@ -38,10 +38,11 @@ aliases and dotted code symbols are excluded. Bare dotted names with conventiona
 file suffixes (such as .md, .json or .ts) are treated as filenames. Use a `./`
 prefix or Markdown link for other ambiguous filenames that resemble code symbols.
 Multi-part dotfiles are path candidates too. Link paths and fragments are decoded
-separately so encoded filename delimiters stay in the filename. Fenced examples
+separately so encoded filename delimiters stay in the filename. Fenced and indented examples
 do not count as root guidance imports or satisfy the required Claude import.
-Heading anchors are derived from parsed text, not HTML sanitization. The Nx test
-hash includes `marked` so dependency changes invalidate parser coverage.
+Heading anchors decode HTML character references in text. Explicit HTML anchors
+use `parse5`, excluding comments, scripts, styles and template contents.
+The Nx test hash includes `marked` and `parse5` so dependency changes invalidate parser coverage.
 It cannot prove semantic equivalence; review changed contracts as well.
 
 ## Protected Markdown edits