@azure-id/orc 0.56.0 → 1.0.0

package/bin/webui/app.html

@@ -24,6 +24,7 @@
 <link rel="stylesheet" href="css/panels/overview.css">
 <link rel="stylesheet" href="css/05-tour.css">
 <link rel="stylesheet" href="css/panels/settings.css">
+<link rel="stylesheet" href="css/panels/lanes.css">
 <link rel="stylesheet" href="css/panels/runs.css">
 <link rel="stylesheet" href="css/panels/knowledge.css">
 <link rel="stylesheet" href="css/panels/stats.css">
@@ -69,6 +70,13 @@
     <ul class="nav" id="nav">
       <li><a href="#/overview"    data-panel="overview"    data-idx="1" data-i18n="nav.overview">Overview</a></li>
       <li><a href="#/settings"    data-panel="settings"    data-idx="2" data-i18n="nav.settings">Settings</a></li>
+      <!--
+        v1.0.0 W16. Lanes sits directly under Settings because it answers the
+        other half of the same question. Settings says what a key resolves to
+        and which lanes read it; this says what those lanes then DO with it —
+        which shared phases they run, in order, and which CLI calls they make.
+      -->
+      <li><a href="#/lanes"       data-panel="lanes"       data-idx="l" data-i18n="nav.lanes">Lanes</a></li>
       <li><a href="#/runs"        data-panel="runs"        data-idx="3" data-i18n="nav.runs">Runs</a></li>
       <li><a href="#/knowledge"   data-panel="knowledge"   data-idx="4" data-i18n="nav.knowledge">Knowledge</a></li>
       <li><a href="#/stats"       data-panel="stats"       data-idx="5" data-i18n="nav.stats">Stats</a></li>
@@ -176,6 +184,7 @@
 <script src="js/06-edit.js"></script>
 <script src="js/panels/overview.js"></script>
 <script src="js/panels/settings.js"></script>
+<script src="js/panels/lanes.js"></script>
 <script src="js/panels/runs.js"></script>
 <script src="js/panels/knowledge.js"></script>
 <script src="js/panels/stats.js"></script>

package/bin/webui/css/06-responsive.css

@@ -1,108 +1,120 @@
-/* 06-responsive.css — orc ui
-   The width breakpoints that cross panel boundaries (the rail becomes a strip,
-   the Learn rail becomes a scrollable row). They override rules from the shell
-   AND from four panels, so they load after every one of them — the same reason
-   04-motion.css is last. Breakpoints that only touch ONE panel stay in that
-   panel's file.
-
-   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. */
-
-/* --------------------------------------------------------------- RESPONSIVE */
-
-@media (max-width: 1040px) {
-  /* The Learn rail stops being a rail and becomes a scrollable strip above the
-     reading pane — a 244px column plus prose does not fit twice over. */
-  .learn { grid-template-columns: 1fr; }
-  .learn-side { position: static; max-height: none; }
-  .learn-nav { flex-direction: row; overflow-x: auto; padding-bottom: 2px; }
-  .learn-nav-item { flex: 0 0 auto; max-width: 210px; }
-}
-
-@media (max-width: 900px) {
-  .shell { grid-template-columns: 1fr; }
-  .rail {
-    position: static;
-    height: auto;
-    flex-direction: row;
-    align-items: center;
-    gap: var(--sp-4);
-    overflow-x: auto;
-    border-right: 0;
-    border-bottom: 1px solid var(--line-soft);
-  }
-  .nav { flex-direction: row; flex-wrap: nowrap; }
-  .nav a { white-space: nowrap; }
-  .rail-foot { flex-direction: row; align-items: center; }
-  .rail-project { max-width: 180px; }
-  .main { padding: var(--sp-4); }
-  .setting { grid-template-columns: 1fr; }
-  .setting-control { align-items: flex-start; }
-  /* Every `.run-card` VARIANT collapses explicitly. A variant that inherits a
-     column count it does not have is the v0.49.2 Overview collision again, just
-     at a narrower width. */
-  .run-card { grid-template-columns: 16px 80px minmax(0, 1fr); }
-  .run-card.no-caret { grid-template-columns: 80px minmax(0, 1fr); }
-  .run-card.has-extra { grid-template-columns: 16px 80px auto minmax(0, 1fr); }
-  .run-card.no-caret.has-extra { grid-template-columns: 80px auto minmax(0, 1fr); }
-  .run-age { grid-column: 3; }
-  .run-card.no-caret .run-age { grid-column: 2; }
-  .run-card.has-extra .run-age { grid-column: 4; }
-  .run-card.no-caret.has-extra .run-age { grid-column: 3; }
-  .todo { grid-template-columns: 4px minmax(0, 1fr); }
-  .todo-cta { grid-column: 2; margin-top: var(--sp-2); }
-  /* Extra. v0.50.0 brought the rail's segment floor down here so a band was
-     never squeezed to a sliver. v0.53.0 deleted that floor entirely: the band
-     ladder puts the proportional bar INSIDE a full-width row, so there is
-     nothing left to squeeze and nothing left to tune per viewport. What the
-     ladder does need at this width is for its head to stop pretending it has
-     five columns. */
-  .ex-band-head { grid-template-columns: minmax(0, 30%) minmax(0, auto) minmax(0, 1fr) 16px; }
-  /* v0.55.0 — EVERY VARIANT COLLAPSES EXPLICITLY. A position row has no bar, so
-     its first column is the slot name rather than a track; leaving it on the
-     band template here would put the target under the caret. */
-  .ex-slot-head { grid-template-columns: minmax(0, 40%) minmax(0, 1fr) 16px; }
-  .ex-slot-when { grid-column: 1 / -1; }
-  .ex-band-chips { grid-column: 1 / -1; justify-content: flex-start; }
-  .ex-route-controls { align-items: stretch; }
-  .ex-route-controls .btn { width: 100%; }
-  /* v0.53.0 — `.ex-tool` was the one `.ex-*` block with no entry here at all.
-     At this width a tool card's actions are the reason you opened the panel, so
-     they go full width rather than being squeezed onto the end of a row. */
-  .ex-tool > .row-actions:not(:first-child) { align-items: stretch; }
-  .ex-tool > .row-actions:not(:first-child) .btn { width: 100%; }
-  /* v0.54.0 — a recovery row's identity is the longest thing in it, so at this
-     width it takes its own line rather than truncating a profile and a model
-     into nothing. The row is a FLEX COLUMN, so this is a wrap rather than a
-     second grid template. */
-  .ex-rec-head { flex-wrap: wrap; }
-  .ex-rec-who { flex: 1 1 100%; white-space: normal; }
-}
-
-@media (max-width: 600px) {
-  /* Below this there is no honest way to keep a chip, a slug and an age on one
-     line, so the card stacks: chip, then the slug and where it stands, then the
-     age. One column, in reading order. */
-  .run-card,
-  .run-card.no-caret,
-  .run-card.has-extra,
-  .run-card.no-caret.has-extra {
-    grid-template-columns: minmax(0, 1fr);
-    gap: var(--sp-2);
-  }
-  .run-caret { display: none; }
-  .run-card .run-age { grid-column: 1; }
-  /* Extra: the provider catalog stops being a grid — below this a two-column
-     tile cannot hold a base URL and two links without wrapping mid-word — and
-     the connect form's two columns become one. */
-  .ex-provider-grid { grid-template-columns: minmax(0, 1fr); }
-  .ex-strip { gap: var(--sp-3); }
-  .ex-route-controls > * { flex: 1 1 100%; }
-  /* The tool card's head stops being a row: a label, a binary name and a state
-     chip cannot share a line honestly below this. */
-  .ex-tool > .row-actions:first-child { flex-direction: column; align-items: flex-start; }
-  /* A per-file position line cannot hold a path, a state word and a line delta
-     on one row below this — and the path is the half that must stay readable. */
-  .ex-rec-file { flex-direction: column; align-items: flex-start; }
-}
+/* 06-responsive.css — orc ui
+   The width breakpoints that cross panel boundaries (the rail becomes a strip,
+   the Learn rail becomes a scrollable row). They override rules from the shell
+   AND from four panels, so they load after every one of them — the same reason
+   04-motion.css is last. Breakpoints that only touch ONE panel stay in that
+   panel's file.
+
+   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. */
+
+/* --------------------------------------------------------------- RESPONSIVE */
+
+@media (max-width: 1040px) {
+  /* The Learn rail stops being a rail and becomes a scrollable strip above the
+     reading pane — a 244px column plus prose does not fit twice over. */
+  .learn { grid-template-columns: 1fr; }
+  .learn-side { position: static; max-height: none; }
+  .learn-nav { flex-direction: row; overflow-x: auto; padding-bottom: 2px; }
+  .learn-nav-item { flex: 0 0 auto; max-width: 210px; }
+}
+
+@media (max-width: 900px) {
+  .shell { grid-template-columns: 1fr; }
+  .rail {
+    position: static;
+    height: auto;
+    flex-direction: row;
+    align-items: center;
+    gap: var(--sp-4);
+    overflow-x: auto;
+    border-right: 0;
+    border-bottom: 1px solid var(--line-soft);
+  }
+  .nav { flex-direction: row; flex-wrap: nowrap; }
+  .nav a { white-space: nowrap; }
+  .rail-foot { flex-direction: row; align-items: center; }
+  .rail-project { max-width: 180px; }
+  .main { padding: var(--sp-4); }
+  .setting { grid-template-columns: 1fr; }
+  .setting-control { align-items: flex-start; }
+  /* The rank ladder keeps its prio column — it is 34px and it is the thing
+     that makes the row readable as a ladder rather than a list. The state
+     chip wraps under instead, which is the only child that can spare the
+     line. Declared explicitly, like every `.run-card` variant below. */
+  .rank-row { grid-template-columns: 34px minmax(0, 1fr); }
+  .rank-row > .chip { grid-column: 2; justify-self: start; }
+  /* A phase row drops its right-hand column under the body rather than
+     squeezing it: `read`, `when` and the layer list are facts, and a fact
+     wrapped to one character per line is not readable. Declared explicitly. */
+  .phase-row { grid-template-columns: 28px minmax(0, 1fr); }
+  .phase-right { grid-column: 2; flex-direction: row; flex-wrap: wrap; align-items: center; }
+  .call-detail { padding-left: var(--sp-3); }
+  /* Every `.run-card` VARIANT collapses explicitly. A variant that inherits a
+     column count it does not have is the v0.49.2 Overview collision again, just
+     at a narrower width. */
+  .run-card { grid-template-columns: 16px 80px minmax(0, 1fr); }
+  .run-card.no-caret { grid-template-columns: 80px minmax(0, 1fr); }
+  .run-card.has-extra { grid-template-columns: 16px 80px auto minmax(0, 1fr); }
+  .run-card.no-caret.has-extra { grid-template-columns: 80px auto minmax(0, 1fr); }
+  .run-age { grid-column: 3; }
+  .run-card.no-caret .run-age { grid-column: 2; }
+  .run-card.has-extra .run-age { grid-column: 4; }
+  .run-card.no-caret.has-extra .run-age { grid-column: 3; }
+  .todo { grid-template-columns: 4px minmax(0, 1fr); }
+  .todo-cta { grid-column: 2; margin-top: var(--sp-2); }
+  /* Extra. v0.50.0 brought the rail's segment floor down here so a band was
+     never squeezed to a sliver. v0.53.0 deleted that floor entirely: the band
+     ladder puts the proportional bar INSIDE a full-width row, so there is
+     nothing left to squeeze and nothing left to tune per viewport. What the
+     ladder does need at this width is for its head to stop pretending it has
+     five columns. */
+  .ex-band-head { grid-template-columns: minmax(0, 30%) minmax(0, auto) minmax(0, 1fr) 16px; }
+  /* v0.55.0 — EVERY VARIANT COLLAPSES EXPLICITLY. A position row has no bar, so
+     its first column is the slot name rather than a track; leaving it on the
+     band template here would put the target under the caret. */
+  .ex-slot-head { grid-template-columns: minmax(0, 40%) minmax(0, 1fr) 16px; }
+  .ex-slot-when { grid-column: 1 / -1; }
+  .ex-band-chips { grid-column: 1 / -1; justify-content: flex-start; }
+  .ex-route-controls { align-items: stretch; }
+  .ex-route-controls .btn { width: 100%; }
+  /* v0.53.0 — `.ex-tool` was the one `.ex-*` block with no entry here at all.
+     At this width a tool card's actions are the reason you opened the panel, so
+     they go full width rather than being squeezed onto the end of a row. */
+  .ex-tool > .row-actions:not(:first-child) { align-items: stretch; }
+  .ex-tool > .row-actions:not(:first-child) .btn { width: 100%; }
+  /* v0.54.0 — a recovery row's identity is the longest thing in it, so at this
+     width it takes its own line rather than truncating a profile and a model
+     into nothing. The row is a FLEX COLUMN, so this is a wrap rather than a
+     second grid template. */
+  .ex-rec-head { flex-wrap: wrap; }
+  .ex-rec-who { flex: 1 1 100%; white-space: normal; }
+}
+
+@media (max-width: 600px) {
+  /* Below this there is no honest way to keep a chip, a slug and an age on one
+     line, so the card stacks: chip, then the slug and where it stands, then the
+     age. One column, in reading order. */
+  .run-card,
+  .run-card.no-caret,
+  .run-card.has-extra,
+  .run-card.no-caret.has-extra {
+    grid-template-columns: minmax(0, 1fr);
+    gap: var(--sp-2);
+  }
+  .run-caret { display: none; }
+  .run-card .run-age { grid-column: 1; }
+  /* Extra: the provider catalog stops being a grid — below this a two-column
+     tile cannot hold a base URL and two links without wrapping mid-word — and
+     the connect form's two columns become one. */
+  .ex-provider-grid { grid-template-columns: minmax(0, 1fr); }
+  .ex-strip { gap: var(--sp-3); }
+  .ex-route-controls > * { flex: 1 1 100%; }
+  /* The tool card's head stops being a row: a label, a binary name and a state
+     chip cannot share a line honestly below this. */
+  .ex-tool > .row-actions:first-child { flex-direction: column; align-items: flex-start; }
+  /* A per-file position line cannot hold a path, a state word and a line delta
+     on one row below this — and the path is the half that must stay readable. */
+  .ex-rec-file { flex-direction: column; align-items: flex-start; }
+}

package/bin/webui/css/panels/extra.css

@@ -534,3 +534,32 @@
   border-radius: var(--r-sm);
   padding: var(--sp-2) var(--sp-3);
 }
+
+/* ── the run demotion (v1.0.0 W16) ────────────────────────────────────────────
+   A FLEX COLUMN, never a declared grid. Four evidence lines are optional —
+   `why`, a live stale attempt, a counter reset, a resume count — so the child
+   count changes with the state, and a card whose child count changes with its
+   state must not declare its rows. That is exactly what stretched `.ex-tool`'s
+   chip into a 250px ellipse in v0.53.0. */
+.ex-dem-row {
+  display: flex;
+  flex-direction: column;
+  gap: 4px;
+  padding: var(--sp-2) var(--sp-3);
+  background: var(--surface-2);
+  border: 1px solid var(--line-soft);
+  border-radius: var(--radius-sm);
+  margin-top: 4px;
+}
+.ex-dem-row.is-demoted { border-color: var(--bad); background: var(--bad-wash, var(--surface-2)); }
+.ex-dem-head {
+  display: flex;
+  flex-wrap: wrap;
+  align-items: center;
+  gap: var(--sp-2);
+}
+.ex-dem-profile { font-family: var(--mono); font-size: 13px; color: var(--text); }
+/* The counter renders at zero too, so it is a stated fact and never a badge
+   that only appears when something is wrong. */
+.ex-dem-count { font-family: var(--mono); font-size: 11px; color: var(--text-faint); margin-left: auto; }
+.ex-dem-why { font-size: 12px; color: var(--text-faint); overflow-wrap: anywhere; }

package/bin/webui/css/panels/lanes.css

@@ -0,0 +1,134 @@
+/* panels/lanes.css — the `orc lane` noun, rendered.
+   Loaded by app.html in the order its <link> names, which for CSS is the
+   cascade order. Every colour is a token from 00-tokens.css. */
+
+/* ── the lane picker ──────────────────────────────────────────────────────── */
+.lane-meta {
+  display: flex;
+  flex-wrap: wrap;
+  align-items: center;
+  gap: 6px;
+  margin-bottom: var(--sp-3);
+}
+.lane-meta-label { font-size: 12px; color: var(--text-faint); }
+
+/* ── a phase row ──────────────────────────────────────────────────────────────
+   A GRID that DECLARES its columns, and whose child count never varies with
+   state: ordinal · body · right-hand facts. `optional_when` is an optional
+   FOURTH child, so it takes a full-width line of its own rather than a column
+   it usually leaves empty — the `.ex-tool` lesson (v0.53.0), where a card
+   declaring rows its states did not all have stretched a chip into an ellipse. */
+.phase-row {
+  display: grid;
+  grid-template-columns: 28px minmax(0, 1fr) auto;
+  align-items: start;
+  gap: var(--sp-3);
+  padding: var(--sp-2) var(--sp-3);
+  background: var(--surface-2);
+  border: 1px solid var(--line-soft);
+  border-radius: var(--radius-sm);
+  margin-bottom: 4px;
+}
+.phase-ord {
+  font-family: var(--mono);
+  font-size: 12px;
+  color: var(--text-faint);
+  text-align: right;
+}
+.phase-mid { min-width: 0; }
+.phase-id { font-family: var(--mono); font-size: 13px; color: var(--text); }
+.phase-file {
+  font-family: var(--mono);
+  font-size: 11px;
+  color: var(--text-faint);
+  overflow-wrap: anywhere;
+  margin-top: 2px;
+}
+.phase-calls {
+  display: flex;
+  flex-wrap: wrap;
+  align-items: center;
+  gap: 4px;
+  margin-top: 6px;
+}
+.phase-calls-label { font-size: 11px; color: var(--text-faint); }
+.phase-right {
+  display: flex;
+  flex-direction: column;
+  align-items: flex-end;
+  gap: 4px;
+}
+.phase-read,
+.phase-layers { font-family: var(--mono); font-size: 11px; color: var(--text-faint); }
+.phase-why {
+  grid-column: 1 / -1;
+  font-size: 12px;
+  color: var(--text-faint);
+  overflow-wrap: anywhere;
+}
+
+/* ── a call row ───────────────────────────────────────────────────────────────
+   Expands IN PLACE, one at a time (the Runs-row rule, v0.43.6). The head is a
+   FLEX row rather than a grid: its child count genuinely varies — `cost` is
+   optional — and a card whose child count changes with its state must not
+   declare its columns. */
+.call-row {
+  border: 1px solid var(--line-soft);
+  border-radius: var(--radius-sm);
+  background: var(--surface-2);
+  margin-bottom: 4px;
+  overflow: hidden;
+}
+.call-head {
+  display: flex;
+  align-items: center;
+  gap: var(--sp-3);
+  width: 100%;
+  padding: var(--sp-2) var(--sp-3);
+  background: none;
+  border: 0;
+  color: inherit;
+  text-align: left;
+  cursor: pointer;
+  font: inherit;
+}
+.call-head:hover { background: var(--surface-3, var(--surface-2)); }
+.call-caret {
+  color: var(--text-faint);
+  transition: transform 140ms ease;
+  flex: 0 0 auto;
+}
+.call-head[aria-expanded="true"] .call-caret { transform: rotate(90deg); }
+.call-cmd {
+  font-family: var(--mono);
+  font-size: 12px;
+  color: var(--text);
+  flex: 1 1 auto;
+  min-width: 0;
+  overflow-wrap: anywhere;
+}
+.call-lanes-n { font-size: 11px; color: var(--text-faint); flex: 0 0 auto; }
+.call-detail {
+  padding: 0 var(--sp-3) var(--sp-3) calc(var(--sp-3) + 20px);
+  border-top: 1px solid var(--line-soft);
+}
+.call-exits,
+.call-lane-chips {
+  display: flex;
+  flex-wrap: wrap;
+  align-items: center;
+  gap: 4px;
+  margin-top: var(--sp-2);
+}
+.call-exits-label { font-size: 12px; color: var(--text-faint); }
+/* An exit code is a CONTRACT a lane branches on, so it is drawn as a fixed
+   token rather than folded into the surrounding prose. */
+.call-exit {
+  font-family: var(--mono);
+  font-size: 11px;
+  color: var(--text-dim);
+  background: var(--surface-1, var(--surface-2));
+  border: 1px solid var(--line-soft);
+  border-radius: var(--radius-sm);
+  padding: 2px 6px;
+}

package/bin/webui/css/panels/settings.css

@@ -110,9 +110,9 @@
   to   { transform: none; opacity: 1; }
 }
 
-/* THE SHADOWING ANIMATION (plan §6.2). Flip opus5_only on and the fable5_*
-   rows desaturate, a lock slides in, and the reason is right there. The
-   animation teaches the precedence rule — that is the whole point. */
+/* THE SHADOWING ANIMATION (plan §6.2). A row a higher rank already answered
+   desaturates, a lock slides in, and the reason is right there. The animation
+   teaches the precedence rule — that is the whole point. */
 .setting.shadowed { opacity: .42; filter: saturate(.15); }
 .lock {
   display: inline-flex;
@@ -225,3 +225,79 @@
 .rung-bar { height: 4px; border-radius: 2px; background: var(--accent); opacity: .55; }
 .rung-agent { color: var(--text-dim); }
 .ladder-note { font-size: 12px; color: var(--text-faint); margin-top: var(--sp-2); }
+
+/* ── who decides what: the contested families, resolved (v1.0.0 W16) ────────
+   A precedence LADDER, drawn the same way the score ladder above it is drawn
+   — one row per rank, in resolution order, top-down. The row that answered is
+   the only one given weight, because "read down and stop at the first one that
+   resolves" is a rule a picture can teach and a paragraph cannot. */
+.rank-family { margin-top: var(--sp-4); }
+.rank-family:first-of-type { margin-top: var(--sp-2); }
+.rank-family-head {
+  display: flex;
+  flex-wrap: wrap;
+  align-items: baseline;
+  gap: var(--sp-2);
+  margin-bottom: 4px;
+}
+.rank-family-name { font-family: var(--mono); font-size: 12px; color: var(--text-dim); }
+.rank-family-q { font-size: 12px; color: var(--text-faint); }
+.rank-answer { font-size: 12px; color: var(--text-faint); margin-bottom: 6px; }
+
+/* A GRID whose column count never changes with state. `.ex-tool`'s 250px
+   ellipse (v0.53.0) was a card DECLARING rows its states did not all have; the
+   `why` here is an optional FOURTH child, so it is given its own full-width
+   line rather than a column it sometimes leaves empty. */
+.rank-row {
+  display: grid;
+  grid-template-columns: 34px minmax(0, 1fr) auto;
+  align-items: center;
+  gap: var(--sp-3);
+  padding: 5px var(--sp-3);
+  background: var(--surface-2);
+  border: 1px solid var(--line-soft);
+  border-radius: var(--radius-sm);
+  margin-bottom: 4px;
+}
+.rank-row.is-resolved { border-color: var(--ok); background: var(--ok-wash); }
+.rank-prio { font-family: var(--mono); font-size: 12px; color: var(--text-faint); }
+.rank-key { font-family: var(--mono); font-size: 12px; color: var(--text-dim); overflow-wrap: anywhere; }
+/* The terminal floor is not a key and must not read as one, or somebody goes
+   looking for it in the config file. */
+.rank-key.is-terminal { font-family: inherit; font-style: italic; color: var(--text-faint); }
+.rank-why {
+  grid-column: 1 / -1;
+  font-size: 12px;
+  color: var(--text-faint);
+  overflow-wrap: anywhere;
+}
+.rank-legend {
+  display: flex;
+  flex-wrap: wrap;
+  align-items: center;
+  gap: 6px;
+  margin-top: var(--sp-3);
+  padding-top: var(--sp-3);
+  border-top: 1px solid var(--line-soft);
+}
+.rank-legend-label { font-size: 12px; color: var(--text-faint); }
+
+/* which lanes read a key — chips, because the list is short and unordered */
+.setting-lanes {
+  display: flex;
+  flex-wrap: wrap;
+  align-items: center;
+  gap: 4px;
+  margin-top: 6px;
+}
+.setting-lanes-label { font-size: 12px; color: var(--text-faint); }
+.chip-lane {
+  font-family: var(--mono);
+  font-size: 11px;
+  color: var(--text-faint);
+  background: var(--surface-2);
+  border-color: var(--line-soft);
+}
+/* "no lane reads this" is an ANSWER, so it is styled as a stated fact rather
+   than as a missing chip. */
+.setting-lanes-none { font-size: 11px; color: var(--text-faint); font-style: italic; }