deploy.

App/wwwroot/HiAPI-docsite/anatomy/conventions/rendering-canvas-web-service.html

@@ -153,9 +153,11 @@ can put its own content on a canvas without touching the transport.</p>
 Execution displayee to it</li>
 </ul>
 <p>Six further controllers bind content the same way — the STL preview, the Tool House, the General
-Setup equipment, the machine tool, the Mech Builder general mechanism and the Controller page —
-each with its own route and its own displayee, all reaching the engine through the same connection
-ID.</p>
+Setup equipment, the machine tool, the Mech Builder general mechanism and the legacy HardNcEnv
+controller — each with its own route, all reaching the engine through the same connection ID. The
+first five bind a displayee of their own; the last binds the shared Execution displayee, and it has
+had no caller since the Legacy Controller page was removed on 2026-09-11 — the route is still
+mounted, but no canvas in the SPA initializes against it.</p>
 <h2 id="key-points">Key Points</h2>
 <ul>
 <li>Every canvas data-stream operation is indexed by the connection ID.</li>
@@ -186,8 +188,9 @@ Execution displayee to the engine named by the connection ID.</li>
 (<code>api/mech/machine-tool/display</code>).</li>
 <li><code>Mech/MechBuilder/GeneralMechanismDisplayController.cs</code> — the Mech Builder canvas binding
 (<code>api/general-mechanism/display</code>).</li>
-<li><code>Controller/ControllerController.cs</code> — the Controller page's canvas binding
-(<code>initialize-display/{connectionId}</code>).</li>
+<li><code>Controller/ControllerController.cs</code> — the legacy controller surface's canvas binding
+(<code>initialize-display/{connectionId}</code>), which assigns the shared Execution displayee; still mounted,
+with no SPA caller since the Legacy Controller page was removed.</li>
 </ul>
 <h3 id="web-page-application-source-code-path">Web Page Application Source Code Path</h3>
 <ul>