[BUGFIX] Resolve double-backslash escape in code text roles

[CybotTM]

Summary

Demonstrates a possible fix for #1188 — :rst: (and all other code-type text roles) display \\ literally instead of resolving to \.

All 20 code-type text roles pass $rawContent to CodeInlineNode, which preserves RST escape sequences literally. This means \\ in the RST source stays as \\ in the rendered output instead of resolving to \ as the author intended.

Approach: Add str_replace('\\\\', '\\', $value) in the CodeInlineNode constructor to resolve double-backslash escape sequences.

Changes

• CodeInlineNode.php — one line added in constructor
• New integration test code-textrole-escape covering :rst:, :shell:, :typoscript:, :yaml: with \\ and plain content
• Render-test examples added to Inline-code-and-textroles/Index.rst

Scope

This PR addresses Test B from the issue (double backslash). Tests A, D, E involve the upstream InlineLexer in phpDocumentor/guides consuming \` as ESCAPED_SIGN before text role boundaries are resolved — that requires a separate upstream fix.

⚠️ Known limitation — this is a demonstration, not a complete fix

The str_replace approach is blind — it cannot distinguish between:

• \\ meaning "RST escaped backslash → display \" (the bug we're fixing)
• \\ meaning "literal double backslash in code that should stay as \\"

PHP code samples that would break:

RST source	Before this PR	After this PR	Problem
:php:'/\d+/'``	'/\\d+/'	'/\d+/'	Lost the PHP string escape
:php:"hello\nworld"``	"hello\\nworld"	"hello\nworld"	Looks like a newline now
:php:preg_match('/\\/')``	preg_match('/\\\\/')	preg_match('/\\/')	Regex completely wrong

This is the fundamental tension identified in the issue: $rawContent was introduced by phpDocumentor/guides#533 to preserve literal backslashes for PHP namespaces (\TYPO3\CMS\Core), but that same literalness prevents \\ from resolving to \.

A proper fix needs to happen upstream in the parser/lexer layer where ESCAPED_SIGN tokens are available — only the parser knows which \\ came from an intentional RST escape vs which \ was just a literal backslash character in code.

Test plan

• make test-integration ENV=local — all 113 tests pass
• make code-style ENV=local — 0 issues
• make phpstan ENV=local — no errors
• make rendertest ENV=local — inspect "Escape handling in code text roles" section
• Verify :php: namespace paths still render correctly (existing code-php test)

[linawolf]

Did you note there was a change in the guide on friday? Not sure we would still need this change?

phpDocumentor/guides#1312

[CybotTM]

@linawolf ,

yes I know, was initiated by phpDocumentor/guides#1308

[CybotTM]

so, yes, should make this "demonstration" obsolete.

[linawolf]

@CybotTM would you like to close this pr then? Or maybe just keep the tests?