@azure-id/orc 0.55.0

package/bin/webui/css/03-components.css

@@ -0,0 +1,462 @@
+/* 03-components.css — orc ui
+   Shared furniture: page-head, stack, card, grid, stat tile, kv list, chip,
+   button, scroll-x, pre, table, note, empty, banner, changelog entry,
+   skeleton, toast, modal, the busy veil, kbd.
+
+   The <link> ORDER in app.html is the cascade order, and the numeric
+   prefix is that order. No @import: it would carry no session token and
+   401. */
+
+
+/* ------------------------------------------------------------ COMPONENTS -- */
+
+.page-head {
+  display: flex;
+  align-items: flex-end;
+  justify-content: space-between;
+  gap: var(--sp-4);
+  flex-wrap: wrap;
+  margin-bottom: var(--sp-5);
+}
+.page-head h1 { font-size: 20px; font-weight: 600; letter-spacing: -.01em; }
+.page-sub { color: var(--text-dim); font-size: 13px; margin-top: 2px; }
+
+/* SPACING IS OWNED BY THE CONTAINER, never by adjacent-sibling pairs.
+   The original model spaced `.card + .card` — which only ever matched two cards
+   in a row. A `.grid` of stat tiles followed by a card, a `.tier` followed by a
+   card, a `.run-list` followed by a card: all of those are the COMMON sequences
+   in these panels, none of them matched, and every one of them collided. A rule
+   that has to be re-stated for each new pair of block types is a rule that will
+   be forgotten the next time a panel gains a block type.
+
+   `.stack` is that container. Every panel body and async slot carries it, so
+   spacing holds for any mix of children, in any order, forever. Because the gap
+   belongs to the parent, NO block type may carry its own outer margin — that is
+   what would double up. */
+.stack { display: flex; flex-direction: column; gap: var(--sp-4); min-width: 0; }
+.stack-sm { gap: var(--sp-3); }
+/* A flex column child will not shrink below its content without this, which is
+   how a wide table or a long path escapes its card. */
+.stack > * { min-width: 0; }
+
+.card {
+  background: var(--surface);
+  border: 1px solid var(--line);
+  border-radius: var(--radius);
+  padding: var(--sp-4) var(--sp-5);
+}
+/* Card internals get the same treatment: a card holds a head, then any mix of
+   notes, tables, lists and action rows, and those collided too. */
+.card > * + * { margin-top: var(--sp-3); }
+.card-head {
+  display: flex;
+  align-items: center;
+  justify-content: space-between;
+  gap: var(--sp-3);
+}
+.card-head h2 { font-size: 13px; font-weight: 600; text-transform: uppercase; letter-spacing: .07em; color: var(--text-dim); }
+
+.grid { display: grid; gap: var(--sp-4); }
+.grid-2 { grid-template-columns: repeat(auto-fit, minmax(280px, 1fr)); }
+.grid-3 { grid-template-columns: repeat(auto-fit, minmax(200px, 1fr)); }
+
+.stat { background: var(--surface); border: 1px solid var(--line); border-radius: var(--radius); padding: var(--sp-4); }
+.stat-label { font-size: 11px; text-transform: uppercase; letter-spacing: .07em; color: var(--text-faint); }
+.stat-value { font-size: 26px; font-weight: 600; line-height: 1.2; margin-top: 4px; letter-spacing: -.02em; }
+.stat-value .chip { vertical-align: middle; margin-left: var(--sp-2); }
+.stat-note { font-size: 10px; color: var(--text-dim); margin-top: 2px; }
+.stat-ok   { color: var(--ok); }
+.stat-warn { color: var(--warn); }
+.stat-bad  { color: var(--bad); }
+/* The version tile answers over the network, so it has a waiting state. It
+   dims rather than moves: a tile that reflows when the answer lands shifts the
+   three tiles beside it. */
+.stat-pending .stat-value { color: var(--text-faint); font-size: 18px; }
+.stat-pending { animation: breathe 1.6s ease-in-out infinite; }
+@keyframes breathe {
+  0%, 100% { opacity: 1; }
+  50%      { opacity: .62; }
+}
+
+/* A tile that LEADS somewhere says so by moving; a tile that leads nowhere is a
+   plain div and never reacts. `text-align: left` because it is a <button> now
+   and would otherwise centre its own text. */
+.stat-link {
+  text-align: left;
+  width: 100%;
+  font: inherit;
+  cursor: pointer;
+  position: relative;
+  transition: border-color var(--dur-fast) var(--ease), transform var(--dur-fast) var(--ease),
+              background var(--dur-fast) var(--ease);
+}
+.stat-link::after {
+  content: "→";
+  position: absolute;
+  top: var(--sp-3);
+  right: var(--sp-3);
+  color: var(--text-faint);
+  opacity: 0;
+  transform: translateX(-4px);
+  transition: opacity var(--dur-fast) var(--ease), transform var(--dur-fast) var(--ease);
+}
+.stat-link:hover { border-color: var(--accent-dim); background: var(--surface-2); transform: translateY(-2px); }
+.stat-link:hover::after { opacity: 1; transform: none; }
+
+.kv { display: grid; grid-template-columns: minmax(120px, max-content) minmax(0, 1fr); gap: 6px var(--sp-4); }
+.kv dt { color: var(--text-faint); font-size: 12px; }
+.kv dd { margin: 0; font-family: var(--mono); font-size: 12px; word-break: break-all; }
+/* A copy button that is always visible turns a value list into a row of
+   buttons, so it fades in with the row it belongs to. It stays reachable by
+   keyboard regardless — :focus-within, not hover alone. */
+.kv-copy { display: flex; align-items: baseline; gap: var(--sp-2); }
+.copy-btn {
+  border: 1px solid var(--line);
+  background: var(--surface-2);
+  color: var(--text-dim);
+  border-radius: 4px;
+  padding: 0 6px;
+  font-size: 10px;
+  font-family: var(--font);
+  cursor: pointer;
+  opacity: 0;
+  flex: none;
+  transition: opacity var(--dur-fast) var(--ease), color var(--dur-fast) var(--ease),
+              border-color var(--dur-fast) var(--ease);
+}
+.kv-copy:hover .copy-btn, .copy-btn:focus-visible { opacity: 1; }
+.copy-btn:hover { color: var(--accent); border-color: var(--accent-dim); }
+
+.chip {
+  display: inline-flex;
+  align-items: center;
+  gap: 6px;
+  padding: 2px 9px;
+  border-radius: 100px;
+  font-size: 11px;
+  font-weight: 600;
+  letter-spacing: .04em;
+  text-transform: uppercase;
+  background: var(--idle-wash);
+  color: var(--text-dim);
+  border: 1px solid transparent;
+}
+.chip-ok   { background: var(--ok-wash);   color: var(--ok); }
+.chip-warn { background: var(--warn-wash); color: var(--warn); }
+.chip-bad  { background: var(--bad-wash);  color: var(--bad); }
+.chip-info { background: var(--accent-wash); color: var(--accent); }
+
+/* STALE gets a slow pulse; FRESH is static. Motion here is information. */
+.chip-bad.chip-pulse { animation: pulse 2.4s ease-in-out infinite; }
+@keyframes pulse {
+  0%, 100% { box-shadow: 0 0 0 0 var(--bad-wash); }
+  50%      { box-shadow: 0 0 0 5px transparent; }
+}
+
+.btn {
+  display: inline-flex;
+  align-items: center;
+  gap: 6px;
+  padding: 6px 13px;
+  border: 1px solid var(--line);
+  border-radius: var(--radius-sm);
+  background: var(--surface-2);
+  color: var(--text);
+  cursor: pointer;
+  transition: background var(--dur-fast) var(--ease), border-color var(--dur-fast) var(--ease), opacity var(--dur-fast);
+}
+.btn:hover:not(:disabled) { background: var(--surface-3); border-color: var(--accent-dim); }
+/* A press that moves confirms the click landed — the one bit of feedback that
+   is never wrong, even when the request behind it is slow. */
+.btn:active:not(:disabled) { transform: translateY(1px); }
+.btn:disabled { opacity: .45; cursor: not-allowed; }
+.btn-sm { padding: 3px 9px; font-size: 12px; }
+.btn-primary { background: var(--accent); border-color: var(--accent); color: #fff; }
+.btn-primary:hover:not(:disabled) { background: var(--accent-dim); border-color: var(--accent-dim); }
+.btn-danger { background: var(--bad-wash); border-color: var(--bad); color: var(--bad); }
+.btn-danger:hover:not(:disabled) { background: var(--bad); color: #fff; }
+.btn-ghost { background: transparent; }
+
+.row-actions { display: flex; gap: var(--sp-2); flex-wrap: wrap; }
+
+/* Wide content scrolls in its OWN container — the page body never scrolls
+   horizontally.
+
+   THE SCROLLBAR IS PART OF THE PICTURE (v0.44.0). The default platform bar is
+   an opaque grey slab with its own track colour, and under the flow stepper it
+   cut a hard band across the bottom of the rail — the loudest thing on a card
+   whose whole job is to be read as a diagram. So: no track at all (the card's
+   own background shows through), a thin rounded thumb in the panel's line
+   colour, and full contrast only on hover. It is quiet until you reach for it.
+
+   Both syntaxes are given because they are not interchangeable: Firefox reads
+   `scrollbar-width`/`scrollbar-color`, WebKit and Chromium read the
+   pseudo-elements, and neither falls back to the other. */
+.scroll-x { overflow-x: auto; }
+
+.scroll-x, .file-list, .block, .modal, .run-detail, pre {
+  scrollbar-width: thin;
+  scrollbar-color: var(--line) transparent;
+}
+.scroll-x::-webkit-scrollbar,
+.file-list::-webkit-scrollbar,
+.block::-webkit-scrollbar,
+.modal::-webkit-scrollbar,
+pre::-webkit-scrollbar { height: 9px; width: 9px; }
+/* Transparent TRACK, transparent corner — the card behind it is the background,
+   so a scrolling box no longer announces itself with a grey gutter. */
+.scroll-x::-webkit-scrollbar-track,
+.file-list::-webkit-scrollbar-track,
+.block::-webkit-scrollbar-track,
+.modal::-webkit-scrollbar-track,
+pre::-webkit-scrollbar-track { background: transparent; }
+.scroll-x::-webkit-scrollbar-corner,
+.file-list::-webkit-scrollbar-corner,
+.block::-webkit-scrollbar-corner,
+.modal::-webkit-scrollbar-corner,
+pre::-webkit-scrollbar-corner { background: transparent; }
+.scroll-x::-webkit-scrollbar-thumb,
+.file-list::-webkit-scrollbar-thumb,
+.block::-webkit-scrollbar-thumb,
+.modal::-webkit-scrollbar-thumb,
+pre::-webkit-scrollbar-thumb {
+  background: var(--line);
+  border-radius: 999px;
+  /* A transparent border with `background-clip: content-box` is what keeps the
+     thumb visually THINNER than the track it needs for a comfortable hit area. */
+  border: 2px solid transparent;
+  background-clip: content-box;
+  transition: background var(--dur-fast) var(--ease);
+}
+.scroll-x:hover::-webkit-scrollbar-thumb,
+.file-list:hover::-webkit-scrollbar-thumb,
+.block:hover::-webkit-scrollbar-thumb,
+.modal:hover::-webkit-scrollbar-thumb,
+pre:hover::-webkit-scrollbar-thumb { background: var(--accent-dim); background-clip: content-box; }
+.scroll-x::-webkit-scrollbar-thumb:active,
+.file-list::-webkit-scrollbar-thumb:active,
+.block::-webkit-scrollbar-thumb:active,
+.modal::-webkit-scrollbar-thumb:active,
+pre::-webkit-scrollbar-thumb:active { background: var(--accent); background-clip: content-box; }
+
+table { border-collapse: collapse; width: 100%; font-size: 13px; }
+th, td { text-align: left; padding: 7px var(--sp-3); border-bottom: 1px solid var(--line-soft); vertical-align: top; }
+th { font-size: 11px; text-transform: uppercase; letter-spacing: .06em; color: var(--text-faint); font-weight: 600; }
+tbody tr:last-child td { border-bottom: 0; }
+tbody tr:hover { background: var(--surface-2); }
+
+pre.block {
+  background: var(--surface-2);
+  border: 1px solid var(--line-soft);
+  border-radius: var(--radius-sm);
+  padding: var(--sp-3);
+  overflow-x: auto;
+  font-size: 12px;
+  line-height: 1.5;
+  white-space: pre;
+  color: var(--text-dim);
+}
+pre.block.wrap { white-space: pre-wrap; word-break: break-word; }
+
+.note { color: var(--text-dim); font-size: 12.5px; }
+.note + .note { margin-top: var(--sp-2); }
+/* `note bad` was written by six panels and styled by NONE of them (found at
+   v0.50.0): a malformed boundary card, a rejected house rule and an unpriced
+   band all rendered in the same grey as the sentence explaining them. The class
+   was always the intent; this is the rule that was missing. */
+.note.bad { color: var(--bad); }
+.note.warn { color: var(--warn); }
+.empty {
+  padding: var(--sp-6) var(--sp-4);
+  text-align: center;
+  color: var(--text-dim);
+  border: 1px dashed var(--line);
+  border-radius: var(--radius);
+}
+/* The reason a read failed, in the CLI's own output. Left-aligned inside a
+   centred box on purpose: it is a transcript, not a sentence. */
+.empty .fail-detail {
+  margin-top: var(--sp-3);
+  text-align: left;
+  max-height: 220px;
+  overflow: auto;
+  font-size: 12px;
+}
+
+.banner {
+  display: flex;
+  gap: var(--sp-3);
+  padding: var(--sp-3) var(--sp-4);
+  border-radius: var(--radius);
+  border: 1px solid var(--warn);
+  background: var(--warn-wash);
+  font-size: 13px;
+}
+.banner-bad { border-color: var(--bad); background: var(--bad-wash); }
+.banner strong { display: block; margin-bottom: 2px; }
+.banner-fix { display: flex; align-items: center; gap: var(--sp-2); margin-top: var(--sp-2); flex-wrap: wrap; }
+
+/* The update banner is a button: "what changed" is the useful question, and it
+   should not require leaving for GitHub to answer it. */
+.banner-update {
+  width: 100%;
+  align-items: center;
+  border-color: var(--accent);
+  background: var(--accent-wash);
+  color: inherit;
+  cursor: pointer;
+  text-align: left;
+  font: inherit;
+  transition: background var(--dur-fast) var(--ease), transform var(--dur-fast) var(--ease);
+  animation: banner-drop var(--dur-slow) var(--ease);
+}
+.banner-update:hover { background: var(--surface-3); transform: translateY(-1px); }
+.banner-update .note { color: var(--text-dim); }
+/* All three children on ONE vertical centre line (v0.44.1). The badge used to
+   be `align-self: flex-start` while the row was `align-items: center` and the
+   CTA sat on the centre — three items, three different alignments, in a row
+   that is 69px tall. Nothing about a "NEW" pill wants to be pinned to the top
+   of a two-line message. */
+.banner-badge {
+  flex: none;
+  background: var(--accent);
+  color: #fff;
+  border-radius: 100px;
+  padding: 1px 8px;
+  font-size: 10px;
+  font-weight: 700;
+  letter-spacing: .08em;
+}
+.banner-more { margin-left: auto; flex: none; color: var(--accent); font-size: 12px; white-space: nowrap; }
+@keyframes banner-drop {
+  from { opacity: 0; transform: translateY(-10px); }
+  to   { opacity: 1; transform: none; }
+}
+
+.cl-entry { border-left: 2px solid var(--line); padding-left: var(--sp-3); }
+.cl-head { display: flex; align-items: baseline; gap: var(--sp-2); flex-wrap: wrap; }
+.cl-version { font-family: var(--mono); font-size: 13px; color: var(--accent); font-weight: 600; }
+.cl-date { font-size: 11px; color: var(--text-faint); margin-left: auto; }
+.cl-title { font-size: 13px; font-weight: 600; margin-top: 2px; }
+/* `pre-wrap` is still right — the body carries real paragraph breaks — but the
+   text reaching it has been REFLOWED first (see `reflowMd`), so a paragraph is
+   one long line that wraps to this box instead of the README's 78-column
+   hard wraps ending raggedly in the middle of it. */
+.cl-body { font-size: 12.5px; color: var(--text-dim); white-space: pre-wrap; margin-top: var(--sp-2); line-height: 1.6; overflow-wrap: anywhere; }
+
+/* Loading is a skeleton shimmer, never a spinner. */
+.skeleton {
+  height: 12px;
+  border-radius: 4px;
+  background: linear-gradient(90deg, var(--surface-2) 25%, var(--surface-3) 37%, var(--surface-2) 63%);
+  background-size: 400% 100%;
+  animation: shimmer 1.3s ease-in-out infinite;
+}
+.skeleton.w-60 { width: 60%; }
+.skeleton.w-40 { width: 40%; }
+.skeleton.tall { height: 56px; }
+@keyframes shimmer {
+  from { background-position: 100% 0; }
+  to   { background-position: 0 0; }
+}
+
+.toasts {
+  position: fixed;
+  right: var(--sp-5);
+  bottom: var(--sp-5);
+  display: flex;
+  flex-direction: column;
+  gap: var(--sp-2);
+  z-index: 40;
+}
+.toast {
+  background: var(--surface-3);
+  border: 1px solid var(--line);
+  border-left: 3px solid var(--accent);
+  border-radius: var(--radius-sm);
+  padding: var(--sp-3) var(--sp-4);
+  box-shadow: var(--shadow);
+  font-size: 13px;
+  max-width: 460px;
+  animation: toast-in var(--dur) var(--ease);
+}
+.toast-ok  { border-left-color: var(--ok); }
+.toast-bad { border-left-color: var(--bad); }
+.toast pre { margin-top: 6px; font-size: 11px; color: var(--text-dim); white-space: pre-wrap; }
+@keyframes toast-in {
+  from { opacity: 0; transform: translateX(12px); }
+  to   { opacity: 1; transform: none; }
+}
+
+/* v0.52.0 — A MODAL MUST NOT SCROLL THE PAGE BEHIND IT, and this was every
+   modal in the app rather than an Extra defect. Two things were missing and
+   neither existed anywhere in bin/webui/: the modal's own scroll CHAINED to
+   <body> the moment it reached either end, and a wheel over the backdrop — most
+   of the screen — was never the modal's to begin with, so the page moved
+   immediately. `overscroll-behavior: contain` stops the chain; `body.modal-open`
+   stops the rest. The scroll position is preserved by `scrollbar-gutter: stable`
+   on <html> (01-base.css), so nothing here has to remember a number. */
+.modal-host { position: fixed; inset: 0; z-index: 50; display: grid; place-items: center; padding: var(--sp-4); overscroll-behavior: contain; }
+body.modal-open { overflow: hidden; }
+/* A LOCKED modal: the backdrop is not a button, so it must not look like one. */
+.modal-host.modal-locked .modal-backdrop { cursor: default; }
+.modal-host[hidden] { display: none; }
+.modal-backdrop { position: absolute; inset: 0; background: rgba(0, 0, 0, .55); }
+.modal {
+  position: relative;
+  width: min(720px, 100%);
+  max-height: 84vh;
+  overflow-y: auto;
+  overscroll-behavior: contain;
+  background: var(--surface);
+  border: 1px solid var(--line);
+  border-radius: var(--radius-lg);
+  box-shadow: var(--shadow);
+  padding: var(--sp-5);
+  animation: modal-in var(--dur) var(--ease);
+}
+@keyframes modal-in {
+  from { opacity: 0; transform: translateY(10px) scale(.99); }
+  to   { opacity: 1; transform: none; }
+}
+.modal-title { font-size: 16px; font-weight: 600; margin-bottom: var(--sp-3); }
+.modal-body { display: flex; flex-direction: column; gap: var(--sp-3); font-size: 13px; }
+.modal-foot { display: flex; justify-content: flex-end; gap: var(--sp-2); margin-top: var(--sp-5); }
+
+/* The whole UI goes read-only while a mutation runs (single-flight). */
+body.busy .btn:not(.btn-allow-busy) { pointer-events: none; opacity: .45; }
+body.busy .setting-control { pointer-events: none; opacity: .5; }
+/* …and it SAYS so. A frozen panel with no explanation reads as a hang; a moving
+   bar at the top edge reads as "something of mine is running". */
+body.busy::before {
+  content: "";
+  position: fixed;
+  inset: 0 0 auto 0;
+  height: 2px;
+  z-index: 60;
+  background: linear-gradient(90deg, transparent, var(--accent), transparent);
+  background-size: 40% 100%;
+  background-repeat: no-repeat;
+  animation: busy-sweep 1.1s var(--ease) infinite;
+}
+@keyframes busy-sweep {
+  from { background-position: -40% 0; }
+  to   { background-position: 140% 0; }
+}
+
+/* Cards lift slightly on hover ONLY where they are interactive. A static card
+   that reacts to the pointer promises a click that does not exist. */
+.run-card:hover, .action:hover { transform: translateY(-1px); }
+.action { transition: border-color var(--dur-fast) var(--ease), transform var(--dur-fast) var(--ease); }
+.action:hover { border-color: var(--accent-dim); }
+
+kbd {
+  background: var(--surface-3);
+  border: 1px solid var(--line);
+  border-bottom-width: 2px;
+  border-radius: 4px;
+  padding: 1px 6px;
+  font-size: 11px;
+  color: var(--text);
+  white-space: nowrap;
+}

package/bin/webui/css/04-motion.css

@@ -0,0 +1,91 @@
+/* 04-motion.css — orc ui
+   The panel entrance, the staggered block entrance, and THE ONE
+   @media (prefers-reduced-motion) block.
+   
+   LOADED LAST, and that is load-bearing. Several reduced-motion rules are
+   plain declarations rather than !important (.vault-pulse and .step-flow are
+   removed with `display: none`, because capping an infinite animation to one
+   iteration freezes it mid-cycle). An equal-specificity rule in a panel file
+   loading afterwards would win on order and quietly switch the animation back
+   on. A test asserts this media query appears here and in no panels/*.css.
+
+   The <link> ORDER in app.html is the cascade order, and the numeric
+   prefix is that order. No @import: it would carry no session token and
+   401. */
+
+/* Panel swap: 180ms slide + fade, ease-out. */
+.panel { animation: panel-in var(--dur) var(--ease); }
+@keyframes panel-in {
+  from { opacity: 0; transform: translateY(6px); }
+  to   { opacity: 1; transform: none; }
+}
+
+/* Staggered entrance. The blocks of a panel arrive in reading order rather than
+   all at once, which makes a panel of six cards parse as a sequence instead of
+   a flash. Capped at 8 so a long list never becomes a slow one — every child
+   past the cap shares the last delay. */
+.stack > * { animation: block-in var(--dur) var(--ease) backwards; }
+.stack > *:nth-child(1) { animation-delay: 0ms; }
+.stack > *:nth-child(2) { animation-delay: 30ms; }
+.stack > *:nth-child(3) { animation-delay: 60ms; }
+.stack > *:nth-child(4) { animation-delay: 90ms; }
+.stack > *:nth-child(5) { animation-delay: 120ms; }
+.stack > *:nth-child(6) { animation-delay: 150ms; }
+.stack > *:nth-child(7) { animation-delay: 180ms; }
+.stack > *:nth-child(n+8) { animation-delay: 210ms; }
+@keyframes block-in {
+  from { opacity: 0; transform: translateY(8px); }
+  to   { opacity: 1; transform: none; }
+}
+/* ---------------------------------------------------------- REDUCED MOTION */
+/* Non-negotiable: every animation and transition above is off. */
+
+@media (prefers-reduced-motion: reduce) {
+  *, *::before, *::after {
+    animation-duration: 1ms !important;
+    animation-iteration-count: 1 !important;
+    /* Load-bearing, not tidiness: the staggered entrance fills `backwards`, so
+       a delay that survives here leaves a block sitting at opacity 0 for its
+       whole delay — reduced motion would mean things simply do not appear. */
+    animation-delay: 0ms !important;
+    transition-duration: 1ms !important;
+    scroll-behavior: auto !important;
+  }
+  /* Reduced motion means no movement, not fast movement — the hover and press
+     nudges are removed outright rather than sped up. */
+  .nav a:hover, .btn:active:not(:disabled), .action:hover,
+  .todo:hover, .stat-link:hover, button.step:hover { transform: none !important; }
+  /* The vault pulse is one of two INFINITE animations on the page. Capping it to
+     a single 1ms run would still leave a dash frozen mid-edge, so it is removed
+     outright and the edge reads as a plain line. */
+  .vault-pulse { display: none; }
+  /* The other one: the looping flow sweep. `animation-iteration-count: 1` above
+     would still fire it once and then leave the connector segment collapsed at
+     its final keyframe, so both halves are removed outright — the rail is drawn
+     in its resting state and the hairlines read as plain connectors. */
+  .step, .step::before { animation: none !important; }
+  .step-flow { display: none; }
+  /* The cost bar grows in two dimensions (the stack's width, each segment's
+     flex-grow). Both are removed rather than shortened, so the bar is simply
+     drawn at its final proportions. */
+  .bar-stack, .bar-seg { transition: none !important; }
+  /* The challenge timeline and its convergence bar. Both are removed rather
+     than shortened: a capped `ch-grow` leaves a segment frozen part-way, which
+     misreports the count it is drawn from — worse than no animation at all. */
+  .ch-rail-node, .ch-conv-seg { animation: none !important; }
+  /* The Docs ribbon (v0.48.0). Three animations, all REMOVED rather than
+     capped: `doc-seg-in` capped at one iteration would still leave a segment
+     mid-`scaleY`, and the two INFINITE ones (the written sheen and the
+     user-edited pulse) would freeze at whatever opacity the single run stopped
+     on — a segment drawn at 40% height misreports the line count it is drawn
+     from, which is worse than no animation at all. The wave rows and the health
+     bars go the same way: a bar frozen part-way is a wrong number. */
+  .doc-seg, .doc-seg-box, .doc-wave, .doc-bar-seg { animation: none !important; }
+  /* The Extra connect pulse (v0.50.0). A probe has no known duration, so the
+     dot loops until an answer arrives — the third INFINITE animation on the
+     page, and removed outright for the same reason as the other two: capped at
+     one iteration it would stop half way across the wire, which reads as a
+     request that hung. The wire itself still turns green or red, so the RESULT
+     of the test is never carried by motion alone. */
+  .ex-wire-dot { display: none; }
+}

package/bin/webui/css/05-tour.css

@@ -0,0 +1,100 @@
+/* 05-tour.css — orc ui
+   The spotlight ring, .tour-block, and the z-index ladder.
+
+   The <link> ORDER in app.html is the cascade order, and the numeric
+   prefix is that order. No @import: it would carry no session token and
+   401. */
+
+/* --- the tour ------------------------------------------------------------ */
+/* The spotlight is a RING, not a dimming overlay over a cut-out: the page stays
+   fully READABLE underneath, so a step can point at a real control and you can
+   see what it is pointing at.
+   It is not, however, clickable during the guided tour. `.tour-block` sits above
+   everything except the popover and swallows every click, so Next and Skip are
+   the only live controls on screen. The upgrade spotlight opts out of the
+   blocker (`interactive: true`) because its whole design is that clicking the
+   thing dismisses it. */
+
+/* `display: contents` is load-bearing. This wrapper used to be `position:
+   fixed`, which ALWAYS creates a stacking context — so the ring and the popover
+   were trapped at the layer's own z-index and the highlighted element (46)
+   painted straight over both. Step one targets the sticky rail, which is why
+   the very first spotlight appeared underneath the sidebar. Generating no box
+   at all lets each child stack against the page directly, while still being one
+   node to remove on cleanup. */
+.tour-layer { display: contents; }
+
+/* The ladder, in paint order: scrim/ring 45 → the highlighted element 46 (so it
+   stays lit) → the click blocker 47 → the popover 48 (always readable and
+   always the only live thing) → modals 50.
+   The blocker sits ABOVE the highlighted element on purpose: lifting the target
+   to 46 is what keeps it visible through the scrim, and a blocker underneath it
+   would leave that one element clickable — which is precisely the click that
+   navigates away mid-tour. */
+.tour-block {
+  position: fixed;
+  inset: 0;
+  z-index: 47;
+  /* Fully transparent: the scrim is already drawn by the ring's outward shadow,
+     and a second dimming layer would double it. This element exists only to
+     receive clicks. */
+  background: transparent;
+  cursor: not-allowed;
+}
+.tour-ring {
+  position: fixed;
+  border: 2px solid var(--accent);
+  border-radius: var(--radius);
+  /* The scrim is thrown OUTWARD from the ring, so the target itself is never
+     covered by anything. */
+  z-index: 45;
+  box-shadow: 0 0 0 4px var(--accent-wash), 0 0 0 9999px rgba(0, 0, 0, .55);
+  pointer-events: none;
+  transition: top var(--dur-slow) var(--ease), left var(--dur-slow) var(--ease),
+              width var(--dur-slow) var(--ease), height var(--dur-slow) var(--ease);
+  animation: ring-in var(--dur) var(--ease);
+}
+:root[data-theme="light"] .tour-ring { box-shadow: 0 0 0 4px var(--accent-wash), 0 0 0 9999px rgba(16, 24, 40, .38); }
+@keyframes ring-in {
+  from { opacity: 0; transform: scale(1.04); }
+  to   { opacity: 1; transform: none; }
+}
+
+.tour-pop {
+  position: fixed;
+  z-index: 48;
+  width: min(340px, calc(100vw - 16px));
+  background: var(--surface);
+  border: 1px solid var(--accent-dim);
+  border-radius: var(--radius);
+  box-shadow: var(--shadow);
+  padding: var(--sp-4);
+  pointer-events: auto;
+  animation: pop-in var(--dur) var(--ease);
+}
+@keyframes pop-in {
+  from { opacity: 0; transform: translateY(6px); }
+  to   { opacity: 1; transform: none; }
+}
+.tour-title { font-size: 14px; font-weight: 600; margin-bottom: var(--sp-2); }
+.tour-text { font-size: 12.5px; color: var(--text-dim); line-height: 1.6; }
+.tour-foot { display: flex; align-items: center; gap: var(--sp-2); margin-top: var(--sp-4); }
+.tour-count { font-size: 11px; color: var(--text-faint); margin-right: auto; font-variant-numeric: tabular-nums; }
+.tour-waiting { font-size: 11px; color: var(--accent); margin-left: auto; }
+/* The highlighted element rides above the scrim so it stays LIT. During the
+   guided tour it is not clickable — `.tour-block` is above it — which is the
+   point: it is being explained, not operated.
+   z-index ONLY — forcing `position: relative` here broke the sticky rail, which
+   is a positioned element already. The relative fallback is applied separately,
+   and only to targets that are actually static. */
+.tour-target { z-index: 46; }
+.tour-target-rel { position: relative; }
+
+/* While a spotlight is up, the panel's entrance animations are FROZEN (v0.44.0).
+   `panel-in` and `block-in` both animate `transform`, and an element with a
+   running transform animation is a stacking context — so for the ~300ms a panel
+   takes to arrive, `.tour-target`'s z-index is trapped inside `.panel` and the
+   ladder above is decided by whether the spotlight landed before or after the
+   animation finished. Freezing them makes the ladder the only thing that
+   orders these layers, at any timing. */
+body.tour-on .panel, body.tour-on .stack > * { animation: none !important; }