Running an action via svc start doesn't update runners environment variables - causing failures on jobs

How to reproduce:

method 1:

1. install and run self-hosted runner on a mac build machine (i.e. ./svc.sh install and ./svc.sh start`)
2. Add some new items to your $PATH variable
3. restart your runner so changes take effect with ./svc.sh stop and ./svc.sh start
4. Run your job that requires the new PATH dependencies

Expected behaviour:
New variables added to path can now be accessed via the Action

Actual behaviour:
You'll get the same error as the path was not updated for some reason. But if you activate the runner via run.sh then the changes will take effect.

I've worked around this by manually editing the .paths file in actions-runner. But I recently tried the same with my homebrew installation and it isn't working even after updating the path. Is there a saved version of the .zshrc file within the actions-runner folder or something?

Start with the macOS service path using svc.sh install, svc.sh start, and svc.sh stop, then compare it with run.sh. Review how the runner uses the .paths file and whether .zshrc is involved. Done means newly added PATH entries are available to jobs after restarting the service, as they are when using run.sh.