The shell takes spaces off both ends of a line, not just the front

Tab completion leaves a space after the word it finished, which is right
when another word is coming. When nothing else was coming, that space
stayed on the end of the line and a command taking a file name looked
for one whose name ended in a space:

  load greet.sbx      loaded, starting at 5000
  load greet.sbx      no such file      (the same line, finished with Tab)

Which took most of the good out of completion, since finishing a name
and pressing Return is the whole of what it is for. The existing tab
tests all typed more characters after completing, so none of them ever
submitted a completed line.

lineTrim already took the leading spaces off for indented blocks, so the
trailing ones come off in the same place, on the whole line, rather than
at each of the dozen commands that take a name. Walking back needs no
guard against running off the front: by then the first character cannot
be a space, and a line that was nothing but spaces has already become an
empty one.

CONSEQUENCE WORTH SEEING: echo no longer prints a trailing space it was
given, which is why cosmosTabPath's recording moved. That is the
conventional behaviour and it means what echo is handed is what somebody
would have typed, but it is a real change and not only a bug fix.

cosmosTrim covers a line completed and run straight away, the same
trailing space typed by hand, spaces at both ends at once, and a line of
nothing but spaces, which still has to do nothing rather than fail.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01E2JrLzFvuFX9fgi1LDRjrW

Programs/CosmOS/README.md

@@ -169,7 +169,10 @@ skipping happens before names are filled in, so `$whatever` inside a branch nobo
 is not a mistake, and a line nobody is running cannot fail.
 
 **Lines may be indented**, which they could not be before there was anything to indent
-inside. Leading spaces are taken off before anything looks at the line.
+inside. Spaces are taken off both ends of a line before anything looks at it - the leading
+ones so that a block can be indented, and the trailing ones because finishing a word with
+Tab leaves a space behind it, and a command that takes a file name would otherwise be
+looking for one whose name ends in a space.
 
 ## Names For Things: