§10 - one menu everywhere (buildPluginChrome) + shell on every page; instructional starter dashboard; Kratos-native email docs

Collapse the three nav builders into buildPluginChrome: chrome.bestHref does longest-prefix matching so deep admin routes mark their leaf. Delete adminNav; buildConfirmModel and the admin model builders take the resolved nav. The same role-filtered sidebar now renders signed in or out, collapsing to a burger on narrow screens.

shell.ejs gains menu (default true; menu:false -> single-column .app-bare), docTitle (separate <title> from the topbar, so the body keeps the single <h1>), and hideSignIn (suppress the footer Sign-in on auth pages to avoid a login loop). auth/home/landing now render inside the shell.

Dashboard is a replaceable instructional starter (definePlugin snippet, no mock data). Email stays delegated to Kratos: documented its built-in courier.template_override_path instead of adding web-side SMTP.

views/partials/landing-body.ejs

@@ -0,0 +1,13 @@
+<%#
+  Public landing body (§10): hero + intro + a prominent way in (or a dashboard link when signed in).
+  Rendered into the app-shell content. Locals: brand (name), signedIn (bool).
+%><div class="shell-auth">
+  <div class="landing">
+    <h1 class="landing-title">Operational web apps, without the boilerplate.</h1>
+    <p class="landing-lead"><%= brand %> is a self-hostable foundation for admin and operational UIs — sign-in, a config-driven menu, and a server-rendered, zero-JS design system. You add the domain-specific screens by dropping in plugin folders.</p>
+    <div class="landing-actions">
+      <% if (signedIn) { %><a class="btn btn-primary" href="/dashboard">Go to your dashboard</a>
+      <% } else { %><a class="btn btn-primary" href="/login">Log in</a><a class="btn" href="/registration">Create account</a><% } %>
+    </div>
+  </div>
+</div>