big slow change: prebuilt shaders (SPIR-V/Metal), core gui reflow, docs, web + snapshot refresh

1 files changed, 56 insertions, 24 deletions

diff --git a/src/tutor.txt b/src/tutor.txt
index c2db239d..7c4c2733 100644
--- a/src/tutor.txt
+++ b/src/tutor.txt
@@ -89,10 +89,10 @@
                Once a gesture becomes a scroll it cannot also LOOK on
                release. The browser has no host filesystem or ptys:
                LOOK opens URLs or read-only Pardes .zig sources that
-               were Git-tracked and embedded when the web build was made.
+               were tracked or new/nonignored when the web build was made.
                The published launcher is a real Pardes terminal dump of
-               `git ls-files '*.zig'`: every listed path opens, and the
-               opened source uses tree-sitter syntax colors.
+               Git's tracked-plus-new/nonignored source list: every listed
+               path opens, and the opened source uses tree-sitter colors.
                A touch beginning on a tagline or pane separator instead
                latches a left-mouse gesture, so layout drags never scroll.
                Touch circles/trails and the click flash are the SDL
@@ -186,8 +186,8 @@
  wear the one you stopped on. The bar holds only what you reach for
  often — the rest of the builtins are words you execute and keys you
  press. Nearly every one has a KEY PATH under SPC (part 3.13): "Colors"
- (the syntax/ansi recolor) is SPC t c, "Crt" is SPC t r, and SPC ? lists
- the lot.
+ (the syntax/ansi recolor) is SPC t c, the native GUI scene effects are
+ SPC t r/R/g, panel transitions are SPC a s/z/d/a/v, and SPC ? lists the lot.
  Right-click a directory in any body to open a terminal there.
 
  SEARCH: `/` in normal mode types a pattern into that pane's own tag (it
@@ -213,7 +213,10 @@
  recent first, then the output buffers you have not, newest first, and
  only when there is neither does it step the pane in front of you — so
  n/N work on a shell that never had a search armed, and off the end
- they come round to the start. After the FIRST press `N` is `n`
+ they come round to the start. A Look from a result row may move focus
+ into the source file; the result pane remains the walk's owner, so the
+ next n/N returns there instead of starting from the file that opened.
+ After the FIRST press `N` is `n`
  backwards exactly; the first one is not a step but an arrival, since
  from a cursor the walk has never stood on there is nothing yet to step
  back from.
@@ -256,8 +259,9 @@
    - the scrollbar is the gutter below the box: left-click scrolls UP
      to that point, right-click scrolls DOWN
    - the FIRST document you open — a file, an image, a PDF, this tutor —
-     takes a new leftmost column of its own (nothing is displaced, the
-     other columns just narrow); every later one splits below a doc
+     takes a new leftmost column of its own, paid for only by the column
+     you opened it from; every unrelated column keeps its exact rectangle.
+     Every later document splits below a doc
      already open, so docs share that column
    - closing a window (Del, or its shell exiting) hands focus back to the
      window you were in before it, not to whichever one comes first
@@ -846,13 +850,13 @@ abc
 
  Nearly every builtin has a NAME you can execute anywhere text lives,
  and a KEY PATH you can press. SPC in body normal mode starts the
- path; the keys you have typed so far show at the right edge of the
- pane's tag until the sequence fires. Esc abandons it — so does any
+ path; the keys you have typed so far show on the active pane's
+ transient body/message row until it fires. Esc abandons it — so does any
  key that leads nowhere, rather than leaving the next keystroke armed.
 
  The groups are shared first letters and nothing cleverer: f files,
- h docs, c columns, t toggles, s session, j jumps, l language,
- w windows.
+ h docs, c columns, t toggles, a animations, s session, j jumps,
+ l language, w windows.
 
    SPC ?            Help: every builtin and the keys that run it
    SPC k            Kill (quit)          SPC d   Del (close this pane)
@@ -866,7 +870,11 @@ abc
 
    SPC t d          Debug        SPC t c  Colors (syntax/ansi recolor)
    SPC t n          NextColor    SPC t t  ThemeSel (the list of 228)
-   SPC t r          Crt          SPC t f  FontSel (gui and macOS only)
+   SPC t r/R/g      Crt / Ripple / Glitch (gui and macOS only)
+   SPC t f          FontSel (gui and macOS only)
+   SPC a s/z/d/a/v  PanelSlide / PanelZoom / PanelDissolve / PanelAscii /
+                    PanelVertical
+                    (native tty, SDL GUI, and macOS; press again to turn off)
    SPC t w          Wrap: soft line breaks in a file pane, ON to start
                     with — so this is the switch that lets a long line
                     run off the edge again, hscroll and all. A wrapped
@@ -972,7 +980,9 @@ abc
  render at all rather than as a stack of blank pages.
 
  An IMAGE — .png .jpg .jpeg .gif .bmp .ppm .pgm .tga — opens an image
- pane, tagged `img <path>`. Where the shell can place real pixels it
+ pane. Its tag reports `petscii:on/off`, `palette:commodore/terminal`,
+ and `ascii:on/off` before the path, so every pane-local choice is
+ visible even though only the builtins mutate it. Where the shell can place real pixels it
  does; where it cannot, the petscii matcher draws the picture out of
  block glyphs. The three toggles all act on THAT matcher, so with real
  pixels on screen only the first of them changes anything:
@@ -1061,24 +1071,46 @@ abc
  WHOLE, since a command line has no place inside it to pick out; Tab (or
  a middle click) runs the row you stopped on and puts that face on. So
  walking with n and pressing Tab is trying faces on, and stopping is
- choosing. `Font <name>` on its own takes the font file's
- stem.
+ choosing. `Font <name>` on its own takes the font file's stem.
+ `TaglineSize 70` changes the tagline face and visible band to 70 percent
+ of the body face, live; values 1 through 100 are accepted, `Config`
+ reports the active value, and both native GUI renderers retain the same
+ body cell grid while drawing that separate role.
+
+ Native panel transitions are the five SPC a choices listed in 3.13. They
+ start off. Only one is selected; running it again turns it off. Slide and
+ zoom animate geometry. Dissolve and ASCII animate only the old/new cell
+ diff, leaving unchanged content alone. Vertical raises only the pane being
+ added or deleted inside its own box, leaving every survivor still. The
+ native GUI scene switches Crt, Ripple
+ and Glitch may be combined. `EffectCode PanelAscii` (or any other
+ effect builtin as its argument) opens the exact backend sources that
+ were embedded when this binary was built.
 
  Before its first frame a native pardes reads ONE file: a file called
  `pardes` in your config directory — $XDG_CONFIG_HOME/pardes when that
  is set to an absolute path, else ~/.config/pardes, and on macOS
- ~/Library/Application Support/pardes. `SPC f c` prints the resolved
- path into a "+Config" buffer whether or not anything is there, which
- is the case you ask in. (A right click on that row opens the file when
- there IS one. When there is not, the click has nothing to open and
- falls back to searching for the text — pardes will not create it for
- you.)
+ ~/Library/Application Support/pardes. `SPC f c` opens a refreshable
+ "+Config" buffer containing the resolved path and every live setting:
+ theme, shell, requested/effective font, panel/scene effects, hover
+ delay, and the ordinary display toggles. The path is printed whether
+ or not anything is there, which is the case you ask in. (A right click
+ on that row opens the file when there IS one. When there is not, the
+ click has nothing to open and falls back to searching for the text —
+ pardes will not create it for you.)
+
+ Resting the pointer over look-able text for that reported delay paints
+ a quiet preview of the exact operand a right click would expand. It is
+ only a preview: it does not focus, select, move a cursor, or run Look.
+ Set `look_preview_delay_frames` to null in src/config.zig to compile it
+ out.
 
  The format is one BUILTIN COMMAND per line, spelled exactly the way
  you would execute it anywhere else:
 
    Theme gruvbox_dark_hard
    Shell zsh
+   TaglineSize 70
    Tagbottom
 
  Blank, unknown or malformed lines are ignored in silence, and a bad
@@ -1096,7 +1128,7 @@ abc
 
  The browser build reads no such file, has no ptys, and has no language
  backend compiled in. It is not without a filesystem, though: LOOK
- there resolves against a read-only archive of the tracked .zig sources
+ there resolves against a read-only archive of working-tree .zig sources
  that was generated when the build was made. What you get is a dump,
  replayed, with those sources openable. (The core still ASKS for the
  rest. A host that answers gets terminals; that is the seam, not a
@@ -1115,7 +1147,7 @@ abc
                 top bar = New Newcol Find Grep Help Tutor Dump ... Debug Kill
                           (keyboard: k off the topmost tagline)
  WEB TOUCH:     one-finger tap = LOOK; drag = natural scroll
-                LOOK opens URLs or embedded tracked .zig source (read-only)
+                LOOK opens URLs or embedded working-tree .zig source (read-only)
                 published TTY dump lists every source; tree-sitter colors it
                 tag/separator start = left drag; touch HUD requires Debug
  TTY:           a terminal IS a pane;  Ctrl-b (or Shift-Esc) toggles the shell,