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/wiki/03_start_an_app/index.html

@@ -708,8 +708,7 @@ machine-facing checklist lives in the reference page
    <strong><code>start_app</code></strong> to intake-and-build in one call.</li>
 <li>The prompt hands off to <code>docs://modules/build_recipe</code>; the agent scaffolds
    with <code>get_app_template()</code> and pulls exact files with
-   <code>get_app_component(kind, resource=..., family=...)</code>, authoring only the
-   app-specific parts.</li>
+   <code>get_app_component(kind)</code>, authoring only the app-specific parts.</li>
 <li>To validate the standard without touching a real app, invoke <strong><code>trial</code></strong>
    (<code>trial(app_name=..., build_path=...)</code>) to build into a scratch directory,
    prove it builds, and report findings.</li>