`entry.sh:10` and `entry.sh:16` write argument-validation errors to stdout instead of stderr

[edmoffo]

The argument-validation checks in entry.sh print their failure messages to stdout, not stderr.

At entry.sh:10:

echo "The first argument must be the ID of the job to process"
exit 1

and the same pattern repeats at entry.sh:16 for the missing-home check. Both branches exit 1 on the next line, but the diagnostic line is written to file descriptor 1.

A caller that runs entry.sh ... 2>/dev/null or pipes the script's stdout into another stage gets a silent failure: stderr stays empty, stdout carries a sentence the next stage interprets as data. The same script enables set -ex on entry.sh:5, which sends the shell trace to stderr by convention; mixing diagnostic output between the two streams forces every caller to special-case which fd carries which kind of message.

Fix: redirect both echo calls to stderr — echo "..." >&2 on entry.sh:10 and entry.sh:16.

[edmoffo]

@yegor256 happy to clarify the symptom or to send the two-character redirect in a follow-up pull request if the fix should be split off from this issue.