docs(xce-test-cli-ux): document jobsub -n's min,max task-range format

The hand-written per-flag description explaining -n's <min>[,<max>]
format was dropped when task 3.5 moved the flag list to the generated
flagspec block (which only shows short/long/required/default, with no
room for a flag's value-format semantics). Restore the explanation as
prose in USAGE_JOBSUB_HEAD, following the same pattern already used by
resupdate's HEAD (-n/-v pairing, -t's conditional meaning).

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019jaMf9QEwpugH2W9KAuc7f
This commit is contained in:
Rongsong Shen 2026-09-10 08:39:05 +00:00
parent f09fbdb342
commit a83d7087f2
No known key found for this signature in database
GPG key ID: 5BCDAAE0123E9FE2

View file

@ -607,9 +607,12 @@ static const char USAGE_JOBRUN_TAIL[] =
static const char USAGE_JOBSUB_HEAD[] =
"jobsub -u <user> -q <queue> -c <cmdline> [-R <resreq>]\n"
" [-n <min>[,<max>]] [-x <exdata>] [-a <arraysize>]\n"
" Submits a new job to the cluster under the given user and queue;\n"
" -x's exdata JSON, when given, overrides the command's built-in\n"
" PATH env instead of the default.\n";
" Submits a new job to the cluster under the given user and queue.\n"
" -n accepts either a single task count, or a comma-separated\n"
" <min>,<max> pair to request an elastic task count the scheduler\n"
" may dispatch anywhere in that range; -x's exdata JSON, when\n"
" given, overrides the command's built-in PATH env instead of the\n"
" default.\n";
static const char USAGE_JOBSUB_TAIL[] =
" On success, captures the submitted JobId into the $jobid\n"