@stapel/listings-react 0.18.1 → 0.19.0

package/src/default/ListingFeedCard.tsx

@@ -24,13 +24,27 @@
  * has no line to spare. A full row of "Sign in to save this" under every one
  * of twenty tiles is not twenty pieces of help — it is the feed.
  *
- * The fleet already has the mechanism for exactly this and it is not "hide the
- * reason": `GateReasonScopeContext` / `<PaneGate>` pool identical reasons and
- * render each ONCE for everything inside the scope, with every control's
- * `aria-describedby` still pointing at that single copy. **A container drawing
- * a feed should wrap `<FeedGrid>` in a `<PaneGate>`.** Unscoped, the reason
- * still renders — over the photo, visible, never behind a hover — because a
- * reason a person cannot read is the one outcome the doctrine forbids.
+ * The answer this card ships with is the INTERACTION DISCLOSURE the grid card
+ * and the SERP card were given in the desktop and mobile fix packs, and it is
+ * this card's DEFAULT rather than an opt-in — a two-column tile is the one
+ * surface in the pair with no line to put a sentence on, so a standing volume
+ * here has to overprint the photograph to exist at all.
+ *
+ * That default is a fix, not a preference. Measured on a live home feed: this
+ * was the last surface still printing "Sign in to do this" as standing copy,
+ * over the picture, under every tile — and the heart under it was html-
+ * `disabled`, so the one gesture that could have replaced the caption was
+ * swallowed by the control. Both halves are gone: nothing stands in the tile,
+ * and a tap on the heart discloses the reason and the container's sign-in
+ * door (`signIn`) while a visually-hidden copy keeps the refusal in the
+ * accessibility tree. A host that genuinely wants the standing sentence back
+ * asks for it by name with `blockedReason="text"`.
+ *
+ * `GateReasonScopeContext` / `<PaneGate>` remain the answer for the STANDING
+ * arm: they pool identical reasons and render each ONCE for everything inside
+ * the scope, with every control's `aria-describedby` still pointing at that
+ * single copy. A container drawing a feed in that arm should wrap
+ * `<FeedGrid>` in a `<PaneGate>`.
  *
  * ── Two lines of title, and then it stops ─────────────────────────────────
  *
@@ -43,14 +57,18 @@
 import type { CSSProperties, ReactElement, ReactNode } from "react";
 import { Flex, Typography } from "antd";
 import { SkinTheme } from "@stapel/tokens-antd/skin";
+import type { SignInCta } from "@stapel/core";
 import { useT } from "@stapel/core";
 import { radii, spacing } from "@stapel/tokens";
 import type { ListingCard as ListingCardData } from "../api/types.js";
 import { lifecycleCaption } from "../model/status.js";
+import { isListingViewed } from "../model/engagement.js";
+import { useEngagedListing } from "../headless/Engagement.js";
 import { LISTINGS_I18N_KEYS } from "../i18n/keys.js";
 import { FavoriteHeart } from "./favorite.js";
 import {
   CARD_TARGET_STYLE_HREF,
+  CARD_VIEWED_CLASS,
   CardTarget,
   cardTargetCss,
 } from "./ListingCard.js";
@@ -118,18 +136,32 @@ export interface ListingFeedCardBaseProps extends ThemeModeProp {
   /** Hide the favourite entirely — for a surface where it makes no sense.
    * NOT a way to hide it from visitors. */
   readonly showFavorite?: boolean;
+  /**
+   * How loudly a blocked heart states its refusal. **`"popover"` by default
+   * on this card, unlike the other two** — a feed tile has no line to print a
+   * sentence on, so the standing arm can only overprint the photograph. See
+   * the file header for the measurement that made it the default.
+   */
+  readonly blockedReason?: "text" | "popover";
+  /** The container's sign-in door, rendered INSIDE the disclosure. Absent:
+   * the disclosure holds the reason alone. */
+  readonly signIn?: SignInCta;
 }
 
 export type ListingFeedCardProps = ListingFeedCardBaseProps & ListingCardOpenProps;
 
 export function ListingFeedCard(props: ListingFeedCardProps): ReactElement {
   const t = useT();
-  const { listing } = props;
+  // See `<ListingCard>`: the scope's overlay over the row, or the row. This
+  // is the surface it matters most on — a home feed is drawn from search.
+  const listing = useEngagedListing(props.listing);
   const status =
     listing.status === undefined ? undefined : lifecycleCaption(listing.status);
   const title = listing.title ?? "";
   const targetLabel =
     title.length > 0 ? title : t(LISTINGS_I18N_KEYS.cardUntitled);
+  // Already seen — `false` for every response that carries no such field.
+  const viewed = isListingViewed(listing);
 
   return (
     <SkinTheme
@@ -149,6 +181,9 @@ export function ListingFeedCard(props: ListingFeedCardProps): ReactElement {
         {...(status !== undefined
           ? { "data-listing-status": status.status }
           : {})}
+        {...(viewed
+          ? { className: CARD_VIEWED_CLASS, "data-listing-viewed": "true" }
+          : {})}
       >
         {/* One anchor over the whole tile. The photo is a still `<img>`, so
             unlike the SERP card's swipeable strip it is safe inside a link —
@@ -211,6 +246,8 @@ export function ListingFeedCard(props: ListingFeedCardProps): ReactElement {
             listingId={listing.id}
             favorited={listing.is_favorited}
             testId="listings-feed-favorite"
+            blockedReason={props.blockedReason ?? "popover"}
+            {...(props.signIn !== undefined ? { signIn: props.signIn } : {})}
             style={HEART}
           />
         )}

package/src/default/ListingPrice.tsx

@@ -37,8 +37,19 @@ import {
 import { LISTINGS_I18N_KEYS } from "../i18n/keys.js";
 
 export interface ListingPriceProps {
-  /** The amount as the wire spells it — a decimal string. */
-  readonly amount: string | undefined;
+  /**
+   * The amount as the wire spells it — a decimal string, or `null` for a
+   * listing that carries no price at all.
+   *
+   * `null` is in the TYPE since stapel-listings 0.17 spelled it in the
+   * schema (`price?: string | null`, D51: a blank price stays null
+   * server-side). It was always in the DATA — `hasAmount` below has guarded
+   * for it from the start, with a comment saying the serializer hands it
+   * through an unguarded `string | undefined`. Now the type says what the
+   * runtime already knew, and the guard stops being a defence against its
+   * own signature.
+   */
+  readonly amount: string | null | undefined;
   /** The code the amount is quoted in (`Listing.currency`). */
   readonly currency?: string | undefined;
 }

package/src/default/ListingSerpCard.tsx

@@ -76,6 +76,7 @@
 import type { CSSProperties, ReactElement, ReactNode } from "react";
 import { Card, Flex, Typography, theme as antdTheme } from "antd";
 import { SkinTheme } from "@stapel/tokens-antd/skin";
+import type { SignInCta } from "@stapel/core";
 import { useT } from "@stapel/core";
 import { fontSize, spacing } from "@stapel/tokens";
 import { FeatureBadges } from "@stapel/attributes-react/default";
@@ -87,6 +88,8 @@ import {
 } from "../model/features.js";
 import type { FeatureCopySource } from "../model/features.js";
 import { lifecycleCaption } from "../model/status.js";
+import { isListingViewed } from "../model/engagement.js";
+import { useEngagedListing } from "../headless/Engagement.js";
 import { LISTINGS_I18N_KEYS } from "../i18n/keys.js";
 import { PriceTrendIcon } from "./icons.js";
 import { FavoriteHeart } from "./favorite.js";
@@ -96,6 +99,7 @@ import {
   CARD_MEDIA_CLASS,
   CARD_QUERY_CLASS,
   CARD_TARGET_STYLE_HREF,
+  CARD_VIEWED_CLASS,
   CardTarget,
   cardTargetCss,
 } from "./ListingCard.js";
@@ -149,6 +153,14 @@ export interface ListingSerpCardBaseProps
   /** Hide the favourite entirely — for a surface where it makes no sense (the
    * owner's own listings). NOT a way to hide it from visitors. */
   readonly showFavorite?: boolean;
+  /** How loudly the blocked heart states its refusal (D45) — `"text"`
+   * (default) keeps the standing sentence, `"popover"` moves it onto the
+   * gesture. A phone SERP is the surface that needed the choice: fourteen
+   * cards printed fourteen copies of one sentence. */
+  readonly blockedReason?: "text" | "popover";
+  /** The container's sign-in door, shown inside the disclosure when the
+   * refusal is a `"popover"`. */
+  readonly signIn?: SignInCta;
 }
 
 export type ListingSerpCardProps = ListingSerpCardBaseProps & ListingCardOpenProps;
@@ -163,7 +175,9 @@ const BODY: CSSProperties = { flex: "1 1 auto", minWidth: 0 };
 
 export function ListingSerpCard(props: ListingSerpCardProps): ReactElement {
   const t = useT();
-  const { listing, priceTrend } = props;
+  const { priceTrend } = props;
+  // See `<ListingCard>`: the scope's overlay over the row, or the row.
+  const listing = useEngagedListing(props.listing);
   const { token } = antdTheme.useToken();
 
   const badgeDaos = asFeatureDaoList(listing.features_badges);
@@ -191,6 +205,8 @@ export function ListingSerpCard(props: ListingSerpCardProps): ReactElement {
   const photos = listing.images ?? [];
   const currency =
     listing.currency !== undefined ? { currency: listing.currency } : {};
+  // Already seen — `false` for every response that carries no such field.
+  const viewed = isListingViewed(listing);
 
   const rail =
     props.actionsRail !== undefined || props.showFavorite !== false ? (
@@ -207,6 +223,10 @@ export function ListingSerpCard(props: ListingSerpCardProps): ReactElement {
             listingId={listing.id}
             favorited={listing.is_favorited}
             testId="listings-serp-favorite"
+            {...(props.blockedReason !== undefined
+              ? { blockedReason: props.blockedReason }
+              : {})}
+            {...(props.signIn !== undefined ? { signIn: props.signIn } : {})}
           />
         )}
       </Flex>
@@ -227,6 +247,9 @@ export function ListingSerpCard(props: ListingSerpCardProps): ReactElement {
         {...(status !== undefined
           ? { "data-listing-status": status.status }
           : {})}
+        {...(viewed
+          ? { className: CARD_VIEWED_CLASS, "data-listing-viewed": "true" }
+          : {})}
         styles={{ body: { minWidth: 0, padding: token.paddingSM } }}
         style={{ ["--listing-card-focus" as string]: token.colorPrimary }}
       >

package/src/default/favorite.tsx

@@ -26,11 +26,14 @@
  * list or a grid of these cards should wrap it in one.
  */
 import type { CSSProperties, ReactElement } from "react";
+import { theme as antdTheme } from "antd";
 import { SkinButton as Button } from "@stapel/tokens-antd/skin";
-import { GatedControl } from "@stapel/tokens-antd/skin";
-import { useT } from "@stapel/core";
+import { ErrorAlert, GatedControl } from "@stapel/tokens-antd/skin";
+import type { SignInCta } from "@stapel/core";
+import { useActionGate, useT } from "@stapel/core";
 import { useFavoriteToggle } from "../headless/Favorites.js";
 import { LISTINGS_I18N_KEYS } from "../i18n/keys.js";
+import { GateReasonPopover } from "./GateReasonPopover.js";
 import { HeartIcon } from "./icons.js";
 
 export interface FavoriteHeartProps {
@@ -43,6 +46,22 @@ export interface FavoriteHeartProps {
   /** `"inline"` puts the reason beside the heart, `"stack"` (default) under
    * it — the choice belongs to the surface, which knows its own geometry. */
   readonly layout?: "stack" | "inline";
+  /**
+   * How loudly the refusal is stated on THIS surface (D45).
+   *
+   * `"text"` (default) keeps the standing sentence beside the heart — what
+   * this control has always done, and the right answer where one card is the
+   * screen. `"popover"` moves it onto the gesture: a signed-out phone SERP
+   * printed "sign in to do this" once under every one of fourteen cards, in
+   * the line where a price belongs, and fourteen copies of one sentence is
+   * not fourteen pieces of help. The reason never leaves the accessibility
+   * tree either way — see {@link GateReasonPopover}.
+   */
+  readonly blockedReason?: "text" | "popover";
+  /** The surface's sign-in door, rendered INSIDE the disclosure. Absent: the
+   * disclosure holds the reason alone. Only read in the `"popover"` arm; the
+   * standing arm's door is the container's, as it always was. */
+  readonly signIn?: SignInCta;
   readonly style?: CSSProperties;
 }
 
@@ -52,15 +71,75 @@ export interface FavoriteHeartProps {
  * (`signIn`) is the surface's business, not this control's — a disabled antd
  * button fires no pointer events, so a tooltip here would be a reason nobody
  * could read on any device (`stapel/no-tooltip-in-skin`).
+ *
+ * ── It is never html-`disabled`, in either volume ─────────────────────────
+ *
+ * `aria-disabled` plus a live handler, always. The refusal happens on
+ * ACTIVATION — `useFavoriteToggle().toggle` is a no-op while the gate is
+ * blocked, so the click cannot write anything — and that is the only shape of
+ * refusal a person can interrogate. A `disabled` DOM button is inert: it
+ * takes no focus, receives no pointer events, and swallows the very tap that
+ * was supposed to explain it. Measured on a phone: a signed-out visitor's
+ * heart produced no toast, no reason and no navigation, and on a touch device
+ * there is no hover to fall back on.
  */
 export function FavoriteHeart(props: FavoriteHeartProps): ReactElement {
   const t = useT();
+  const { token } = antdTheme.useToken();
   const favorite = useFavoriteToggle(props.listingId, props.favorited);
   const label = t(
     favorite.favorited
       ? LISTINGS_I18N_KEYS.cardFavoriteRemove
       : LISTINGS_I18N_KEYS.cardFavoriteAdd
   );
+  // Saved is a SOLID accent shape, not-saved is the outline. `is_favorited:
+  // null` — an anonymous read's "nobody asked" — resolves to not-saved in the
+  // bag, so it draws the outline and never a third look of its own.
+  const icon = (
+    <HeartIcon
+      filled={favorite.favorited}
+      {...(favorite.favorited ? { color: token.colorPrimary } : {})}
+    />
+  );
+  // The RESOLVED sentence, not the gate's key — `useActionGate` is the one
+  // place a blocked reason becomes words in this fleet.
+  const reason = useActionGate(favorite.gate).reason;
+  // A failed save, stated where the heart is. The rollback already put the
+  // icon back; this says why it went back.
+  const failure = (
+    <ErrorAlert
+      testId={`${props.testId}-error`}
+      thrown={favorite.error}
+      variant="inline"
+    />
+  );
+  if (props.blockedReason === "popover" && reason !== undefined) {
+    return (
+      <GateReasonPopover
+        reason={reason}
+        cta={props.signIn}
+        testId={`${props.testId}-reason`}
+        signInTestId={`${props.testId}-sign-in`}
+      >
+        {(bind) => (
+          <Button
+            shape="circle"
+            aria-disabled
+            {...bind}
+            aria-label={label}
+            aria-pressed={favorite.favorited}
+            data-testid={props.testId}
+            data-favorited={String(favorite.favorited)}
+            data-analytics="none"
+            data-analytics-reason="business action — host app wraps with its own tracked()"
+            onClick={favorite.toggle}
+            icon={icon}
+            {...(props.style !== undefined ? { style: props.style } : {})}
+          />
+        )}
+      </GateReasonPopover>
+    );
+  }
   return (
     <GatedControl
       gate={favorite.gate}
@@ -69,22 +148,22 @@ export function FavoriteHeart(props: FavoriteHeartProps): ReactElement {
       {...(props.style !== undefined ? { style: props.style } : {})}
     >
       {(bind) => (
-        <Button
-          shape="circle"
-          disabled={bind.disabled}
-          data-disabled-reason="the enclosing <GatedControl> renders the gate's reason beside this button"
-          {...(bind["aria-describedby"] !== undefined
-            ? { "aria-describedby": bind["aria-describedby"] }
-            : {})}
-          aria-label={label}
-          aria-pressed={favorite.favorited}
-          data-testid={props.testId}
-          data-favorited={String(favorite.favorited)}
-          data-analytics="none"
-          data-analytics-reason="business action — host app wraps with its own tracked()"
-          onClick={favorite.toggle}
-          icon={<HeartIcon filled={favorite.favorited} />}
-        />
+        <>
+          <Button
+            shape="circle"
+            // See `<ListingCard>`: the substrate's binding, spread whole.
+            {...bind}
+            aria-label={label}
+            aria-pressed={favorite.favorited}
+            data-testid={props.testId}
+            data-favorited={String(favorite.favorited)}
+            data-analytics="none"
+            data-analytics-reason="business action — host app wraps with its own tracked()"
+            onClick={favorite.toggle}
+            icon={icon}
+          />
+          {failure}
+        </>
       )}
     </GatedControl>
   );

package/src/default/icons.tsx

@@ -13,14 +13,32 @@
  */
 import type { ReactElement } from "react";
 
-export function HeartIcon(props: { filled: boolean }): ReactElement {
+export interface HeartIconProps {
+  /** Saved: the glyph is a solid shape rather than an outline. THE state a
+   * person reads off a card, so it is the one prop this icon has. */
+  readonly filled: boolean;
+  /**
+   * The accent a SAVED heart is painted in — an antd theme token the caller
+   * resolved (`token.colorPrimary`), never a literal.
+   *
+   * The icon stays `currentColor` by default, which is what keeps it
+   * theme-neutral in every other state; this is the one place a colour is
+   * warranted, because "filled" and "outline" of the same neutral grey is a
+   * difference a person reads at a glance on a mock-up and misses entirely on
+   * a 170px feed tile in daylight.
+   */
+  readonly color?: string;
+}
+
+export function HeartIcon(props: HeartIconProps): ReactElement {
+  const paint = props.color ?? "currentColor";
   return (
     <svg
       width="16"
       height="16"
       viewBox="0 0 24 24"
-      fill={props.filled ? "currentColor" : "none"}
-      stroke="currentColor"
+      fill={props.filled ? paint : "none"}
+      stroke={paint}
       strokeWidth="2"
       strokeLinecap="round"
       strokeLinejoin="round"

package/src/default/index.ts

@@ -39,6 +39,10 @@ export {
   // threshold (and for a test that measures it). See `<ListingCard>`'s header.
   LISTING_CARD_ROW_MIN,
   LISTING_CARD_ROW_MEDIA,
+  // The already-seen mark, for a container that wants to dim its own chrome
+  // on the same rule (and for a test that reads it). All three cards take it.
+  CARD_VIEWED_CLASS,
+  LISTING_VIEWED_OPACITY,
 } from "./ListingCard.js";
 export type {
   ListingCardProps,

package/src/headless/Engagement.tsx

@@ -0,0 +1,177 @@
+/**
+ * The ENGAGEMENT OVERLAY as a scope: one request for a page of cards, read by
+ * every card in it without a single extra prop.
+ *
+ * ── The problem this shape exists to solve ────────────────────────────────
+ *
+ * `viewed`, `view_count` and `is_favorited` are on stapel-listings' own card
+ * and detail serializers, so a listing PAGE and this module's own card list
+ * carry them and need nothing here. The two surfaces a buyer actually
+ * scrolls do not: a storefront's home feed and its SERP are drawn by
+ * `@stapel/search-react` from the search index, whose stored document can
+ * hold neither a flag that differs per reader nor a counter that moves faster
+ * than a re-index. Those rows reach `<ListingCard>` with no engagement fields
+ * at all — so without this, every card on the two screens the feature was
+ * built for renders undimmed with an outline heart no matter what the person
+ * has done, and nothing anywhere reports a fault.
+ *
+ * ── Why a SCOPE and not a prop ────────────────────────────────────────────
+ *
+ * Because the cost is per PAGE and the reader is per CARD, and a design that
+ * puts those in the same place gets one of them wrong. A `engagement` prop on
+ * the card would make each card responsible for its own answer, and the
+ * shortest way to satisfy that is one request per card — forty requests for a
+ * decoration, which is the exact N+1 the batch endpoint exists to prevent.
+ * The container knows the page; the card knows its id. So the container opens
+ * a scope with the ids it just rendered, ONE query runs, and each card looks
+ * itself up. It is the arrangement `GateReasonScopeContext` / `<PaneGate>`
+ * already use in this fleet for the same shape of problem.
+ *
+ * ```tsx
+ * <ListingEngagementScope ids={items.map((item) => item.id)}>
+ *   <FeedGrid>
+ *     {items.map((item) => <ListingFeedCard key={item.id} listing={item.card} … />)}
+ *   </FeedGrid>
+ * </ListingEngagementScope>
+ * ```
+ *
+ * ── No scope is a first-class answer ──────────────────────────────────────
+ *
+ * A card outside a scope fires NOTHING and draws from its row exactly as it
+ * did before this module existed — which is right for this module's own card
+ * list and for the listing page, whose rows already carry the fields. Absent,
+ * empty, in-flight and FAILED are all the same silent no-op: no dimming, no
+ * count, no banner over a grid that is otherwise working. A grid that renders
+ * is worth more than a flag.
+ */
+import { createContext, useContext, useMemo } from "react";
+import type { Context, ReactElement, ReactNode } from "react";
+import { loadFailed, loadLoading, loadReady } from "@stapel/core";
+import type { LoadState } from "@stapel/core";
+import type {
+  ListingCard,
+  ListingEngagement,
+  ListingEngagementBatch,
+} from "../api/types.js";
+import { engagementIds } from "../api/types.js";
+import { useListingEngagement } from "../model/queries.js";
+import { engagementFor, withEngagement } from "../model/engagement.js";
+
+/** What the scope publishes: the batch, however it is doing. */
+export interface ListingEngagementBag {
+  /** This listing's entry, or `undefined` for an id the answer did not carry
+   * — which includes "the read has not landed" and "the read failed". */
+  overlayFor(id: number): ListingEngagement | undefined;
+  /** The read's own state, for a host that wants to know. NOTHING in this
+   * pair renders the failed arm: see the file header. */
+  readonly state: LoadState<ListingEngagementBatch>;
+  /** The normalized ids actually asked for — after the sort, the de-dupe and
+   * the server's own cap. A caller can compare it with what it handed in to
+   * see that a hundred-and-forty-card page was truncated. */
+  readonly ids: readonly number[];
+}
+
+const NO_OVERLAY: ListingEngagementBag = {
+  overlayFor: () => undefined,
+  state: loadLoading(),
+  ids: [],
+};
+
+/**
+ * The scope. `null` outside a provider — and `null` is not an error, it is a
+ * container that never opted in.
+ */
+export const ListingEngagementContext: Context<ListingEngagementBag | null> =
+  createContext<ListingEngagementBag | null>(null);
+
+export interface UseListingEngagementOverlayOptions {
+  /** Hold the request (a grid that has not resolved its rows yet). */
+  readonly enabled?: boolean;
+}
+
+/**
+ * Run the batch read for a page of ids and get the bag back.
+ *
+ * The headless half: a host rendering its own visuals over its own grid calls
+ * this directly. A host using this pair's cards wraps them in
+ * {@link ListingEngagementScope} instead, which calls this once and puts the
+ * bag where the cards can find it.
+ */
+export function useListingEngagementOverlay(
+  ids: readonly number[],
+  options: UseListingEngagementOverlayOptions = {}
+): ListingEngagementBag {
+  const query = useListingEngagement(
+    ids,
+    options.enabled !== undefined ? { enabled: options.enabled } : {}
+  );
+  const wanted = useMemo(() => engagementIds(ids), [ids]);
+  const batch = query.data;
+  return useMemo(
+    () => ({
+      overlayFor: (id: number) => engagementFor(batch, id),
+      state:
+        query.status === "error"
+          ? loadFailed(query.error)
+          : batch !== undefined
+            ? loadReady(batch)
+            : loadLoading(),
+      ids: wanted,
+    }),
+    [batch, query.status, query.error, wanted]
+  );
+}
+
+export interface ListingEngagementScopeProps
+  extends UseListingEngagementOverlayOptions {
+  /** The listing ids on this page — normalized before the request, so the
+   * caller may hand them in any order and need not de-duplicate. */
+  readonly ids: readonly number[];
+  readonly children: ReactNode;
+}
+
+/**
+ * One request for the page, one lookup for every card inside it.
+ *
+ * Renderless: it draws no element of its own, so it can be wrapped around a
+ * grid without entering its layout.
+ */
+export function ListingEngagementScope(
+  props: ListingEngagementScopeProps
+): ReactElement {
+  const bag = useListingEngagementOverlay(
+    props.ids,
+    props.enabled !== undefined ? { enabled: props.enabled } : {}
+  );
+  return (
+    <ListingEngagementContext.Provider value={bag}>
+      {props.children}
+    </ListingEngagementContext.Provider>
+  );
+}
+
+/** The scope's bag, or a permanently-empty one outside a scope. Never throws:
+ * a card must render everywhere, wired or not. */
+export function useListingEngagementScope(): ListingEngagementBag {
+  return useContext(ListingEngagementContext) ?? NO_OVERLAY;
+}
+
+/** One listing's overlay entry, or `undefined`. */
+export function useEngagementOverlay(
+  id: number
+): ListingEngagement | undefined {
+  return useListingEngagementScope().overlayFor(id);
+}
+
+/**
+ * A row with the scope's answer laid over it — what every card in this pair
+ * actually reads.
+ *
+ * Outside a scope, or for an id the batch did not carry, this returns the
+ * SAME object it was given, so a card that never opted in re-renders exactly
+ * as often as it used to.
+ */
+export function useEngagedListing(row: ListingCard): ListingCard {
+  const overlay = useEngagementOverlay(row.id);
+  return useMemo(() => withEngagement(row, overlay), [row, overlay]);
+}