Release by level, and `prel usage` ends with the command list has been fixed.

See more details at : https://github.com/pdulvp/prel/issues/15

• prel release major|minor|micro works the number out of the version file

rather than being told it, and prel release current releases the version
the file already reads; patch is micro under its other name

• a pre-release suffix comes off whichever digit moves, so a micro off

1.2.3-rc1 is 1.2.3, the release the candidate was a candidate for

• prel release artifacts <level> resolves the same four words, so what a

release would upload can be asked for before the release is run

• nothing else about a release changes: the first line names the version the

word came out of, as release: 0.2.7 -> 0.2.8 (micro)

• the list of commands is repeated at the foot of prel usage, where two

hundred lines of help have scrolled past and a terminal leaves the reader

prel usage ends with the list of commands

_{2026-10-27-0905-prel-usage-command-list.md — 2026-10-27 09:05}

prel usage prints the help of every command in full - some two hundred
lines - under a heading that reads Available commands: and is then never
answered: by the time the text ends, the list of what there is has scrolled
past. The list belongs at the end, where a terminal leaves the reader.

Steps

• [x] prel.sh: _prel_command_lines, the one-line summary of each command,

lifted out of show_command_list so both renderers print the same list

• [x] show_all_usage: the header says the help is in full and the list is at

the end; the list goes after the last command's help, above
Global options:

• [x] show_command_list reads the list from the same helper, unchanged

output

• [x] checked: prel usage head and tail, prel and prel help byte for

byte as before, bash -n clean

• [x] docs/plans/sumup.md rewritten so one title covers this and the pbus

batch it is waiting with, plan marked complete and archived

prel release major|minor|micro works the number out itself

_{2026-10-30-2158-release-by-level.md — 2026-10-30 21:58}

prel release is told a version, and the version is worked out in the head
every time: the file reads 0.2.7, so the release is 0.2.8, unless it is the
one that moves the middle digit. A release knows which of the three it is
long before it knows the number, and the number is what it has to be typed.

So the three names go where the <x.y.z> goes. prel release micro reads the
version file, moves the last number on and releases that; major and minor
move theirs. Nothing else about a release changes - the same commit, tag,
build, push, publish, milestone and pbus event, at a version it worked out
rather than one it was given.

prel release current is the fourth of them: the version the file already
reads, released as it stands, for a file moved on by hand or by an earlier
step.

No new command: a version that is bumped and not released is a file edit, and
the bump is only ever the first half of this.

Steps

• [x] _rel_next_version <level> <version>: major/minor/micro, patch an

alias of micro; a pre-release suffix is dropped by the move, and micro
on 1.2.3-rc1 is 1.2.3, the suffix coming off being itself the move

• [x] _rel_resolve_version <token>: an <x.y.z> is itself, current is what

the version file reads, a level is that version moved on; the one place
both commands resolve what they were given

• [x] release(): the argument is a version or one of the four words,

refused early as a bad version is, resolved once the version file has
been read; the release: 0.2.7 -> 0.2.8 line already says what came out

• [x] prel release artifacts <level|current> resolves the same way, so what

a release would upload can be asked for before it is run

• [x] usage of both: the four words in the Usage block and a line in the

Description, prel release micro -n named as the way to see the number
before it is used

• [x] README: the release section's command list and a paragraph on the levels
• [x] checked: each level off a plain and a pre-release version, current,

an unknown word, a missing and an empty version file, -n end to end,
bash -n

• [x] docs/plans/sumup.md, plan marked complete and archived

_{Filed by prel from the completed plans at commit time.}