[Bug] service install --chain generates a unit that runs sailor run --chain, which run does not accept

[walkonwayvs]

Summary

sailor service install --chain <id> writes a systemd unit whose ExecStart calls
sailor run --chain <id>. But run only accepts --chains (plural). The
generated service fails immediately on every start and never recovers.

OS

Pop!_OS (Linux 6.18.7-76061807-generic)

Node.js version

v20.20.0

Install method

npm (@sail.money/sailor)

Sailor version

2.2.1

Chain

Base (8453) — but the bug is chain-independent

Command run / code executed

sailor service install --chain 8453

Expected behavior

The generated systemd unit starts and the agent runs on the specified chain.

Actual behavior

The unit's ExecStart calls sailor run --chain 8453, but run only accepts
--chains (plural). The service fails on every start and never recovers.

The mismatch is visible in the two help outputs:

$ sailor service install --help
  --chain <id>      Chain ID to run on

$ sailor run --help
  --chains <ids>    Only run active-strategy steps on these chains
                    (comma-separated ids or slugs)

Additional context

Workaround: install with no chain flag. On a single-chain project the chain
resolves from the active strategy and the service runs correctly.

Suggested fix: emit --chains in the generated unit, or accept --chain as an
alias on run — the second also covers anyone who types the singular by hand.

[aadopii]

Confirmed and fixed. The installer was emitting the singular --chain while run only accepts --chains, so the generated unit failed on every start. The generator now emits --chains and the systemd unit test asserts the corrected ExecStart.

Merged to feature/harbor (e3f842a) and will land in the next release. Your workaround (install with no chain flag on a single-chain project) is exactly right in the interim.

Really appreciate the clean report, the two help outputs side by side made it unambiguous. Thank you.