deploy.

App/wwwroot/HiAPI-docsite/anatomy/execution/mission/PostExecutionCommand-panel.html

@@ -87,8 +87,7 @@
         <article data-uid="Anatomy-PostExecutionCommandPanel">
           <h1 id="postexecutioncommand-panel-post-execution">PostExecutionCommand Panel (Post-Execution)</h1>
 
-<p>The key model is <a class="xref" href="../../../api/Hi.SessionCommands.PostExecutionCommand.html">PostExecutionCommand</a>, the command both clients label
-<strong>Post-Execution</strong>. It is the Output category's first catalog entry, and it carries five outputs
+<p>The key model is <a class="xref" href="../../../api/Hi.SessionCommands.PostExecutionCommand.html">PostExecutionCommand</a>, labelled <strong>Post-Execution</strong>. It is the Output category's first catalog entry, and it carries five outputs
 derived from what the session has played: step files, shot files, optimization files, a CL → NC
 writeback, and a geometry-difference detection.</p>
 <h2 id="when-it-runs-and-what-it-covers">When It Runs, and What It Covers</h2>
@@ -103,9 +102,7 @@ command before this command — and it re-serializes every control file the sess
 play is written back too. Read this together with
 <a class="xref" href="PreSettingCommand-panel.html">General Config</a>, the other half of the pair: those settings
 apply from their position forward, these outputs cover everything up to this position.</p>
-<p>The web client places the command anywhere in the list, like any other. The WPF client pins it to
-the end: a new command is inserted before a trailing Post-Execution while that is the list's only
-one, and the drag guard refuses to move it off the last position.</p>
+<p>The command sits anywhere in the list, like any other; nothing pins it to the end.</p>
 <p><code>Run</code> executes the enabled outputs in an order of its own, which is <strong>not</strong> the order the tree and
 the list below show them in: shot files, then step files, then optimization, then the CL → NC
 writeback, then the geometry difference. Output timestamps follow that order rather than the layout.</p>
@@ -218,14 +215,6 @@ carries the catalog attribute, so they load from a project file but are not offe
 Command dialog. Post-Execution is the catalogued carrier of these outputs, which is why they are
 edited as its sections.</p>
 </div>
-<h2 id="the-wpf-clients-panel">The WPF Client's Panel</h2>
-<p>There four of the outputs are group boxes on one panel, each an enable checkbox over a grid that is
-disabled until the box is ticked: Step Files Output, Shot Files Output, Optimization Output and
-Geometry Difference Detection. The physics condition collapses the Shot Files and Optimization group
-boxes rather than omitting tree nodes.</p>
-<p>CL → NC Writeback is the one output the web client has and this panel does not. Its two properties
-live on the same engine command, and the web section and its two endpoints are where they are
-edited.</p>
 <h2 id="source-code-path">Source Code Path</h2>
 <p>See <a class="xref" href="../../index.html">HiNC App Anatomy</a> for git repository links.</p>
 <h3 id="web-application">Web Application</h3>
@@ -251,7 +240,7 @@ overview caption and the writeback paragraph.</li>
 <li><code>wwwroot-src/src/stores/appState.ts</code> — the physics preference and licence flags the tree builder
 reads.</li>
 <li><code>Environments/PreferenceController.cs</code> — serves the physics preference already combined with the
-advanced-physics licence, the same condition the WPF panel evaluates.</li>
+advanced-physics licence.</li>
 <li><code>Missions/MissionController.cs</code> — the <code>commands/{path}/postexecution/*</code> endpoints: the five enable
 flags, the four templates, the shot-file time resolution and the geom-diff detect radius.</li>
 </ul>