Update hapi runner command to use start-sync

[lekoOwO]

--foreground is ignored by hapi cli
Use start-sync instead.

[github-actions]

Findings

• [Minor] macOS launchd instructions still use the ignored foreground flag — this PR updates pm2/nohup/systemd to run the foreground runner process directly, but the same deployment section still tells launchd users to run hapi runner start --foreground; start detaches and the CLI implementation only treats start-sync as the runner process, so launchd can supervise the short-lived parent instead of the runner. Evidence: docs/guide/installation.md:540; related stale context: docs/guide/installation.md:473.
  Suggested fix:

  <array>
      <string>/usr/local/bin/hapi</string>
      <string>runner</string>
      <string>start-sync</string>
  </array>

Summary

• Review mode: initial
• One docs consistency issue found in the same background deployment section. The changed examples move to start-sync, but the launchd example remains stale.

Testing

• Not run (automation)

HAPI Bot

[github-actions]

Findings

• No issues found in the modified lines.

Summary

• Review mode: follow-up after new commits
• The follow-up change updates the remaining launchd runner example to hapi runner start-sync, matching the CLI behavior for supervised foreground runner processes. Residual risk: docs-only change; command examples were reviewed against current CLI source, but not executed under pm2/nohup/launchd/systemd.

Testing

• Not run (automation)

HAPI Bot