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/src/lib/40_ui_admin.md

@@ -57,7 +57,7 @@ docs://modules/react-openapi        # module: specExtensions — the full catalo
 
 The app's own spec carries the per-resource values; the catalog explains what
 each field does. The template's `openapi.yaml` shows the convention on the
-example `Item` and `Job` schemas.
+example `Job` schema.
 
 ---
 
@@ -82,5 +82,7 @@ example `Item` and `Job` schemas.
 - The server template ships authless by default (see
   [22 – Auth Integration](22_auth_integration.md)); the client template pairs
   with it and degrades to "no login" until a security scheme is declared.
-- `react/vet` is the full-stack reference implementation: spec with x-
-  extensions, server, and the consuming client in one tree.
+- The standards **app + client templates** are the full-stack reference: the
+  server spec carries the x- extensions, and the client renders the admin from
+  it. The wiki's **Reference App** walkthrough (`06_reference_app`) documents
+  the pairing end to end.