Notices become tagline bands at the top of the body

A message, a leader chord and a prompt used to share one row of body text at
the bottom of a pane, wearing the tagline font and nothing else about a
tagline. Now each one is a TagLayer of its own, emitted through the same
renderHeaderLayer the pane and column tags go through, so it gets the tagline
height, the small-font metrics, the band offset and the border for free --
none of which a body-grid row can have by changing its font role. The text is
right aligned. The prompt stays on the canonical grid because it owns a
cursor, and a cursor has to sit on a real cell.

The body starts BELOW the bands rather than under them, the way tree-sitter
context rows already worked. Pane.body_offset is how many rows they took and
Pardes.bodyTop(pane, rect) is the one place that answers "where does the body
begin" -- replacing fifteen copies of `if (tag_bottom) r.y else r.y + BOX_H`
spread across the paint, hit-test, scroll, PDF and image paths, which is what
let the bands and the text under them come adrift. Every notice is painted on
the grid as well, because the grid is what a terminal client draws and a band
it cannot see is a message it never gets; the GUI skips grid cells a tag layer
covers, so nothing is drawn twice.

Three bugs the bands exposed, fixed here:
  - a prompt band flush with the right edge put its caret one column past the
    pane, which the detached wire refuses -- so every frame was dropped for as
    long as the prompt was open. The band now reserves that column.
  - a click on a band mapped to Sel row 0, which is the TAG row: clicking
    chrome expanded a word out of the tagline and ran it as a builtin.
  - a watched file reloading under the editor changed the core without going
    through update, so needs_frame was never set and the reload was never
    drawn. Pardes.invalidate() is the name for that, and the file and theme
    reloads call it.

A session can now drive its own 9P namespace instead of being refused one:
ownMountSuffix answers what a path names inside this editors own tree and
resolve, readLimit and write serve it from memory rather than making the
syscall that never returns. The match is anchored to whole components under
the registrys 9p/pardes/<name>, because a bare /pardes/<name> anywhere in a
string would claim ~/src/pardes/<name>/README -- and, before write learned the
same trick, write the trees bytes over the real file. readFileLimit and
writeFile refuse instead, having no core to answer from.

A toggle setting SETS when given `on` or `off` and only flips when it is bare,
so the report LocationsConfig prints can be fed back as configuration and mean
what it says.

Snapshots: 97/98, from 0/98. The goldens were several commits stale and 17
scripts had stopped running; `config <line>` is a new script command that
appends to the per-script startup config, so a script that clicks body
coordinates pins `Verbose off` instead of counting the rows an announcement
moves. nested-optout is left failing on purpose: two levels of nesting prepend
vaxis F3 codepoints to typed lines, which is a real bug and is written down in
docs/divergences.md with a repro.

Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>

1 files changed, 31 insertions, 7 deletions

diff --git a/docs/divergences.md b/docs/divergences.md
index fada830c..6679d962 100644
--- a/docs/divergences.md
+++ b/docs/divergences.md
@@ -43,17 +43,41 @@ there, deliberately, because that box serves a public site.
 
 ## Known-failing on `main`, not caused by the 9P work
 
-* **`zig build fs-test`** fails on a syntax-highlighting assertion — the
-  word `fn` is expected bold and comes back unstyled:
+* **`zig build snap` fails `nested-optout`, and the cause is a real bug.**
+  At the SECOND level of nesting -- a pardes whose shell runs a pardes whose
+  shell runs a command -- two U+E016 codepoints are prepended to whatever is
+  typed. U+E016 is 57366, which is vaxis's private-use spelling of **F3**
+  (`Key.zig`, "kitty encodes these keys directly in the private use area"), so
+  something in the chain is decoding a capability-query REPLY as a key and
+  forwarding it to the shell as text. bash then sees
+  `$'\356\200\226\356\200\226echo'` and answers `command not found`; with a
+  path it answers `No such file or directory` for a path that exists and runs
+  perfectly from the same shell a moment later.
+
+  Minimal repro, in a snapshot script:
 
   ```
-  AssertionError: ('fn', [{'fg': {'rgb': [201, 176, 228]}, ..., 'bold': False}, ...])
+  dirmk innerdir
+  file innerdir/deeper.txt deepest-marker\n
+  start 31 100
+  wait 8000 $
+  stable 700 20000
+  text (cd innerdir && $(readlink /proc/$PPID/exe) --nested)
+  key enter
+  wait 20000 cwd/innerdir
+  stable 700 20000
+  text E=$(readlink /proc/$PPID/exe); "$E" deeper.txt
+  key enter
+  settle 5000
+  stable 700 10000
+  snap probe
   ```
 
-  Verified by restoring `main`'s own `src/9p_io.zig`, `build.zig` and
-  `build.zig.zon` and re-running: it fails identically. The editor line
-  (`rruwvuzm`) has substantial `src/syntax.zig` changes and may well be the
-  fix in progress.
+  `bash: E=/home/.../pardes: No such file or directory` -- bash did not even
+  parse the assignment, because the line does not start where it looks like it
+  starts. `--nested` is exactly the flag meant to opt a child out of this, so
+  the fix belongs next to the key-forwarding path in `panes.Terminal.forwardKey`
+  and whatever answers terminal capability queries on a nested stdin.
 
 * **pardes does not start headless.** `pardes --9p=<name>` with no terminal
   exits 1 from the argument-forwarding path; the installed build fails