Tab reaches the disk

Paths and programs, which is the half that makes it worth having. The first word
of a line is a command or a PROGRAM, offered under the name somebody would type
- the extension taken off - and anything after it is a file, offered as it
really is. A separator anywhere in the word says which directory to look in.

A directory answers with a separator on the end instead of a space, which says
what it is and lets the next part be typed straight away. The answer ending in
one is also what stops a space being added, so that is one test rather than a
flag.

PROGRAMS ARE LOOKED FOR WHERE THE SHELL WOULD LOOK to run one: where you are,
/Apps on the disk you are on, and /Apps on drive 0. Offering something the shell
would not find would be finishing a word into a thing that then does not work.
Drive 0's is skipped when that is already the drive, or every program in it
would be offered twice and nothing would ever be the only match.

Walking somebody else's directory means standing in it, which is the only way to
walk one here, so where the person was and which drive they were on are put down
first and restored whatever happens.

Three bugs, all found by running it:

THE DIRECTORY TEST WAS INVERTED. dir asks the same question the same way round
four hundred lines further up, which is what made it obvious once looked at.

THE /Apps WALK OVERWROTE THE TYPED PATH. The whole search runs a second time to
list the matches, and by then TabDir said "/Apps" - so a word that had named
nowhere went looking in the wrong place and listed nothing at all. Two ways into
the walk now, and the typed path is never written over.

AND LISTING ONLY KNEW ABOUT COMMANDS, because it was a second copy of the walk.
It is the same walk with a flag now: finding the answer and showing the matches
are the same question asked twice.

Also cosmosMonitor, which had been RE-BLESSED INTO MEANINGLESSNESS by the wall
move. It disassembles a loaded program, at an address the input names - and that
address moved a page while the recording was simply re-recorded to whatever came
out, which was a page of zeroes. It is pointed at 5000 again.

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

Tests/manifest

@@ -389,6 +389,17 @@ cosmosHistory        | CosmOS/Source/cosmos.asm           | run      | cosmosHis
 # The last line is the one that says it works on what is actually there rather than on what
 # was typed: two backspaces take "help" down to "he", and Tab finishes it again.
 cosmosTab            | CosmOS/Source/cosmos.asm           | run      | cosmosTab.in       | -     | disks/cosmos.img
+# And the half of it that reaches the disk. A program is offered under the name somebody
+# would type - the extension taken off - because that is what a first word can usefully be;
+# anywhere after the first word everything is offered as it really is. A directory answers
+# with a separator rather than a space, which says what it is and lets the next part be
+# typed straight away.
+#
+# A path in the word says where to look, and the shell looks in the three places it would
+# look to RUN something: where you are, /Apps on the disk you are on, and /Apps on drive 0.
+# Offering what the shell would not find would be finishing a word into something that then
+# does not work.
+cosmosTabPath        | CosmOS/Source/cosmos.asm           | run      | cosmosTabPath.in   | -     | disks/cosmos.img
 # The same editing offered to a PROGRAM, through osReadLine. Edit reads its lines that way,
 # so a word typed with two letters the wrong way round is put right without starting the line
 # again - which is the whole of what A4 buys.