@gjsify/adwaita-core 0.36.0 → 0.38.0

package/lib/types/conformance/split-button.d.ts

@@ -1,7 +1,6 @@
 import type { AdwArrowIcon, AdwMenuEntry, SplitButtonContentMode, SplitButtonDirection, SplitButtonHalfState, SplitButtonProperty, SplitButtonStyleClass } from '../split-button.js';
 /** One mutation in a {@link SplitButtonContentVector} sequence, with its outcome. */
 export interface SplitButtonContentStep {
-    /** Which slot is being set. */
     op: 'label' | 'icon-name' | 'child';
     /**
      * The value passed. For `label`/`icon-name` the string itself; for `child` a
@@ -13,7 +12,6 @@ export interface SplitButtonContentStep {
     changed: boolean;
     /** The `notify::*` properties C emits for this one call, in emission order. */
     notified: readonly SplitButtonProperty[];
-    /** The content mode after the step. */
     mode: SplitButtonContentMode;
     /** `get_label()` after the step. */
     label: string | null;
@@ -21,31 +19,26 @@ export interface SplitButtonContentStep {
     iconName: string | null;
     /** The root style classes after the step. */
     styleClasses: readonly SplitButtonStyleClass[];
-    /** Why this step exists — the rule or edge case it pins down. */
     rule: string;
 }
 /** A scripted sequence of content mutations applied to a FRESH state. */
 export interface SplitButtonContentVector {
     /** Which upstream test (or derivation) this sequence transcribes. */
     name: string;
-    /** The mutations, in order. */
     steps: readonly SplitButtonContentStep[];
 }
 /**
- * The content machine (adw-split-button.c:661-682, :749-771, :799-824).
+ * The content machine.
  *
- * Two things in here are easy to get wrong and are asserted explicitly. First,
- * the `notified` ORDER: C freezes, notifies the slots it is about to CLEAR, sets
- * the new one, notifies it, then thaws — so one `set_label()` can emit three
- * notifications. Second, `child` is notified far more often than a reader
- * expects, because `adw_split_button_get_child()` returns GtkButton's INTERNAL
- * label/image widget in label/icon mode (the upstream suite states this at
- * tests/test-split-button.c:155-157) and the C guard tests that pointer, not
- * whether the app ever set a child.
+ * Two things are easy to get wrong and are asserted explicitly. The `notified` ORDER: C
+ * freezes, notifies the slots it is about to CLEAR, sets the new one, notifies it, then
+ * thaws — so one `set_label()` can emit three notifications. And `child` is notified far
+ * more often than a reader expects, because `adw_split_button_get_child()` returns
+ * GtkButton's INTERNAL label/image widget in label/icon mode (the upstream suite says so)
+ * and the C guard tests that pointer, not whether the app ever set a child.
  *
- * A driver that cannot express a step — a DOM element has no `child` slot —
- * asserts the sequence up to that step and stops; every sequence is written so
- * the interesting rows come first.
+ * A driver that cannot express a step — a DOM element has no `child` slot — asserts the
+ * sequence up to that step and stops; every sequence puts the interesting rows first.
  */
 export declare const SPLIT_BUTTON_CONTENT_VECTORS: ReadonlyArray<SplitButtonContentVector>;
 /** One `update_style_classes` expectation. */
@@ -56,11 +49,10 @@ export interface SplitButtonStyleClassVector {
     iconName: string | null;
     /** The classes on the `splitbutton` node. */
     classes: readonly SplitButtonStyleClass[];
-    /** Why this row exists. */
     rule: string;
 }
 /**
- * `update_style_classes` (adw-split-button.c:145-165). Both branches read the
+ * `update_style_classes`. Both branches read the
  * FIRST CHARACTER, which is why `''` and `'  '` land on opposite sides.
  */
 export declare const SPLIT_BUTTON_STYLE_CLASS_VECTORS: ReadonlyArray<SplitButtonStyleClassVector>;
@@ -68,40 +60,35 @@ export declare const SPLIT_BUTTON_STYLE_CLASS_VECTORS: ReadonlyArray<SplitButton
 export interface SplitButtonTooltipVector {
     /** The value passed to `adw_split_button_set_dropdown_tooltip`. */
     tooltip: string;
-    /** What the dropdown actually shows. */
     text: string;
     /** Whether it is Pango MARKUP (`set_tooltip_markup`) rather than plain text. */
     markup: boolean;
-    /** Why this row exists. */
     rule: string;
 }
 /**
- * The tooltip fallback (adw-split-button.c:1044-1051, initial value :531-532).
+ * The tooltip fallback in `adw_split_button_set_dropdown_tooltip`, plus its initial value.
  *
- * `has_dropdown_tooltip = tooltip && *tooltip`. The empty branch is the one both
- * renderers got wrong: the browser port hardcoded `Menu` and, because `''` is not
- * nullish, `dropdown-tooltip=""` left the button with NO accessible name at all;
- * the NativeScript port had neither tooltip nor accessible name.
+ * `has_dropdown_tooltip = tooltip && *tooltip`. The empty branch is the trap: `''` is not
+ * nullish, so a nullish-coalescing fallback leaves `dropdown-tooltip=""` with NO accessible
+ * name at all instead of the translated `More Options`.
  */
 export declare const SPLIT_BUTTON_TOOLTIP_VECTORS: ReadonlyArray<SplitButtonTooltipVector>;
 /** One direction expectation. */
 export interface SplitButtonDirectionVector {
     /** The `GtkArrowType`. */
     direction: SplitButtonDirection;
-    /** The symbolic icon the arrow node draws. */
     arrowIcon: AdwArrowIcon;
-    /** Where the popup is placed. */
     popupDirection: SplitButtonDirection;
     /** Why this row exists — naming the selector that WINS, not the one that loses. */
     rule: string;
 }
 /**
  * Direction → glyph for the dropdown half of a SPLIT BUTTON, and → popup
- * placement (adw-split-button.c:415).
+ * placement.
  *
  * `none` is the row that matters, and it is the row that was WRONG here until the
  * override was found: the four shared directions come from `menubutton arrow`
- * (_buttons.scss:457-468), but `.none` is re-declared inside `splitbutton { … }`
+ * (`_buttons.scss`), but `.none` is re-declared inside `splitbutton { … }`
  * at :621-623, and that selector wins. See the header of `./index.ts` — "cite the
  * winning selector" — for what this table cost.
  */
@@ -123,17 +110,14 @@ export interface SplitButtonRootStateVector {
     action: SplitButtonHalfState;
     /** State flags of the dropdown (arrow) half. */
     dropdown: SplitButtonHalfState;
-    /** Whether the root reads ACTIVE. */
     active: boolean;
-    /** Whether the root reads CHECKED. */
     checked: boolean;
-    /** Why this row exists. */
     rule: string;
 }
 /**
- * `update_state` (adw-split-button.c:118-143) — an OR-fold of both halves onto
+ * `update_state` — an OR-fold of both halves onto
  * the root, which is what `splitbutton.flat:active/:checked` styles
- * (_buttons.scss:542-549).
+ * (`_buttons.scss`).
  *
  * CORE-ONLY: GAP — two of its three axes are hardcoded in the renderer, so there is nothing to vary. Tracked in #1072
  */
@@ -142,9 +126,7 @@ export declare const SPLIT_BUTTON_ROOT_STATE_VECTORS: ReadonlyArray<SplitButtonR
 export interface SplitButtonMenuParseVector {
     /** The raw `menu` attribute (or `null` when absent). */
     json: string | null;
-    /** The entries it yields. */
     entries: readonly AdwMenuEntry[];
-    /** Why this row exists. */
     rule: string;
 }
 /**
@@ -154,18 +136,15 @@ export interface SplitButtonMenuParseVector {
 export declare const SPLIT_BUTTON_MENU_PARSE_VECTORS: ReadonlyArray<SplitButtonMenuParseVector>;
 /** One activate-by-position expectation. */
 export interface SplitButtonMenuActivationVector {
-    /** The menu model. */
     entries: readonly AdwMenuEntry[];
-    /** The position activated. */
     index: number;
     /** The entry that must be dispatched, or `null`. */
     activated: AdwMenuEntry | null;
-    /** Why this row exists. */
     rule: string;
 }
 /**
  * Activation is BY POSITION, never by label lookup: a `GMenuModel` addresses its
- * items by index and each carries its own detailed action (adw-split-button.c:385-388).
+ * items by index and each carries its own detailed action.
  */
 export declare const SPLIT_BUTTON_MENU_ACTIVATION_VECTORS: ReadonlyArray<SplitButtonMenuActivationVector>;
 /**
@@ -182,12 +161,11 @@ export interface SplitButtonDropdownVector {
     enabled: boolean;
     /** Whether the menu can be popped up at all. */
     canOpen: boolean;
-    /** Why this row exists. */
     rule: string;
 }
 /**
- * "If the menu model is `NULL`, the dropdown is disabled" (adw-split-button.c:376-378),
- * and the same for the popover (:394-396). An empty entry list is the renderers'
+ * "If the menu model is `NULL`, the dropdown is disabled",
+ * and the same for the popover. An empty entry list is the renderers'
  * only spelling of "no menu", so it collapses onto the `NULL` case.
  */
 export declare const SPLIT_BUTTON_DROPDOWN_VECTORS: ReadonlyArray<SplitButtonDropdownVector>;

package/lib/types/conformance/split-view.d.ts

@@ -6,12 +6,12 @@ export interface AdwLengthUnitVector {
     value: number;
     /** The `gtk-xft-dpi` in play. */
     dpi: number;
-    /** The resulting pixel length. */
     px: number;
-    /** Why this row exists. */
     rule: string;
 }
-/** `adw_length_unit_to_px` (adw-length-unit.c:72-81).  *
+/**
+ * `adw_length_unit_to_px`.
+ *
  * CORE-ONLY: an internal step of a pipeline whose COMPOSED result is renderer-driven — driving it separately would assert the same thing twice (SIDEBAR_BOUNDS_VECTORS, which both renderers drive)
  */
 export declare const ADW_LENGTH_UNIT_VECTORS: ReadonlyArray<AdwLengthUnitVector>;
@@ -20,7 +20,6 @@ export interface GlibClampVector {
     x: number;
     low: number;
     high: number;
-    /** What GLib's CLAMP returns. */
     clamped: number;
     rule: string;
 }
@@ -46,9 +45,8 @@ export interface SidebarBoundsVector {
     rule: string;
 }
 /**
- * The `MAX (…, adw_length_unit_to_px (…))` pair both widgets open with —
- * allocate flavour at adw-navigation-split-view.c:292-300 /
- * adw-overlay-split-view.c:452-460, measure flavour at :251-256 / :545-550.
+ * The `MAX (…, adw_length_unit_to_px (…))` pair both widgets open with, in both the
+ * allocate and the measure flavour.
  */
 export declare const SIDEBAR_BOUNDS_VECTORS: ReadonlyArray<SidebarBoundsVector>;
 /** One allocated-sidebar-width expectation. */
@@ -63,13 +61,12 @@ export interface SidebarWidthVector {
     sidebarChildMin: number;
     /** Overlay only: collapsed ignores the fraction and clamps the VIEW width. */
     collapsed: boolean;
-    /** The allocated sidebar width. */
     width: number;
     rule: string;
 }
 /**
- * `allocate_uncollapsed` (adw-navigation-split-view.c:292-304) versus
- * `get_sidebar_width` + `allocate_uncollapsed` (adw-overlay-split-view.c:441-466, :585).
+ * `allocate_uncollapsed` versus
+ * `get_sidebar_width` + `allocate_uncollapsed`.
  *
  * The 300px pair is the reason this table keys on `widget`: identical input, 180 in
  * the navigation split view and 100 in the overlay, because one caps the BOUND and
@@ -86,8 +83,7 @@ export interface NaturalSidebarWidthVector {
     rule: string;
 }
 /**
- * `measure_uncollapsed`'s sidebar estimate (adw-navigation-split-view.c:260-262,
- * adw-overlay-split-view.c:554-556) — the sidebar's OWN natural width is ignored.
+ * `measure_uncollapsed`'s sidebar estimate  — the sidebar's OWN natural width is ignored.
  *
  * CORE-ONLY: an internal step of a pipeline whose COMPOSED result is renderer-driven — driving it separately would assert the same thing twice (SIDEBAR_WIDTH_VECTORS)
  */
@@ -105,11 +101,10 @@ export interface SplitViewMeasureVector {
     rule: string;
 }
 /**
- * `measure_uncollapsed` (adw-overlay-split-view.c:558-563; the navigation variant at
- * adw-navigation-split-view.c:264-267 is the same rule at progress 1).
+ * `measure_uncollapsed`; the navigation variant is the same rule at progress 1.
  *
- * This is the container minimum neither renderer had — which is why in both of them
- * the content pane shrinks to nothing instead of the window refusing to get narrower.
+ * Without this container minimum the content pane shrinks to nothing instead of the window
+ * refusing to get narrower.
  *
  * CORE-ONLY: the container minimum lands as `min-width: min-content` on the content pane, which is CSS’s own spelling of the same rule — there is no computed number of ours to compare. Asserted in the renderer as "the pane is not crushable" instead
  */
@@ -124,7 +119,7 @@ export interface NavigationLayoutVector {
     content: SplitViewPaneRect;
     rule: string;
 }
-/** `allocate_uncollapsed` (adw-navigation-split-view.c:306-316). */
+/** `allocate_uncollapsed`. */
 export declare const NAVIGATION_SPLIT_VIEW_LAYOUT_VECTORS: ReadonlyArray<NavigationLayoutVector>;
 /** One `layoutOverlaySplitView` expectation. */
 export interface OverlayLayoutVector {
@@ -139,11 +134,10 @@ export interface OverlayLayoutVector {
     rule: string;
 }
 /**
- * `allocate_uncollapsed` (adw-overlay-split-view.c:572-610) and `allocate_collapsed`
- * (:653-703), plus `update_shield` (:249-256) and the snapshot gate (:757).
+ * `allocate_uncollapsed` and `allocate_collapsed`,
+ * plus `update_shield` and the snapshot gate.
  *
- * `shadowProgress` is inverted relative to the reveal — 1 means NO shadow
- * (adw-shadow-helper.c:234-249).
+ * `shadowProgress` is inverted relative to the reveal — 1 means NO shadow.
  */
 export declare const OVERLAY_SPLIT_VIEW_LAYOUT_VECTORS: ReadonlyArray<OverlayLayoutVector>;
 /** One `tagsConflict` expectation. */
@@ -153,7 +147,9 @@ export interface TagsConflictVector {
     conflict: boolean;
     rule: string;
 }
-/** `tags_equal` (adw-navigation-split-view.c:413-429).  *
+/**
+ * `tags_equal`.
+ *
  * CORE-ONLY: an internal step of a pipeline whose COMPOSED result is renderer-driven — driving it separately would assert the same thing twice (the tag guard, driven through NAVIGATION_ACTION_VECTORS and the refusal tests in both renderer suites)
  */
 export declare const TAGS_CONFLICT_VECTORS: ReadonlyArray<TagsConflictVector>;
@@ -169,7 +165,7 @@ export interface NavigationStackVector {
     rule: string;
 }
 /**
- * `update_navigation_stack` (adw-navigation-split-view.c:342-405).
+ * `update_navigation_stack`.
  *
  * The lone-child rows are the ones both renderers fail: their CSS / `visibility`
  * tables key on `show-content` alone, so a collapsed split view holding only a
@@ -193,8 +189,8 @@ export interface NavigationActionVector {
     rule: string;
 }
 /**
- * `navigation_push_cb` (adw-navigation-split-view.c:644-685) and `navigation_pop_cb`
- * (:687-702) — documented as working even when NOT collapsed (:124-132).
+ * `navigation_push_cb` and `navigation_pop_cb`
+ * — documented as working even when NOT collapsed.
  */
 export declare const NAVIGATION_ACTION_VECTORS: ReadonlyArray<NavigationActionVector>;
 /** The observable state of an `OverlaySplitViewState`. */
@@ -208,25 +204,22 @@ export interface OverlaySplitViewSnapshot {
 }
 /** One collapse-coupling expectation. */
 export interface OverlayCollapseVector {
-    /** Constructor options. */
     initial: {
         collapsed?: boolean;
         showSidebar?: boolean;
         pinSidebar?: boolean;
     };
-    /** State right after construction. */
     before: OverlaySplitViewSnapshot;
     /** The `collapsed` value to set. */
     setCollapsed: boolean;
-    /** State after the change. */
     after: OverlaySplitViewSnapshot;
     /** Which `notify::*` properties fire, in order. */
     notifications: ReadonlyArray<'show-sidebar' | 'collapsed'>;
     rule: string;
 }
 /**
- * `adw_overlay_split_view_init` (:1106-1116) + `set_collapsed` (:1439-1481) +
- * the can-focus pair (:330-331).
+ * `adw_overlay_split_view_init` + `set_collapsed` +
+ * the can-focus pair.
  *
  * `if (!self->pin_sidebar) set_show_sidebar (self, !self->collapsed, FALSE, 0);` is
  * the single rule BOTH storybooks re-implemented by hand because neither widget
@@ -243,7 +236,7 @@ export interface SwipeSnapPointVector {
     snapPoints: number[];
     rule: string;
 }
-/** `adw_overlay_split_view_get_snap_points` (adw-overlay-split-view.c:1214-1243). */
+/** `adw_overlay_split_view_get_snap_points`. */
 export declare const OVERLAY_SWIPE_SNAP_POINT_VECTORS: ReadonlyArray<SwipeSnapPointVector>;
 /** One `resolveSwipeStart` expectation. */
 export interface SwipeStartVector {
@@ -255,7 +248,7 @@ export interface SwipeStartVector {
     detected: boolean;
     rule: string;
 }
-/** `prepare_cb` (adw-overlay-split-view.c:362-387). */
+/** `prepare_cb`. */
 export declare const OVERLAY_SWIPE_START_VECTORS: ReadonlyArray<SwipeStartVector>;
 /** One `resolveSwipeRelease` expectation. */
 export interface SwipeReleaseVector {
@@ -267,7 +260,7 @@ export interface SwipeReleaseVector {
     showSidebarAfter: boolean;
     rule: string;
 }
-/** `end_swipe_cb` (adw-overlay-split-view.c:414-429). */
+/** `end_swipe_cb`. */
 export declare const OVERLAY_SWIPE_RELEASE_VECTORS: ReadonlyArray<SwipeReleaseVector>;
 /** One `swipeCancelProgress` expectation. */
 export interface SwipeCancelVector {
@@ -275,7 +268,7 @@ export interface SwipeCancelVector {
     cancelProgress: number;
     rule: string;
 }
-/** `adw_overlay_split_view_get_cancel_progress` (adw-overlay-split-view.c:1253-1258). */
+/** `adw_overlay_split_view_get_cancel_progress`. */
 export declare const OVERLAY_SWIPE_CANCEL_VECTORS: ReadonlyArray<SwipeCancelVector>;
 /** One `resolveSwipeArea` expectation. */
 export interface SwipeAreaVector {
@@ -295,7 +288,7 @@ export interface SwipeAreaVector {
     rule: string;
 }
 /**
- * `adw_overlay_split_view_get_swipe_area` (adw-overlay-split-view.c:1261-1290);
- * `ADW_SWIPE_BORDER` is 32 (adw-swipe-tracker-private.h:17).
+ * `adw_overlay_split_view_get_swipe_area`;
+ * `ADW_SWIPE_BORDER` is 32.
  */
 export declare const OVERLAY_SWIPE_AREA_VECTORS: ReadonlyArray<SwipeAreaVector>;

package/lib/types/conformance/tab-view.d.ts

@@ -109,11 +109,8 @@ export interface TabViewVectorSelection {
 }
 /** One expected page-list notification. */
 export interface TabViewVectorPagesChange {
-    /** Which kind of change. */
     kind: 'attached' | 'detached' | 'reordered' | 'pinned' | 'updated';
-    /** The page it happened to. */
     id: string;
-    /** Its index after the change. */
     position: number;
     /** Its index before the change, `-1` for `'attached'`. */
     previousPosition: number;
@@ -122,18 +119,15 @@ export interface TabViewVectorPagesChange {
  * How the `close-page` handler behaves for the whole row.
  *
  * `'default'` reproduces libadwaita's own default handler, `close_page_cb`'s
- * `close_page_finish (self, page, !adw_tab_page_get_pinned (page))`
- * (adw-tab-view.c:1986-1993) — the suites install a RECORDING wrapper around it
- * so the close-attempt order is observable, and the core suite additionally
- * replays the row with NO handler at all to prove the built-in default agrees.
- * `'defer'` holds every page in the closing state so `closePageFinish` decides.
+ * `close_page_finish (self, page, !adw_tab_page_get_pinned (page))`; the suites wrap it
+ * in a RECORDER so the close-attempt order is observable, and the core suite also
+ * replays the row with NO handler to prove the built-in default agrees. `'defer'` holds
+ * every page in the closing state so `closePageFinish` decides.
  */
 export type TabViewVectorHandler = 'default' | 'defer';
 /** One end-to-end tab-view expectation. */
 export interface TabViewVector {
-    /** What this row pins down. */
     rule: string;
-    /** The C function + lines it is derived from. */
     derivedFrom: string;
     /** The pages, seeded in this order (pinned ones via appendPinnedPage, parented ones via addPage). */
     pages: readonly TabViewVectorPage[];
@@ -141,7 +135,6 @@ export interface TabViewVector {
     handler?: TabViewVectorHandler;
     /** Selection changes emitted WHILE the pages are seeded (the auto-select), in order. */
     setupChanges: readonly TabViewVectorSelection[];
-    /** Operations applied after the pages exist. */
     ops: readonly TabViewVectorOp[];
     /**
      * Return value of each op, in order — `null` for the ops that return nothing.
@@ -157,7 +150,6 @@ export interface TabViewVector {
     closeAttempts?: readonly string[];
     /** Final page order. */
     order: readonly string[];
-    /** Final pinned-prefix length. */
     nPinnedPages: number;
     /** Final selected id, `null` for none. */
     selectedId: string | null;
@@ -171,19 +163,17 @@ export interface TabViewVector {
 /**
  * `Adw.TabView`'s selection, close protocol, partition and ordering, end to end.
  *
- * Read the `rule` of a row before changing it: most of them encode behaviour
- * NEITHER port had, and several encode behaviour a port had backwards.
+ * Read the `rule` of a row before changing it: most encode behaviour neither renderer had,
+ * and several encode behaviour a port had backwards.
  */
 export declare const TAB_VIEW_VECTORS: ReadonlyArray<TabViewVector>;
 /**
  * The surface a vector driver needs.
  *
- * Deliberately STRUCTURAL and named exactly as `TabViewState` names things, so
- * all three suites hand their subject straight to {@link applyTabViewOp} with no
- * translation layer: the core suite passes a `TabViewState`, the NativeScript
- * suite passes the state its widget delegates to, and the browser suite passes
- * the `<adw-tab-view>` element itself. A renderer that cannot be passed here has
- * stopped being a thin adapter, which is the thing these vectors exist to catch.
+ * Deliberately STRUCTURAL and named exactly as `TabViewState` names things, so all
+ * three suites hand their subject straight to {@link applyTabViewOp} with no
+ * translation layer. A renderer that cannot be passed here has stopped being a
+ * thin adapter, which is the thing these vectors exist to catch.
  */
 export interface TabViewVectorTarget {
     /** The ordered pages — only the three fields a vector reads. */
@@ -192,7 +182,6 @@ export interface TabViewVectorTarget {
         readonly title: string;
         readonly pinned: boolean;
     }[];
-    /** Length of the pinned prefix. */
     readonly nPinnedPages: number;
     /** Selected page id, `null` when the view is empty. */
     readonly selectedId: string | null;
@@ -251,14 +240,14 @@ export interface TabViewVectorTarget {
     setPageTitle(id: string, title: string | null): boolean;
 }
 /**
- * Seed a vector's pages, choosing the insertion call each page's declaration
- * implies: a pinned page through `appendPinnedPage` (so the pinned prefix builds up
- * in declaration order), a parented one through `addPage` (so the position is
- * DERIVED, which is itself under test), everything else through `append`.
+ * Seed a vector's pages, choosing the insertion call each page's declaration implies: a
+ * pinned page through `appendPinnedPage` (so the pinned prefix builds up in declaration
+ * order), a parented one through `addPage` (so the position is DERIVED, which is itself
+ * under test), everything else through `appendPage`.
  *
- * Every vector's declared order is also the order this produces — the core suite
- * asserts that right after seeding, which is what turns the fixtures themselves
- * into a test of `adw_tab_view_add_page`'s position derivation.
+ * Every vector's declared order is also the order this produces, asserted right after
+ * seeding — which turns the fixtures into a test of `adw_tab_view_add_page`'s position
+ * derivation.
  */
 export declare function seedTabViewPages(target: TabViewVectorTarget, pages: readonly TabViewVectorPage[]): void;
 /**
@@ -272,21 +261,17 @@ export declare function tabViewOrder(target: TabViewVectorTarget): string[];
 export declare function tabViewClosing(target: TabViewVectorTarget): string[];
 /** One `successorAfterClose` expectation — the close-successor kernel on its own. */
 export interface TabSuccessorVector {
-    /** What this row pins down. */
     rule: string;
     /** The C lines it is derived from. */
     derivedFrom: string;
-    /** The page list. */
     pages: readonly TabViewVectorPage[];
-    /** The page being closed. */
     closingId: string;
-    /** The currently-selected id. */
     selectedId: string | null;
     /** Who ends up selected — `null` when the view empties. */
     successorId: string | null;
 }
 /**
- * `select_previous_page` (adw-tab-view.c:1857-1897) with no view around it.
+ * `select_previous_page` with no view around it.
  *
  * These are the same rules the end-to-end rows exercise, stated as pure inputs
  * so a failure names the RULE rather than the script that reached it.
@@ -296,18 +281,15 @@ export interface TabSuccessorVector {
 export declare const TAB_SUCCESSOR_VECTORS: ReadonlyArray<TabSuccessorVector>;
 /** One `isDescendantOfPage` expectation. */
 export interface TabDescendantVector {
-    /** What this row pins down. */
     rule: string;
-    /** The page list. */
     pages: readonly TabViewVectorPage[];
-    /** The candidate descendant. */
     pageId: string | null;
-    /** The candidate ancestor. */
     parentId: string;
-    /** Whether the walk reaches the ancestor. */
     descendant: boolean;
 }
-/** `is_descendant_of` (adw-tab-view.c:1735-1742).  *
+/**
+ * `is_descendant_of`.
+ *
  * CORE-ONLY: an internal step of a pipeline whose COMPOSED result is renderer-driven — driving it separately would assert the same thing twice (TAB_VIEW_VECTORS)
  */
 export declare const TAB_DESCENDANT_VECTORS: ReadonlyArray<TabDescendantVector>;
@@ -321,36 +303,28 @@ export interface TabsRevealedVector {
     nPinnedPages: number;
     /** `adw_tab_view_get_is_transferring_page`. */
     isTransferringPage: boolean;
-    /** Whether the bar shows its tabs. */
     revealed: boolean;
-    /** What this row pins down. */
     rule: string;
 }
 /**
- * `update_autohide_cb` (adw-tab-bar.c:142-164), verbatim:
+ * `update_autohide_cb`, verbatim:
  * `!autohide || n_tabs > 1 || n_pinned_tabs >= 1 || is_transferring_page`.
  */
 export declare const TABS_REVEALED_VECTORS: ReadonlyArray<TabsRevealedVector>;
 /** One `tabCloseVisible` expectation. */
 export interface TabCloseVisibleVector {
-    /** Pointer is over the tab. */
     hovering: boolean;
     /** The tab is not clipped by the bar's scroll region. */
     fullyVisible: boolean;
-    /** The tab is selected. */
     selected: boolean;
-    /** The tab is being dragged. */
     dragging: boolean;
-    /** The tab is pinned. */
     pinned: boolean;
-    /** Whether the close button shows. */
     visible: boolean;
-    /** What this row pins down. */
     rule: string;
 }
 /**
- * `update_state`'s `show_close` (adw-tab.c:124) plus the pinned gate applied at
- * construction (adw-tab.c:645-650). Each port shipped a different single term of
+ * `update_state`'s `show_close` plus the pinned gate applied at
+ * construction. Each port shipped a different single term of
  * this — web showed it always, NS only on the selected tab.
  */
 export declare const TAB_CLOSE_VISIBLE_VECTORS: ReadonlyArray<TabCloseVisibleVector>;
@@ -360,26 +334,20 @@ export interface TabTooltipVector {
     tooltip: string;
     /** `AdwTabPage:title`. */
     title: string;
-    /** What the tab shows. */
     text: string;
     /** Whether that text is Pango markup rather than plain text. */
     markup: boolean;
-    /** What this row pins down. */
     rule: string;
 }
 /**
- * `update_tooltip` (adw-tab.c:137-146): a non-empty tooltip wins and is set as
+ * `update_tooltip`: a non-empty tooltip wins and is set as
  * MARKUP; an empty one falls back to the title, set as TEXT.
  *
- * WHO DRIVES THIS TABLE: only the core suite — and that is a GAP, not a reason.
- * "Neither port has tooltips at all" was true when this was written and is not
- * any more: the browser sets `tab.title = tabTooltip(page)`
- * (`elements/adw-tab-view.ts`) and NativeScript re-exports it as
- * `tabTooltipText` (`widgets/tab-view-state.ts`), so BOTH renderers consume
- * these rows today and neither is held to them. Both surfaces are readable from
- * their own suites, so wiring them is a loop, not new capability.
- *
- * CORE-ONLY: an internal step of a pipeline whose COMPOSED result is renderer-driven — driving it separately would assert the same thing twice (TAB_VIEW_VECTORS — both ports consume the derivation, which this header once denied)
+ * CORE-ONLY: GAP, not a reason. Both renderers consume the derivation — the
+ * browser sets `tab.title = tabTooltip(page)` (`elements/adw-tab-view.ts`),
+ * NativeScript re-exports it as `tabTooltipText` (`widgets/tab-view-state.ts`) —
+ * and neither is held to these rows. Both surfaces are readable from their own
+ * suites, so wiring them is a loop, not new capability.
  */
 export declare const TAB_TOOLTIP_VECTORS: ReadonlyArray<TabTooltipVector>;
 /** One `tabIconState` expectation. */
@@ -396,24 +364,17 @@ export interface TabIconStateVector {
     defaultIcon: string | null;
     /** The icon actually painted, `null` for none. */
     resolvedIcon: string | null;
-    /** Whether a spinner replaces the icon image. */
     spinner: boolean;
-    /** Whether the icon slot shows. */
     iconVisible: boolean;
-    /** Whether the indicator slot shows. */
     indicatorVisible: boolean;
-    /** What this row pins down. */
     rule: string;
 }
-/** `update_icons` (adw-tab.c:171-198). */
+/** `update_icons`. */
 export declare const TAB_ICON_STATE_VECTORS: ReadonlyArray<TabIconStateVector>;
 /** One page-descriptor normalization expectation. */
 export interface TabPageDescriptorVector {
-    /** What this row pins down. */
     rule: string;
-    /** The C property it is derived from. */
     derivedFrom: string;
-    /** The declared page. */
     spec: {
         id: string;
         title?: string | null;
@@ -423,11 +384,9 @@ export interface TabPageDescriptorVector {
         loading?: boolean;
         needsAttention?: boolean;
     };
-    /** Resolved `title`. */
     title: string;
     /** Resolved `tooltip`. */
     tooltip: string;
-    /** Resolved `icon`. */
     icon: string | null;
     /** Resolved `indicatorIcon`. */
     indicatorIcon: string | null;
@@ -440,7 +399,7 @@ export interface TabPageDescriptorVector {
  * What a declared page resolves to.
  *
  * The `null → ''` coercions are `g_set_str (&self->title, title ? title : "")`
- * (adw-tab-view.c:3021) and its tooltip twin (:3064). The icon fields do NOT
+ * and its tooltip twin. The icon fields do NOT
  * coerce: "no icon" is a state `tabIconState` branches on, so `null` has to
  * survive.
  *