template: my-service-template + retrofit my-server / my-telegram-bot / my-dashboard

[lorenzoliuzzo]

Blocked by MyThingsLab/my-things-core#57 (declare the service archetype: a canonical service-harness.md in core).

Once that harness exists:

1. Create my-service-template scaffolded from my-template's bones (guard tests, CI, seams) but vendoring service-harness.md; its drift test pins against the service harness, not the tool one.
2. Retrofit the three repos currently wearing the wrong harness: my-server, my-telegram-bot, my-dashboard — swap the vendored harness, adjust each CLAUDE.md to the service seams, one PR per repo.
3. Deliberately no third template for casual apps (my-raytracer et al.) — nothing to enforce, keep them ungoverned.

Sequencing: after my-template#8/#9 (runtime skeleton + init script) merge, so the service template forks from the improved bones.