@variance-authority/tribunal 0.1.0

package/dist/ui/shell.d.ts

@@ -0,0 +1,76 @@
+/**
+ * The chrome every page wears, and the three things every page needs.
+ *
+ * Apart from the pages because it is the part that must not differ between them:
+ * a topbar that moves by four pixels between the docket and a subject reads as a
+ * page that reloaded, and a failure rendered two ways is a failure a reader has
+ * to learn twice.
+ */
+import { type ReactElement, type ReactNode } from 'react';
+import { type Route } from './route.js';
+/** Something fetched, in the three states it can be in. Never two. */
+export type Loaded<T> = {
+    readonly state: 'loading';
+} | {
+    readonly state: 'failed';
+    readonly why: string;
+} | {
+    readonly state: 'ready';
+    readonly value: T;
+};
+/** An error as a sentence a reader can act on, never an empty list. */
+export declare function Failure({ why, retry, }: {
+    readonly why: string;
+    readonly retry: () => void;
+}): ReactElement;
+/**
+ * Report prose, with its identifiers set as identifiers.
+ *
+ * The sentences on this page were written by the observer, not by this surface,
+ * and they are shown as written — this is the record, and a review page that
+ * paraphrases it is a review page a reviewer cannot check. The only thing done
+ * to them is typographic.
+ */
+export declare function Prose({ text }: {
+    readonly text: string;
+}): ReactElement;
+/**
+ * A link that is a link.
+ *
+ * `<a href>` rather than a button, because the address is real: a reviewer who
+ * middle-clicks a change gets it in a tab, and one who copies the link gets a
+ * link that opens on the same change. The click is intercepted so an ordinary
+ * navigation stays a repaint — but only the ordinary one. A modified click, or
+ * anything but the primary button, is the browser's.
+ */
+export declare function Go({ to, go, className, title, children, }: {
+    readonly to: Route;
+    readonly go: (route: Route) => void;
+    readonly className?: string | undefined;
+    readonly title?: string | undefined;
+    readonly children: ReactNode;
+}): ReactElement;
+/**
+ * The bar at the top of every page: who you are looking at, and the way back.
+ *
+ * The crumbs are the whole navigation. There is no menu, because there are seven
+ * pages and five of them are *about* the page above them — a build is about a
+ * project, a change is about a build. A trail says that; a menu asserts they are
+ * peers.
+ */
+export declare function Topbar({ crumbs, go, title, subtitle, children, }: {
+    readonly crumbs: readonly {
+        readonly at: Route;
+        readonly say: string;
+    }[];
+    readonly go: (route: Route) => void;
+    readonly title: string;
+    readonly subtitle?: string | undefined;
+    readonly children?: ReactNode;
+}): ReactElement;
+/** The one page with no data on it: an address this surface does not answer. */
+export declare function Nowhere({ go }: {
+    readonly go: (route: Route) => void;
+}): ReactElement;
+export declare function messageOf(error: unknown): string;
+//# sourceMappingURL=shell.d.ts.map

package/dist/ui/shell.js

@@ -0,0 +1,65 @@
+import { Fragment as _Fragment, jsx as _jsx, jsxs as _jsxs } from "react/jsx-runtime";
+/**
+ * The chrome every page wears, and the three things every page needs.
+ *
+ * Apart from the pages because it is the part that must not differ between them:
+ * a topbar that moves by four pixels between the docket and a subject reads as a
+ * page that reloaded, and a failure rendered two ways is a failure a reader has
+ * to learn twice.
+ */
+import { Fragment } from 'react';
+import { Mark } from './mark.js';
+import { hrefOf } from './route.js';
+import { segments } from './text.js';
+/** An error as a sentence a reader can act on, never an empty list. */
+export function Failure({ why, retry, }) {
+    return (_jsxs("p", { className: "va-failure", children: [why, ' ', _jsx("button", { type: "button", onClick: retry, children: "retry" })] }));
+}
+/**
+ * Report prose, with its identifiers set as identifiers.
+ *
+ * The sentences on this page were written by the observer, not by this surface,
+ * and they are shown as written — this is the record, and a review page that
+ * paraphrases it is a review page a reviewer cannot check. The only thing done
+ * to them is typographic.
+ */
+export function Prose({ text }) {
+    return (_jsx(_Fragment, { children: segments(text).map((part, index) => part.code ? (_jsx("code", { children: part.text }, `${String(index)}-${part.text}`)) : (_jsx(Fragment, { children: part.text }, `${String(index)}-${part.text}`))) }));
+}
+/**
+ * A link that is a link.
+ *
+ * `<a href>` rather than a button, because the address is real: a reviewer who
+ * middle-clicks a change gets it in a tab, and one who copies the link gets a
+ * link that opens on the same change. The click is intercepted so an ordinary
+ * navigation stays a repaint — but only the ordinary one. A modified click, or
+ * anything but the primary button, is the browser's.
+ */
+export function Go({ to, go, className, title, children, }) {
+    return (_jsx("a", { href: hrefOf(to), className: className, ...(title === undefined ? {} : { title }), onClick: (event) => {
+            if (event.metaKey || event.ctrlKey || event.shiftKey || event.altKey || event.button !== 0) {
+                return;
+            }
+            event.preventDefault();
+            go(to);
+        }, children: children }));
+}
+/**
+ * The bar at the top of every page: who you are looking at, and the way back.
+ *
+ * The crumbs are the whole navigation. There is no menu, because there are seven
+ * pages and five of them are *about* the page above them — a build is about a
+ * project, a change is about a build. A trail says that; a menu asserts they are
+ * peers.
+ */
+export function Topbar({ crumbs, go, title, subtitle, children, }) {
+    return (_jsxs("header", { className: "va-topbar", children: [_jsx(Mark, {}), _jsx("nav", { className: "va-crumbs", children: crumbs.map((crumb) => (_jsxs(Fragment, { children: [_jsx(Go, { to: crumb.at, go: go, className: "va-crumb", children: crumb.say }), _jsx("span", { className: "va-crumb-sep", children: "/" })] }, hrefOf(crumb.at)))) }), _jsxs("span", { className: "va-topbar-title", children: [_jsx("strong", { children: title }), subtitle === undefined ? null : _jsx("span", { className: "va-topbar-sub", children: subtitle })] }), children] }));
+}
+/** The one page with no data on it: an address this surface does not answer. */
+export function Nowhere({ go }) {
+    return (_jsxs("div", { className: "va-app", children: [_jsx(Topbar, { crumbs: [], go: go, title: "No page at this address" }), _jsx("div", { className: "va-body va-scroll", children: _jsxs("div", { className: "va-page", children: [_jsx("p", { className: "va-note", children: "This service answers the build list, a build, a change, a subject, a run and the changelog. Whatever this link pointed at, it is not one of them \u2014 a link from a later version of the surface, or one that has been edited." }), _jsx("p", { children: _jsx(Go, { to: { page: 'builds' }, go: go, className: "va-mode", children: "Go to the builds" }) })] }) })] }));
+}
+export function messageOf(error) {
+    return error instanceof Error ? error.message : String(error);
+}
+//# sourceMappingURL=shell.js.map

package/dist/ui/shell.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"shell.js","sourceRoot":"","sources":["../../src/ui/shell.tsx"],"names":[],"mappings":";AAAA;;;;;;;GAOG;AAEH,OAAO,EAAE,QAAQ,EAAqC,MAAM,OAAO,CAAC;AACpE,OAAO,EAAE,IAAI,EAAE,MAAM,WAAW,CAAC;AACjC,OAAO,EAAE,MAAM,EAAc,MAAM,YAAY,CAAC;AAChD,OAAO,EAAE,QAAQ,EAAE,MAAM,WAAW,CAAC;AAQrC,uEAAuE;AACvE,MAAM,UAAU,OAAO,CAAC,EACtB,GAAG,EACH,KAAK,GAIN;IACC,OAAO,CACL,aAAG,SAAS,EAAC,YAAY,aACtB,GAAG,EAAE,GAAG,EACT,iBAAQ,IAAI,EAAC,QAAQ,EAAC,OAAO,EAAE,KAAK,sBAE3B,IACP,CACL,CAAC;AACJ,CAAC;AAED;;;;;;;GAOG;AACH,MAAM,UAAU,KAAK,CAAC,EAAE,IAAI,EAA6B;IACvD,OAAO,CACL,4BACG,QAAQ,CAAC,IAAI,CAAC,CAAC,GAAG,CAAC,CAAC,IAAI,EAAE,KAAK,EAAE,EAAE,CAClC,IAAI,CAAC,IAAI,CAAC,CAAC,CAAC,CACV,yBAA6C,IAAI,CAAC,IAAI,IAA3C,GAAG,MAAM,CAAC,KAAK,CAAC,IAAI,IAAI,CAAC,IAAI,EAAE,CAAoB,CAC/D,CAAC,CAAC,CAAC,CACF,KAAC,QAAQ,cAAwC,IAAI,CAAC,IAAI,IAA3C,GAAG,MAAM,CAAC,KAAK,CAAC,IAAI,IAAI,CAAC,IAAI,EAAE,CAAwB,CACvE,CACF,GACA,CACJ,CAAC;AACJ,CAAC;AAED;;;;;;;;GAQG;AACH,MAAM,UAAU,EAAE,CAAC,EACjB,EAAE,EACF,EAAE,EACF,SAAS,EACT,KAAK,EACL,QAAQ,GAOT;IACC,OAAO,CACL,YACE,IAAI,EAAE,MAAM,CAAC,EAAE,CAAC,EAChB,SAAS,EAAE,SAAS,KAChB,CAAC,KAAK,KAAK,SAAS,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,EAAE,KAAK,EAAE,CAAC,EAC1C,OAAO,EAAE,CAAC,KAAK,EAAE,EAAE;YACjB,IAAI,KAAK,CAAC,OAAO,IAAI,KAAK,CAAC,OAAO,IAAI,KAAK,CAAC,QAAQ,IAAI,KAAK,CAAC,MAAM,IAAI,KAAK,CAAC,MAAM,KAAK,CAAC,EAAE,CAAC;gBAC3F,OAAO;YACT,CAAC;YACD,KAAK,CAAC,cAAc,EAAE,CAAC;YACvB,EAAE,CAAC,EAAE,CAAC,CAAC;QACT,CAAC,YAEA,QAAQ,GACP,CACL,CAAC;AACJ,CAAC;AAED;;;;;;;GAOG;AACH,MAAM,UAAU,MAAM,CAAC,EACrB,MAAM,EACN,EAAE,EACF,KAAK,EACL,QAAQ,EACR,QAAQ,GAOT;IACC,OAAO,CACL,kBAAQ,SAAS,EAAC,WAAW,aAC3B,KAAC,IAAI,KAAG,EACR,cAAK,SAAS,EAAC,WAAW,YACvB,MAAM,CAAC,GAAG,CAAC,CAAC,KAAK,EAAE,EAAE,CAAC,CACrB,MAAC,QAAQ,eACP,KAAC,EAAE,IAAC,EAAE,EAAE,KAAK,CAAC,EAAE,EAAE,EAAE,EAAE,EAAE,EAAE,SAAS,EAAC,UAAU,YAC3C,KAAK,CAAC,GAAG,GACP,EACL,eAAM,SAAS,EAAC,cAAc,kBAAS,KAJ1B,MAAM,CAAC,KAAK,CAAC,EAAE,CAAC,CAKpB,CACZ,CAAC,GACE,EACN,gBAAM,SAAS,EAAC,iBAAiB,aAC/B,2BAAS,KAAK,GAAU,EACvB,QAAQ,KAAK,SAAS,CAAC,CAAC,CAAC,IAAI,CAAC,CAAC,CAAC,eAAM,SAAS,EAAC,eAAe,YAAE,QAAQ,GAAQ,IAC7E,EACN,QAAQ,IACF,CACV,CAAC;AACJ,CAAC;AAED,gFAAgF;AAChF,MAAM,UAAU,OAAO,CAAC,EAAE,EAAE,EAA2C;IACrE,OAAO,CACL,eAAK,SAAS,EAAC,QAAQ,aACrB,KAAC,MAAM,IAAC,MAAM,EAAE,EAAE,EAAE,EAAE,EAAE,EAAE,EAAE,KAAK,EAAC,yBAAyB,GAAG,EAC9D,cAAK,SAAS,EAAC,mBAAmB,YAChC,eAAK,SAAS,EAAC,SAAS,aACtB,YAAG,SAAS,EAAC,SAAS,iPAIlB,EACJ,sBACE,KAAC,EAAE,IAAC,EAAE,EAAE,EAAE,IAAI,EAAE,QAAQ,EAAE,EAAE,EAAE,EAAE,EAAE,EAAE,SAAS,EAAC,SAAS,iCAElD,GACH,IACA,GACF,IACF,CACP,CAAC;AACJ,CAAC;AAED,MAAM,UAAU,SAAS,CAAC,KAAc;IACtC,OAAO,KAAK,YAAY,KAAK,CAAC,CAAC,CAAC,KAAK,CAAC,OAAO,CAAC,CAAC,CAAC,MAAM,CAAC,KAAK,CAAC,CAAC;AAChE,CAAC","sourcesContent":["/**\n * The chrome every page wears, and the three things every page needs.\n *\n * Apart from the pages because it is the part that must not differ between them:\n * a topbar that moves by four pixels between the docket and a subject reads as a\n * page that reloaded, and a failure rendered two ways is a failure a reader has\n * to learn twice.\n */\n\nimport { Fragment, type ReactElement, type ReactNode } from 'react';\nimport { Mark } from './mark.js';\nimport { hrefOf, type Route } from './route.js';\nimport { segments } from './text.js';\n\n/** Something fetched, in the three states it can be in. Never two. */\nexport type Loaded<T> =\n  | { readonly state: 'loading' }\n  | { readonly state: 'failed'; readonly why: string }\n  | { readonly state: 'ready'; readonly value: T };\n\n/** An error as a sentence a reader can act on, never an empty list. */\nexport function Failure({\n  why,\n  retry,\n}: {\n  readonly why: string;\n  readonly retry: () => void;\n}): ReactElement {\n  return (\n    <p className=\"va-failure\">\n      {why}{' '}\n      <button type=\"button\" onClick={retry}>\n        retry\n      </button>\n    </p>\n  );\n}\n\n/**\n * Report prose, with its identifiers set as identifiers.\n *\n * The sentences on this page were written by the observer, not by this surface,\n * and they are shown as written — this is the record, and a review page that\n * paraphrases it is a review page a reviewer cannot check. The only thing done\n * to them is typographic.\n */\nexport function Prose({ text }: { readonly text: string }): ReactElement {\n  return (\n    <>\n      {segments(text).map((part, index) =>\n        part.code ? (\n          <code key={`${String(index)}-${part.text}`}>{part.text}</code>\n        ) : (\n          <Fragment key={`${String(index)}-${part.text}`}>{part.text}</Fragment>\n        ),\n      )}\n    </>\n  );\n}\n\n/**\n * A link that is a link.\n *\n * `<a href>` rather than a button, because the address is real: a reviewer who\n * middle-clicks a change gets it in a tab, and one who copies the link gets a\n * link that opens on the same change. The click is intercepted so an ordinary\n * navigation stays a repaint — but only the ordinary one. A modified click, or\n * anything but the primary button, is the browser's.\n */\nexport function Go({\n  to,\n  go,\n  className,\n  title,\n  children,\n}: {\n  readonly to: Route;\n  readonly go: (route: Route) => void;\n  readonly className?: string | undefined;\n  readonly title?: string | undefined;\n  readonly children: ReactNode;\n}): ReactElement {\n  return (\n    <a\n      href={hrefOf(to)}\n      className={className}\n      {...(title === undefined ? {} : { title })}\n      onClick={(event) => {\n        if (event.metaKey || event.ctrlKey || event.shiftKey || event.altKey || event.button !== 0) {\n          return;\n        }\n        event.preventDefault();\n        go(to);\n      }}\n    >\n      {children}\n    </a>\n  );\n}\n\n/**\n * The bar at the top of every page: who you are looking at, and the way back.\n *\n * The crumbs are the whole navigation. There is no menu, because there are seven\n * pages and five of them are *about* the page above them — a build is about a\n * project, a change is about a build. A trail says that; a menu asserts they are\n * peers.\n */\nexport function Topbar({\n  crumbs,\n  go,\n  title,\n  subtitle,\n  children,\n}: {\n  readonly crumbs: readonly { readonly at: Route; readonly say: string }[];\n  readonly go: (route: Route) => void;\n  readonly title: string;\n  readonly subtitle?: string | undefined;\n  readonly children?: ReactNode;\n}): ReactElement {\n  return (\n    <header className=\"va-topbar\">\n      <Mark />\n      <nav className=\"va-crumbs\">\n        {crumbs.map((crumb) => (\n          <Fragment key={hrefOf(crumb.at)}>\n            <Go to={crumb.at} go={go} className=\"va-crumb\">\n              {crumb.say}\n            </Go>\n            <span className=\"va-crumb-sep\">/</span>\n          </Fragment>\n        ))}\n      </nav>\n      <span className=\"va-topbar-title\">\n        <strong>{title}</strong>\n        {subtitle === undefined ? null : <span className=\"va-topbar-sub\">{subtitle}</span>}\n      </span>\n      {children}\n    </header>\n  );\n}\n\n/** The one page with no data on it: an address this surface does not answer. */\nexport function Nowhere({ go }: { readonly go: (route: Route) => void }): ReactElement {\n  return (\n    <div className=\"va-app\">\n      <Topbar crumbs={[]} go={go} title=\"No page at this address\" />\n      <div className=\"va-body va-scroll\">\n        <div className=\"va-page\">\n          <p className=\"va-note\">\n            This service answers the build list, a build, a change, a subject, a run and the\n            changelog. Whatever this link pointed at, it is not one of them — a link from a later\n            version of the surface, or one that has been edited.\n          </p>\n          <p>\n            <Go to={{ page: 'builds' }} go={go} className=\"va-mode\">\n              Go to the builds\n            </Go>\n          </p>\n        </div>\n      </div>\n    </div>\n  );\n}\n\nexport function messageOf(error: unknown): string {\n  return error instanceof Error ? error.message : String(error);\n}\n"]}

package/dist/ui/shift.d.ts

@@ -0,0 +1,52 @@
+/**
+ * What became of each subject between two runs — the fold, with nothing drawn.
+ *
+ * A build page compares a candidate to a baseline and stops. So a difference that
+ * arrived on Tuesday, went undecided, and arrived again on Wednesday is drawn on
+ * Wednesday exactly as it was on Tuesday: eighteen thumbnails, no memory, and a
+ * reviewer re-reading a docket they already read. The second reading costs the
+ * same as the first, which is why the fourth one does not happen.
+ *
+ * The shape digest is what makes the answer exact rather than approximate. Two
+ * runs whose leading regions carry the same fingerprint are carrying *the same
+ * difference*, not a similar one, and that licenses the only sentence worth
+ * printing anywhere off this: **you have seen this, and it has not moved since.**
+ *
+ * ## Absent is not equal
+ *
+ * A run that recorded no shape for its leading region said nothing, and two runs
+ * that both said nothing did not agree. Those get their own state, because
+ * folding them into *the same difference again* would be a confident claim about
+ * a pair nothing measured — on the one screen where the claim tells somebody they
+ * can skip looking.
+ *
+ * Separate from the panels that read it because there are now three of them: the
+ * build reads the whole crossing, a change reads the rows under one component,
+ * and a subject reads its own single row. One fold, and none of them may reach a
+ * different answer than the others about the same pair of runs.
+ */
+import type { BuildDetail, SubjectView } from '../review-types.js';
+/** What became of one subject between the two runs. */
+export type Shift = 'differently' | 'unsaid' | 'first' | 'new' | 'again' | 'settled' | 'declared' | 'absorbed' | 'unmasked' | 'unplaced' | 'uncompared' | 'dropped' | 'held';
+export interface Shifted {
+    readonly subject: string;
+    readonly shift: Shift;
+    /** This run's reading. Absent only when the subject was dropped. */
+    readonly now?: SubjectView;
+    /** The earlier run's reading, including whatever was decided about it. */
+    readonly earlier?: SubjectView;
+}
+export interface Divergence {
+    readonly shifts: readonly Shifted[];
+    /** Subjects both runs compared and neither found a difference in. */
+    readonly held: number;
+}
+/**
+ * The two runs crossed, one row per subject either of them named.
+ *
+ * Union rather than intersection: a subject the earlier run had and this one does
+ * not is a suite that shrank, and an intersection would report that as nothing
+ * having happened.
+ */
+export declare function divergeFrom(now: BuildDetail, prior: BuildDetail): Divergence;
+//# sourceMappingURL=shift.d.ts.map

package/dist/ui/shift.js

@@ -0,0 +1,98 @@
+/**
+ * What became of each subject between two runs — the fold, with nothing drawn.
+ *
+ * A build page compares a candidate to a baseline and stops. So a difference that
+ * arrived on Tuesday, went undecided, and arrived again on Wednesday is drawn on
+ * Wednesday exactly as it was on Tuesday: eighteen thumbnails, no memory, and a
+ * reviewer re-reading a docket they already read. The second reading costs the
+ * same as the first, which is why the fourth one does not happen.
+ *
+ * The shape digest is what makes the answer exact rather than approximate. Two
+ * runs whose leading regions carry the same fingerprint are carrying *the same
+ * difference*, not a similar one, and that licenses the only sentence worth
+ * printing anywhere off this: **you have seen this, and it has not moved since.**
+ *
+ * ## Absent is not equal
+ *
+ * A run that recorded no shape for its leading region said nothing, and two runs
+ * that both said nothing did not agree. Those get their own state, because
+ * folding them into *the same difference again* would be a confident claim about
+ * a pair nothing measured — on the one screen where the claim tells somebody they
+ * can skip looking.
+ *
+ * Separate from the panels that read it because there are now three of them: the
+ * build reads the whole crossing, a change reads the rows under one component,
+ * and a subject reads its own single row. One fold, and none of them may reach a
+ * different answer than the others about the same pair of runs.
+ */
+import { shapeOf } from './lead.js';
+/**
+ * The two runs crossed, one row per subject either of them named.
+ *
+ * Union rather than intersection: a subject the earlier run had and this one does
+ * not is a suite that shrank, and an intersection would report that as nothing
+ * having happened.
+ */
+export function divergeFrom(now, prior) {
+    const before = new Map(prior.subjects.map((subject) => [subject.subject, subject]));
+    const shifts = [];
+    let held = 0;
+    for (const subject of now.subjects) {
+        const earlier = before.get(subject.subject);
+        before.delete(subject.subject);
+        const shift = shiftOf(subject, earlier);
+        if (shift === 'held')
+            held += 1;
+        else
+            shifts.push({ subject: subject.subject, shift, now: subject, ...(earlier === undefined ? {} : { earlier }) });
+    }
+    for (const earlier of before.values()) {
+        shifts.push({ subject: earlier.subject, shift: 'dropped', earlier });
+    }
+    return { shifts, held };
+}
+/**
+ * Whether a verdict describes a pair this run actually put side by side.
+ *
+ * `ignored` belongs here and reads as though it does not. A declaration decided
+ * it, but the comparison it decided happened: there was a baseline, there were
+ * differing pixels, and every one of them landed somewhere the operator wrote
+ * down. Filing it with `incomparable` told a reviewer *no baseline was put beside
+ * them here* about subjects that were compared — an absence invented on top of a
+ * measurement, which is the one thing this panel exists not to do.
+ */
+function compared(subject) {
+    return (subject.verdict === 'changed' ||
+        subject.verdict === 'unchanged' ||
+        subject.verdict === 'ignored');
+}
+function shiftOf(now, earlier) {
+    if (earlier === undefined)
+        return 'new';
+    if (!compared(now))
+        return 'uncompared';
+    if (!compared(earlier))
+        return 'unplaced';
+    // A declaration standing over both runs is bookkeeping; one that arrived
+    // between them is a rule that has just taken a subject out of review, and the
+    // subject it took is named. That is the moment a mask starts covering
+    // something, and it is visible exactly once — here.
+    if (now.verdict === 'ignored')
+        return earlier.verdict === 'ignored' ? 'declared' : 'absorbed';
+    // The other direction. A subject a rule absorbed there and nothing absorbs
+    // here either stopped differing — which is `settled`, and true whether or not
+    // a rule was watching — or is being reported, which is the rule failing to
+    // cover what it was written for.
+    if (earlier.verdict === 'ignored')
+        return now.verdict === 'unchanged' ? 'settled' : 'unmasked';
+    if (now.verdict === 'unchanged')
+        return earlier.verdict === 'unchanged' ? 'held' : 'settled';
+    if (earlier.verdict === 'unchanged')
+        return 'first';
+    const here = shapeOf(now);
+    const there = shapeOf(earlier);
+    if (here === undefined || there === undefined)
+        return 'unsaid';
+    return here === there ? 'again' : 'differently';
+}
+//# sourceMappingURL=shift.js.map

package/dist/ui/shift.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"shift.js","sourceRoot":"","sources":["../../src/ui/shift.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;GA0BG;AAGH,OAAO,EAAE,OAAO,EAAE,MAAM,WAAW,CAAC;AAiCpC;;;;;;GAMG;AACH,MAAM,UAAU,WAAW,CAAC,GAAgB,EAAE,KAAkB;IAC9D,MAAM,MAAM,GAAG,IAAI,GAAG,CAAC,KAAK,CAAC,QAAQ,CAAC,GAAG,CAAC,CAAC,OAAO,EAAE,EAAE,CAAC,CAAC,OAAO,CAAC,OAAO,EAAE,OAAO,CAAC,CAAC,CAAC,CAAC;IACpF,MAAM,MAAM,GAAc,EAAE,CAAC;IAC7B,IAAI,IAAI,GAAG,CAAC,CAAC;IAEb,KAAK,MAAM,OAAO,IAAI,GAAG,CAAC,QAAQ,EAAE,CAAC;QACnC,MAAM,OAAO,GAAG,MAAM,CAAC,GAAG,CAAC,OAAO,CAAC,OAAO,CAAC,CAAC;QAC5C,MAAM,CAAC,MAAM,CAAC,OAAO,CAAC,OAAO,CAAC,CAAC;QAC/B,MAAM,KAAK,GAAG,OAAO,CAAC,OAAO,EAAE,OAAO,CAAC,CAAC;QACxC,IAAI,KAAK,KAAK,MAAM;YAAE,IAAI,IAAI,CAAC,CAAC;;YAC3B,MAAM,CAAC,IAAI,CAAC,EAAE,OAAO,EAAE,OAAO,CAAC,OAAO,EAAE,KAAK,EAAE,GAAG,EAAE,OAAO,EAAE,GAAG,CAAC,OAAO,KAAK,SAAS,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,EAAE,OAAO,EAAE,CAAC,EAAE,CAAC,CAAC;IACrH,CAAC;IAED,KAAK,MAAM,OAAO,IAAI,MAAM,CAAC,MAAM,EAAE,EAAE,CAAC;QACtC,MAAM,CAAC,IAAI,CAAC,EAAE,OAAO,EAAE,OAAO,CAAC,OAAO,EAAE,KAAK,EAAE,SAAS,EAAE,OAAO,EAAE,CAAC,CAAC;IACvE,CAAC;IAED,OAAO,EAAE,MAAM,EAAE,IAAI,EAAE,CAAC;AAC1B,CAAC;AAED;;;;;;;;;GASG;AACH,SAAS,QAAQ,CAAC,OAAoB;IACpC,OAAO,CACL,OAAO,CAAC,OAAO,KAAK,SAAS;QAC7B,OAAO,CAAC,OAAO,KAAK,WAAW;QAC/B,OAAO,CAAC,OAAO,KAAK,SAAS,CAC9B,CAAC;AACJ,CAAC;AAED,SAAS,OAAO,CAAC,GAAgB,EAAE,OAAgC;IACjE,IAAI,OAAO,KAAK,SAAS;QAAE,OAAO,KAAK,CAAC;IACxC,IAAI,CAAC,QAAQ,CAAC,GAAG,CAAC;QAAE,OAAO,YAAY,CAAC;IACxC,IAAI,CAAC,QAAQ,CAAC,OAAO,CAAC;QAAE,OAAO,UAAU,CAAC;IAE1C,yEAAyE;IACzE,8EAA8E;IAC9E,sEAAsE;IACtE,oDAAoD;IACpD,IAAI,GAAG,CAAC,OAAO,KAAK,SAAS;QAAE,OAAO,OAAO,CAAC,OAAO,KAAK,SAAS,CAAC,CAAC,CAAC,UAAU,CAAC,CAAC,CAAC,UAAU,CAAC;IAE9F,2EAA2E;IAC3E,8EAA8E;IAC9E,2EAA2E;IAC3E,iCAAiC;IACjC,IAAI,OAAO,CAAC,OAAO,KAAK,SAAS;QAAE,OAAO,GAAG,CAAC,OAAO,KAAK,WAAW,CAAC,CAAC,CAAC,SAAS,CAAC,CAAC,CAAC,UAAU,CAAC;IAE/F,IAAI,GAAG,CAAC,OAAO,KAAK,WAAW;QAAE,OAAO,OAAO,CAAC,OAAO,KAAK,WAAW,CAAC,CAAC,CAAC,MAAM,CAAC,CAAC,CAAC,SAAS,CAAC;IAC7F,IAAI,OAAO,CAAC,OAAO,KAAK,WAAW;QAAE,OAAO,OAAO,CAAC;IAEpD,MAAM,IAAI,GAAG,OAAO,CAAC,GAAG,CAAC,CAAC;IAC1B,MAAM,KAAK,GAAG,OAAO,CAAC,OAAO,CAAC,CAAC;IAC/B,IAAI,IAAI,KAAK,SAAS,IAAI,KAAK,KAAK,SAAS;QAAE,OAAO,QAAQ,CAAC;IAC/D,OAAO,IAAI,KAAK,KAAK,CAAC,CAAC,CAAC,OAAO,CAAC,CAAC,CAAC,aAAa,CAAC;AAClD,CAAC","sourcesContent":["/**\n * What became of each subject between two runs — the fold, with nothing drawn.\n *\n * A build page compares a candidate to a baseline and stops. So a difference that\n * arrived on Tuesday, went undecided, and arrived again on Wednesday is drawn on\n * Wednesday exactly as it was on Tuesday: eighteen thumbnails, no memory, and a\n * reviewer re-reading a docket they already read. The second reading costs the\n * same as the first, which is why the fourth one does not happen.\n *\n * The shape digest is what makes the answer exact rather than approximate. Two\n * runs whose leading regions carry the same fingerprint are carrying *the same\n * difference*, not a similar one, and that licenses the only sentence worth\n * printing anywhere off this: **you have seen this, and it has not moved since.**\n *\n * ## Absent is not equal\n *\n * A run that recorded no shape for its leading region said nothing, and two runs\n * that both said nothing did not agree. Those get their own state, because\n * folding them into *the same difference again* would be a confident claim about\n * a pair nothing measured — on the one screen where the claim tells somebody they\n * can skip looking.\n *\n * Separate from the panels that read it because there are now three of them: the\n * build reads the whole crossing, a change reads the rows under one component,\n * and a subject reads its own single row. One fold, and none of them may reach a\n * different answer than the others about the same pair of runs.\n */\n\nimport type { BuildDetail, SubjectView } from '../review-types.js';\nimport { shapeOf } from './lead.js';\n\n/** What became of one subject between the two runs. */\nexport type Shift =\n  | 'differently'\n  | 'unsaid'\n  | 'first'\n  | 'new'\n  | 'again'\n  | 'settled'\n  | 'declared'\n  | 'absorbed'\n  | 'unmasked'\n  | 'unplaced'\n  | 'uncompared'\n  | 'dropped'\n  | 'held';\n\nexport interface Shifted {\n  readonly subject: string;\n  readonly shift: Shift;\n  /** This run's reading. Absent only when the subject was dropped. */\n  readonly now?: SubjectView;\n  /** The earlier run's reading, including whatever was decided about it. */\n  readonly earlier?: SubjectView;\n}\n\nexport interface Divergence {\n  readonly shifts: readonly Shifted[];\n  /** Subjects both runs compared and neither found a difference in. */\n  readonly held: number;\n}\n\n/**\n * The two runs crossed, one row per subject either of them named.\n *\n * Union rather than intersection: a subject the earlier run had and this one does\n * not is a suite that shrank, and an intersection would report that as nothing\n * having happened.\n */\nexport function divergeFrom(now: BuildDetail, prior: BuildDetail): Divergence {\n  const before = new Map(prior.subjects.map((subject) => [subject.subject, subject]));\n  const shifts: Shifted[] = [];\n  let held = 0;\n\n  for (const subject of now.subjects) {\n    const earlier = before.get(subject.subject);\n    before.delete(subject.subject);\n    const shift = shiftOf(subject, earlier);\n    if (shift === 'held') held += 1;\n    else shifts.push({ subject: subject.subject, shift, now: subject, ...(earlier === undefined ? {} : { earlier }) });\n  }\n\n  for (const earlier of before.values()) {\n    shifts.push({ subject: earlier.subject, shift: 'dropped', earlier });\n  }\n\n  return { shifts, held };\n}\n\n/**\n * Whether a verdict describes a pair this run actually put side by side.\n *\n * `ignored` belongs here and reads as though it does not. A declaration decided\n * it, but the comparison it decided happened: there was a baseline, there were\n * differing pixels, and every one of them landed somewhere the operator wrote\n * down. Filing it with `incomparable` told a reviewer *no baseline was put beside\n * them here* about subjects that were compared — an absence invented on top of a\n * measurement, which is the one thing this panel exists not to do.\n */\nfunction compared(subject: SubjectView): boolean {\n  return (\n    subject.verdict === 'changed' ||\n    subject.verdict === 'unchanged' ||\n    subject.verdict === 'ignored'\n  );\n}\n\nfunction shiftOf(now: SubjectView, earlier: SubjectView | undefined): Shift {\n  if (earlier === undefined) return 'new';\n  if (!compared(now)) return 'uncompared';\n  if (!compared(earlier)) return 'unplaced';\n\n  // A declaration standing over both runs is bookkeeping; one that arrived\n  // between them is a rule that has just taken a subject out of review, and the\n  // subject it took is named. That is the moment a mask starts covering\n  // something, and it is visible exactly once — here.\n  if (now.verdict === 'ignored') return earlier.verdict === 'ignored' ? 'declared' : 'absorbed';\n\n  // The other direction. A subject a rule absorbed there and nothing absorbs\n  // here either stopped differing — which is `settled`, and true whether or not\n  // a rule was watching — or is being reported, which is the rule failing to\n  // cover what it was written for.\n  if (earlier.verdict === 'ignored') return now.verdict === 'unchanged' ? 'settled' : 'unmasked';\n\n  if (now.verdict === 'unchanged') return earlier.verdict === 'unchanged' ? 'held' : 'settled';\n  if (earlier.verdict === 'unchanged') return 'first';\n\n  const here = shapeOf(now);\n  const there = shapeOf(earlier);\n  if (here === undefined || there === undefined) return 'unsaid';\n  return here === there ? 'again' : 'differently';\n}\n"]}

package/dist/ui/styles-docket.d.ts

@@ -0,0 +1,18 @@
+/**
+ * The two panes a build is worked in: the docket rail, and the change beside it.
+ *
+ * Its own module for the same reason [`styles-stage.ts`](./styles-stage.ts) is:
+ * the sheet is one string handed to an operator, and the number of rules a person
+ * has to hold at once to change one of them is a real cost. What is decided here
+ * is *where a reviewer's eye goes first*, which is a layout question with a
+ * correct answer — the band headings and the row a change occupies, above the
+ * fold, in a column that does not grow with the build.
+ *
+ * The rule that matters most is the least visible one: nothing in this block
+ * scrolls the document. The rail scrolls through the changes, the stage scrolls
+ * through the one that is open, and the page itself is fixed to the viewport. A
+ * surface where the document scrolls is a report; a surface where the panes
+ * scroll is a place a reviewer navigates.
+ */
+export declare const DOCKET_STYLES = "\n/* The trail, which is the whole navigation. Five of the seven pages are *about*\n   the page above them, and a trail says that where a menu would assert they are\n   peers. */\n.va-crumbs { align-items: center; display: flex; gap: 0.3rem; min-width: 0; }\n.va-crumb { color: var(--va-ink-3); font-size: 0.8rem; text-decoration: none; white-space: nowrap; }\n.va-crumb:hover { color: var(--va-accent); }\n.va-crumb-sep { color: var(--va-line-firm); font-size: 0.8rem; }\n\n/* Changes or subjects: the two ways to work a build, as two addresses rather\n   than as a piece of component state. */\n.va-switch { background: var(--va-sunken); border-radius: 9px; display: flex; flex: none; gap: 0.15rem; margin-bottom: 0.5rem; padding: 0.2rem; }\n.va-switch .va-mode { flex: 1; text-align: center; text-decoration: none; }\n.va-switch .va-mode.va-on { background: var(--va-accent-soft); color: var(--va-accent); font-weight: 650; }\n.va-switch .va-mode.va-off { color: var(--va-ink-3); cursor: not-allowed; }\n\n.va-rail-head { align-items: center; display: flex; flex: none; flex-wrap: wrap; gap: 0.4rem; padding: 0 0.15rem 0.5rem; }\n.va-rail-tally { color: var(--va-ink-3); font-size: 0.76rem; margin-right: auto; }\n.va-rail-empty { padding: 0.6rem 0.15rem; }\n/* The scrolling half. `min-height: 0` is what keeps it scrolling rather than\n   pushing the rail past the bottom of the window \u2014 a flex child's default\n   minimum is its content, and a build of forty changes would take the viewport\n   with it. */\n.va-rail-list { flex: 1 1 auto; min-height: 0; overflow-y: auto; }\n\n/* The orders. Small, and deliberately not a select: four addresses a reader can\n   middle-click, which a select cannot be. */\n.va-sorting { display: inline-flex; gap: 0.1rem; }\n.va-sort { border-radius: 6px; color: var(--va-ink-3); font-family: var(--va-mono); font-size: 0.66rem; letter-spacing: 0.06em; padding: 0.15rem 0.4rem; text-decoration: none; text-transform: uppercase; }\n.va-sort:hover { background: var(--va-sunken); color: var(--va-ink); }\n.va-sort.va-on { background: var(--va-accent-soft); color: var(--va-accent); }\n\n/* A band, and the sentence that says why its rows are together. The left edge\n   carries the band's meaning: an alarm is red, a decision is green, and the\n   ordinary work you asked for is the accent. */\n.va-band { border-left: 2px solid var(--va-line-firm); margin: 0 0 0.9rem 0.15rem; padding-left: 0.7rem; }\n.va-band h3 { align-items: center; display: flex; font-size: 0.76rem; font-weight: 700; gap: 0.4rem; letter-spacing: 0.05em; margin-bottom: 0.15rem; text-transform: uppercase; }\n.va-band h3 .va-num { background: var(--va-sunken); border-radius: 999px; color: var(--va-ink-2); font-size: 0.7rem; letter-spacing: 0; padding: 0 0.4rem; }\n.va-band > .va-note { font-size: 0.74rem; margin-bottom: 0.35rem; }\n.va-band-stranded { border-left-color: var(--va-bad); }\n.va-band-stranded h3 { color: var(--va-bad-ink); }\n.va-band-reached { border-left-color: var(--va-accent); }\n.va-band-contradicted { border-left-color: var(--va-warn); }\n.va-band-contradicted h3 { color: var(--va-warn-ink); }\n.va-band-unexplained { border-left-color: var(--va-warn); }\n.va-band-unexplained h3 { color: var(--va-warn-ink); }\n.va-band-upstream { border-left-color: var(--va-collateral); }\n.va-band-token { border-left-color: var(--va-collateral); }\n.va-band-unnamed { border-left-color: var(--va-line-firm); }\n.va-band-unread { border-left-color: var(--va-warn); }\n.va-band-decided { border-left-color: var(--va-good); }\n.va-band-orphan { border-left-color: var(--va-warn); }\n\n/* A heading that is a path or a property, not a claim, so it overrides the\n   band's uppercase: a name a reviewer uppercases is a name they cannot grep. */\n.va-band h3.va-root, .va-root { flex-wrap: wrap; font-family: var(--va-mono); font-size: 0.78rem; font-weight: 600; gap: 0.15rem; letter-spacing: 0; text-transform: none; }\n.va-root .va-root-in { color: var(--va-ink-3); font-weight: 400; }\n.va-root .va-root-name { color: var(--va-ink); }\n.va-root-component .va-root-name { font-family: var(--va-sans); font-weight: 700; }\n\n/* The same cause on the change page: one line under the name, and the other\n   changes it made. */\n.va-from { align-items: baseline; display: flex; flex-wrap: wrap; font-size: 0.8rem; gap: 0.3rem; margin-top: 0.2rem; }\n.va-from-mark { color: var(--va-ink-3); font-size: 0.72rem; letter-spacing: 0.05em; text-transform: uppercase; }\n.va-from .va-root { font-size: 0.8rem; }\n.va-from-go { color: var(--va-accent); text-decoration: none; }\n.va-from-go:hover { text-decoration: underline; }\n\n/* The prediction under a root, and the same claim about the whole build. It sits\n   between a heading and the rows it explains, so it is quieter than both. */\n.va-foreseen { color: var(--va-ink-3); font-size: 0.72rem; line-height: 1.5; margin: 0.1rem 0 0.4rem; }\n.va-foreseen .va-num { color: var(--va-ink-2); font-family: var(--va-mono); }\n.va-foreseen .va-from-go { color: var(--va-ink-2); font-family: var(--va-mono); text-decoration: none; }\n.va-foreseen .va-from-go:hover { color: var(--va-accent); text-decoration: underline; }\n.va-foreseen-off { color: var(--va-warn-ink); }\n.va-rail-head + .va-foreseen { margin: -0.2rem 0 0.5rem; }\n\n/* One change, in a row a reviewer scans a column of. The name is the only thing\n   at full contrast; everything else on the row is there to be skipped. */\n.va-row { margin-bottom: 0.1rem; }\n.va-row-link { align-items: baseline; border: 1px solid transparent; border-radius: 8px; column-gap: 0.5rem; display: grid; grid-template-columns: minmax(0, 1fr) auto; padding: 0.35rem 0.5rem; row-gap: 0.05rem; text-decoration: none; }\n.va-row-link:hover { background: var(--va-sunken); }\n.va-row.va-here .va-row-link { background: var(--va-accent-soft); border-color: var(--va-accent); }\n.va-row-name { font-size: 0.88rem; font-weight: 550; grid-area: 1 / 1; overflow: hidden; text-overflow: ellipsis; white-space: nowrap; }\n.va-row-spread { font-size: 0.74rem; grid-area: 2 / 1; }\n.va-row-size { color: var(--va-ink-3); font-size: 0.74rem; grid-area: 2 / 2; text-align: right; }\n.va-row .va-mark { font-size: 0.68rem; grid-area: 1 / 2; justify-self: end; }\n.va-row-from { color: var(--va-ink-3); font-family: var(--va-mono); font-size: 0.7rem; grid-area: 3 / 1 / 4 / 3; overflow: hidden; text-overflow: ellipsis; white-space: nowrap; }\n\n/* The page with nothing open: four sentences and two links, and no encyclopedia.\n   Everything a reader could want past this has an address of its own. */\n.va-opening { max-width: 44rem; }\n.va-opening h1 { margin-bottom: 0.3rem; }\n.va-opening-links { align-items: baseline; display: flex; flex-wrap: wrap; gap: 0.6rem; margin-top: 1.4rem; }\n\n/* The change itself. The two buttons are in the head, level with the component\n   name: every line below them is a reason to press one or to refuse, and a\n   reviewer who has read them should not scroll back past the reasons to act. */\n.va-decide { max-width: 62rem; }\n.va-decide-head { align-items: flex-start; border-bottom: 1px solid var(--va-line); display: flex; flex-wrap: wrap; gap: 0.8rem; justify-content: space-between; padding-bottom: 0.8rem; }\n.va-decide-head h1 { margin: 0; }\n.va-decide-lead { font-size: 1rem; margin-top: 0.8rem; }\n.va-decide-act { align-items: center; display: flex; flex-wrap: wrap; gap: 0.55rem; }\n.va-decide-act button { font-weight: 600; }\n.va-decide-act .va-approve { background: var(--va-good); border-color: var(--va-good); color: #ffffff; }\n.va-decide-act .va-approve:disabled { background: var(--va-sunken); border-color: var(--va-line-firm); color: var(--va-ink-3); }\n.va-decide h2 { font-size: 0.78rem; letter-spacing: 0.08em; margin-top: 1.6rem; text-transform: uppercase; }\n\n/* Whether the commit arrives, in the three colours the three answers deserve.\n   The alarm is spent on one of them and must stay that way: a page that shouted\n   over every component out of a dependency trained the alarm out of its readers\n   inside a build. */\n.va-reaches { border-radius: 7px; font-size: 0.9rem; margin-top: 0.9rem; padding: 0.5rem 0.7rem; }\n.va-reaches.va-reached { background: var(--va-info-bg); color: var(--va-info-ink); }\n.va-reaches.va-alarm { background: var(--va-bad-bg); color: var(--va-bad-ink); }\n.va-reaches.va-unnamed { background: var(--va-info-bg); color: var(--va-info-ink); }\n\n/* The run's own conclusion, above the file graph's. Left-marked rather than\n   filled: it sits directly over the reach block, and two filled panels in a row\n   read as one panel with a seam in it. The colour is the rung \u2014 the two that\n   say *the run found nothing* borrow the alarm, and the three that explain\n   something do not, because an explanation is not a finding. */\n.va-attributed { border-left: 3px solid var(--va-line-firm); font-size: 0.92rem; margin-top: 0.9rem; padding-left: 0.7rem; }\n.va-attributed code { font-size: 0.86em; }\n.va-attributed-edited { border-left-color: var(--va-accent); }\n.va-attributed-upstream { border-left-color: var(--va-collateral); }\n.va-attributed-token { border-left-color: var(--va-collateral); }\n.va-attributed-contradicted { border-left-color: var(--va-bad); }\n.va-attributed-unexplained { border-left-color: var(--va-bad); }\n.va-attributed-go { color: var(--va-accent); font-weight: 600; white-space: nowrap; }\n\n/* A band this change did not move on its own. Directly under the lead and\n   marked in the collateral colour, which is what it is: the sense moved here,\n   the decision is one file up, and the two belong on one screen without the\n   second looking like a second change. */\n.va-handed { color: var(--va-ink-2); font-size: 0.95rem; margin-top: 0.35rem; }\n.va-handed em { color: var(--va-ink); font-style: normal; font-weight: 600; }\n.va-handed-go { color: var(--va-accent); font-weight: 600; white-space: nowrap; }\n\n/* The three counts, side by side rather than in a sentence. A sentence has to\n   pick an order and an emphasis; these are three answers of equal standing to\n   three questions a reviewer asks in the same breath. */\n.va-tally { align-items: baseline; color: var(--va-ink-2); display: flex; flex-wrap: wrap; font-size: 0.9rem; gap: 0.15rem 1.1rem; margin: 0.2rem 0 0.9rem; }\n.va-tally strong { color: var(--va-ink); font-size: 1rem; }\n.va-tally > .va-note { margin-left: auto; }\n\n/* What happened to the things that draw this one \u2014 the question an author of a\n   leaf actually has. The list is ordered worst first, so the row that needs a\n   look is the one under the summary. */\n.va-consumers { margin: 1.1rem 0; }\n.va-consumers-tally { color: var(--va-ink-2); font-size: 0.92rem; margin: 0 0 0.5rem; }\n.va-consumers-own { color: var(--va-bad-ink); font-weight: 600; }\n.va-consumers-list { display: grid; gap: 0.3rem; list-style: none; margin: 0; padding: 0; }\n.va-consumers-list li { align-items: baseline; border-left: 3px solid var(--va-collateral); display: flex; flex-wrap: wrap; gap: 0.5rem; padding: 0.15rem 0 0.15rem 0.6rem; }\n.va-consumer-name { color: var(--va-ink); font-weight: 600; }\n.va-consumer-moved { border-left-color: var(--va-bad); }\n.va-consumers-rest { color: var(--va-ink-3); font-size: 0.85rem; margin: 0.5rem 0 0; }\n.va-consumers-rest span[title] { color: var(--va-ink-2); }\n.va-alarm-text { color: var(--va-bad-ink); }\n\n/* What a press of Approve settles that is not the change it is under. Directly\n   under the counts, because it is a correction to one of them: the seven renders\n   to accept are seven whole pictures, and four of them hold somebody else's\n   undecided difference. */\n.va-carries { background: var(--va-bad-bg); border-radius: 6px; color: var(--va-ink-2); font-size: 0.88rem; margin: 0 0 0.9rem; padding: 0.4rem 0.6rem; }\n.va-carries-go { color: var(--va-accent); font-weight: 600; white-space: nowrap; }\n.va-carries-mark { background: var(--va-bad-bg); border-radius: 999px; color: var(--va-bad-ink); font-size: 0.68rem; padding: 0.05rem 0.4rem; }\n\n/* What a band claim is made of. At the foot, because it is the same sentence for\n   all of them and a reviewer needs it once \u2014 and not behind a disclosure,\n   because the complaint that produced it was a page hiding its sources. */\n.va-held { border-left: 2px solid var(--va-good); color: var(--va-ink-2); font-size: 0.86rem; margin: 0.6rem 0 0; padding-left: 0.7rem; }\n.va-held-mark { color: var(--va-good); font-weight: 600; }\n.va-held-none { border-left-color: var(--va-ink-3); }\n.va-held-none .va-held-mark { color: var(--va-ink-2); }\n.va-held-go { color: inherit; text-decoration: underline; text-decoration-style: dotted; }\n.va-evidence { border-top: 1px solid var(--va-line); color: var(--va-ink-3); font-size: 0.8rem; margin-top: 1.6rem; padding-top: 0.6rem; }\n.va-evidence em { color: var(--va-ink-2); font-style: normal; }\n\n/* What the last run said, beside the change rather than nine thousand pixels\n   below it. Warm rather than red: *you have seen this* is not an alarm, it is\n   the sentence a reviewer skips work on. */\n.va-since { border-radius: 7px; font-size: 0.9rem; margin-top: 0.7rem; padding: 0.5rem 0.7rem; }\n.va-since.va-known { background: var(--va-warn-bg); color: var(--va-warn-ink); }\n.va-collateral-note { margin-top: 1.6rem; }\n\n/* Where the renders stopped agreeing. Directly above the list they divide, so a\n   reviewer reads the groups and then finds them in order \u2014 and the sizes are the\n   left column in both, which is what makes the two readable as one list. */\n.va-parted { margin: 1.4rem 0 0.6rem; }\n.va-parted h2 { margin-bottom: 0.4rem; }\n.va-parted ul { display: grid; gap: 0.5rem; list-style: none; margin: 0; padding: 0; }\n.va-parted li { border-left: 3px solid var(--va-line); padding: 0.1rem 0 0.1rem 0.7rem; }\n.va-parted li:first-child { border-left-color: var(--va-collateral); }\n.va-parted-head { align-items: baseline; display: flex; flex-wrap: wrap; gap: 0.6rem; margin: 0; }\n.va-parted-head .va-num { color: var(--va-ink); font-family: var(--va-mono); font-size: 0.95rem; }\n.va-parted-only { color: var(--va-ink-2); font-size: 0.85rem; font-weight: 600; }\n.va-parted-take { background: var(--va-sunken); border-radius: 5px; color: var(--va-ink-3); font-size: 0.74rem; margin-left: auto; padding: 0.1rem 0.4rem; }\n.va-parted-in { font-size: 0.8rem; margin: 0.15rem 0 0; overflow-wrap: anywhere; }\n\n/* Where it showed up: one row per render, each decidable on its own, because a\n   batch that could only be taken whole would be a batch nobody could refuse\n   part of. */\n.va-where { display: grid; gap: 0.15rem; margin-top: 0.5rem; }\n.va-where-row { align-items: baseline; border-radius: 8px; column-gap: 0.6rem; display: grid; grid-template-columns: minmax(6rem, 15rem) auto auto minmax(0, 1fr) auto; padding: 0.35rem 0.5rem; }\n.va-where-row:hover { background: var(--va-sunken); }\n.va-where-subject { font-size: 0.88rem; font-weight: 550; grid-column: 1; overflow: hidden; text-overflow: ellipsis; text-decoration: none; white-space: nowrap; }\n.va-where-size { grid-column: 2; text-align: right; }\n.va-where-row .va-mark { grid-column: 3; }\n.va-where-with { grid-column: 4; overflow: hidden; text-overflow: ellipsis; white-space: nowrap; }\n.va-where-row .va-note { font-size: 0.76rem; }\n.va-where-act { display: flex; gap: 0.25rem; grid-column: 5; justify-self: end; }\n.va-where-row > .va-mark:last-child { grid-column: 5; justify-self: end; }\n.va-where-act button { border-radius: 6px; font-size: 0.8rem; line-height: 1; padding: 0.2rem 0.5rem; }\n.va-where-act .va-approve:not(:disabled) { border-color: var(--va-good); color: var(--va-good-ink); }\n.va-mark.va-known { background: var(--va-warn-bg); border-radius: 999px; color: var(--va-warn-ink); font-size: 0.68rem; padding: 0.05rem 0.4rem; }\n.va-mark.va-alarm { background: var(--va-bad-bg); border-radius: 999px; color: var(--va-bad-ink); font-size: 0.68rem; padding: 0.05rem 0.4rem; }\n\n/* What moved, in the sense the hashes recorded. The lead sentence is emphasis\n   inside the existing lead paragraph and gets no box of its own \u2014 it is the\n   subject of the page, not a note beside it. What follows is detail, and the\n   only part that raises its voice is a component the picture lost: the hashes\n   name it and no region does, which is the one state a reviewer cannot see. */\n.va-decide-lead em { font-style: normal; font-weight: 600; }\n.va-moved-lost { background: var(--va-bad-bg); border-radius: 7px; color: var(--va-bad-ink); font-size: 0.9rem; margin-top: 0.7rem; padding: 0.5rem 0.7rem; }\n.va-moved h3 { font-size: 0.72rem; letter-spacing: 0.06em; margin-top: 1rem; text-transform: uppercase; }\n.va-moved-with { display: grid; gap: 0.15rem; margin-top: 0.35rem; }\n.va-moved-with li { align-items: baseline; column-gap: 0.5rem; display: flex; flex-wrap: wrap; font-size: 0.88rem; }\n.va-moved-list { display: grid; gap: 0.3rem; }\n.va-moved-row { align-items: baseline; column-gap: 0.5rem; display: flex; flex-wrap: wrap; font-size: 0.85rem; }\n/* Pushed rather than edited, and dimmed to say so. The list is ordered by name\n   and not by consequence, so without this a passenger reads level with a cause. */\n.va-moved-passenger .va-moved-name { color: var(--va-ink-3); font-weight: 400; }\n.va-moved-name { font-weight: 600; }\n/* How far a passenger is from the change, in the import graph. A chip and not a\n   sentence, and only on the rows the records place: a column that says the same\n   thing on every row is read once and skipped after. */\n.va-moved-far { background: var(--va-sunken); border-radius: 5px; color: var(--va-ink-3); font-size: 0.74rem; padding: 0.05rem 0.35rem; }\n\n/* The commit, its files, and how far out it landed \u2014 the build page's own\n   section, above the docket rather than beside it, because it is true of every\n   change on the page and nothing on it is decided. */\n.va-impact { border-top: 1px solid var(--va-line); display: grid; gap: 1rem; margin-top: 1.4rem; padding-top: 1.1rem; }\n.va-impact-commit { align-items: baseline; display: flex; flex-wrap: wrap; font-size: 0.9rem; }\n.va-impact-files ul { display: grid; gap: 0.1rem; margin-top: 0.35rem; }\n.va-impact-files li { font-size: 0.82rem; }\n.va-impact-depth h2 { font-size: 0.72rem; letter-spacing: 0.06em; text-transform: uppercase; }\n.va-rungs { display: grid; gap: 0.3rem; margin-top: 0.5rem; max-width: 34rem; }\n.va-rung { align-items: center; display: grid; gap: 0.6rem; grid-template-columns: 7.5rem 1fr auto; }\n.va-rung-at { font-size: 0.8rem; text-align: right; }\n/* The bar is the reached count and the fill is the moved count inside it, so the\n   two are read as a share rather than as two lengths a reader has to divide. */\n.va-rung-bar { background: var(--va-collateral); border-radius: 3px; display: block; height: 0.6rem; min-width: 2px; }\n.va-rung-moved { background: var(--va-cause); border-radius: 3px; display: block; height: 100%; }\n.va-rung-num { font-size: 0.78rem; }\n/* The movement the bars cannot hold, which is the one part of the spread they\n   are silent about. A list and not a sentence, because each row carries its own\n   reason and a paragraph of them is a paragraph nobody finishes. */\n.va-unheld { background: var(--va-bad-bg); border-radius: 7px; color: var(--va-bad-ink); font-size: 0.85rem; margin-top: 0.7rem; max-width: 34rem; padding: 0.5rem 0.7rem; }\n.va-unheld ul { display: grid; gap: 0.25rem; margin-top: 0.4rem; }\n.va-unheld li { align-items: baseline; column-gap: 0.45rem; display: flex; flex-wrap: wrap; }\n.va-unheld-name { font-weight: 600; }\n.va-unheld-why { opacity: 0.78; }\n";
+//# sourceMappingURL=styles-docket.d.ts.map