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)

doc/edit/emacs/README.md

@@ -76,7 +76,8 @@ The name ends at the first non-name character, so a target suffix like
 body (between `@@name` and the closing `@@`) is highlighted like ordinary
 Klammertext — e.g. an `@i … @` inside it shows as a normal application.
 
-**System/target commands** (`@@@`) — `@@@target`, `@@@argtype`, `@@@state` — get
+**System/target commands** (`@@@`) — `@@@target`, `@@@argtype`, `@@@state`,
+`@@@klammerset` — get
 a third pair of colors, so the three `@`-levels (application, definition, system)
 are visually distinct:
 

doc/edit/emacs/klammertext-mode.el

@@ -382,7 +382,8 @@ POS and POS+1 are both @.  BEFORE is the character before POS.  Mirrors
 (defun klammertext--emit-system (pos before)
   "Emit a @@@ system/target delimiter token at POS (groups 8 open / 9 close).
 POS, POS+1 and POS+2 are all @.  BEFORE is the character before POS.  These
-commands (@@@target, @@@argtype, @@@state) do not nest, so each delimiter is
+commands (@@@target, @@@argtype, @@@state, @@@klammerset) do not nest, so
+each delimiter is
 coloured independently, mirroring `klammertext--emit-def' with @@@ for @@."
   (let ((after (char-after (+ pos 3))))    ; char right after the @@@
     (cond

doc/klammertext_for_llm.md

@@ -47,7 +47,7 @@ target coverage is wrong — including inside branches this render will not take
 It applies nothing, so it is safe and fast. Use it before claiming a document is
 correct.
 
-**Inspect how text is being parsed:** `kdiag --type '<text>'` shows the tokens
+**Inspect how text is being parsed:** `kdiag --type '<text>'` shows the katoms
 ("katoms") and their types. This settles arguments about what a piece of syntax
 actually means.
 
@@ -57,7 +57,7 @@ actually means.
 
 | assumption | reality |
 |---|---|
-| It is a macro language like TeX | No catcodes. Token structure is fixed when a file is read and cannot be changed by anything later. This is why static checking works. |
+| It is a macro language like TeX | No catcodes. Katom structure — the indivisible input units, which `kdiag` displays — is fixed when a file is read and cannot be changed by anything later. This is why static checking works. |
 | `\command{arg}` | `@name arg @` — an `@` opens, and a **closing delimiter is required**. |
 | Arguments are `{a}{b}` | Positional arguments are separated by `|` — `@sup 2 \| 3 @`. |
 | Options are `[key=value]` | `:name value`, anywhere in the argument list — `@link URL :text Click @`. |
@@ -69,7 +69,7 @@ actually means.
 
 ---
 
-## 3. Lexical core
+## 3. Core syntax
 
 Three prefix tiers, distinguished by how many `@`:
 
@@ -110,7 +110,7 @@ klammer's name immediately before it: `@i text i@.
 **Abbreviated form.** `@name-arg1-arg2` is `@name arg1 | arg2 @`, valid only
 while every argument is letters and digits: `@i-italic`, `@sup-2-3`, `@date@`.
 
-**Literal klammers** take their content uninterpreted. It is not scanned for
+**Literal klammers** take their content uninterpreted. It is not examined for
 `@`, `|`, `#`, or `^`, so the machine cannot find the end by counting and **the
 named close is required**: