Characters that killed a render, what may sit next to a klammer, and ref/

A character written in the ^...^ mnemonic form -- ^oe^, ^zz^, ^hello^ --
used to kill ktext outright: no message, no output, and an exit status
that looked like a crash because it was one.  Only the forms that happen
to spell hexadecimal digits escaped, and they were right by luck rather
than by reading.  Any caret form that names no character is now a located
error that quotes what was written.

A klammer may now sit inside square brackets and braces as it already
could inside parentheses, and may be followed by the punctuation that
ends a sentence: [@i word@], {@b word@}, @i word@'s.  The rule is a fixed
list of characters, because none of them can occur inside a klammer name
and so none of them is ambiguous next to a delimiter.  A letter still
cannot: "x@" is the named closing delimiter, so a letter before "@" has
two readings and no rule can separate them.

The abbreviations an author writes -- the hyphen form @i-word, a klammer
glued to its neighbouring punctuation -- are now recognised as author
conveniences only.  They are not applied to @@ definitions or @@@ system
commands, which are written by someone who needs no such shorthand and
whose forms are already whole.

Also fixed, each of them silent: an exported shell function in the
environment broke every @eval in the document; a line break written with
@nl was destroyed when it passed through a klammer that generates a
table, printing as \textbackslash{}newline in the finished PDF; and
"kdesc --coverage" shortened its file column by comparing the spelling of
a path rather than the path, so a klammer set reached by a symbolic link
showed a full path where its neighbours showed a short one.

New in the distribution: ref/, a small klammerset that describes the
Klammermachine's own tables in Klammertext.  It currently provides the
character tables -- the diacritics and the extended Latin letters -- as
klammers that render to any target, so the documentation of what can be
written cannot drift from what the machine accepts.  It is early, and
will grow.

The Klammertext taxonomy now has a section on targets, describes the
@@@klammerset system command alongside the other three, and states the
precedence of "^" -- what a caret means before a letter, a digit, a
punctuation character, and a quote, in one ordered list.

(from dev 6594c7ff8c1f)

tst/coverage_test.sh

@@ -281,6 +281,34 @@ else
     echo "${red}FAIL${reset} 22. an underivable klammer still renders — got [$out]"; FAIL=$((FAIL+1))
 fi
 
+echo
+echo "-- the file column survives a symlinked KLAMMERTEXT_HOME --"
+# The column is shortened by stripping the KLAMMERTEXT_HOME prefix, and that
+# was a plain string compare: the engine resolves a definition's file to its
+# PHYSICAL path while KLAMMERTEXT_HOME is whatever the user typed.  Where the
+# two spellings differ the prefix never matched and every row printed its
+# full path instead of the tail.
+#
+# macOS finds this on its own -- /tmp and /var are symlinks to /private/tmp
+# and /private/var, so the distribution leg (which builds under a temp dir)
+# failed five cases there on 2026-09-07 while the dev tree passed.  A symlink
+# reproduces it anywhere, which is what this does.
+link=$(mktemp -u)/kt_home_link
+mkdir -p "$(dirname "$link")"
+ln -s "$K" "$link"
+out=$(KLAMMERTEXT_HOME="$link" "$link/bin/kdesc" --klammersets none \
+        -i "$link/tst/coverage/basic.k" --coverage all 2>&1 \
+      | grep -E '^ +@ab ')
+rm -f "$link"
+case "$out" in
+    *" tst/coverage/basic.k"*)
+        echo "${green}PASS${reset} 58. a symlinked KLAMMERTEXT_HOME still shortens the path"
+        PASS=$((PASS+1));;
+    *)  echo "${red}FAIL${reset} 58. a symlinked KLAMMERTEXT_HOME still shortens the path"
+        echo "       got: [$out]"
+        FAIL=$((FAIL+1));;
+esac
+
 echo
 echo "====================="
 echo "Results: ${PASS} passed, ${FAIL} failed"