Phase 7: serve the vet sample from the template tools and docs

- build.py: _TEMPLATE_COMPONENTS rewritten around the vet sample (53 kinds —
  per-resource slices, jobs, worked appointment_reminder family, tests);
  seed tokens dropped from the manifest ('sample: vet' instead)
- registry.py: get_app_component(kind) no longer renames item/example seeds;
  prompts and tool docs updated to 'copy a slice and adapt'
- templates/README.md, 01_build_recipe, 40_ui_admin, wiki/03 updated off the
  old seed scheme; repo inventory/config now exclude vet (docs move under
  standards; react/vet itself is deleted in a later phase)
- regenerated MCP bundle, vendored templates, and site output

standards/lib/40_ui_admin/index.html

@@ -713,7 +713,7 @@ Read it from the MCP bundle:</p>
 </span></code></pre></div></td></tr></table></div>
 <p>The app's own spec carries the per-resource values; the catalog explains what
 each field does. The template's <code>openapi.yaml</code> shows the convention on the
-example <code>Item</code> and <code>Job</code> schemas.</p>
+example <code>Job</code> schema.</p>
 <hr />
 <h2 id="golden-rules">Golden rules</h2>
 <ol>
@@ -735,8 +735,10 @@ example <code>Item</code> and <code>Job</code> schemas.</p>
 <li>The server template ships authless by default (see
   <a href="../22_auth_integration/">22 – Auth Integration</a>); the client template pairs
   with it and degrades to "no login" until a security scheme is declared.</li>
-<li><code>react/vet</code> is the full-stack reference implementation: spec with x-
-  extensions, server, and the consuming client in one tree.</li>
+<li>The standards <strong>app + client templates</strong> are the full-stack reference: the
+  server spec carries the x- extensions, and the client renders the admin from
+  it. The wiki's <strong>Reference App</strong> walkthrough (<code>06_reference_app</code>) documents
+  the pairing end to end.</li>
 </ul>