fix(agents): validate visible headings and spaced paths

docs/development/agent-workflow.md

@@ -37,6 +37,7 @@ Write generic filenames as prose; commands, templates, globs, URLs, package
 aliases and dotted code symbols are excluded. Bare dotted names with conventional
 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.
+Explicit relative literal paths may contain spaces; command-option snippets are excluded.
 Multi-part dotfiles are path candidates too.
 Conventional extensionless filenames such as Dockerfile, Makefile and LICENSE
 are also path candidates; use an explicit `./` prefix for other extensionless files.
@@ -49,8 +50,9 @@ The parsed HTML tree also verifies that this paragraph is outside HTML container
 including templates split across Markdown tokens. Generated HTML is inspected
 in memory only; it is never executed or emitted.
 Heading anchors decode HTML character references in text and use `github-slugger`
-for GitHub-compatible character filtering and duplicate suffixes. Explicit HTML anchors
-use `parse5`, excluding comments, scripts, styles and template contents.
+for GitHub-compatible character filtering and duplicate suffixes.
+Only headings present outside inert HTML containers contribute slugs or duplicate counters.
+Explicit HTML anchors use `parse5`, excluding comments, scripts, styles and template contents.
 Rendered HTML anchor hrefs and image sources use the same local-reference checks
 as Markdown links, including decoded attributes and fragment validation.
 Image references check file existence without interpreting image fragments as