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]>

1 files changed, 22 insertions, 22 deletions

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: