feat: add service startup hooks

[asturur]

Summary

Adds configurable startup ZapScript hooks:

• launchers.on_service_start, which runs after the service finishes platform post-start
• launchers.on_boot_start, which runs only once per detected OS boot

The boot-scoped hook persists the last observed boot ID in the Zaparoo data directory. Linux platforms use /proc/sys/kernel/random/boot_id; other platforms fall back to an uptime-derived boot time.

Impact

This gives users a native way to run ZapScript on service startup, including launch-at-boot workflows, without external startup scripts calling the HTTP /run/ endpoint.

Validation

• go test ./pkg/config ./pkg/service

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: ac887f89-c109-44f4-8453-a471de534c9b

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch track-boot-launch-boot

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[asturur]

i made this for discussion is a feature i was suggested

[wizzomafizzo]

I think it's a cool idea. My only nitpick would bet put it in the service config group instead of launchers