fix: repair cp1252-mangled em-dashes and ellipsis in the reference-app wiki

All four 06_reference_app pages round-tripped U+2014 (em-dash) and U+2026
(ellipsis) through cp1252 during earlier PowerShell edits; restored the
characters and regenerated the wiki HTML + MCP modules.

standards/wiki/06_reference_app/04_client_admin/index.html

@@ -74,7 +74,7 @@
     <div data-md-component="skip">
       
         
-        <a href="#client-admin-a-the-spec-driven-frontend" class="md-skip">
+        <a href="#client-admin-the-spec-driven-frontend" class="md-skip">
           Skip to content
         </a>
       
@@ -851,18 +851,18 @@
 
 
 
-<h1 id="client-admin-a-the-spec-driven-frontend">Client Admin — the spec-driven frontend</h1>
-<p>The client sample (<code>standards/src/templates/client/</code>) renders a full admin —
-auth pages, resource lists, forms, detail views — <strong>from the server's
+<h1 id="client-admin-the-spec-driven-frontend">Client Admin — the spec-driven frontend</h1>
+<p>The client sample (<code>standards/src/templates/client/</code>) renders a full admin —
+auth pages, resource lists, forms, detail views — <strong>from the server's
 <code>openapi.yaml</code></strong>, driven entirely by the x- extension fields. There are no
 hand-written screens per resource.</p>
 <h2 id="what-ships">What ships</h2>
 <p>A Vite + React + MUI app wiring the two Aetos packages:</p>
 <ul>
-<li><strong><code>@aetoskia/react-openapi</code></strong> — fetches <code>${VITE_API_BASE_URL}/openapi.json</code>,
+<li><strong><code>@aetoskia/react-openapi</code></strong> — fetches <code>${VITE_API_BASE_URL}/openapi.json</code>,
   builds the router and the resource admin from the spec's schemas and x-
-  fields (list columns, autocomplete, fk pickers, enum selects, hidden fields…)</li>
-<li><strong><code>@aetoskia/react-auth</code></strong> — login/register/logout against the auth-server
+  fields (list columns, autocomplete, fk pickers, enum selects, hidden fields…)</li>
+<li><strong><code>@aetoskia/react-auth</code></strong> — login/register/logout against the auth-server
   paths declared in the spec's <code>securitySchemes.bearerAuth</code>, and attaches the
   JWT to every API call</li>
 <li>a shared MUI theme (<code>src/shared-theme/</code>) and the shell
@@ -892,7 +892,7 @@ hand-written screens per resource.</p>
 </span></code></pre></div></td></tr></table></div>
 <p>Open the dev-server URL; the admin lists Parents, Pets, Treatments, Vets,
 Appointments and Jobs straight from the vet spec. Edit <code>openapi.yaml</code> on the
-server and the client follows on reload — the spec is the contract on both
+server and the client follows on reload — the spec is the contract on both
 sides.</p>
 <h2 id="where-the-x-extensions-come-from">Where the x- extensions come from</h2>
 <p>The canonical catalog lives in the react-openapi package