The composer decides what a chat is, and the topbar stops trying

The mode select in the topbar posted with hx-post against a route that only
answers PATCH, so every change returned 405 and the mode never moved. htmx
shows nothing when a request fails, so the control looked like it worked: the
select stayed where you put it and the server ignored you. It has never worked.

Two more of the same kind. A mode could not be chosen at all until the chat
existed, so reaching Plan meant sending something in Manual first and letting
the model answer under the wrong rules. And the project directory box was real
and submitted, but unlabelled and squeezed to a few characters by the select
beside it, so it read as broken -- which is how it was reported.

So the kind, the connection, the directory and the mode move out of the strip
above the text and into one toolbar row beneath it, where attach and send
already are. The directory becomes a button that opens a browser over SFTP,
because a path is something you would rather find than spell. `scan_dir` is new
beside `list_dir`: a picker has to tell a directory from a file before it can
draw the row, and `list_dir` backs a tool whose contract is a list of names and
must not change under a model mid-conversation.

Browsing is a person clicking, not a model calling, so it does not pass through
policy.py -- the same argument the terminal panel rests on. It does mean Manual
mode has a second exception now.

Also: .chip was two components with one name, and the attachment card won, so
the Chat/Agent pills silently wore its padding. --radius-md was used twice and
declared nowhere, so both fell back to 0. .btn.is-active has been set by
syncToggles since the terminal landed and styled by nothing. Enter-to-send
ignored isComposing, so committing an IME candidate sent the message. The
terminal had five colours of a sixteen-colour palette, with fallbacks from a
palette that no longer exists.

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

src/lembas/web/static/css/tokens.css

@@ -47,6 +47,7 @@
   /* --- Radius & shadow -------------------------------------------------- */
   --radius-sm: 4px;
   --radius: 8px;
+  --radius-md: 10px;
   --radius-lg: 12px;
   --radius-xl: 18px;
   --radius-full: 999px;
@@ -70,11 +71,35 @@
      of --font-mono do not fit in 24rem, and a terminal narrower than eighty
      re-wraps everything a program prints. */
   --terminal-width: 34rem;
+  --terminal-width-min: 24rem;
   --thread-max-width: 48rem;
   --header-height: 3.5rem;
 
+  /* The terminal's own type. xterm holds this as a number rather than reading
+     it from CSS, so terminal.js parses it back out -- it must stay a plain
+     pixel value. */
+  --terminal-font-size: 13px;
+
+  /*
+    --- Stacking ----------------------------------------------------------
+    These were four bare numbers scattered across two stylesheets, which is
+    fine until something new has to sit between two of them and nobody can
+    say what is already there.
+  */
+  --z-raised: 5;
+  --z-handle: 10;
+  --z-dropdown: 30;
+  --z-panel: 40;
+  --z-overlay: 50;
+  --z-toast: 60;
+
   --transition-fast: 120ms ease;
   --transition: 200ms ease;
+
+  /* The focus treatment, written once. Three components spelled it out. It
+     resolves --accent-soft at the point of use, so it follows the theme even
+     though it is declared above them. */
+  --ring: 0 0 0 3px var(--accent-soft);
 }
 
 /*
@@ -144,6 +169,35 @@
   --shadow-lg: 0 12px 34px rgba(0, 0, 0, 0.55);
 
   --scrim: rgba(6, 8, 10, 0.66);
+
+  /*
+    The sixteen ANSI colours, for the terminal panel.
+
+    A shell picks its own colours -- `ls --color`, a git diff, htop's meters --
+    and until these existed it got xterm's defaults, which are a different
+    palette from this one and read as a foreign window pasted into the
+    application. Where a slot has an obvious counterpart above it takes it, so
+    an error in the terminal is the same ember as an error anywhere else.
+
+    "black" is not #000: it is what a program picks for a dim background or
+    faint text, and on a near-black surface a true black is invisible.
+  */
+  --ansi-black: #1A1F26;
+  --ansi-red: #E2795A;
+  --ansi-green: #9BCC5A;
+  --ansi-yellow: #DFAE58;
+  --ansi-blue: #8FB3CC;
+  --ansi-magenta: #C08FCC;
+  --ansi-cyan: #5FBFA0;
+  --ansi-white: #C6CDD4;
+  --ansi-bright-black: #4A535E;
+  --ansi-bright-red: #EC8E72;
+  --ansi-bright-green: #B1DD74;
+  --ansi-bright-yellow: #EFC87A;
+  --ansi-bright-blue: #A9C6DA;
+  --ansi-bright-magenta: #D4A9DE;
+  --ansi-bright-cyan: #7FD4BA;
+  --ansi-bright-white: #E4E8EC;
 }
 
 /*
@@ -203,6 +257,30 @@
   --shadow-lg: 0 12px 34px rgba(72, 58, 34, 0.16);
 
   --scrim: rgba(44, 36, 25, 0.4);
+
+  /*
+    The same sixteen on parchment, and the reason they are not the Moria set
+    lightened: every one of these has to be readable as *text* on #F2EBD9, so
+    the whole palette is darkened rather than brightened. "bright" therefore
+    means more emphatic here, not lighter -- a light terminal theme that made
+    bright yellow actually bright would render it invisible.
+  */
+  --ansi-black: #2C2419;
+  --ansi-red: #A6432B;
+  --ansi-green: #4C7A22;
+  --ansi-yellow: #98701A;
+  --ansi-blue: #3E6B7A;
+  --ansi-magenta: #7A3E6B;
+  --ansi-cyan: #2C7360;
+  --ansi-white: #6A5C48;
+  --ansi-bright-black: #94856D;
+  --ansi-bright-red: #8C3722;
+  --ansi-bright-green: #3C6318;
+  --ansi-bright-yellow: #7A5A14;
+  --ansi-bright-blue: #325867;
+  --ansi-bright-magenta: #63325A;
+  --ansi-bright-cyan: #235C4D;
+  --ansi-bright-white: #453A2A;
 }
 
 /* Respect a stated preference for reduced motion everywhere, at once. */