fix SoftNcRunner GM code normalization.

App/wwwroot/HiAPI-docsite/app-anatomy/index.html

@@ -87,7 +87,7 @@
         <article data-uid="">
           <h1 id="hinc-app-anatomy">HiNC App Anatomy</h1>
 
-<p>This section is a <strong>transparent, per-component anatomy of the HiNC application family</strong> — the <strong>HiNC-2025-webservice</strong> (the current flagship product: Quasar SPA + ASP.NET Core) and the <strong>HiNC-2025-win-desktop</strong> (the WPF desktop client). Every page dissects one UI component and exposes three layers:</p>
+<p>This section is a <strong>transparent, per-component anatomy of the HiNC application family</strong>. The forward-looking flagship is <strong>HiNC-2025-webservice</strong> (Quasar SPA + ASP.NET Core); <strong>HiNC-2025-win-desktop</strong> (the WPF client) is included only as a <strong>legacy reference</strong> — it is waiting to be fully obsoleted and is kept here so readers can map old screens onto their web-service successors. Every page dissects one UI component and exposes three layers:</p>
 <ol>
 <li><strong>Layout</strong> — the visual / widget tree the user sees.</li>
 <li><strong>Key Model</strong> — the backing HiAPI types (<a class="xref" href="../api/Hi.MachiningProcs.MachiningProject.html">MachiningProject</a>, <a class="xref" href="../api/Hi.HiNcKits.UserService.html">UserService</a>, …).</li>
@@ -104,14 +104,14 @@
 </ul>
 </div>
 <h2 id="source-code-repositories">Source Code Repositories</h2>
-<p>The anatomy covers two codebases in parallel. Each page's <em>Source Code Path</em> section lists the file in each repository that implements the same component.</p>
+<p>The anatomy covers two codebases. Each page's <em>Source Code Path</em> section lists the implementing file in each repository, but the two are <strong>not</strong> peers: the web service is the live target, the WPF desktop is the outgoing legacy that the web service replaces.</p>
 <h3 id="hinc-2025-webservice-current-flagship">HiNC-2025-webservice (current flagship)</h3>
-<p>Quasar CLI SPA (Vue 3 + TypeScript + Pinia + Quasar) served by ASP.NET Core. This is the primary product delivered to end users today.</p>
+<p>Quasar CLI SPA (Vue 3 + TypeScript + Pinia + Quasar) served by ASP.NET Core. This is the primary product delivered to end users today and the only target for new feature work.</p>
 <ul>
 <li>Repository: <a href="https://superhightech-gitea.webredirect.org/HiNC-Deploy/HiNC-2025-webservice.git">https://superhightech-gitea.webredirect.org/HiNC-Deploy/HiNC-2025-webservice.git</a></li>
 </ul>
-<h3 id="hinc-2025-win-desktop">HiNC-2025-win-desktop</h3>
-<p>Native Windows desktop client built on WPF.</p>
+<h3 id="hinc-2025-win-desktop-legacy-pending-obsoletion">HiNC-2025-win-desktop (legacy, pending obsoletion)</h3>
+<p>Native Windows desktop client built on WPF. <strong>Slated to be fully obsoleted</strong> — listed here only so readers familiar with the desktop UI can locate the equivalent web-service component. Do not start new work against this codebase.</p>
 <ul>
 <li>Repository: <a href="https://superhightech-gitea.webredirect.org/HiNC-Deploy/HiNC-2025-win-desktop.git">https://superhightech-gitea.webredirect.org/HiNC-Deploy/HiNC-2025-win-desktop.git</a></li>
 </ul>
@@ -158,7 +158,7 @@
 <ol>
 <li>Start at <strong>Layout</strong> to see the widget tree and understand the user-visible structure.</li>
 <li>Drop down to <strong>Key Model</strong> to learn which backing type each widget edits; click the <code>&lt;xref:…&gt;</code> links to open the API reference.</li>
-<li>Finish at <strong>Source Code Path</strong> to open the actual file in each repository. &ldquo;Web Page Application Source Code Path&rdquo; is authoritative for the current flagship product; the WPF entry supplies the desktop-client comparison.</li>
+<li>Finish at <strong>Source Code Path</strong> to open the actual file in each repository. &ldquo;Web Page Application Source Code Path&rdquo; is the authoritative entry for the current flagship product; the WPF entry is a legacy cross-reference for users migrating off the desktop client.</li>
 </ol>
 <div class="TIP">
 <h5>Tip</h5>
@@ -166,7 +166,7 @@
 </div>
 <div class="NOTE">
 <h5>Note</h5>
-<p>If you are using an AI agent to make changes across both apps, point it at the specific anatomy page whose component you are editing. Each page intentionally names the WPF and Quasar source files in lock-step so the agent keeps the two in sync.</p>
+<p>If you are using an AI agent to extend the product, point it at the specific anatomy page whose component you are editing and have it work on the <strong>Quasar / ASP.NET Core</strong> side. The WPF source paths remain listed so the agent can read the legacy behavior for reference, but new features should land in the web service only — the WPF client is on its way out.</p>
 </div>
 
 </article>