[Patrick-Erichsen]

Summary

Preserve the shell projection's conservative fenced-code boundary when the canonical Markdown parser exits a nested-list fence at dedentation. This keeps executable-looking backtick text available to the scanner. Companion to #111.

 canonical inline-code refinement
+ exclude existing literal fence ranges
+ coalesce contiguous fence lines into one range

Evidence

• Before: the nested-list/deeply-indented fence control removes literal command backticks: 1 failed, 2 passed.
  After: all 3 native fence controls pass, including the 10,000 blank-line/100-paragraph exclusion bound; all 17 table/fence controls pass together.
• Applied the complete runtime patch to pinned upstream 95a52d8: all 118 source/dependency files match composed producer ff4faee byte-for-byte; all 278 native adoption tests and 2,020 related producer controls pass.
• Six unchanged original reports, 18 analyzer comparisons: every finding signature preserved. Solaris data-engineer clears its false marker limit; unrelated incomplete shell/parser cases remain incomplete. This is scanner regression proof, not production-unblocked proof.

Merge Danger

Door: two-way

Blast Radius: scanner

Raw instruction text, findings, workflow/concurrency limits, PDF and OSV repairs remain intact. The fence exclusions are bounded by contiguous blocks rather than individual blank lines.

[clawsweeper]

🦞👀
ClawSweeper picked this up.

Pull request received. I will update this pull request when review starts.