deploy.

App/wwwroot/HiAPI-docsite/manual/run/playing-a-program.html

@@ -91,8 +91,9 @@
 lives rather than what it does: <strong>Program File</strong> references a file on disk, <strong>NC Code</strong> carries the
 text inside the project.</p>
 <h2 id="where-they-are">Where they are</h2>
-<p>The Execution page's <strong>Mission</strong> branch. Both sit in the <strong>Program</strong> category of <strong>Add Command</strong>,
-and both are placed like any other command — see <a href="building-a-mission.html">Building a Mission</a>.</p>
+<p><strong>Mission</strong>, the first root of the Execution page's Control Tree. Both sit in the <strong>Program</strong>
+category of <strong>Add Command</strong>, the <strong>+</strong> on the Mission row or on a List row, and both are placed
+like any other command — see <a href="building-a-mission.html">Building a Mission</a>.</p>
 <h2 id="which-one-to-use">Which one to use</h2>
 <ul>
 <li><strong>Program File</strong> — the program stays a file, and the project stores the path. Editing the file
@@ -139,7 +140,7 @@ reached by typing its absolute path into the field instead.</p>
 </table>
 <p><strong>The picker takes more than one file.</strong> The first goes on the command you opened it from; every
 further pick becomes a <strong>new Program File command</strong> placed directly after it, in the order you
-picked them, inside the same list — including inside a group. That is the quick way to bring a
+picked them, inside the same list — including inside a nested List. That is the quick way to bring a
 folder of CAM output into a mission.</p>
 <h3 id="choose-the-reader">Choose the reader</h3>
 <p><strong>Play As</strong> decides which reader plays the file:</p>
@@ -183,17 +184,19 @@ and what its words mean is <a href="../../technique/nc-dialects/index.html">NC D
 <p>Typing saves the path as you type; the banner refreshes when you leave the field or press
 <kbd>Enter</kbd>. An orange banner is worth trusting: it means the path does not resolve on the
 machine that will play it, which is not always the machine you are typing on.</p>
-<p>The first Program File in the demo mission's <strong>Roughing</strong> group, at
-<code>/execution?tree=execution/mission/2/0</code>. The path field carries a project-relative path, <strong>Play As</strong>
-reads <em>Auto</em>, and the green banner below reports the file's size, modified time and line count with
-<strong>Preview</strong> beside it. The row and the tree label both read <code>Program File</code> followed by the path,
-which is how a mission of several programs stays readable.</p>
-<p><img src="playing-a-program-img/program-file.en.png" alt="The Program File command panel in the Control Tree dock: a program file path field with a Browse button, a Play As select reading Auto, and a green file information banner giving size, modified time and line count with a Preview button"></p>
+<p>The first Program File in the demo mission's <strong>List [Roughing]</strong>, at
+<code>/execution?tree=execution/mission/2/0</code>, selected in the tree under the run header with its move,
+duplicate and delete buttons revealed. The path field carries a project-relative path, <strong>Play As</strong>
+reads <em>Auto (by extension)</em>, and the green banner below reports the file's size, modified time and
+line count with <strong>Preview</strong> beside it. The tree row and the panel's header both read <code>Program File</code>
+followed by the path in brackets, which is how a mission of several programs stays readable.</p>
+<p><img src="playing-a-program-img/program-file.en.png" alt="The Execution page's Control Tree with the six transport buttons and a green ready badge above the tree; the Mission root row carries a + at its right edge, and under it Machining Resolution 1 mm, Collision Detection On, then List Roughing expanded with its own + over a selected Program File NC/circle.ptp row showing its move up, move down, duplicate and delete buttons and a Program File NC/drill_slot.ptp row, a collapsed List Finishing with a +, Program File NC/circle.ptp, NC Code Inline finishing pass, a greyed Program File NC/slide-test-resolution-script.ptp with its checkbox cleared, NC Optimization Config expanded over Distances, Feedrate, Motion Dynamics, Force &amp; Safety and Compensation, and a greyed Post-Execution with its checkbox cleared over a child row cut off at the tree's bottom edge, every command row with a checkbox and a drag handle; the panel below is headed Mission / List [Roughing] / Program File [NC/circle.ptp] and holds a Program File Path field reading NC/circle.ptp with a Browse button, a Play As select reading Auto (by extension), and a green banner reading 298 B, modified 2024-09-05 10:38:37, 21 lines with a Preview button"></p>
 <h2 id="nc-code">NC Code</h2>
 <h3 id="name-it">Name it</h3>
 <p><strong>Title</strong> is optional in the sense that the field may be cleared, but it is not decoration: it is
-the program name the run reports under, and it is the detail the mission row brackets. A new command
-arrives with <code>NC Code</code> already in the field; rename it and both the log and the row follow.</p>
+the program name the run reports under, and it is the detail the command's row in the Control Tree
+brackets. A new command arrives with <code>NC Code</code> already in the field; rename it and both the log and
+the row follow.</p>
 <h3 id="write-it">Write it</h3>
 <p>The editor is a plain monospace area — no line numbers and no syntax highlighting, because this is
 NC text, not a program in a language the application parses while you type. Line and character
@@ -207,10 +210,11 @@ counts sit below it and follow what you type.</p>
 <p><strong>Nothing is checked while you type.</strong> The text is stored exactly as written, and a mistake in it
 surfaces when the mission plays it — in <strong>NC Diagnostics</strong>, see
 <a href="when-something-goes-wrong.html">When Something Goes Wrong</a>.</p>
-<p>The demo mission's short hand-written pass, at <code>/execution?tree=execution/mission/5</code>. The title
-above the editor is what the row brackets, and the line and character counts below it are the whole
-of the feedback this editor gives.</p>
-<p><img src="playing-a-program-img/nc-code.en.png" alt="The NC Code command panel: a Title field reading Inline finishing pass above a monospace text area holding a short NC program, with line and character counts and the Trim Blank Lines and Clear buttons below it"></p>
+<p>The demo mission's short hand-written pass, at <code>/execution?tree=execution/mission/5</code>, selected in
+the tree as <code>NC Code [Inline finishing pass]</code>. The title above the editor is what that row brackets,
+and the editor holds the whole program, the closing % of which is cut off at the bottom edge; the
+counts and the two buttons sit beneath it, past the bottom of this view.</p>
+<p><img src="playing-a-program-img/nc-code.en.png" alt="The Execution page's Control Tree with the six transport buttons and a green ready badge above the tree; the Mission root row carries a + at its right edge, List Roughing and the collapsed List Finishing carry their own +, and the NC Code Inline finishing pass row is selected with its move up, move down, duplicate and delete buttons revealed, the greyed Post-Execution at the bottom over a child row cut off at the tree's bottom edge, every command row with a checkbox and a drag handle; the panel below is headed Mission / NC Code [Inline finishing pass] and holds a Title (optional) field reading Inline finishing pass above a monospace NC Code text area whose program runs from a % line through N0010 to N0170 M30 and a closing % cut off at the bottom edge, the text area reaching the bottom edge of the panel"></p>
 <h2 id="after-it-has-played">After it has played</h2>
 <p>Every program a session read appears under the <strong>Program</strong> branch, with the passes that went over it
 and the marks the run left on each line. That is where you see what happened to a line, as opposed