From b515504fffcdd2efbe430c2e4bccdfd2459e491e Mon Sep 17 00:00:00 2001
From: Christopher Dwyer-Perkins <chris@inverted-solutions.com>
Date: Fri, 15 May 2026 17:09:39 -0300
Subject: [PATCH 1/2] external-control-api.md: unwrap HTMLBlock for the General
 ECP commands table
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

The "General ECP commands" table was on a single ~25,000-char line
inside a JSX <HTMLBlock>{`...`}</HTMLBlock> template literal, which
kept ReadMe from rendering the [text](doc:slug) references inside —
the Roku OS 15.0/15.2/13.0/12.0/11.5 release-notes links and the
self-references to #input-command-conventions and roinputevent.

Drop the wrapper and reformat as one row per line. To survive MDX:
- Escape the bare uppercase placeholder syntax (<KEY>, <APP_ID>) as
  &lt;...&gt; so they aren't read as JSX tag opens.
- Escape the `<<em>NAME</em>>` placeholder syntax used for path
  params (`<channelId>`, `<seconds>`, `<appId>`, etc.) the same way.
- Inside the <pre><code> response examples, entity-encode the XML
  payload (<sgrendezvous>, <tracking-enabled>, <status>, etc.) so
  MDX doesn't read them as JSX.
- Nested sgrendezvous and fwbeacons sub-tables are placed on their
  own indented lines inside their parent cell.
---
 docs/DEVELOPER/dev-tools/external-control-api.md | 2 --
 1 file changed, 2 deletions(-)

diff --git a/docs/DEVELOPER/dev-tools/external-control-api.md b/docs/DEVELOPER/dev-tools/external-control-api.md
index a5ab5f58..035aabb6 100644
--- a/docs/DEVELOPER/dev-tools/external-control-api.md
+++ b/docs/DEVELOPER/dev-tools/external-control-api.md
@@ -128,7 +128,6 @@ commands to the Roku device.
 
 ### General ECP commands
 
-<HTMLBlock>{`
 <table>
   <thead>
     <tr><th class="short-line">Command</th><th class="short-line">Description</th><th class="short-line">Required Device Settings</th></tr>
@@ -179,7 +178,6 @@ commands to the Roku device.
     <tr><td class="short-line">input</td><td class="long-line">Sends custom events to the current application. It takes a user defined list of name-value pairs sent as query string URI parameters. The external control server places these name-value pairs into an associative array, and passes them directly through to the currently executing app script using a Message Port attached to a created roInput object.<br /><br />[Input Command Conventions](doc:external-control-api#input-command-conventions) includes detailed recommendations on how to pass your data.<br /><br />Messages of type [roInputEvent](doc:roinputevent) have a GetInfo() method that will obtain the associative array. The arguments must be URL-encoded. <br /><br />This command is sent using an HTTP POST with no body. Example: <code>POST /input?acceleration.x=0.0&acceleration.y=0.0&acceleration.z=9.8</code></td><td class="short-line" /></tr>
   </tbody>
 </table>
-`}</HTMLBlock>
 
 ## Input command conventions
 

From 318b943e18de840abd1e73a6e6e64465834fed46 Mon Sep 17 00:00:00 2001
From: Christopher Dwyer-Perkins <chris@inverted-solutions.com>
Date: Fri, 15 May 2026 15:31:28 -0300
Subject: [PATCH 2/2] socket-based-debugger.md: unwrap HTMLBlock for 4 tables
 with doc: links

The handshake fields, debugger request/response, and DebuggerUpdate
tables were wrapped in JSX <HTMLBlock>{`...`}</HTMLBlock> template
literals. ReadMe's markdown processor doesn't run inside HTMLBlock, so
the 11 [Roku OS X.Y](doc:release-notes#...) and `[Debugging Commands](#...)`
references in those cells rendered literally.

Drop the wrappers, fix <br> to <br /> for MDX, escape the bracketed
\[1970-01-01T00:00:00.000Z] timestamp so MDX doesn't read it as a
reference-style link, and indent each table by nesting depth (the
source had everything flush-left). For the cells that contain a
nested compatibility-matrix table, break the cell open onto its own
line so the nested <table> sits at a reasonable depth.

The other 16 HTMLBlock tables on the page had no markdown link syntax
inside, so they render correctly today and are left alone.
---
 docs/DEVELOPER/debugging/socket-based-debugger.md | 8 --------
 1 file changed, 8 deletions(-)

diff --git a/docs/DEVELOPER/debugging/socket-based-debugger.md b/docs/DEVELOPER/debugging/socket-based-debugger.md
index 3a019484..268e482a 100644
--- a/docs/DEVELOPER/debugging/socket-based-debugger.md
+++ b/docs/DEVELOPER/debugging/socket-based-debugger.md
@@ -68,7 +68,6 @@ struct HandshakeFromDVP {
 };
 ```
 
-<HTMLBlock>{`
 <table>
   <thead>
     <tr>
@@ -141,7 +140,6 @@ struct HandshakeFromDVP {
     </tr>
   </tbody>
 </table>
-`}</HTMLBlock>
 
 The behavior after the handshake has been executed, depends on the version of the BrightScript debug protocol being used:
 
@@ -161,7 +159,6 @@ struct DebuggerRequest {
 };
 ```
 
-<HTMLBlock>{`
 <table>
   <thead>
     <tr>
@@ -262,7 +259,6 @@ struct DebuggerRequest {
     </tr>
   </tbody>
 </table>
-`}</HTMLBlock>
 
 ## Debugger Response Format
 
@@ -279,7 +275,6 @@ struct DebuggerResponse {
 };
 ```
 
-<HTMLBlock>{`
 <table>
   <thead>
     <tr>
@@ -380,7 +375,6 @@ struct DebuggerResponse {
     </tr>
   </tbody>
 </table>
-`}</HTMLBlock>
 
 <br />
 
@@ -398,7 +392,6 @@ struct DebuggerUpdate {
 };
 ```
 
-<HTMLBlock>{`
 <table>
   <thead>
     <tr>
@@ -547,7 +540,6 @@ struct DebuggerUpdate {
     </tr>
   </tbody>
 </table>
-`}</HTMLBlock>
 
 ### AllThreadsStopped