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/90_drone_pipelines/index.html

@@ -693,7 +693,7 @@ chosen by what the repository produces:</p>
 <td><strong>C — Docker deployment</strong></td>
 <td><code>templates/drone/service-docker.yaml</code></td>
 <td>An image pushed to the registry and run as a container</td>
-<td><code>auth-server</code>, <code>vet</code></td>
+<td><code>auth-server</code></td>
 </tr>
 </tbody>
 </table>