Config opens the startup file, DumpConfig the settings report, and the workspace tag reads Dump Themes Config Debug Exit

Config (SPC f c) opens init, found as the settings report finds it
(opts.startup_config_path: $XDG_CONFIG_HOME/pardes/init or
~/.config/pardes/init, and the macOS and Windows paths config.md gives). A
pane that already holds it is gone to instead; a file on disk is looked at;
with none, an empty pane is named for it, and Save makes its directory and
any above it first (File.make_dirs, fs.makeDirs) before writing. Without a
configuration directory it says so and opens nothing.

The report Config used to open, the startup path and every live setting, is
DumpConfig, in a +DumpConfig pane. No alias keeps the old meaning.

The workspace tag's default words put Themes where NextColor was, NextColor
staying a builtin, and Config beside it. A tag the user edited is kept as it
was: a dump stores only an edited one (topbar_custom), and a restore puts
back only that.

theme.snap types NextColor onto the workspace tag to click it, and tagnav's
walk back to Dump takes five long-word steps. The rest of the re-recorded
goldens differ in the workspace words and their widths only.

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

1 files changed, 7 insertions, 4 deletions

diff --git a/docs/config.md b/docs/config.md
index f25c8746..bc4acf12 100644
--- a/docs/config.md
+++ b/docs/config.md
@@ -31,10 +31,13 @@ not stop later ones. Text that is no builtin is not run as a shell command
 (`Exec ...` still is). Key bindings are compile-time choices in
 `src/config.zig`; `init` does not remap them.
 
-`Config` (`SPC f c`) opens a `+Config` pane with the startup path (a right
-click opens it) and every live setting; a setting the frontend cannot show
-reads `unsupported`. The root `ctl` file reads the settings back in the
-words a write takes ([fs.md](fs.md#the-root-ctl)).
+`Config` (`SPC f c`) opens `init` itself in a pane, or goes to its pane when
+it is open. With no file there yet, the pane is named for it, empty, and
+Save writes it, making its directory first. `DumpConfig` opens a
+`+DumpConfig` pane with the startup path (a right click opens it) and every
+live setting; a setting the frontend cannot show reads `unsupported`. The
+root `ctl` file reads the settings back in the words a write takes
+([fs.md](fs.md#the-root-ctl)).
 
 ## Settings