Pages, with the pages under it in the nav

The section is real, and the nav draws the site's pages as rows beneath it. That is the one place this
admin has a hierarchy and it earns it: a page is a thing you go to, and the list of them is the site.

Drawn whether or not Pages is the open section — hiding the list until you click makes the nav a menu
of menus.

Three kinds of change, saved three different ways, and the split is deliberate. TEXT — a title, a menu
label, an address — is drafted and written by the one Save in the bar, because typing is something
people do halfway and change their minds about. ADDING, DELETING and REORDERING are immediate: each is
a single deliberate gesture with an obvious result, and holding them in a draft would put a list on
screen that does not exist yet, then leave Save to decide what order to apply three kinds of change in.

Only the rows that actually changed are sent, so a save touches what somebody edited and nothing else.
A failed save reloads from the server rather than leaving the typed values on screen, where they would
look saved.

Home's address and delete button are ABSENT, not disabled. A greyed control invites somebody to work
out why they cannot use it; there is nothing to work out, the front page is always `/`.

The two panels share the list through a channel rather than both fetching it. They are siblings and
neither can pass the other a prop, and two fetches means two lists that agree until somebody renames a
page. Selection stays in the URL — `?page=` — because that is addressable and the list is not.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

web/sections.ts

@@ -89,18 +89,18 @@ export const SECTIONS: Section[] = [
   },
   {
     /*
-      The pages, built rather than hard-coded. Not started.
+      The pages, built rather than hard-coded — what replaced the seven per-page sections.
 
-      This is what replaced the seven per-page sections that used to be here. Listed while unbuilt on
-      purpose: the nav says what is coming, which is a better answer than a nav that quietly lost seven
-      entries and offers no account of where they went.
+      The nav draws its rows UNDER this one, so the site's pages are visible without opening it. That is
+      the one place this admin has a hierarchy, and it earns it: a page is a thing you go to, and the
+      list of them is the site.
     */
     key: 'pages',
     label: 'Pages',
     icon: Files,
-    hint: 'Build a page from blocks, and choose where it sits',
-    path: null,
-    built: false,
+    hint: 'Every page: what it is called, and where it lives',
+    path: '/fofos-admin/pages',
+    built: true,
     requires: 'connection',
   },
   {