deploy.

App/wwwroot/HiAPI-docsite/manual/run/running-a-simulation.html

@@ -91,10 +91,11 @@
 can press at a given moment is the part worth learning</strong>, because the availability of a button is
 what tells you where the run actually is.</p>
 <h2 id="where-it-is">Where it is</h2>
-<p>The Execution page at <code>/execution</code>. The transport sits along the top of the editor panel in the left
-dock, and it is mounted for the <strong>Execution</strong> root and every node beneath it — so it stays reachable
-while you are editing a Mission command one level in. There is exactly one of it on the page, and it
-is the thing that binds <kbd>F5</kbd> to <kbd>F8</kbd>.</p>
+<p>The Execution page at <code>/execution</code>. The transport sits in the run header at the top of the Control
+Tree pane in the left dock, above the <strong>Mission</strong> and <strong>Program</strong> roots, with the run-state badge at
+its right end. It is there whatever the tree has selected — so it stays reachable while you are
+editing a Mission command — and its keys keep working while the Control Tree row is collapsed. There
+is exactly one of it on the page, and it is the thing that binds <kbd>F5</kbd> to <kbd>F8</kbd>.</p>
 <h2 id="the-six-controls">The six controls</h2>
 <table>
 <thead>
@@ -196,19 +197,21 @@ the run has not stopped yet.</p>
 <p>The bar at rest, with the demo project open and nothing run yet, at <code>/execution</code>. Start, the two
 single-advance buttons and Reset are live; Pause and Stop are greyed, because there is no run to hold
 or to end — and the two single-advance buttons carry the <strong>L</strong> and the <strong>S</strong> that tell them apart. The
-badge on the <strong>Execution</strong> tree item reads <em>ready</em>, and the block on the canvas is uncut.</p>
-<p><img src="running-a-simulation-img/transport-ready.en.png" alt="The Execution page with the Control Tree on the left showing the Mission and Program branches, a green ready badge on the Execution item, the transport row above the editor panel with the pause and stop buttons greyed, and the 3D canvas showing an uncut rectangular aluminium block on its fixture"></p>
+badge at the right end of the run header reads <em>ready</em>, and the block on the canvas is uncut.</p>
+<p><img src="running-a-simulation-img/transport-ready.en.png" alt="The Execution page with the run header at the top of the Control Tree pane — the six transport buttons with the pause and stop buttons greyed, and a green ready badge at the right end — above the Mission root with its nine command rows, each with a checkbox and a drag handle and two of them unticked and dimmed, a + on the Mission row and on the two List rows, and the Program root listing four .ptp files and an inline entry; the Mission editor panel below reads Commands 9; the 3D canvas shows an uncut light-grey rectangular block on its grey fixture, and the Session Messages Shell tab reads No messages match the current filter"></p>
 <h2 id="reading-the-run-state">Reading the run state</h2>
-<p>The state rides the <strong>Execution</strong> item in the Control Tree as a coloured badge — <em>ready</em>, <em>running</em>,
-<em>paused</em>, <em>finished</em> — so it is readable from wherever you are in the tree rather than only from the
-transport. The footer along the bottom of the window carries the session's own messages beside it.</p>
-<p>The same page with the mission paused part way through. The badge now reads <em>paused</em> in orange, Pause
-has gone grey, and Stop has joined the live ones — so the bar alone tells you a run is open and held.
+<p>The state sits at the right end of the run header, beside the transport, as a coloured badge —
+<em>ready</em>, <em>running</em>, <em>paused</em>, <em>finished</em> — pinned above the tree, so it stays in view however far you
+scroll the tree. When the left dock is narrowed the buttons scroll out of view before the badge does:
+the run state is the last thing a resize hides. The footer along the bottom of the window carries the
+session's own messages.</p>
+<p>The same page with the mission paused part way through. The badge reads <em>paused</em> in orange, Pause is
+grey, and Stop has joined the live ones — so the bar alone tells you a run is open and held.
 On the canvas the tool path the run has laid down so far is now drawn over the block, and the tabs
 under it are counting what the run has reported: <strong>Shell</strong> is badged with the eleven messages the
 load and the run have written between them and <strong>NC Diagnostics</strong> with the one the parser raised,
 while <strong>Step Diagnostics</strong> and <strong>NC Manipulation</strong> carry no badge at all.</p>
-<p><img src="running-a-simulation-img/transport-paused.en.png" alt="The Execution page with the Control Tree on the left, its Execution item carrying an orange paused badge, the transport row above the editor panel with the pause button greyed and the rest live, the 3D canvas showing a gold disc cutter sunk into the top face of the white block on its grey fixture with a single thin green tool path entering from the upper left and dropping to it, and a footer reading Ready"></p>
+<p><img src="running-a-simulation-img/transport-paused.en.png" alt="The Execution page with the run header at the top of the Control Tree pane — the six transport buttons with only the pause button greyed, and an orange paused badge at the right end — above the Mission root with its nine command rows and the Program root with its five entries, the Mission editor panel below reading Commands 9, the 3D canvas showing a gold disc cutter sunk into the top face of the white block on its grey fixture with a single thin tool path entering from the upper left and dropping straight down in green to it, the Session Messages Shell tab badged 11 and NC Diagnostics badged 1 over a list of system messages, and a footer reading Ready"></p>
 <h2 id="the-keys-and-where-they-stop">The keys, and where they stop</h2>
 <p><kbd>F5</kbd> to <kbd>F8</kbd> are bound only while the Execution page is the one on screen. On every
 other page <kbd>F5</kbd> is the browser's own reload, and the same is true here in two cases: when