1 files changed, 0 insertions, 21 deletions
diff --git a/test/snapshots/nested.snap b/test/snapshots/nested.snap
index 0beeabf8..790b9b0c 100644
--- a/test/snapshots/nested.snap
+++ b/test/snapshots/nested.snap
@@ -1,34 +1,14 @@
-# a pardes launched INSIDE a pardes hands its argument to the outer one.
-#
-# No harness support is needed to get a genuinely nested launch: a pane
-# shell's parent IS the app under test, so `$(readlink /proc/$PPID/exe)` in a
-# pane is this exact binary, and running it from there makes a real
-# descendant — the same process tree a person typing `pardes foo.txt` in a
-# pane produces. Each arm gets its own `start` so the Look never has to be
-# aimed at a pane a previous arm moved.
-#
-# What discriminates is the GOLDEN GRID, not the `wait` below it: a nested
-# pardes that opened its own UI in the pane would show the same file, so the
-# content wait passes either way. The layout is what differs — an outer file
-# pane beside the shell versus a whole second topbar inside it — and the
-# `cursor=` on the first arm's header moves the moment that changes.
-#
-# Long waits on purpose: this forks and execs a whole second pardes.
 dirmk nestdir
 file nestdir/inside-nested.txt marker
 file nested.txt hello-from-nested\nsecond-nested-line\n
-# --- a FILE argument: a file pane appears in the OUTER instance ---
 start 30 100
 wait 8000 $
 stable 700 20000
 text $(readlink /proc/$PPID/exe) nested.txt
 key enter
-# the CONTENT, not the border: the shell only ever echoed the file's NAME
-# (see above for why the grid, not this line, is the real assertion)
 wait 15000 hello-from-nested
 stable 700 20000
 snap file-arg
-# --- no argument: the spicy message, in the pane, and no second UI ---
 start 30 100
 wait 8000 $
 stable 700 20000
@@ -37,7 +17,6 @@ key enter
 wait 15000 already inside pardes
 stable 700 20000
 snap no-arg
-# --- a DIRECTORY argument: a shell there, greeted with ls ---
 start 30 100
 wait 8000 $
 stable 700 20000