Administration is a section, not an overlay

the connection form — where fofos is, and the token — was reached through
`?config=1` and a link in the detail header, because it was not one of the nine
sections. it is now the tenth, called Administration, last in the nav.

that removes the overlay and the second route to it. the two could disagree: the
form covered whatever section was selected underneath, so the nav highlighted one
thing while the panel showed another, and an unconfigured plugin rendered the form
with no header at all — which reads as the selected section being broken rather
than as one setup step not done yet. unconfigured now goes to Administration and
the header says so.

`site` and `administration` are deliberately separate and the file says why. Site
settings is the CLIENT's — partners, social links, contact details, all of it
public copy. Administration is Officer's end: how this plugin reaches fofos, and
whatever else it will need to know. nothing in it ever appears on the site, and
the people who touch the two are not the same people.

`path: null`, alone among the sections: it reads nothing from fofos, which is why
it keeps working when fofos is unreachable and the others do not.

the header's settings link is replaced by the section's own hint, so the row still
says what it is once you are in it.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

web/sections.ts

@@ -1,13 +1,21 @@
 import type { LucideIcon } from 'lucide-react';
-import { Home, Info, Layers, Images, Handshake, Sparkles, Wrench, Settings, Mail } from 'lucide-react';
+import { Home, Info, Layers, Images, Handshake, Sparkles, Wrench, Settings, Mail, Cog } from 'lucide-react';
 
 /**
  * The sections of the fofos admin, in nav order.
  *
  * ── The order is the client's site, not the database's ──
  *
- * It follows the sitemap: the pages someone edits most, first. Site settings and Messages sit at the
- * bottom because they are not pages — one is configuration and the other is an inbox.
+ * It follows the sitemap: the pages someone edits most, first. Site settings, Messages and
+ * Administration sit at the bottom because they are not pages — the site's settings, an inbox, and the
+ * plugin's own machinery.
+ *
+ * ── `site` and `administration` are different things ──
+ *
+ * "Site settings" is the CLIENT's — partners, social links, contact details, all of it public copy that
+ * whoever edits the site edits. "Administration" is OFFICER's end: where fofos is, how to reach it, and
+ * whatever else this plugin needs to know to do its job. One is content, the other is plumbing, and the
+ * people who touch them are not the same people. Nothing in Administration ever appears on the site.
  *
  * ── `built` ──
  *
@@ -20,6 +28,7 @@ import { Home, Info, Layers, Images, Handshake, Sparkles, Wrench, Settings, Mail
  */
 
 export type SectionKey =
+  | 'administration'
   | 'messages'
   | 'site'
   | 'about'
@@ -114,6 +123,19 @@ export const SECTIONS: Section[] = [
     path: '/fofos-admin/messages',
     built: true,
   },
+  {
+    /*
+      Last, and `path: null` — it reads nothing from fofos. Every other section is a window onto the
+      client's site; this one is the window onto the connection itself, which is why it keeps working
+      when fofos is unreachable and the others do not.
+    */
+    key: 'administration',
+    label: 'Administration',
+    icon: Cog,
+    hint: 'Where fofos is, and the token to reach it',
+    path: null,
+    built: true,
+  },
 ];
 
 /** Where the detail panel goes when the URL says nothing, or says something it does not recognise. */