The tutor follows the guide's order, points at its sections, and no longer teaches $ as line end or the terminal tag's old words; a test checks the words, paths, chords and tags it names

Co-Authored-By: Claude Opus 5.5 <[email protected]>

3 files changed, 65 insertions, 65 deletions

diff --git a/test/snapshots/builtins.golden b/test/snapshots/builtins.golden
index 0f13ed7c..27b43a3a 100644
--- a/test/snapshots/builtins.golden
+++ b/test/snapshots/builtins.golden
@@ -34,48 +34,48 @@
 |19:      4
 |20:      5         The model is acme's: EVERYTHING is text, editable and executable
 |21:      6         the same way. Modal editing (helix-style) lives on top of that.
-|22:      7         Press j until you reach the introduction.
+|22:      7         Press j until you reach part 1.
 |23:      8
-|24:      9
-|25:     10 =================================================================
-|26:     11 =                      INTRODUCTION                              =
-|27:     12 =================================================================
-|28:     13
-|29:     14  A pane is just text on screen. There is no separate "buffer" type —
-|30:     15  what you see is what you edit. Some panes happen to be live terminals;
-|31:     16  most are text you move a cursor over. Modal editing is layered on top.
-|32:     17
-|33:     18  Three modes (the BOX at the pane's top-left corner shows which):
-|34:     19       NORMAL   block cursor, keys move and edit. The box is BLANK.
-|35:     20    ^  INSERT   keys type text at the cursor.
-|36:     21    $  TTY      keys go straight to the shell. (terminals only)
-|37:     22
-|38:     23  A bare `pardes` opens one shell already in TTY. Give it a file or a
-|39:     24  directory and you start in NORMAL.
-|40:     25
-|41:     26  SIX PARTS, ordered by what is most different from editors you know:
-|42:     27    1 — THE MOUSE.      Acme's three buttons; nothing like vim.
-|43:     28    2 — PANES.          Moving between them. Esc, Shift-Esc, Ctrl-w.
-|44:     29    3 — THE TTY.        Raw input, prompt-aware Esc, and the mode tag.
-|45:     30    4 — DETACHED.       The core outliving the terminal showing it.
-|46:     31    5 — THE KEYS.       Helix-style modal, and where it differs.
-|47:     32    6 — THE REST.       PDFs, images, the language backend, scripting.
+|24:      9  The lessons follow the guide (docs/typ/guide.typ, the "Guide"
+|25:     10  chapter of the pardes book), and each ends by naming its section.
+|26:     11
+|27:     12  Words written in backticks, like `Save`, are builtins: type one in
+|28:     13  any tag and middle-click it. Lines starting with "| " are tags as
+|29:     14  pardes draws them, words only.
+|30:     15
+|31:     16  PRACTICE BLOCKS (part 9): the "# keys:" line lists keystrokes
+|32:     17  (space-separated; esc/enter/bs are special, the rest type each char).
+|33:     18  The lines under "# before" are what you practise on; "# after" is
+|34:     19  what you should end up with. Nothing runs them. What pins the real
+|35:     20  behaviour is `zig build hxdiff`, which replays test/hxcases against
+|36:     21  goldens recorded from a real helix, and `zig build hxparity`, which
+|37:     22  runs each case in a file pane and in a shell and demands they agree.
+|38:     23
+|39:     24
+|40:     25 =================================================================
+|41:     26 =   PART 1 — MODES                                              =
+|42:     27 =================================================================
+|43:     28
+|44:     29  A pane is text on screen, a tag over a body. Some panes are live
+|45:     30  terminals; most are text you move a cursor over. Each pane has its
+|46:     31  own mode and keeps it while you are elsewhere. The BOX at the left
+|47:     32  of a pane's tag shows it:
 |48:     33
-|49:     34  PRACTICE BLOCKS (part 5): the "# keys:" line lists keystrokes
-|50:     35  (space-separated; esc/enter/bs are special, the rest type each char).
-|51:     36  The lines under "# before" are what you practice on; "# after" is what
-|52:     37  you should end up with. They are here to be TYPED and nothing runs
-|53:     38  them. What pins the real behaviour is `zig build hxdiff`, which replays
-|54:     39  test/hxcases against goldens recorded from a real helix, and
-|55:     40  `zig build hxparity`, which runs each case twice — once in a file pane,
-|56:     41  once in a shell — and demands the two agree.
+|49:     34       NORMAL   keys move and select. The box is BLANK.
+|50:     35    ^  INSERT   keys type text at the cursor.
+|51:     36    $  RAW      keys go straight to the program (terminals only).
+|52:     37
+|53:     38  Where each pane starts: a file or a PDF in NORMAL; a terminal from
+|54:     39  `Tty` in RAW, one from Alt-n in NORMAL; a command pane in RAW while
+|55:     40  its command runs. A bare `pardes` starts a shell in RAW with an
+|56:     41  empty text pane under it; `pardes FILE` starts on the file.
 |57:     42
-|58:     43  Hold j to reach part 1.
+|58:     43  Esc and Shift-Esc, by mode:
 |59:     44
-|60:     45
-|61:     46 =================================================================
-|62:     47 =   PART 1 — THE MOUSE (acme chording)                          =
-|63:     48 =================================================================
-|64:     49
-|65:     50  Three buttons, three verbs:
-|66:     51    LEFT    select, and focus the pane. Also pins the cursor.
+|60:     45    NORMAL   Esc       back to the previous pane (`Last`, SPC j j)
+|61:     46             Shift-Esc the same; in a terminal it switches to RAW
+|62:     47    INSERT   Esc       back to NORMAL
+|63:     48             Shift-Esc the same; in a terminal it switches to RAW
+|64:     49    RAW      Esc       goes to the program, except at an idle,
+|65:     50                       EMPTY shell prompt: back to the previous pane
+|66:     51             Shift-Esc always back to the previous pane
diff --git a/test/snapshots/leader.golden b/test/snapshots/leader.golden
index bde9f7bf..59f6930c 100644
--- a/test/snapshots/leader.golden
+++ b/test/snapshots/leader.golden
@@ -25,29 +25,29 @@
 |15:      4
 |16:      5         The model is acme's: EVERYTHING is text, editable and executable
 |17:      6         the same way. Modal editing (helix-style) lives on top of that.
-|18:      7         Press j until you reach the introduction.
+|18:      7         Press j until you reach part 1.
 |19:      8
-|20:      9
-|21:     10 =================================================================
-|22:     11 =                      INTRODUCTION                              =
-|23:     12 =================================================================
-|24:     13
-|25:     14  A pane is just text on screen. There is no separate "buffer" type —
-|26:     15  what you see is what you edit. Some panes happen to be live terminals;
-|27:     16  most are text you move a cursor over. Modal editing is layered on top.
-|28:     17
-|29:     18  Three modes (the BOX at the pane's top-left corner shows which):
-|30:     19       NORMAL   block cursor, keys move and edit. The box is BLANK.
-|31:     20    ^  INSERT   keys type text at the cursor.
-|32:     21    $  TTY      keys go straight to the shell. (terminals only)
-|33:     22
-|34:     23  A bare `pardes` opens one shell already in TTY. Give it a file or a
-|35:     24  directory and you start in NORMAL.
-|36:     25
-|37:     26  SIX PARTS, ordered by what is most different from editors you know:
-|38:     27    1 — THE MOUSE.      Acme's three buttons; nothing like vim.
-|39:     28    2 — PANES.          Moving between them. Esc, Shift-Esc, Ctrl-w.
-|40:     29    3 — THE TTY.        Raw input, prompt-aware Esc, and the mode tag.
+|20:      9  The lessons follow the guide (docs/typ/guide.typ, the "Guide"
+|21:     10  chapter of the pardes book), and each ends by naming its section.
+|22:     11
+|23:     12  Words written in backticks, like `Save`, are builtins: type one in
+|24:     13  any tag and middle-click it. Lines starting with "| " are tags as
+|25:     14  pardes draws them, words only.
+|26:     15
+|27:     16  PRACTICE BLOCKS (part 9): the "# keys:" line lists keystrokes
+|28:     17  (space-separated; esc/enter/bs are special, the rest type each char).
+|29:     18  The lines under "# before" are what you practise on; "# after" is
+|30:     19  what you should end up with. Nothing runs them. What pins the real
+|31:     20  behaviour is `zig build hxdiff`, which replays test/hxcases against
+|32:     21  goldens recorded from a real helix, and `zig build hxparity`, which
+|33:     22  runs each case in a file pane and in a shell and demands they agree.
+|34:     23
+|35:     24
+|36:     25 =================================================================
+|37:     26 =   PART 1 — MODES                                              =
+|38:     27 =================================================================
+|39:     28
+|40:     29  A pane is text on screen, a tag over a body. Some panes are live
 == snap deleted grid=100x41 cursor=7,3
 |5:
 |6:
diff --git a/test/snapshots/tutor.golden b/test/snapshots/tutor.golden
index 2976f99a..c78fe3d8 100644
--- a/test/snapshots/tutor.golden
+++ b/test/snapshots/tutor.golden
@@ -13,8 +13,8 @@
 |       table
 |     6         the same way. Modal editing (helix-style) lives on top of t↩
 |       hat.
-|     7         Press j until you reach the introduction.
+|     7         Press j until you reach part 1.
 |     8
-|     9
+|     9  The lessons follow the guide (docs/typ/guide.typ, the "Guide"
 |   /tmp/pardes-snap/tutor/cwd Tty+bash Save Mode Filter Collapse Del
 |  ls