@celestia-island/hikari 0.55.156 → 0.55.158

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@celestia-island/hikari",
-  "version": "0.55.156",
+  "version": "0.55.158",
   "private": false,
   "type": "module",
   "description": "Hikari Vue 3 component library — production-grade UI components based on shittim-chest design system",

package/src/animation/registerAnimations.ts

@@ -108,7 +108,6 @@ registerCssAnimation("hk-picker-pane-back-out");
 // once; keyframes ride the component's inline <style>).
 registerCssAnimation("hk-flip-out");
 registerCssAnimation("hk-flip-in");
-// components/HkVoiceInputPopup.scss — voice waveform bounce (loops
 // forever while listening; upstreamed from chest's plana-legacy).
 // components/HkPlaceholderMarquee.scss — overflowing placeholder sweep
 // (loops forever; pure CSS, loop geometry on inline custom properties).

package/src/components/HkMarkdownRenderer.scss

@@ -137,7 +137,7 @@
 }
 
 /* Rendered GFM links are real anchors — keyboard-focusable, so they need
-   the house :focus-visible ring (HkFab/HkContextRing pattern). Ring uses
+   the house :focus-visible ring (HkFab house pattern). Ring uses
    the same contract var as the link ink so it matches in every theme. */
 .hk-markdown a:focus-visible {
   outline: 2px solid var(--hi-color-primary, #7aa2f7);

package/src/components/HkPopover.scss

@@ -205,7 +205,7 @@
  * long-press selected it; every other window in the app carries an ✕).
  * The title aligns to the CONTENT edge: the leading inset defaults to
  * --space-12, matching the padded content blocks popover sheets host
- * (e.g. HkContextRing's 0.75rem body). Hosts tune it via
+ * (e.g. the house 0.75rem popover body). Hosts tune it via
  * --hk-sheet-title-inset; the trailing inset hugs the close button. */
 .hk-popover-sheet-header {
   flex-shrink: 0;

package/src/components/HkProgressBar.scss

@@ -135,7 +135,7 @@
   }
 
   // Width is a size animation — progress steps snap instead of animating
-  // (house guard: HkTokenUsagePanel's bar fill).
+  // (house guard: the family bar-fill pattern).
   .hk-progress-bar-fill,
   .hk-progress-bar-secondary,
   .hk-progress-bar-seg {

package/src/components/HkScrollContainer.test.ts

@@ -404,7 +404,7 @@ describe("HkScrollContainer back-to-top signal", () => {
 });
 
 describe("HkScrollContainer change-mark rail", () => {
-  it("renders the marks prop, and re-applies new marks without rebuilding the chrome", async () => {
+  it("widens the track, renders the marks prop, and re-applies them without rebuilding", async () => {
     const markers = ref<OverlayScrollbarMarker[]>([{ start: 0.1, end: 0.2, kind: "added" }]);
     const container = document.createElement("div");
     document.body.appendChild(container);
@@ -419,9 +419,11 @@ describe("HkScrollContainer change-mark rail", () => {
     mounts.push(app);
     app.mount(container);
 
-    const rail = () => container.querySelector<HTMLElement>(".hk-scrollbar-markers");
+    // The marks live INSIDE the vertical track: the rail IS the track.
+    const rail = () => container.querySelector<HTMLElement>(".hk-scrollbar-track:not([data-axis='horizontal'])");
     const firstRail = rail();
-    expect(firstRail, "the rail exists once marks arrive").not.toBeNull();
+    expect(firstRail, "the track exists once marks arrive").not.toBeNull();
+    expect(firstRail!.classList.contains("has-markers"), "the track widens for marks").toBe(true);
     expect(firstRail!.querySelectorAll(".hk-scrollbar-marker").length).toBe(1);
 
     markers.value = [
@@ -438,8 +440,10 @@ describe("HkScrollContainer change-mark rail", () => {
     app.unmount();
   });
 
-  it("keeps the rail out of the DOM when no marks are passed", () => {
+  it("keeps the narrow track and no marks when none are passed", () => {
     const m = mountScroller({});
-    expect(m.container.querySelector(".hk-scrollbar-markers")).toBeNull();
+    const track = m.container.querySelector<HTMLElement>(".hk-scrollbar-track:not([data-axis='horizontal'])");
+    expect(track?.classList.contains("has-markers") ?? false, "no widening").toBe(false);
+    expect(track?.querySelectorAll(".hk-scrollbar-marker").length ?? 0).toBe(0);
   });
 });

package/src/components/HkScrollContainer.tsx

@@ -52,6 +52,9 @@ export default defineComponent({
      *  it out renders exactly the chrome this container had before the
      *  rail existed. */
     markers: { type: Array as PropType<OverlayScrollbarMarker[]>, default: () => [] },
+    /** Width the vertical track widens to while marks show, in px. Omitted
+     *  = the library default (14). Only read when `markers` is non-empty. */
+    markersWidth: { type: Number, default: undefined },
     autoFollow: { type: Boolean, default: false },
     overscanScreens: { type: Number, default: 1 },
     /** Inline-axis alignment of the content when it fits the viewport.
@@ -271,7 +274,7 @@ export default defineComponent({
       const vp = viewportRef.value;
       if (!vp) return;
       overlay?.detach();
-      overlay = attachOverlayScrollbars(vp, { axis: props.axis, markers: props.markers });
+      overlay = attachOverlayScrollbars(vp, { axis: props.axis, markers: props.markers, markersWidth: props.markersWidth });
     }
 
     /** Re-apply marks without rebuilding the chrome: a diff re-renders its

package/src/components/HkStatCard.tsx

@@ -104,7 +104,7 @@ export const HkStatCard = defineComponent({
         tabindex: props.clickable ? 0 : undefined,
         onClick: props.clickable ? (e: MouseEvent) => emit("click", e) : undefined,
         // role="button" promises keyboard activation (Enter/Space) — the
-        // same contract HkContextRing's clickable ring honors. Key events
+        // same contract the house clickable-ring convention honors. Key events
         // bubbling from a focusable INSIDE the card (an aside button) are
         // left alone so they don't double-fire the card's click.
         onKeydown: props.clickable

package/src/components/HkTag.scss

@@ -51,7 +51,7 @@
   opacity: 1;
 }
 
-/* Keyboard focus indicator (house HkContextRing pattern). */
+/* Keyboard focus indicator (house focus-ring pattern). */
 .hk-tag-close:focus-visible {
   outline: 2px solid rgb(var(--color-primary));
   outline-offset: 2px;

package/src/components/HkTimeline.scss

@@ -416,7 +416,7 @@
   cursor: pointer;
 
   // Keyboard parity: the tsx gives completed steps role="button" +
-  // tabindex 0 (HkContextRing outer-ring pattern).
+  // tabindex 0 (house outer-ring pattern).
   &:focus-visible {
     outline: 2px solid var(--hi-color-primary);
     outline-offset: 2px;

package/src/components/overlayScrollbarChrome.contract.test.ts

@@ -71,43 +71,58 @@ describe("overlay scrollbar chrome contract", () => {
     expect(chrome).toMatch(/&?\.is-scrolling,\s*&?\.is-hovering\s*\{[^}]*pointer-events:\s*auto/);
   });
 
-  it("keeps the change-mark rail clear of the track and out of the click path", () => {
-    // The rail is a SECOND overlay in the same corner. Two facts have to
-    // survive any future restyle:
+  it("widens the track into the ruler and keeps the click rules straight", () => {
+    // The marks live INSIDE the track, which widens only when it carries
+    // them (`.has-markers`) — VS Code's overview ruler is the scrollbar's
+    // own strip widened, not a second strip. Three facts must survive any
+    // future restyle:
     //
-    //  1. It must not overlap the track (right 2px + width 6px), or marks
-    //     would draw across the thumb;
-    //  2. it must not take pointer input — it spans the WHOLE host, docks
-    //     included, so a live hot zone there eats presses meant for
-    //     right-aligned dock controls. Only the marks accept input, and
-    //     that exemption is exactly why the rail itself must stay `none`.
-    // The vertical geometry lives in the track's own nested
-    // `&:not([data-axis="horizontal"])` block, not a top-level selector.
-    const track = /&:not\(\[data-axis="horizontal"\]\)\s*\{[^}]*\}/.exec(chrome)?.[0] ?? "";
-    expect(track, "positive control: the vertical track rule was found").not.toBe("");
-    const trackRight = Number(/right:\s*(\d+)px/.exec(track)?.[1]);
-    const trackWidth = Number(/width:\s*(\d+)px/.exec(track)?.[1]);
+    //  1. The widened ground is FAINT and theme-adaptive (a translucent
+    //     mid-grey: grey over a light page, slightly lighter over a dark
+    //     one), with the 2px rounding the band promised;
+    //  2. it stays pointer-transparent AT REST — the widened band spans
+    //     the whole host, docks included, and a live hot zone there would
+    //     eat presses meant for right-aligned dock controls;
+    //  3. the MARKS are the hit area and hug the band's edges: removed
+    //     content at the start, added at the end (VS Code's two lanes),
+    //     so one vertical position can carry both.
+    expect(chrome, "no second strip — the separate rail is gone").not.toContain(".hk-scrollbar-markers");
 
-    const rail = /\.hk-scrollbar-markers\s*\{[^}]*\}/.exec(chrome)?.[0] ?? "";
-    expect(rail, "positive control: the rail rule was found").not.toBe("");
-    const railRight = Number(/right:\s*(\d+)px/.exec(rail)?.[1]);
-    const railWidth = Number(/width:\s*(\d+)px/.exec(rail)?.[1]);
-
-    expect(
-      railRight,
-      "the rail starts outboard of the track's inner edge",
-    ).toBeGreaterThanOrEqual(trackRight + trackWidth);
-    expect(railRight + railWidth, "and stays inside the host").toBeLessThanOrEqual(24);
+    const widened = /&\.has-markers:not\(\[data-axis="horizontal"\]\)\s*\{[^}]*\}/.exec(chrome)?.[0] ?? "";
+    expect(widened, "positive control: the widened-band rule was found").not.toBe("");
+    expect(widened, "the ground is faint (translucent grey)").toMatch(
+      /color-mix\(in srgb,\s*var\(--hi-color-muted,\s*rgb\(118 122 128\)\)\s*\d+%,\s*transparent\)/,
+    );
+    expect(widened, "the band keeps its 2px rounding").toMatch(/border-radius:\s*2px/);
+    expect(widened, "and a parameterised width the engine overrides").toMatch(/width:\s*\d+px/);
+    // The base track's own pointer contract (pinned above) is untouched;
+    // the widened rule must not sneak a `pointer-events: auto` in.
+    expect(widened).not.toMatch(/pointer-events:\s*auto/);
 
-    expect(rail, "the rail itself takes no pointer input").toMatch(/pointer-events:\s*none/);
-    const marker = /\.hk-scrollbar-marker\s*\{[^}]*\}/.exec(chrome)?.[0] ?? "";
-    expect(marker, "positive control: the mark rule was found").not.toBe("");
-    expect(marker, "the marks are the hit area").toMatch(/pointer-events:\s*auto/);
-    // The hover ring must be drawn INSIDE the mark: the rail clips its
+    // The mark's whole rule (it is the file's last block, and its nested
+    // lanes/hover/kind blocks make a single-block regex fragile).
+    const markerBlock = chrome.slice(chrome.indexOf(".hk-scrollbar-marker {"));
+    expect(markerBlock, "positive control: the mark rule was found").not.toBe("");
+    expect(markerBlock, "the marks are the hit area").toMatch(/pointer-events:\s*auto/);
+    expect(markerBlock, "the band's 2px rounding reaches the marks").toMatch(/border-radius:\s*2px/);
+    // The two lanes, at the band's edges (the rules nest inside the mark
+    // selector, so they are written `&[data-side=…]`).
+    expect(markerBlock).toMatch(/&\[data-side="start"\]\s*\{[^}]*left:\s*0/);
+    expect(markerBlock).toMatch(/&\[data-side="end"\]\s*\{[^}]*right:\s*0/);
+    // …and their WIDTH: a restyle that silently stretched a lane across
+    // the whole band would collapse the two-lane reading into one strip
+    // (caught only by the vendored-sync byte comparison before this pin).
+    expect(markerBlock, "the start lane hugs a third of the band").toMatch(
+      /&\[data-side="start"\]\s*\{[^}]*width:\s*34%/,
+    );
+    expect(markerBlock, "and the end lane the other third").toMatch(
+      /&\[data-side="end"\]\s*\{[^}]*width:\s*34%/,
+    );
+    // The hover ring must be drawn INSIDE the mark: the track clips its
     // children, and a plain outline loses both side strokes to that clip,
     // leaving a two-line "ring" that reads as a stray rule rather than a
     // hover cue. Nothing else would notice that regression.
-    expect(marker, "the hover ring is drawn inside the mark").toMatch(
+    expect(markerBlock, "the hover ring is drawn inside the mark").toMatch(
       /outline-offset:\s*-1px/,
     );
   });

package/src/composables/useOverlayScrollbar.test.ts

@@ -1,3 +1,6 @@
+import { readFileSync } from "node:fs";
+import { dirname, resolve } from "node:path";
+import { fileURLToPath } from "node:url";
 import { afterEach, describe, expect, it, vi } from "vitest";
 
 import { attachOverlayScrollbars, type OverlayScrollbarHandle, type OverlayScrollbarOptions } from "./useOverlayScrollbar";
@@ -23,10 +26,11 @@ function mountViewport(
   return { container, wrapper, viewport, handle };
 }
 
-/** A scrollable vertical viewport with a deterministic 100px rail box:
- *  happy-dom performs no layout, so both the geometry and the rail's
- *  bounding box are stubbed. `height` of the rail is what maps a mark's
- *  fraction to a pixel position. */
+/** A scrollable vertical viewport with a deterministic band box: happy-dom
+ *  performs no layout, so both the geometry and the track's bounding box
+ *  are stubbed. `height` of the band is what maps a mark's fraction to a
+ *  pixel position. The marks live INSIDE the vertical track (the widened
+ *  scrollbar is the ruler), so "the rail" below IS the track. */
 function mountRailed(railHeight = 100) {
   const mounted = mountViewport("vertical");
   stubGeometry(mounted.viewport, {
@@ -37,12 +41,13 @@ function mountRailed(railHeight = 100) {
   return {
     ...mounted,
     rail: () => {
-      const el = mounted.wrapper.querySelector<HTMLElement>(".hk-scrollbar-markers");
+      const el = mounted.wrapper.querySelector<HTMLElement>(".hk-scrollbar-track:not([data-axis='horizontal'])");
       if (el) {
         vi.spyOn(el, "getBoundingClientRect").mockReturnValue({
-          top: 0, left: 0, width: 8, height: railHeight,
-          bottom: railHeight, right: 8, x: 0, y: 0, toJSON: () => ({}),
+          top: 0, left: 0, width: 14, height: railHeight,
+          bottom: railHeight, right: 14, x: 0, y: 0, toJSON: () => ({}),
         } as DOMRect);
+        Object.defineProperty(el, "clientHeight", { configurable: true, get: () => railHeight });
       }
       return el;
     },
@@ -354,9 +359,11 @@ describe("attachOverlayScrollbars", () => {
 });
 
 describe("change-mark rail", () => {
-  it("renders no rail at all when the consumer passes no markers", () => {
+  it("keeps the narrow track, unmarked, when the consumer passes no markers", () => {
     const { wrapper } = mountViewport("vertical");
-    expect(wrapper.querySelector(".hk-scrollbar-markers")).toBeNull();
+    const track = wrapper.querySelector<HTMLElement>(".hk-scrollbar-track:not([data-axis='horizontal'])");
+    expect(track?.classList.contains("has-markers") ?? false, "no widening").toBe(false);
+    expect(track?.querySelectorAll(".hk-scrollbar-marker").length ?? 0).toBe(0);
   });
 
   it("creates the rail and one mark per entry, tagged by kind", () => {
@@ -439,6 +446,79 @@ describe("change-mark rail", () => {
     expect(mark.style.height).toBe("60%");
   });
 
+  it("honours the consumer's markersWidth, clamped to a sane band", () => {
+    const m = mountRailed();
+    m.handle.setMarkers([{ start: 0.1, end: 0.2, kind: "added" }]);
+    const width = () => m.rail()!.style.width;
+    // The default band, then the consumer's own, then the clamps.
+    expect(width()).toBe("14px");
+    m.handle.detach();
+    handles.splice(handles.indexOf(m.handle), 1);
+
+    const custom = mountViewport("vertical", { markers: [{ start: 0.1, end: 0.2, kind: "added" }], markersWidth: 22 });
+    custom.handle.update();
+    expect(
+      custom.wrapper.querySelector<HTMLElement>(".hk-scrollbar-track:not([data-axis='horizontal'])")!.style.width,
+    ).toBe("22px");
+    custom.handle.detach();
+    handles.splice(handles.indexOf(custom.handle), 1);
+
+    const clamped = mountViewport("vertical", { markers: [{ start: 0.1, end: 0.2, kind: "added" }], markersWidth: 999 });
+    clamped.handle.update();
+    expect(
+      clamped.wrapper.querySelector<HTMLElement>(".hk-scrollbar-track:not([data-axis='horizontal'])")!.style.width,
+      "above the 40px ceiling it clamps").toBe("40px");
+  });
+
+  it("mirrors side onto data-side so the lanes can be styled", () => {
+    const m = mountRailed();
+    m.handle.setMarkers([
+      { start: 0.1, end: 0.2, kind: "deleted", side: "start" },
+      { start: 0.1, end: 0.2, kind: "added", side: "end" },
+      { start: 0.5, end: 0.6, kind: "modified" },
+    ]);
+    const marks = m.rail()!.querySelectorAll<HTMLElement>(".hk-scrollbar-marker");
+    expect(marks[0].getAttribute("data-side")).toBe("start");
+    expect(marks[1].getAttribute("data-side")).toBe("end");
+    expect(marks[2].getAttribute("data-side"), "no side = full band").toBeNull();
+  });
+
+  it("does not scrub on a press on the band's empty ground", () => {
+    const m = mountRailed();
+    m.handle.setMarkers([{ start: 0.3, end: 0.35, kind: "added" }]);
+    stubGeometry(m.viewport, {
+      scrollHeight: 1000, clientHeight: 100, scrollTop: 0,
+      scrollWidth: 100, clientWidth: 100, scrollLeft: 0,
+    });
+    // A press on the TRACK (not on a mark) keeps the track's own
+    // click-to-page behaviour: no scrub, no drag state.
+    const track = m.rail()!;
+    track.dispatchEvent(new MouseEvent("mousedown", { bubbles: true, cancelable: true, clientY: 0 }));
+    expect(track.classList.contains("is-dragging"), "no drag state").toBe(false);
+    document.dispatchEvent(new MouseEvent("mousemove", { clientY: 100 }));
+    expect(m.viewport.scrollTop, "no scrub followed the pointer").toBe(0);
+    document.dispatchEvent(new MouseEvent("mouseup"));
+  });
+
+  it("keeps the band and its marks visible at rest (an overview ruler is a glance)", () => {
+    const m = mountRailed();
+    m.handle.setMarkers([{ start: 0.1, end: 0.2, kind: "added" }]);
+    // The track is pointer-transparent at rest, but the widened band and
+    // its marks must still SHOW: hiding them made the ruler a hover-only
+    // affordance, which is exactly what an overview ruler is not.
+    // happy-dom does not apply stylesheets to computed styles, so this
+    // pins the rule in the shipped chrome (the vendored copy) instead.
+    const chrome = readFileSync(
+      resolve(dirname(fileURLToPath(import.meta.url)), "../styles/theme/scrollbar.scss"),
+      "utf-8",
+    );
+    const widened = /&\.has-markers:not\(\[data-axis="horizontal"\]\)\s*\{[^}]*\}/.exec(chrome)?.[0] ?? "";
+    expect(widened, "positive control: the widened rule was found").not.toBe("");
+    expect(widened, "the band is visible at rest").toMatch(/opacity:\s*1/);
+    // …and the thumb rides above it.
+    expect(chrome).toMatch(/\.hk-scrollbar-thumb\s*\{[^}]*z-index:\s*2/);
+  });
+
   it("positions marks against the content, so scrolling does not move them", () => {
     const m = mountRailed();
     m.handle.setMarkers([{ start: 0.25, end: 0.3, kind: "added" }]);
@@ -458,7 +538,9 @@ describe("change-mark rail", () => {
     m.handle.setMarkers([{ start: 0.1, end: 0.2, kind: "added" }]);
     expect(m.rail()).not.toBeNull();
     m.handle.setMarkers([]);
-    expect(m.wrapper.querySelector(".hk-scrollbar-markers")).toBeNull();
+    const track = m.wrapper.querySelector<HTMLElement>(".hk-scrollbar-track:not([data-axis='horizontal'])");
+    expect(track?.classList.contains("has-markers") ?? false, "the widening is undone").toBe(false);
+    expect(track?.querySelectorAll(".hk-scrollbar-marker").length ?? 0).toBe(0);
   });
 
   it("hides the rail while the content fits, and shows it again when it scrolls", () => {
@@ -486,7 +568,9 @@ describe("change-mark rail", () => {
     });
     m.handle.update();
     m.handle.setMarkers([{ start: 0.1, end: 0.2, kind: "added" }]);
-    expect(m.wrapper.querySelector(".hk-scrollbar-markers")).toBeNull();
+    const hTrack = m.wrapper.querySelector<HTMLElement>('.hk-scrollbar-track[data-axis="horizontal"]');
+    expect(hTrack?.classList.contains("has-markers") ?? false, "no band on a horizontal track").toBe(false);
+    expect(hTrack?.querySelectorAll(".hk-scrollbar-marker").length ?? 0).toBe(0);
   });
 
   it("ignores non-finite mark bounds instead of parking them at NaN%", () => {
@@ -556,7 +640,7 @@ describe("change-mark rail", () => {
     mark.dispatchEvent(new MouseEvent("mousedown", { bubbles: true, clientY: 0 }));
     m.handle.detach();
     handles.splice(handles.indexOf(m.handle), 1);
-    expect(m.wrapper.querySelector(".hk-scrollbar-markers")).toBeNull();
+    expect(m.wrapper.querySelectorAll(".hk-scrollbar-marker").length).toBe(0);
     m.viewport.scrollTop = 0;
     document.dispatchEvent(new MouseEvent("mousemove", { clientY: 100 }));
     expect(m.viewport.scrollTop, "detach dropped the drag listener").toBe(0);
@@ -568,6 +652,6 @@ describe("change-mark rail", () => {
     m.handle.detach();
     handles.splice(handles.indexOf(m.handle), 1);
     expect(() => m.handle.setMarkers([{ start: 0, end: 1, kind: "added" }])).not.toThrow();
-    expect(m.wrapper.querySelector(".hk-scrollbar-markers")).toBeNull();
+    expect(m.wrapper.querySelectorAll(".hk-scrollbar-marker").length).toBe(0);
   });
 });

package/src/composables/useOverlayScrollbar.ts

@@ -51,6 +51,13 @@ export interface OverlayScrollbarMarker {
   /** Semantic tag mirrored onto `data-kind`, so the consumer's theme owns
    *  the palette (this engine ships no colours of its own). */
   kind?: string;
+  /**
+   * Which third of the band the mark hugs — VS Code's diff overview ruler
+   * draws REMOVED content against the band's start edge and ADDED content
+   * against its end edge, so one vertical position can carry both. Omitted
+   * = the mark spans the full band width.
+   */
+  side?: "start" | "end";
 }
 
 /** Shortest a mark may render, as a fraction of the rail. A one-line edit
@@ -66,6 +73,11 @@ const MARKER_MIN_FRACTION = 0.005;
  *  from the SAME number, which CSS cannot express. */
 const MARKER_MIN_PX = 2;
 
+/** Width the vertical track widens to when marks arrive, unless the
+ *  consumer passes its own. VS Code's scrollbar strip is ~14px; the
+ *  default keeps the marks' two lanes readable at a glance. */
+const DEFAULT_MARKERS_WIDTH = 14;
+
 /** Clamp to [0, 1]; non-finite input is the caller's bug, but the rail
  *  must never render a mark at a meaningless position, so it becomes 0. */
 function clamp01(n: number): number {
@@ -98,6 +110,10 @@ export interface OverlayScrollbarOptions {
    *  "position in the document". Omitted or empty creates no rail at all,
    *  so consumers that never pass markers keep the exact chrome they had. */
   markers?: OverlayScrollbarMarker[];
+  /** Width the vertical track widens to while marks are showing, in CSS
+   *  pixels. Selective: consumers without marks keep the narrow track.
+   *  Clamped to a sane range (the thumb and marks share the band). */
+  markersWidth?: number;
 }
 
 export interface OverlayScrollbarHandle {
@@ -216,22 +232,27 @@ export function attachOverlayScrollbars(
   let detached = false;
 
   // ── Change-mark rail (vertical only) ─────────────────────────────────
-  // Created lazily on the first non-empty marker list: consumers that
-  // never pass markers keep byte-identical chrome, and the rail's own
-  // listeners exist only while the rail does.
-  let rail: HTMLElement | null = null;
+  // The marks live INSIDE the vertical track, which widens to
+  // `markersWidth` for as long as marks are showing (VS Code's overview
+  // ruler is a widening of the same strip, not a second one). Consumers
+  // that never pass markers keep byte-identical chrome.
+  let track: HTMLElement | null = null;
   let markers: OverlayScrollbarMarker[] = [];
   let railDragging = false;
   /** Rail height the marks were last sized against — the pixel floor is a
    *  function of it, so a resize has to re-render them. */
   let renderedRailHeight = 0;
 
+  /** The vertical track, found once and reused. */
+  const verticalTrack = (): HTMLElement | null =>
+    states.find((s) => !s.horizontal)?.track ?? null;
+
   /** Scroll so the rail position under `clientY` lands in the viewport —
    *  the same fraction → scrollTop mapping the track's own click uses, so
    *  a mark and the track at the same height agree. */
   function railScrollTo(clientY: number) {
-    if (!rail) return;
-    const rect = rail.getBoundingClientRect();
+    if (!track) return;
+    const rect = track.getBoundingClientRect();
     if (rect.height <= 0) return;
     const ratio = clamp01((clientY - rect.top) / rect.height);
     const { scrollSize, clientSize } = axisMetrics(viewport, false);
@@ -243,28 +264,34 @@ export function attachOverlayScrollbars(
   }
   function onRailUp() {
     railDragging = false;
-    rail?.classList.remove("is-dragging");
+    track?.classList.remove("is-dragging");
     document.removeEventListener("mousemove", onRailMove);
     document.removeEventListener("mouseup", onRailUp);
   }
   function onRailDown(e: MouseEvent) {
+    // Only a press ON a mark scrubs: the rest of the band keeps the
+    // track's own click-to-page behaviour.
+    const mark = (e.target as Element | null)?.closest?.(".hk-scrollbar-marker");
+    if (!mark) return;
     e.preventDefault();
-    // The rail sits inside a modal/panel that may itself dismiss on an
-    // outside press — scrubbing the rail must not double as that press.
+    // The band rides inside modals/panels that may dismiss on an outside
+    // press — scrubbing a mark must not double as that press.
     e.stopPropagation();
     railDragging = true;
-    rail?.classList.add("is-dragging");
+    track?.classList.add("is-dragging");
     railScrollTo(e.clientY);
     document.addEventListener("mousemove", onRailMove);
     document.addEventListener("mouseup", onRailUp);
   }
 
   function renderMarkers() {
-    if (!rail) return;
-    rail.replaceChildren();
+    if (!track) return;
+    // The thumb is a sibling that must stay on top of the marks (it slides
+    // over them, VS Code's semi-transparent thumb over the ruler).
+    track.querySelectorAll(":scope > .hk-scrollbar-marker").forEach((m) => m.remove());
     // Measured, not assumed: happy-dom and a `display:none` rail both
     // report 0, and the fraction floor is the honest answer there.
-    const railH = rail.clientHeight;
+    const railH = track.clientHeight;
     renderedRailHeight = railH;
     const floor = railH > 0
       ? Math.max(MARKER_MIN_FRACTION, MARKER_MIN_PX / railH)
@@ -283,12 +310,28 @@ export function attachOverlayScrollbars(
       const el = document.createElement("div");
       el.className = "hk-scrollbar-marker";
       if (m.kind) el.setAttribute("data-kind", m.kind);
+      if (m.side) el.setAttribute("data-side", m.side);
       el.style.top = pct(top);
       el.style.height = pct(size);
-      rail.appendChild(el);
+      track.appendChild(el);
     }
   }
 
+  /** Widen the track to the markers width (and back when they go away). */
+  function applyBandWidth() {
+    if (!track) return;
+    if (markers.length === 0) {
+      track.classList.remove("has-markers");
+      track.style.width = "";
+      return;
+    }
+    track.classList.add("has-markers");
+    const w = Math.round(
+      Math.min(Math.max(opts.markersWidth ?? DEFAULT_MARKERS_WIDTH, 8), 40),
+    );
+    track.style.width = `${w}px`;
+  }
+
   // An arrow const, not a function declaration: the guard above narrows
   // `parent` to non-null, and only a closure created AFTER that narrowing
   // keeps it (a hoisted declaration may run at any time, so TS widens the
@@ -296,40 +339,35 @@ export function attachOverlayScrollbars(
   const setMarkers = (next: OverlayScrollbarMarker[]) => {
     if (detached) return;
     markers = Array.isArray(next) ? next : [];
+    track = verticalTrack();
     if (markers.length === 0) {
-      // No marks = no rail, i.e. exactly the pre-marker chrome.
-      if (rail) {
-        rail.removeEventListener("mousedown", onRailDown);
-        rail.remove();
-        rail = null;
-      }
+      // No marks = exactly the pre-marker chrome.
+      track?.querySelectorAll(":scope > .hk-scrollbar-marker").forEach((m) => m.remove());
+      applyBandWidth();
       onRailUp();
       return;
     }
-    if (!wantV) return;
-    if (!rail) {
-      rail = document.createElement("div");
-      rail.className = "hk-scrollbar-markers";
-      rail.addEventListener("mousedown", onRailDown);
-      parent.appendChild(rail);
+    if (!wantV || !track) return;
+    if (!track.dataset.markersWired) {
+      track.dataset.markersWired = "true";
+      track.addEventListener("mousedown", onRailDown);
     }
+    applyBandWidth();
     renderMarkers();
-    // The rail's visibility follows the track's fit test.
+    // The marks' visibility follows the track's own fit test.
     update();
   };
 
   function updateAxis(s: AxisState, horizontal: boolean) {
     const { scrollSize, clientSize, scrollPos } = axisMetrics(viewport, horizontal);
     if (scrollSize <= clientSize) {
-      // Content fits — no bar at all. The rail follows the track: marks on
-      // a region that cannot scroll would claim changes the reader can
-      // never reach.
+      // Content fits — no bar at all. The marks live inside the track, so
+      // hiding it hides them too: marks on a region that cannot scroll
+      // would claim changes the reader can never reach.
       s.track.style.display = "none";
-      if (!horizontal && rail) rail.style.display = "none";
       return;
     }
     s.track.style.display = "";
-    if (!horizontal && rail) rail.style.display = "";
     const trackSize = horizontal ? s.track.clientWidth : s.track.clientHeight;
     const ratio = clientSize / scrollSize;
     const thumbSize = Math.max(ratio * trackSize, 20);
@@ -354,13 +392,14 @@ export function attachOverlayScrollbars(
   function update() {
     if (detached) return;
     for (const s of states) updateAxis(s, s.horizontal);
-    // The marks' pixel floor is a fraction OF the rail, so a height change
-    // invalidates the sizes they were rendered with. A hidden rail reports
+    // The marks' pixel floor is a fraction OF the band, so a height change
+    // invalidates the sizes they were rendered with. A hidden band reports
     // 0 and is skipped here; `renderMarkers` leaves that 0 behind as its
     // "never sized against a real height" sentinel, so the first visible
     // update re-renders even when the height matches the last one used.
-    const railH = rail?.clientHeight ?? 0;
-    if (rail && markers.length > 0 && railH > 0 && railH !== renderedRailHeight) {
+    const band = verticalTrack();
+    const railH = band?.clientHeight ?? 0;
+    if (band && markers.length > 0 && railH > 0 && railH !== renderedRailHeight) {
       renderMarkers();
     }
   }
@@ -480,17 +519,14 @@ export function attachOverlayScrollbars(
       ro = null;
       scheduled?.disconnect();
       scheduled = null;
-      if (rail) {
-        rail.removeEventListener("mousedown", onRailDown);
-        rail.remove();
-        rail = null;
-      }
       onRailUp();
       for (const { state, handlers } of axisBindings) {
         state.thumb.removeEventListener("mousedown", handlers.onDown);
         state.track.removeEventListener("click", handlers.onTrackClick);
         state.track.removeEventListener("mouseenter", handlers.onEnter);
         state.track.removeEventListener("mouseleave", handlers.onLeave);
+        state.track.removeEventListener("mousedown", onRailDown);
+        delete state.track.dataset.markersWired;
         document.removeEventListener("mousemove", handlers.onMove);
         document.removeEventListener("mouseup", handlers.onUp);
         state.hideTimer?.disconnect();

package/src/index.ts

@@ -549,15 +549,12 @@ export {
 export { HK_ENGINE_HEALTH } from "./components/HkConnectionStatus";
 export type { ProbeResult, EngineHealth, EngineNetworkInfo } from "./composables/engineHealthTypes";
 
-// ── Chat kit (upstreamed from shittim-chest's plana-legacy layer) ──────────
+// ── JSON viewer & shared formatters ──
 export {
   HkJsonTree as HJsonTree,
   buildJsonTree,
   type HJsonNode,
 } from "./components/HkJsonTree";
-// Canonical Hk* names for the directly-exported types above (2026-09-24
-// unification follow-up, second batch — caught by the third-scan reverse
-// validation). These types are defined with their H* names at the source.
 
 export {
   formatNumber,

package/src/styles/theme/channels.scss

@@ -7,7 +7,7 @@
 
 /* ── Syntax highlighting palette family: --code-* ───────────────────
  * Token names consumed by hikari's highlighted-code surfaces (the
- * HkToolBlock syntax layer and its JSON viewer, see HkToolBlock.scss).
+ * The JSON-viewer syntax layer and its theme channels (HkJsonTree).
  * The VALUES are intentionally NOT defined here: the family is owned by
  * the host theme, which maps each token to mode-aware colors. The
  * canonical mapping (dark = One Dark, light = GitHub Light) lives in the

package/src/styles/theme/scrollbar.scss

@@ -51,6 +51,31 @@
     opacity: 1;
     pointer-events: auto;
   }
+
+  /* ── The widened band (marks showing) ───────────────────────────────
+     VS Code's overview ruler is the scrollbar's own strip WIDENED, not a
+     second strip beside it. Selective: only a track carrying marks gets
+     the width, the faint ground and the rounding.
+     The ground is a translucent mid-grey — over a light page it reads as
+     a faint grey, over a dark one as slightly lighter than the page, so
+     one declaration serves both modes (the muted token does not flip). */
+  &.has-markers:not([data-axis="horizontal"]) {
+    width: 14px; /* the engine overrides this inline with markersWidth */
+    border-radius: 2px;
+    background: color-mix(in srgb, var(--hi-color-muted, rgb(118 122 128)) 12%, transparent);
+    /* The band and its marks are ALWAYS visible — the whole point of an
+       overview ruler is a glance, not a hover. The track itself stays
+       `pointer-events: none` (below), so the ground still never steals a
+       press; only the marks accept input. */
+    opacity: 1;
+  }
+}
+
+/* The thumb rides OVER the marks (VS Code's translucent thumb over the
+   ruler): without a z-index of its own it would paint UNDER the opaque
+   marks, which are appended after it in the same stacking context. */
+.hk-scrollbar-thumb {
+  z-index: 2;
 }
 
 .hk-scrollbar-thumb {
@@ -84,65 +109,48 @@
   min-height: 20px;
 }
 
-/* ── Change-mark rail (VS Code's overview ruler) ──────────────────────
-   Rendered only when a consumer passes `markers` to
-   attachOverlayScrollbars (HkScrollContainer's `markers` prop), so every
-   existing consumer's chrome above is unchanged. It sits immediately
-   inboard of the vertical track — the two together read as one thick
-   marked scrollbar — and carries no chrome of its own beyond a faint
-   groove: the marks are the content. */
-.hk-scrollbar-markers {
-  position: absolute;
-  z-index: 11;
-  top: 4px;
-  bottom: 4px;
-  /* Vertical track: right 2px + width 6px → occupies 2–8px; a 2px gutter
-     puts the rail at 10px. The contract test pins this non-overlap. */
-  right: 10px;
-  width: 8px;
-  border-radius: 4px;
-  background: color-mix(in srgb, var(--hi-color-muted, rgb(118 122 128)) 18%, transparent);
-  overflow: hidden;
-  transition: background var(--hi-duration-fast, 0.15s) ease;
-
-  /* Pointer-transparent, exactly like the track above and for the same
-     reason: an overlay hugging the region's edge must never steal a press
-     meant for the content beneath it — and this rail spans the WHOLE host,
-     docks included, so it sits over right-aligned dock controls too. Only
-     the MARKS take input (see below): they are the targets that mean
-     something, and they are the rail's entire content. */
-  pointer-events: none;
-
-  &.is-dragging {
-    background: color-mix(in srgb, var(--hi-color-muted, rgb(118 122 128)) 32%, transparent);
-  }
-}
-
-/* One mark. `data-kind` is whatever tag the consumer passed; the three
-   diff kinds get the diff palette, anything else the neutral muted one.
-   The fallbacks mirror the thumb's: a themeless standalone render must
-   still show marks rather than an invalid-at-computed-value-time
-   transparent.
+/* ── Change marks (VS Code's overview ruler) ──────────────────────────
+   The marks live INSIDE the widened track (`.hk-scrollbar-track.has-markers`
+   above), so the scrollbar itself is the ruler — one band, not two. The
+   thumb slides OVER them (its z-index is higher and it is translucent, as
+   in VS Code). Only a track carrying marks changes: every other consumer's
+   chrome above is unchanged.
 
    Height comes ENTIRELY from the engine, which floors a hairline mark in
-   both fractions and pixels and sizes the end-of-rail inset against that
+   both fractions and pixels and sizes the end-of-band inset against that
    same number. A `min-height` here is therefore redundant — the engine
-   already guarantees 2px — and, because the rail clips, would win over
+   already guarantees 2px — and, because the track clips, would win over
    the inset on the occasions it did bite. */
 .hk-scrollbar-marker {
   position: absolute;
+  z-index: 1;
   left: 0;
   width: 100%;
-  border-radius: 1px;
+  border-radius: 2px;
   background: var(--hi-color-muted, rgb(118 122 128));
-  /* The rail is pointer-transparent; the marks are the hit area. */
+  /* The track is pointer-transparent at rest; the marks are the hit area. */
   pointer-events: auto;
   cursor: pointer;
 
+  /* VS Code's two lanes: REMOVED content hugs the band's start edge,
+     ADDED content its end edge, so one vertical position can carry both.
+     No `side` = the mark spans the full band. */
+  &[data-side="start"] {
+    left: 0;
+    right: auto;
+    width: 34%;
+  }
+
+  &[data-side="end"] {
+    left: auto;
+    right: 0;
+    width: 34%;
+  }
+
   &:hover {
-    /* Negative offset: the rail clips its children, and a plain outline
-       lost both side strokes to that clip (only the top/bottom lines
-       survived) — drawn inside, the ring stays whole. */
+    /* Negative offset: an outset ring would draw past the mark's own box
+       and read as a stray rule floating beside it — drawn inside, the cue
+       stays attached to the mark it belongs to. */
     outline: 1px solid color-mix(in srgb, var(--hi-color-muted, rgb(118 122 128)) 60%, transparent);
     outline-offset: -1px;
   }

package/src/tokens.scss

@@ -1,6 +1,6 @@
 /* ── Syntax highlighting palette family: --code-* ───────────────────
  * Token names consumed by hikari's highlighted-code surfaces (the
- * HkToolBlock syntax layer and its JSON viewer, see HkToolBlock.scss).
+ * The JSON-viewer syntax layer and its theme channels (HkJsonTree).
  * The VALUES are intentionally NOT defined here: the family is owned by
  * the host theme, which maps each token to mode-aware colors. The
  * canonical mapping (dark = One Dark, light = GitHub Light) lives in the

package/src/utils/format.ts

@@ -14,7 +14,6 @@
  * under a zh-Hans app on an en browser). */
 import { activeLocale } from "../i18n/context";
 
-/** "1234" -> "1.2k", "2500000" -> "2.5M". */
 
 /** "1234" -> "1.2k". */
 export function formatNumber(n: number): string {
@@ -31,10 +30,7 @@ export function formatBytes(bytes: number): string {
   return `${(bytes / (1024 * 1024 * 1024)).toFixed(1)}GB`;
 }
 
-/** USD amount -> "$0.10" / "$1.5" / "$120". Negative/NaN clamp to 0. */
 
-/** Timestamp -> "Just now" / "5m ago" / "3h ago" / "2d ago" / "2w ago" /
- *  locale date. */
 export type RelativeTimeT = (
   key: string,
   fallback: string,

package/src/utils/powNonce.ts

@@ -11,7 +11,7 @@ export type ChallengeDescriptor =
  * undefined/missed config value would otherwise fetch `undefined/health`
  * — a relative URL resolving to `<origin>/undefined/health` — and fail
  * with a 404 that looks like a backend problem. Same pattern as
- * useEngineHealth's baseUrl guard.
+ * the consuming app's health-probe guard.
  */
 function normalizeBase(baseUrl: string): string {
   return (baseUrl ?? "").replace(/\/+$/, "");