docs: rescan rebased documentation hierarchy

packages/ui/app-boot/src/index.ts

@@ -340,10 +340,10 @@ export async function watchPersonalPatches(
   try {
     return await register
   } catch (error) {
-    // A surface can dispose the whole tree while the watcher is still opening
-    // (a TUI `/exit` typed during startup): the HMR effect registration then
-    // fails with INACTIVE_EFFECT. That is the app exiting exactly as asked,
-    // not a watch failure — return a no-op disposer instead of crashing.
+    // A surface can dispose the whole tree while the watcher is still opening;
+    // the HMR effect registration then fails with INACTIVE_EFFECT. That is the
+    // app exiting exactly as asked, not a watch failure, so return a no-op
+    // disposer instead of crashing.
     if ((error as { code?: string } | null)?.code === 'INACTIVE_EFFECT') return async () => {}
     throw error
   }
@@ -625,11 +625,10 @@ export async function boot(
     stage = 'plugin tree failed to load'
     await mountRootInclude(ctx, absoluteConfigPath, patches)
     // A surface can finish and dispose the whole tree while startup is still
-    // in flight: the TUI renders as soon as its own fiber starts, so an `/exit`
-    // typed before the last entry settles tears the context down under us. The
-    // Loader service goes with it, and the activation audit describes a live
-    // tree — reading `ctx.loader` past this point would throw a TypeError over
-    // an app that exited exactly as asked. Transactional group updates settle
+    // in flight, before the last entry settles. The Loader service goes with
+    // it, and the activation audit describes a live tree — reading `ctx.loader`
+    // past this point would throw a TypeError over an app that exited exactly
+    // as asked. Transactional group updates settle
     // lifecycle inside the mount, so the teardown can land before it returns;
     // re-check after every await.
     await ctx.get('loader')?.await()

packages/ui/app-boot/tests/app-boot.spec.ts

@@ -435,11 +435,10 @@ describe('boot', () => {
   })
 
   it('returns instead of asserting over a tree a surface disposed mid-startup', async () => {
-    // What a TUI `/exit` does (ui-tui's disposeRootAndExit): dispose the root
-    // fiber, which lands while boot() is still awaiting the Loader whenever the
-    // surface renders before the last entry settles. The Loader service goes
-    // with the tree, so reading it for the post-boot assertions would crash an
-    // app that exited exactly as the user asked.
+    // A surface can dispose the root fiber while boot() is still awaiting the
+    // Loader, before the last entry settles. The Loader service goes with the
+    // tree, so reading it for the post-boot assertions would crash an app that
+    // exited exactly as the user asked.
     const dir = tmp()
     writeFileSync(join(dir, 'exiting.mjs'), [
       'export const name = "exiting"',

packages/ui/app-boot/tests/config-reload.spec.ts

@@ -344,9 +344,8 @@ describe('include patches layered over one base', () => {
     // The surface/`--config`/personal composition: `dsh` includes one shared
     // base and applies each source as its own patch list at the SAME include
     // level, because patches never cross an include boundary. A later layer
-    // must therefore be able to reach a row an earlier layer inserted —
-    // otherwise every surface-only row (the whole TUI front door) would be
-    // invisible to the user's `~/.dsh/config.yaml`.
+    // must therefore be able to reach a row an earlier layer inserted, or
+    // surface-only rows would be invisible to the user's personal config.
     const dir = mkdtempSync(join(tmpdir(), 'dsh-config-layered-'))
     writeFileSync(join(dir, 'noop.mjs'), NOOP_PLUGIN)
     writeFileSync(join(dir, 'base.yml'), '- id: shared\n  name: ./noop.mjs\n  config:\n    value: base\n')

packages/ui/app-boot/tests/personal-config.spec.ts

@@ -235,11 +235,11 @@ describe('boot with personal patches', () => {
   })
 
   it('returns a no-op disposer when the tree is disposed while the watcher opens', async () => {
-    // A TUI `/exit` typed during startup disposes the whole tree while
-    // registerConfig's effect registration is still in flight (the HMR effect
-    // then fails with INACTIVE_EFFECT); the app is exiting exactly as asked,
-    // so the watcher must not crash the process. The stub makes the race
-    // deterministic — the live-teardown ordering itself is not stageable.
+    // A surface can dispose the whole tree while registerConfig's effect
+    // registration is still in flight (the HMR effect then fails with
+    // INACTIVE_EFFECT); the app is exiting exactly as asked, so the watcher
+    // must not crash the process. The stub makes the race deterministic — the
+    // live-teardown ordering itself is not stageable.
     const dir = tmp()
     const ctx = await boot(NAME, writeTree(dir))
     try {