/* What is left of the console's own stylesheet, and it draws almost nothing.

   **The console is drawn from `app.css`** — the shell, the sandbox strip, the left column, the status
   bar, the work area, the thread, the preview and every dialog are Tailwind utilities, the same ones
   the platform surface is drawn with. Two rules below are live — the pointer on a button, and the
   page's own two-column row — and the rest is held by a suite rather than worn by anything.

   It is inside one layer, and that is the whole reason it reads correctly beside `app.css`: an
   unlayered rule beats every layered one whatever the link order, so an element rule as ordinary as
   `button { font: inherit }` would undo the size and weight of every control the design system draws.
   `app.tailwind.css` names this layer before Tailwind's own, which puts it underneath them — so a
   utility wins, and what is here is what there is when no utility speaks. The contents are not
   indented into it: this is a wrapper with a life, not a nesting. */
@layer console {

/* Tailwind's own reset does not say this, and a button that does not answer the pointer reads as
   decoration. */
button { cursor: pointer }

/* The two columns — the left column and the work area. It is `.columns` and not `.body` because a
   dialog, a card and a gate each have a body too: a layout rule owning that word laid its two-column
   flex row over every one of their insides, which is what stood the sandbox dialog's three blocks
   side by side and squeezed the local-checkout commands off their own edge. The page says the same
   thing in utilities beside it now, and keeps this word because the word is what the rule is about. */
.columns { flex: 1; display: flex; min-height: 0 }

/* **Below here nothing is worn by anything.** `tools/ui/shell.docker.ts` reads this stylesheet for
   each of these and fails when one is gone, and that file belongs to neither of the two conversions
   — so whoever removes them removes the assertions in the same commit. Each is reduced to what that
   suite reads, because a fuller rule would be a colour scheme kept alive for a grep.

   What each said: a dialog's body stacks rather than relying on a default nothing states; a segmented
   control whose labels wrap has stopped being a control and become two paragraphs; the status bar
   names the container this page is attached to; and a tab can hold a name and a link and still be one
   tab, so the underline and the padding stay on the tab and what sits inside it carries none. All
   four are true of the page today — they are said in utilities, at the element that wears them. */
.dialog .body { display: block }
.modes button { flex: 1 1 auto; white-space: nowrap }
.status-bar .attached { display: flex; align-items: center; white-space: nowrap }
.tab .open { display: grid; place-items: center }
.tab > button { display: flex; align-items: center; border: 0; background: none; font: inherit; color: inherit }

}