Corrected logic for start template

[carsongee]

RATIONALE

Added start by default, and instead gated the loop on finding sub-component start tasks

---

Note

Low Risk
Low risk template change that only affects generated Taskfile output for the start task; behavior changes are limited to always exposing task start while conditionally running component :start subtasks when discovered.

Overview
Always generates the top-level start task in Taskfile.tmpl.yaml instead of omitting it when no component :start tasks are found.

The component {{ .StartComponents }} loop is now the only part gated by {{- if .HasStart }}, so task start consistently runs the base setup steps and only chains into component :start tasks when available.

^{Written by Cursor Bugbot for commit 8262e2b. This will update automatically on new commits. Configure here.}

[c-h-russell-walker]

👍

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

[github-actions]

🔐 Smoke tests approved by maintainer

⏳ Running security scans before executing smoke tests with secrets...

A maintainer has approved this fork PR to run smoke tests. Security scans will run first.

[github-actions]

✅ All smoke tests passed! (Fork PR)

✅ Security Scan: success
✅ Linux: success
✅ Windows: success

View run details