Fix double escaping and decode HTML entities in backticks for command documentation

[Copilot]

Command documentation generator was double-escaping HTML entities and not decoding them inside backtick-enclosed code spans, causing incorrect rendering in generated files.

Changes

Generator fixes (bin/Handbook_Command.php)

1. Prevent double escaping (lines 649-650):
   • Converts < back to < and > back to >
   • Placed after word wrapping logic to prevent double escaping when htmlspecialchars() processes content that already contains entities

// Prevent double escaping of HTML entities.
$docs = preg_replace( '/</', '<', $docs );
$docs = preg_replace( '/>/', '>', $docs );

2. Decode HTML entities inside backticks (lines 653-659):
   • Uses preg_replace_callback to find backtick-enclosed code spans
   • Decodes HTML entities within them using html_entity_decode()
   • Ensures inline code like `--theme=<theme>` renders correctly instead of `--theme=<theme>`

// Decode HTML entities inside backticks.
$docs = preg_replace_callback(
    '/`([^`]*)`/',
    function ( $matches ) {
        return '`' . html_entity_decode( $matches[1], ENT_QUOTES | ENT_HTML401 ) . '`';
    },
    $docs
);

Problem

1. When source docblocks contain <slug> (HTML entities), the htmlspecialchars() call on line 609 converts the & in < to &, resulting in <slug> (double-escaped) in the output.
2. HTML entities inside backtick-enclosed code spans were not being decoded, causing parameter placeholders to display as <theme> instead of <theme> in inline code.

Impact

Future documentation generations will:

• No longer produce double-escaped HTML entities
• Correctly render parameter placeholders in inline code with angle brackets instead of HTML entities
• Display `--theme=<theme>` instead of `--theme=<theme>` on the website

Original prompt

---

This section details on the original issue you should resolve

<issue_title>scaffold taxonomy docs have incorrect rendering</issue_title>
<issue_description>On https://developer.wordpress.org/cli/commands/scaffold/taxonomy/, the docs display < and > instead of the respective glyphs:

--theme and --plugin should probably have identical formatting with regards to whether the =<name> is included inside the square brackets.</issue_description>

<agent_instructions>Don't turn those glyphs such as backticks into HTML entities</agent_instructions>

Comments on the Issue (you are @copilot in this section)

• Fixes scaffold taxonomy docs have incorrect rendering #614

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[swissspidy]

@copilot I think the issue is actually some double escaping.

Revert your changes.

Then, make sure < is turned into < and > into >

[Copilot]

@copilot I think the issue is actually some double escaping.

Revert your changes.
...

Done. Reverted all changes and added fix to prevent double escaping by converting < to < and > to > in the generator. Commit: 81e126b

[swissspidy]

@copilot I think what we need to do is to decode HTML entities inside backticks. So that we for example have ``--theme=instead of--theme=<theme>`.

[Copilot]

@copilot I think what we need to do is to decode HTML entities inside backticks. So that we for example have ``--theme=instead of--theme=<theme>`.

Done. Added regex to decode HTML entities inside backticks using html_entity_decode(). Now `--theme=<theme>` will become `--theme=<theme>` in generated documentation. Commit: 676a107