@azure-id/orc 1.9.1 → 2.0.2

package/bin/webui/css/00-tokens.css

@@ -1,92 +1,110 @@
-/* 00-tokens.css — orc ui
-   Palette, the theme states, the type scale, spacing. Every colour token is
-   defined on bare :root here; the override blocks below redefine tokens ONLY.
-
-   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. */
-
-/* ---------------------------------------------------------------- TOKENS -- */
-
-:root {
-  /* surface ladder — deepest at the back, lightest at the front */
-  --bg:            #0c0e12;
-  --bg-rail:       #090a0d;
-  --surface:       #14171d;
-  --surface-2:     #1a1e26;
-  --surface-3:     #212630;
-  --line:          #262c37;
-  --line-soft:     #1c212a;
-
-  --text:          #e6e9ef;
-  --text-dim:      #98a1b0;
-  --text-faint:    #667084;
-
-  /* one accent; status carries the rest */
-  --accent:        #4c9aff;
-  --accent-dim:    #2f6fc4;
-  --accent-wash:   rgba(76, 154, 255, .12);
-
-  --ok:            #3fb950;
-  --ok-wash:       rgba(63, 185, 80, .12);
-  --warn:          #d8a01a;
-  --warn-wash:     rgba(216, 160, 26, .12);
-  --bad:           #f0533f;
-  --bad-wash:      rgba(240, 83, 63, .12);
-  --idle:          #6b7280;
-  --idle-wash:     rgba(107, 114, 128, .12);
-
-  --radius:        10px;
-  --radius-sm:     6px;
-  --radius-lg:     14px;
-
-  --sp-1: 4px;
-  --sp-2: 8px;
-  --sp-3: 12px;
-  --sp-4: 16px;
-  --sp-5: 24px;
-  --sp-6: 32px;
-  --sp-7: 48px;
-
-  --dur-fast:   120ms;
-  --dur:        180ms;
-  --dur-shadow: 220ms;
-  --dur-slow:   320ms;
-  --ease:       cubic-bezier(.2, .7, .3, 1);
-
-  --rail-w: 208px;
-
-  --font: system-ui, -apple-system, "Segoe UI", Roboto, Helvetica, Arial, sans-serif;
-  --mono: ui-monospace, SFMono-Regular, "SF Mono", Menlo, Consolas, "Liberation Mono", monospace;
-
-  --shadow: 0 10px 30px rgba(0, 0, 0, .45);
-}
-
-:root[data-theme="light"] {
-  --bg:            #f6f7f9;
-  --bg-rail:       #eceef2;
-  --surface:       #ffffff;
-  --surface-2:     #f3f5f8;
-  --surface-3:     #e9ecf1;
-  --line:          #d8dde5;
-  --line-soft:     #e6e9ee;
-
-  --text:          #171a20;
-  --text-dim:      #57616f;
-  --text-faint:    #808a99;
-
-  --accent:        #1f6feb;
-  --accent-dim:    #1a5cc4;
-  --accent-wash:   rgba(31, 111, 235, .10);
-
-  --ok:            #1a7f37;
-  --ok-wash:       rgba(26, 127, 55, .10);
-  --warn:          #9a6700;
-  --warn-wash:     rgba(154, 103, 0, .10);
-  --bad:           #cf222e;
-  --bad-wash:      rgba(207, 34, 46, .10);
-  --idle:          #6b7280;
-  --idle-wash:     rgba(107, 114, 128, .10);
-
-  --shadow: 0 10px 30px rgba(16, 24, 40, .12);
-}
+/* 00-tokens.css — orc ui
+   Palette, the theme states, the type scale, spacing. Every colour token is
+   defined on bare :root here; the override blocks below redefine tokens ONLY.
+
+   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. */
+
+/* ---------------------------------------------------------------- TOKENS -- */
+
+:root {
+  /* surface ladder — deepest at the back, lightest at the front */
+  --bg:            #0c0e12;
+  --bg-rail:       #090a0d;
+  --surface:       #14171d;
+  --surface-2:     #1a1e26;
+  --surface-3:     #212630;
+  --line:          #262c37;
+  --line-soft:     #1c212a;
+
+  --text:          #e6e9ef;
+  --text-dim:      #98a1b0;
+  --text-faint:    #667084;
+
+  /* one accent; status carries the rest */
+  --accent:        #4c9aff;
+  --accent-dim:    #2f6fc4;
+  --accent-wash:   rgba(76, 154, 255, .12);
+
+  --ok:            #3fb950;
+  --ok-wash:       rgba(63, 185, 80, .12);
+  --warn:          #d8a01a;
+  --warn-wash:     rgba(216, 160, 26, .12);
+  --bad:           #f0533f;
+  --bad-wash:      rgba(240, 83, 63, .12);
+  --idle:          #6b7280;
+  --idle-wash:     rgba(107, 114, 128, .12);
+
+  /* seven series colours (v2.0.0 W7) — the Behaviour panel's lane mix, answer
+     sources and gotcha sources. Each is >= 3:1 against --surface (WCAG 1.4.11). */
+  --s1:            #4c9aff;
+  --s2:            #3fb950;
+  --s3:            #d8a01a;
+  --s4:            #b083f0;
+  --s5:            #f0533f;
+  --s6:            #39c5cf;
+  --s7:            #8b949e;
+
+  --radius:        10px;
+  --radius-sm:     6px;
+  --radius-lg:     14px;
+
+  --sp-1: 4px;
+  --sp-2: 8px;
+  --sp-3: 12px;
+  --sp-4: 16px;
+  --sp-5: 24px;
+  --sp-6: 32px;
+  --sp-7: 48px;
+
+  --dur-fast:   120ms;
+  --dur:        180ms;
+  --dur-shadow: 220ms;
+  --dur-slow:   320ms;
+  --ease:       cubic-bezier(.2, .7, .3, 1);
+
+  --rail-w: 208px;
+
+  --font: system-ui, -apple-system, "Segoe UI", Roboto, Helvetica, Arial, sans-serif;
+  --mono: ui-monospace, SFMono-Regular, "SF Mono", Menlo, Consolas, "Liberation Mono", monospace;
+
+  --shadow: 0 10px 30px rgba(0, 0, 0, .45);
+}
+
+:root[data-theme="light"] {
+  --bg:            #f6f7f9;
+  --bg-rail:       #eceef2;
+  --surface:       #ffffff;
+  --surface-2:     #f3f5f8;
+  --surface-3:     #e9ecf1;
+  --line:          #d8dde5;
+  --line-soft:     #e6e9ee;
+
+  --text:          #171a20;
+  --text-dim:      #57616f;
+  --text-faint:    #808a99;
+
+  --accent:        #1f6feb;
+  --accent-dim:    #1a5cc4;
+  --accent-wash:   rgba(31, 111, 235, .10);
+
+  --ok:            #1a7f37;
+  --ok-wash:       rgba(26, 127, 55, .10);
+  --warn:          #9a6700;
+  --warn-wash:     rgba(154, 103, 0, .10);
+  --bad:           #cf222e;
+  --bad-wash:      rgba(207, 34, 46, .10);
+  --idle:          #6b7280;
+  --idle-wash:     rgba(107, 114, 128, .10);
+
+  --s1:            #1f6feb;
+  --s2:            #1a7f37;
+  --s3:            #9a6700;
+  --s4:            #8250df;
+  --s5:            #cf222e;
+  --s6:            #1b7c83;
+  --s7:            #6e7781;
+
+  --shadow: 0 10px 30px rgba(16, 24, 40, .12);
+}

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

@@ -1,152 +1,249 @@
-/* 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; }
-}
-/* ── the CLI Hook Interface (v1.4.1) ─────────────────────────────────────── */
-/* The board is a thing you BUILD, so it moves the way a thing you build moves:
-   a chip arrives, a chip you just staged breathes once so you can find it, and
-   a row in the part picker slides in as the list narrows under your typing.
-   Every one of them is a FINITE animation with a real end state, so the cap in
-   the reduced-motion block below leaves each one at rest rather than frozen
-   part-way. */
-.hk-chip { animation: hk-chip-in 200ms var(--ease) backwards; }
-@keyframes hk-chip-in {
-  from { opacity: 0; transform: translateY(6px) scale(0.97); }
-  to   { opacity: 1; transform: none; }
-}
-/* Staged, not written — and the one thing on the board that has to be findable
-   the instant it appears. Three pulses and it stops: an infinite one would have
-   to be REMOVED below rather than capped, and this one reads correctly at rest.
-   */
-.hk-chip-new { animation: hk-chip-in 200ms var(--ease) backwards, hk-chip-mark 900ms var(--ease) 3; }
-@keyframes hk-chip-mark {
-  0%, 100% { box-shadow: inset 0 0 0 0 var(--accent); }
-  50%      { box-shadow: inset 0 0 0 2px var(--accent); }
-}
-/* Position, drop marker, and the zone's own border: transitions rather than
-   animations, so an interrupted drag never leaves a chip mid-flight. */
-.hk-chip, .hk-zone, .hk-add, .hk-act, .hk-pick-row, .hk-theme, .hk-sample {
-  transition: border-color var(--dur) var(--ease), background var(--dur) var(--ease),
-              box-shadow var(--dur) var(--ease), opacity var(--dur) var(--ease),
-              transform var(--dur) var(--ease);
-}
-.hk-chip:hover:not(.hk-chip-dragging) { transform: translateY(-2px); }
-.hk-add:hover:not(:disabled) { transform: translateY(-2px); }
-.hk-pick-row { animation: hk-row-in 160ms var(--ease) backwards; }
-@keyframes hk-row-in {
-  from { opacity: 0; transform: translateX(-6px); }
-  to   { opacity: 1; transform: none; }
-}
-button.hk-pick-row:hover { transform: translateX(3px); }
-
-/* NOTHING ARRIVES ON A REPAINT (v1.4.2). The CLI Hook Interface rebuilds its
-   whole panel when a change is STAGED — no request, no navigation, the same
-   cards with one value different — and the entrance animations above replayed
-   every time, on a 30ms stagger. With the network tab empty it read exactly
-   like the page reloading, on every keystroke.
-
-   `hk-quiet` is added by `hkPaint` from the SECOND paint onward and by the part
-   editor before every rebuild. It removes the ENTRANCES only: the transitions
-   further up are about the pointer rather than about arriving, so hover, the
-   drop marker and the staged edge are untouched. It must load after the rules
-   it switches off, which is why it is here and not in the panel's own file. */
-.hk-quiet > *,
-.hk-quiet .hk-chip,
-.hk-quiet .hk-chip-new,
-.hk-quiet .hk-pick-row {
-  animation: 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 board's own nudges, removed rather than shortened — a chip that lifts
-     under the pointer is an affordance, and a fast lift is still a lift. The
-     border and box-shadow changes stay: THEY are what says where a drop lands,
-     and a drop marker carried by motion alone would not exist here at all. */
-  .hk-chip:hover:not(.hk-chip-dragging), .hk-add:hover:not(:disabled),
-  button.hk-pick-row: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; }
-}
+/* 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; }
+}
+/* ── the CLI Hook Interface (v1.4.1) ─────────────────────────────────────── */
+/* The board is a thing you BUILD, so it moves the way a thing you build moves:
+   a chip arrives, a chip you just staged breathes once so you can find it, and
+   a row in the part picker slides in as the list narrows under your typing.
+   Every one of them is a FINITE animation with a real end state, so the cap in
+   the reduced-motion block below leaves each one at rest rather than frozen
+   part-way. */
+.hk-chip { animation: hk-chip-in 200ms var(--ease) backwards; }
+@keyframes hk-chip-in {
+  from { opacity: 0; transform: translateY(6px) scale(0.97); }
+  to   { opacity: 1; transform: none; }
+}
+/* Staged, not written — and the one thing on the board that has to be findable
+   the instant it appears. Three pulses and it stops: an infinite one would have
+   to be REMOVED below rather than capped, and this one reads correctly at rest.
+   */
+.hk-chip-new { animation: hk-chip-in 200ms var(--ease) backwards, hk-chip-mark 900ms var(--ease) 3; }
+@keyframes hk-chip-mark {
+  0%, 100% { box-shadow: inset 0 0 0 0 var(--accent); }
+  50%      { box-shadow: inset 0 0 0 2px var(--accent); }
+}
+/* Position, drop marker, and the zone's own border: transitions rather than
+   animations, so an interrupted drag never leaves a chip mid-flight. */
+.hk-chip, .hk-zone, .hk-add, .hk-act, .hk-pick-row, .hk-theme, .hk-sample {
+  transition: border-color var(--dur) var(--ease), background var(--dur) var(--ease),
+              box-shadow var(--dur) var(--ease), opacity var(--dur) var(--ease),
+              transform var(--dur) var(--ease);
+}
+.hk-chip:hover:not(.hk-chip-dragging) { transform: translateY(-2px); }
+.hk-add:hover:not(:disabled) { transform: translateY(-2px); }
+.hk-pick-row { animation: hk-row-in 160ms var(--ease) backwards; }
+@keyframes hk-row-in {
+  from { opacity: 0; transform: translateX(-6px); }
+  to   { opacity: 1; transform: none; }
+}
+button.hk-pick-row:hover { transform: translateX(3px); }
+
+/* NOTHING ARRIVES ON A REPAINT (v1.4.2). The CLI Hook Interface rebuilds its
+   whole panel when a change is STAGED — no request, no navigation, the same
+   cards with one value different — and the entrance animations above replayed
+   every time, on a 30ms stagger. With the network tab empty it read exactly
+   like the page reloading, on every keystroke.
+
+   `hk-quiet` is added by `hkPaint` from the SECOND paint onward and by the part
+   editor before every rebuild. It removes the ENTRANCES only: the transitions
+   further up are about the pointer rather than about arriving, so hover, the
+   drop marker and the staged edge are untouched. It must load after the rules
+   it switches off, which is why it is here and not in the panel's own file. */
+.hk-quiet > *,
+.hk-quiet .hk-chip,
+.hk-quiet .hk-chip-new,
+.hk-quiet .hk-pick-row {
+  animation: none;
+}
+
+/* ── the Behaviour panel (v2.0.0 W7) ──────────────────────────────────────── */
+/* Motion is information here, not decoration: the ring filling says "this
+   share", a bar growing says "this proportion", the proposal breathing says
+   "this one needs you". EVERY animation below is FINITE and ends well inside
+   5 s (WCAG 2.2.2), so the reduced-motion cap leaves each one at rest. */
+.bh-portrait li { animation: bh-portrait-in 420ms var(--ease) backwards; }
+@keyframes bh-portrait-in {
+  from { opacity: 0; transform: translateX(-10px); }
+  to   { opacity: 1; transform: none; }
+}
+.bh-grow-x { transform-origin: left center; animation: bh-grow-x 700ms var(--ease) backwards; }
+@keyframes bh-grow-x {
+  from { transform: scaleX(0); }
+  to   { transform: scaleX(1); }
+}
+.bh-grow-y { transform-origin: bottom center; animation: bh-grow-y 600ms var(--ease) backwards; }
+@keyframes bh-grow-y {
+  from { transform: scaleY(0); }
+  to   { transform: scaleY(1); }
+}
+.bh-heat .c { animation: bh-cell-in 360ms var(--ease) backwards; }
+@keyframes bh-cell-in {
+  from { opacity: 0; transform: scale(.4); }
+  to   { opacity: 1; transform: none; }
+}
+/* The line draws itself. --len is set from the path's own length in the panel. */
+.bh-draw { stroke-dasharray: var(--len, 2000); stroke-dashoffset: var(--len, 2000); animation: bh-draw 1100ms var(--ease) forwards; }
+@keyframes bh-draw { to { stroke-dashoffset: 0; } }
+.bh-fade-late { animation: bh-fade 500ms var(--ease) 700ms backwards; }
+@keyframes bh-fade {
+  from { opacity: 0; }
+  to   { opacity: 1; }
+}
+.bh-habit, .bh-lesson { animation: block-in 260ms var(--ease) backwards; }
+.bh-habit { transition: border-color var(--dur) var(--ease), transform var(--dur) var(--ease), box-shadow var(--dur-shadow) var(--ease); }
+.bh-habit:hover { transform: translateY(-2px); }
+/* A proposal is the one card that has to be FOUND: it breathes three times
+   and stops — the hk-chip-mark rule. */
+.bh-habit[data-state="proposed"] { animation: block-in 260ms var(--ease) backwards, bh-propose 1400ms var(--ease) 400ms 3; }
+@keyframes bh-propose {
+  0%, 100% { box-shadow: 0 0 0 0 transparent; }
+  50%      { box-shadow: 0 0 0 4px var(--accent-wash), 0 0 28px -6px var(--accent); }
+}
+.bh-log-row { animation: bh-row-in 380ms var(--ease) backwards; }
+@keyframes bh-row-in {
+  from { opacity: 0; transform: translateY(-8px); background: var(--accent-wash); }
+  to   { opacity: 1; transform: none; background: transparent; }
+}
+/* The ring is a TRANSITION, so the reduced-motion cap already makes it instant. */
+.bh-ring .fg { transition: stroke-dashoffset 900ms var(--ease); }
+.bh-tab-ink { transition: left var(--dur-slow) var(--ease), width var(--dur-slow) var(--ease); }
+.bh-seg button { transition: background var(--dur) var(--ease), color var(--dur) var(--ease); }
+/* The rail dot: three pulses, then rest. */
+.bh-dot { animation: bh-dot 1600ms var(--ease) 3; }
+@keyframes bh-dot {
+  0%, 100% { box-shadow: 0 0 0 0 var(--accent-wash); }
+  50%      { box-shadow: 0 0 0 5px transparent; }
+}
+/* The hero orbit: ONE slow turn (≈ 4.6 s), then rest. Never infinite. */
+.bh-orbit .sat { transform-box: view-box; transform-origin: 130px 130px; animation: bh-orbit 4.6s var(--ease) 1 both; }
+.bh-orbit .sat-b { animation-duration: 4.2s; animation-direction: reverse; }
+@keyframes bh-orbit {
+  from { transform: rotate(0deg); }
+  to   { transform: rotate(360deg); }
+}
+/* NOTHING ARRIVES ON A REPAINT. After a write the panel repaints with
+   `bh-quiet`, and every entrance above is off — the v1.4.2 hk-quiet rule. */
+.bh-quiet > *,
+.bh-quiet .bh-habit,
+.bh-quiet .bh-lesson,
+.bh-quiet .bh-log-row,
+.bh-quiet .bh-portrait li,
+.bh-quiet .bh-grow-x,
+.bh-quiet .bh-grow-y,
+.bh-quiet .bh-heat .c,
+.bh-quiet .bh-fade-late,
+.bh-quiet .bh-orbit .sat {
+  animation: 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 board's own nudges, removed rather than shortened — a chip that lifts
+     under the pointer is an affordance, and a fast lift is still a lift. The
+     border and box-shadow changes stay: THEY are what says where a drop lands,
+     and a drop marker carried by motion alone would not exist here at all. */
+  .hk-chip:hover:not(.hk-chip-dragging), .hk-add:hover:not(:disabled),
+  button.hk-pick-row: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; }
+  /* The Knowledge ▸ Code graph tab (v1.9.2). Three INFINITE animations — the
+     state beacon, the pipeline dots and the call-edge pulses — are REMOVED, not
+     capped: a capped one stops half way along its path, which reads as a dot
+     that belongs there. Every finite one is removed too, so each bar is drawn
+     at its final width at once: a bar frozen part-way is a wrong number. The
+     tiles already skip their count-up here (cgStill() in the panel). */
+  .cg-beacon, .cg-link-dot, .cg-pulse { display: none; }
+  .cg-step, .cg-step-line, .cg-station, .cg-file, .cg-sym, .cg-edge-line,
+  .cg-seg, .cg-tile, .cg-bchip, .cg-lang, .cg-read, .cg-gloss-group { animation: none !important; }
+  .cg-station:hover { transform: none !important; }
+  /* The Behaviour panel (v2.0.0 W7). The orbit satellites are REMOVED, not
+     capped. A line that draws itself ends drawn: a 1 ms cap on a `forwards`
+     fill could still leave it undrawn for a frame, so its end state is forced.
+     The card lift is removed outright, like every other hover nudge. */
+  .bh-orbit .sat { display: none; }
+  .bh-draw { stroke-dashoffset: 0 !important; }
+  .bh-habit:hover { transform: none !important; }
+}