@agg-build/ui 4.7.2 → 4.7.3

package/dist/trading.mjs

@@ -12,7 +12,7 @@ import {
   parseVenue,
   useClaimWinnings,
   useResolvedMarketClaim
-} from "./chunk-KDBKKJ7W.mjs";
+} from "./chunk-SQ4BA3CC.mjs";
 import {
   SETTLEMENT_SECTION_ID,
   Settlement,
@@ -30,9 +30,9 @@ import {
   prepareSettlementDifferences,
   resolveDifferenceIconClassName,
   useEventTradingContext
-} from "./chunk-WYCSTAN7.mjs";
-import "./chunk-XN2NB2NP.mjs";
-import "./chunk-RDBMHBR2.mjs";
+} from "./chunk-MAQ52KM5.mjs";
+import "./chunk-XR6C3MZX.mjs";
+import "./chunk-UQ7XJIAZ.mjs";
 export {
   FundKalshiModal,
   PlaceOrder,

package/dist/types/pages/event-market/sports-event-market.utils.d.mts

@@ -97,6 +97,16 @@ export declare const resolveSportsSectionMarkets: ({ tab, eventMarkets, sectionM
 }) => VenueMarket[];
 export declare const resolveSportsMarketCardVariant: (market: VenueMarket) => SportsMarketCardVariant;
 export declare const isBinarySportsMoneylineMarket: (market: VenueMarket) => boolean;
+/**
+ * True when this spread row's outcome 0 is the side RECEIVING points.
+ *
+ * `_sp_{team}_m{line}` puts the favourite at outcome 0 ("Yes = {team} covers
+ * −line"); `_sp_{team}_p{line}` puts the underdog there (novig 2026-09-01:
+ * `…_sp_tb_p1p5` outcomes read `Yes/TB +1.5 | No/NYM −1.5`). Callers that label
+ * pills "favourite −X / dog +X" must swap the two indices for these rows or the
+ * card shows the underdog priced as the favourite.
+ */
+export declare const isSpreadUnderdogLeg: (market: VenueMarket) => boolean;
 export declare const isSpreadTeamTitle: (title: string | null | undefined) => boolean;
 /**
  * Resolve favored/dog team display names for a spread market's two outcomes,
@@ -105,9 +115,9 @@ export declare const isSpreadTeamTitle: (title: string | null | undefined) => bo
  * A kalshi/limitless anchor stores `Yes`/`No` labels with no clean team title,
  * so the pill would read "Yes +1.5". But the same signed line has cross-venue
  * twins (identical `_sp_{fav}_{line}` aggKey) from poly/predict that DO carry the
- * team name as the outcome title. Outcome index 0 is the favored side (covers
- * the spread) on every venue keyed `_sp_{fav}`. So borrow the fullest clean
- * title at each index. Returns `null` for a side when no twin has a team title
+ * team name as the outcome title. Outcome index 0 is the team the KEY names, so
+ * borrow the fullest clean title at each index, then assign the favoured/dog
+ * ROLES from the key's leg token (see `isSpreadUnderdogLeg`). Returns `null` for a side when no twin has a team title
  * (→ caller falls back to the raw `Yes`/`No` label). Null-aggKey spreads can't
  * be matched to twins, so only the market's own titles are considered.
  */
@@ -117,17 +127,8 @@ export declare const resolveSpreadOutcomeTeamNames: (activeMarket: VenueMarket,
 };
 /** The per-leg pill label for a combined (decomposed) moneyline group. */
 export declare const resolveCombinedMoneylineLegLabel: (market: VenueMarket) => string;
-/**
- * Combined per-leg moneyline pills are only meaningful when every leg carries a
- * DISTINCT label. Cross-venue duplicates of the SAME 2-way single that never
- * merged (e.g. poly + predict "… (BO5) - Match Winner") collapse to identical
- * labels — rendering them as separate pills shows the same Yes price twice as
- * if it were two different options. Non-distinct → the card falls back to the
- * standard single-market rendering (team-title pills).
- */
-export declare const areCombinedMoneylineLegsDistinct: (markets: VenueMarket[]) => boolean;
-export declare const buildSportsMarketDisplayGroups: (markets: VenueMarket[]) => SportsMarketDisplayGroup[];
-export declare const groupSportsMarketsByPeriod: (markets: VenueMarket[]) => SportsPeriodGroup[];
+export declare const buildSportsMarketDisplayGroups: (markets: VenueMarket[], sport?: string | null) => SportsMarketDisplayGroup[];
+export declare const groupSportsMarketsByPeriod: (markets: VenueMarket[], sport?: string | null) => SportsPeriodGroup[];
 export type SportsGameLineSlideKind = "to_advance" | "moneyline" | "spread" | "total" | "other";
 export type SportsGameLineSlideStop = {
     /** Display value for the ladder chip, e.g. "1.5", "216.5". */
@@ -151,6 +152,38 @@ export declare const collectVenueNames: (market: VenueMarket) => string[];
 export declare const resolveTotalGroupVolume: (markets: VenueMarket[]) => number;
 export declare const resolveSportsExpandedMarkets: (markets: VenueMarket[]) => VenueMarket[];
 export declare const resolveSportsExpandedMarketsVolume: (markets: VenueMarket[]) => number;
+export type SportsCombinedLeg = {
+    /** Pill label — the fullest clean leg name across the venues offering it. */
+    label: string;
+    /** Highest-volume market at this leg; drives the order book and order ticket. */
+    market: VenueMarket;
+    /** Every venue offering this leg, including the representative's own. */
+    venues: string[];
+};
+/**
+ * The per-leg pills for a group a venue published as a DECOMPOSITION — one bare
+ * Yes/No market per outcome of a single N-way question — or `null` when the
+ * group is not one and should render as an ordinary card.
+ *
+ * Two shapes share the same subtype and must NOT render the same way:
+ *
+ *  • a real decomposition (poly's three `soccer_halftime_result` legs), which
+ *    belongs in one card with a pill per leg, and
+ *  • a plain binary that several venues each list once (poly + novig "Both
+ *    Teams to Score"), which is ONE Yes/No market with cross-venue twins.
+ *
+ * "Some venue published more than one leg" separates them structurally, with no
+ * guessing from prose. The moneyline path is deliberately exempt: it is gated on
+ * `isBinarySportsMoneylineMarket` and has shipped this way.
+ *
+ * Cross-venue twins are folded by QUESTION, not by label — poly and predict
+ * phrase a leg identically ("Real Betis Balompié leading at halftime?") while
+ * labelling it "Real Betis Balompié" vs "BET" — and the fullest label wins, the
+ * same preference `resolveSpreadOutcomeTeamNames` applies to spread pills.
+ *
+ * ponytail: O(n) map build over one group's markets (a handful of rows).
+ */
+export declare const resolveSportsCombinedLegs: (group: Pick<SportsMarketDisplayGroup, "markets" | "sportsMarketType">) => SportsCombinedLeg[] | null;
 export declare const buildSportsSlideFromGroup: (group: SportsMarketDisplayGroup) => SportsGameLineSlide;
 /**
  * Derive the Moneyline / Spreads / Total game-line slides (in that order) from a

package/dist/types/pages/event-market/sports-event-market.utils.d.ts

@@ -97,6 +97,16 @@ export declare const resolveSportsSectionMarkets: ({ tab, eventMarkets, sectionM
 }) => VenueMarket[];
 export declare const resolveSportsMarketCardVariant: (market: VenueMarket) => SportsMarketCardVariant;
 export declare const isBinarySportsMoneylineMarket: (market: VenueMarket) => boolean;
+/**
+ * True when this spread row's outcome 0 is the side RECEIVING points.
+ *
+ * `_sp_{team}_m{line}` puts the favourite at outcome 0 ("Yes = {team} covers
+ * −line"); `_sp_{team}_p{line}` puts the underdog there (novig 2026-09-01:
+ * `…_sp_tb_p1p5` outcomes read `Yes/TB +1.5 | No/NYM −1.5`). Callers that label
+ * pills "favourite −X / dog +X" must swap the two indices for these rows or the
+ * card shows the underdog priced as the favourite.
+ */
+export declare const isSpreadUnderdogLeg: (market: VenueMarket) => boolean;
 export declare const isSpreadTeamTitle: (title: string | null | undefined) => boolean;
 /**
  * Resolve favored/dog team display names for a spread market's two outcomes,
@@ -105,9 +115,9 @@ export declare const isSpreadTeamTitle: (title: string | null | undefined) => bo
  * A kalshi/limitless anchor stores `Yes`/`No` labels with no clean team title,
  * so the pill would read "Yes +1.5". But the same signed line has cross-venue
  * twins (identical `_sp_{fav}_{line}` aggKey) from poly/predict that DO carry the
- * team name as the outcome title. Outcome index 0 is the favored side (covers
- * the spread) on every venue keyed `_sp_{fav}`. So borrow the fullest clean
- * title at each index. Returns `null` for a side when no twin has a team title
+ * team name as the outcome title. Outcome index 0 is the team the KEY names, so
+ * borrow the fullest clean title at each index, then assign the favoured/dog
+ * ROLES from the key's leg token (see `isSpreadUnderdogLeg`). Returns `null` for a side when no twin has a team title
  * (→ caller falls back to the raw `Yes`/`No` label). Null-aggKey spreads can't
  * be matched to twins, so only the market's own titles are considered.
  */
@@ -117,17 +127,8 @@ export declare const resolveSpreadOutcomeTeamNames: (activeMarket: VenueMarket,
 };
 /** The per-leg pill label for a combined (decomposed) moneyline group. */
 export declare const resolveCombinedMoneylineLegLabel: (market: VenueMarket) => string;
-/**
- * Combined per-leg moneyline pills are only meaningful when every leg carries a
- * DISTINCT label. Cross-venue duplicates of the SAME 2-way single that never
- * merged (e.g. poly + predict "… (BO5) - Match Winner") collapse to identical
- * labels — rendering them as separate pills shows the same Yes price twice as
- * if it were two different options. Non-distinct → the card falls back to the
- * standard single-market rendering (team-title pills).
- */
-export declare const areCombinedMoneylineLegsDistinct: (markets: VenueMarket[]) => boolean;
-export declare const buildSportsMarketDisplayGroups: (markets: VenueMarket[]) => SportsMarketDisplayGroup[];
-export declare const groupSportsMarketsByPeriod: (markets: VenueMarket[]) => SportsPeriodGroup[];
+export declare const buildSportsMarketDisplayGroups: (markets: VenueMarket[], sport?: string | null) => SportsMarketDisplayGroup[];
+export declare const groupSportsMarketsByPeriod: (markets: VenueMarket[], sport?: string | null) => SportsPeriodGroup[];
 export type SportsGameLineSlideKind = "to_advance" | "moneyline" | "spread" | "total" | "other";
 export type SportsGameLineSlideStop = {
     /** Display value for the ladder chip, e.g. "1.5", "216.5". */
@@ -151,6 +152,38 @@ export declare const collectVenueNames: (market: VenueMarket) => string[];
 export declare const resolveTotalGroupVolume: (markets: VenueMarket[]) => number;
 export declare const resolveSportsExpandedMarkets: (markets: VenueMarket[]) => VenueMarket[];
 export declare const resolveSportsExpandedMarketsVolume: (markets: VenueMarket[]) => number;
+export type SportsCombinedLeg = {
+    /** Pill label — the fullest clean leg name across the venues offering it. */
+    label: string;
+    /** Highest-volume market at this leg; drives the order book and order ticket. */
+    market: VenueMarket;
+    /** Every venue offering this leg, including the representative's own. */
+    venues: string[];
+};
+/**
+ * The per-leg pills for a group a venue published as a DECOMPOSITION — one bare
+ * Yes/No market per outcome of a single N-way question — or `null` when the
+ * group is not one and should render as an ordinary card.
+ *
+ * Two shapes share the same subtype and must NOT render the same way:
+ *
+ *  • a real decomposition (poly's three `soccer_halftime_result` legs), which
+ *    belongs in one card with a pill per leg, and
+ *  • a plain binary that several venues each list once (poly + novig "Both
+ *    Teams to Score"), which is ONE Yes/No market with cross-venue twins.
+ *
+ * "Some venue published more than one leg" separates them structurally, with no
+ * guessing from prose. The moneyline path is deliberately exempt: it is gated on
+ * `isBinarySportsMoneylineMarket` and has shipped this way.
+ *
+ * Cross-venue twins are folded by QUESTION, not by label — poly and predict
+ * phrase a leg identically ("Real Betis Balompié leading at halftime?") while
+ * labelling it "Real Betis Balompié" vs "BET" — and the fullest label wins, the
+ * same preference `resolveSpreadOutcomeTeamNames` applies to spread pills.
+ *
+ * ponytail: O(n) map build over one group's markets (a handful of rows).
+ */
+export declare const resolveSportsCombinedLegs: (group: Pick<SportsMarketDisplayGroup, "markets" | "sportsMarketType">) => SportsCombinedLeg[] | null;
 export declare const buildSportsSlideFromGroup: (group: SportsMarketDisplayGroup) => SportsGameLineSlide;
 /**
  * Derive the Moneyline / Spreads / Total game-line slides (in that order) from a

package/dist/types/primitives/venue-logo/svg/logo-prophetx.d.mts

@@ -0,0 +1,27 @@
+import type { LogoIconProps } from "../logo-props";
+/**
+ * ProphetX's mark: two arrows crossing into an X — one running bottom-left to
+ * top-right, the other top-left to bottom-right — drawn as three filled paths.
+ *
+ * Paths, viewBox and gradient stops are taken VERBATIM from the official asset;
+ * nothing here is redrawn or approximated. All three gradients run the same
+ * #1DC29A green to #00A7AF teal, differing only in direction and intermediate
+ * stops, which is what gives the crossing strokes their depth.
+ *
+ * FIRST gradient logo in this registry — every other venue mark is a single
+ * flat colour. Two consequences worth knowing:
+ *
+ * 1. The gradient ids MUST be per-instance. SVG resolves `url(#id)` against the
+ *    whole document, so two of these on one page with hardcoded ids would both
+ *    paint from whichever mounted first — and since these three gradients carry
+ *    different `gradientTransform`s, the wrong one is visibly wrong, not merely
+ *    duplicated. `useId` gives each instance its own namespace.
+ * 2. The monochrome contract still holds. `isColor={false}` or an explicit
+ *    `color` collapses all three paths to one flat fill, so callers that need a
+ *    single-colour mark (see `logo-probable.tsx`) get exactly that; the gradient
+ *    is the default-brand path only.
+ */
+export declare const LogoProphetXIcon: {
+    ({ title, className, isColor, color, ...props }: LogoIconProps): JSX.Element;
+    displayName: string;
+};

package/dist/types/primitives/venue-logo/svg/logo-prophetx.d.ts

@@ -0,0 +1,27 @@
+import type { LogoIconProps } from "../logo-props";
+/**
+ * ProphetX's mark: two arrows crossing into an X — one running bottom-left to
+ * top-right, the other top-left to bottom-right — drawn as three filled paths.
+ *
+ * Paths, viewBox and gradient stops are taken VERBATIM from the official asset;
+ * nothing here is redrawn or approximated. All three gradients run the same
+ * #1DC29A green to #00A7AF teal, differing only in direction and intermediate
+ * stops, which is what gives the crossing strokes their depth.
+ *
+ * FIRST gradient logo in this registry — every other venue mark is a single
+ * flat colour. Two consequences worth knowing:
+ *
+ * 1. The gradient ids MUST be per-instance. SVG resolves `url(#id)` against the
+ *    whole document, so two of these on one page with hardcoded ids would both
+ *    paint from whichever mounted first — and since these three gradients carry
+ *    different `gradientTransform`s, the wrong one is visibly wrong, not merely
+ *    duplicated. `useId` gives each instance its own namespace.
+ * 2. The monochrome contract still holds. `isColor={false}` or an explicit
+ *    `color` collapses all three paths to one flat fill, so callers that need a
+ *    single-colour mark (see `logo-probable.tsx`) get exactly that; the gradient
+ *    is the default-brand path only.
+ */
+export declare const LogoProphetXIcon: {
+    ({ title, className, isColor, color, ...props }: LogoIconProps): JSX.Element;
+    displayName: string;
+};

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@agg-build/ui",
-  "version": "4.7.2",
+  "version": "4.7.3",
   "description": "Pre-built React component library for the AGG prediction market aggregator. Tailwind-based, themeable, with primitives, event surfaces, trading flows, full pages, and modals.",
   "sideEffects": false,
   "license": "MIT",
@@ -100,7 +100,7 @@
     "liveline": "^0.0.7",
     "react": "^18.0.0 || ^19.0.0",
     "react-dom": "^18.0.0 || ^19.0.0",
-    "@agg-build/hooks": "^4.7.0",
+    "@agg-build/hooks": "^4.7.3",
     "@agg-build/sdk": "^4.7.0"
   },
   "dependencies": {