update docs

users-manual/03-running-seeder-and-booter.md

@@ -11,6 +11,8 @@
 - [Run with Pear (recommended for realistic behavior)](#run-with-pear-recommended-for-realistic-behavior)
 - [Pear channels and released keys](#pear-channels-and-released-keys)
 - [Common mistakes](#common-mistakes)
+- [Boot sequence in plain language](#boot-sequence-in-plain-language)
+- [Choosing Node versus Pear](#choosing-node-versus-pear)
 
 ---
 
@@ -78,4 +80,16 @@ Concrete channel names, keys, versioned links, and host-side environment variabl
 
 ---
 
+## Boot sequence in plain language
+
+Once the booter has replicated enough of the **system** drive, it mounts the **personal** drive (creating one if needed), wires the merged VFS, and executes **`/boot/init.js`**. The stock kernel prints **`/etc/os-release`**, optional **`motd`**, runs **`/etc/bare-os/rc`** and sorted snippets under **`rc.d`**, then enters the interactive shell unless **`BARE_OS_SKIP_REPL`** or **`onboot`** lines consume the session. You do not need to memorize every phase to operate the system; when something fails **during** boot, enable **`BARE_OS_BOOT_TRACE`** (see [environment appendix](../docs/reference/environment-and-posix-appendix.md)) and read the phase lines on stderr.
+
+---
+
+## Choosing Node versus Pear
+
+**Node** (`node index.js` in each package) is ideal when you are debugging protocol or seeding logic quickly and want stack traces identical to your host toolchain. **Pear** tracks production embedding more closely: module layout, **`pear run --dev`**, and host **`BARE_OS_PEAR_*`** toggles matter. If a bug appears **only** under Pear, compare with a Node run using the same Corestore paths to isolate runtime differences. [PEAR-RUN.md](../PEAR-RUN.md) is the channel and environment reference for Pear-specific settings.
+
+---
+
 _Previous: [Chapter 2](02-install-and-repository-layout.md)_ · _Next: [Chapter 4 — Shell, PATH, and scripts](04-shell-path-and-scripts.md)_