Theme snaps walk the new ring: acme, lapis, then Dark+ and Solarized

theme.snap and themesel.snap step past orchard_black into acme and lapis
(now with the current themes) and across the first ported sections; their
step names say where each lands, and only these two goldens are re-recorded.

1 files changed, 18 insertions, 16 deletions

diff --git a/test/snapshots/themesel.snap b/test/snapshots/themesel.snap
index 04a95d23..fa34f030 100644
--- a/test/snapshots/themesel.snap
+++ b/test/snapshots/themesel.snap
@@ -10,9 +10,10 @@
 # running it and stopping. There is still no preview state, nothing to confirm
 # and nothing to cancel: the row you ran is the theme you have.
 #
-# Both halves of the ring are in the buffer: the fifteen native themes come
-# first, then the retained helix, dark and acme, then everything exported from
-# the vendored helix .toml and zed .json files, sorted. The colors below are
+# The whole ring is in the buffer, in sections: the fifteen native themes,
+# acme and lapis, the faithful ports a family at a time, the legacy helix and
+# dark, then everything exported from the vendored helix .toml and zed .json
+# files, sorted. The colors below are
 # read with snapstyle, so this proves the generated themes are real data and
 # not just names in a list.
 lines t.txt 40
@@ -81,7 +82,8 @@ key tab
 stable 700 15000
 snap step-clay
 snapstyle step-clay
-# The three native contrast variants precede the legacy section. Its heading
+# The three native contrast variants precede acme and lapis, and then the first
+# ported family's section. Its heading
 # and blank separator are not stops in the n/N command walk.
 key n
 key tab
@@ -101,27 +103,27 @@ snapstyle step-orchard-black
 key n
 key tab
 stable 700 15000
-snap step-helix
-snapstyle step-helix
+snap step-acme
+snapstyle step-acme
 key n
 key tab
 stable 700 15000
-snap step-dark
-snapstyle step-dark
+snap step-lapis
+snapstyle step-lapis
 key n
 key tab
 stable 700 15000
-snap step-acme
-snapstyle step-acme
-# past the curated eighteen and into the generated half, which is sorted by name
-# — so the next command is whatever sorts first, not whatever was
-# vendored first. That is the point of sorting: the ring is the same everywhere
-# whatever order the directory read handed the files over in.
+snap step-dark-plus
+snapstyle step-dark-plus
+# across the Visual Studio Code section into Solarized: a section heading and
+# its blank line are skipped like the first. (The imported half, past the
+# legacy section, is sorted by name, so the ring is the same everywhere
+# whatever order the directory read handed the files over in.)
 key n
 key tab
 stable 700 15000
-snap step-generated
-snapstyle step-generated
+snap step-solarized-dark
+snapstyle step-solarized-dark
 # N walks back the same way — it is the exact inverse of n — and the Tab after
 # it runs the row it lands on, so the theme rewinds too
 key N