@stapel/listings-react 0.25.10 → 0.27.0

package/manifest.json

@@ -1,10 +1,10 @@
 {
   "$generated": "by scripts/gen-manifest.mjs — do not edit; drift-gated (pnpm gen:manifest:check)",
   "package": "@stapel/listings-react",
-  "version": "0.25.10",
+  "version": "0.27.0",
   "backend": {
     "module": "stapel-listings",
-    "contract": ">=0.21 <0.22"
+    "contract": ">=0.22 <0.23"
   },
   "layers": [
     "api",
@@ -522,6 +522,31 @@
       ],
       "remediation": "fix_input"
     },
+    "error.400.listing_features_draft_shape": {
+      "status": 400,
+      "params": [
+        "got_type",
+        "example"
+      ],
+      "remediation": "fix_input"
+    },
+    "error.400.listing_features_draft_unknown_slug": {
+      "status": 400,
+      "params": [
+        "index",
+        "example"
+      ],
+      "remediation": "fix_input"
+    },
+    "error.400.listing_features_draft_value_shape": {
+      "status": 400,
+      "params": [
+        "slug",
+        "got_type",
+        "example"
+      ],
+      "remediation": "fix_input"
+    },
     "error.400.listing_invalid_status_filter": {
       "status": 400,
       "params": [
@@ -714,6 +739,20 @@
     "flows": []
   },
   "demos": [
+    {
+      "id": "listings.actions",
+      "title": "Save and share cluster",
+      "description": "The reader's two actions in one cluster, so the pair can be given a hit-target tier, a corner and an order ONCE rather than twice. `placement=\"overlay\"` pins it to the trailing-top corner of a card's media — the one corner a gallery leaves free, because the dots own the bottom centre and the photo counter owns the bottom trailing corner. Not to be confused with `useListingActions`, which is the SELLER's lifecycle moves; neither is exported from the other's barrel.",
+      "component": "ListingActions",
+      "tokens": [
+        "surface-raised"
+      ],
+      "variants": [
+        "default",
+        "blocked"
+      ],
+      "source": "demo/ListingActions.demo.tsx"
+    },
     {
       "id": "listings.card",
       "title": "Listing card",
@@ -837,7 +876,7 @@
     {
       "id": "listings.mine",
       "title": "My listings",
-      "description": "stapel-listings 0.7.0 gave the owner's own listings a route (GET my/listings/, every status, ?status= for a tab's set), so the rows here are the contract's own. Four things the pane refuses to smooth over: both axes on every row (a LIVE listing whose edit is under review says so — status alone cannot); a moderation takedown, which my/counters counts in no tab at all, sits ABOVE the tabs; every switched-off action prints its reason beside itself instead of hiding it in a hover a phone cannot open; and Delete asks first, through a bottom sheet — and is drawn only on the rows that HAVE a delete route, never as a switched-off button on a listing that is on sale. The row is a thumbnail plus a min-width:0 column, so four actions wrap at 390px instead of clipping.",
+      "description": "stapel-listings 0.7.0 gave the owner's own listings a route (GET my/listings/, every status, ?status= for a tab's set), so the rows here are the contract's own. Four things the pane refuses to smooth over: both axes on every row (a LIVE listing whose edit is under review says so — status alone cannot); a moderation takedown, which my/counters counts in no tab at all, gets a fourth tab and a count of its own, announced by a line above the tab strip (D407); every switched-off action prints its reason beside itself instead of hiding it in a hover a phone cannot open; and Delete asks first, through a bottom sheet — and is drawn only on the rows that HAVE a delete route, never as a switched-off button on a listing that is on sale. The row is a thumbnail plus a min-width:0 column, so four actions wrap at 390px instead of clipping.",
       "component": "MyListingsPane",
       "covers": [
         "MyListings"
@@ -915,6 +954,24 @@
       ],
       "source": "demo/ListingSerpCard.demo.tsx"
     },
+    {
+      "id": "listings.share",
+      "title": "Share a listing",
+      "description": "One control, two arms, and the device decides: the platform's own sheet where `navigator.share` exists, and a small menu (copy the link, Telegram, WhatsApp, VK) where it does not. The address shared is the route the CONTAINER built — handed in as `url` and used verbatim — never `window.location`, because the address bar on a SERP carries the query, the page and whatever tracking parameters the visitor arrived with, and none of that belongs in a link somebody sends to a friend.",
+      "component": "ShareAction",
+      "covers": [
+        "Share"
+      ],
+      "tokens": [
+        "surface-sunken",
+        "surface-raised"
+      ],
+      "variants": [
+        "default",
+        "menu"
+      ],
+      "source": "demo/Share.demo.tsx"
+    },
     {
       "id": "listings.spec-parts",
       "title": "Badges and specs",
@@ -971,6 +1028,9 @@
     "error.400.invalid_ad_id",
     "error.400.listing_draft_meta_too_large",
     "error.400.listing_feature_not_allowed",
+    "error.400.listing_features_draft_shape",
+    "error.400.listing_features_draft_unknown_slug",
+    "error.400.listing_features_draft_value_shape",
     "error.400.listing_invalid_status_filter",
     "error.400.listing_location_required",
     "error.400.listing_zero_price_not_allowed",
@@ -1017,6 +1077,7 @@
     "listings.card.favorite_add",
     "listings.card.favorite_remove",
     "listings.card.no_photo",
+    "listings.card.photo_counter",
     "listings.card.photo_unavailable",
     "listings.card.photos",
     "listings.card.price_absent",
@@ -1091,6 +1152,9 @@
     "listings.detail.views",
     "listings.detail.withdrawn",
     "listings.error.unknown",
+    "listings.favorite.added",
+    "listings.favorite.count",
+    "listings.favorite.removed",
     "listings.favorites.empty",
     "listings.favorites.empty_hint",
     "listings.favorites.load_failed",
@@ -1106,12 +1170,14 @@
     "listings.mine.counters_failed",
     "listings.mine.delete",
     "listings.mine.delete_confirm_body",
+    "listings.mine.delete_confirm_body.final",
     "listings.mine.delete_confirm_title",
     "listings.mine.edit",
     "listings.mine.empty",
     "listings.mine.empty.active",
     "listings.mine.empty.archived",
     "listings.mine.empty.drafts",
+    "listings.mine.empty.removed",
     "listings.mine.live_under_review",
     "listings.mine.load_failed",
     "listings.mine.loading",
@@ -1124,6 +1190,7 @@
     "listings.mine.tab.active",
     "listings.mine.tab.archived",
     "listings.mine.tab.drafts",
+    "listings.mine.tab.removed",
     "listings.mine.title",
     "listings.mine.view",
     "listings.moderation.first_review",
@@ -1142,6 +1209,13 @@
     "listings.page.indicator",
     "listings.page.next",
     "listings.page.prev",
+    "listings.share.action",
+    "listings.share.copied",
+    "listings.share.copy",
+    "listings.share.copy_failed",
+    "listings.share.telegram",
+    "listings.share.vk",
+    "listings.share.whatsapp",
     "listings.status.archived",
     "listings.status.blocked",
     "listings.status.draft",
@@ -1182,6 +1256,8 @@
       "ListingsProvider",
       "ListingsRuntimeContext",
       "MODERATION_STATUSES",
+      "MY_LISTINGS_COUNTED_TABS",
+      "MY_LISTINGS_REMOVED_TAB",
       "MY_LISTINGS_TABS",
       "MY_LISTINGS_TAB_PARAM",
       "MY_LISTINGS_TAB_STATUSES",
@@ -1190,6 +1266,9 @@
       "NO_ADDRESS",
       "OWNER_TRANSITIONS",
       "PRICE_FIELD",
+      "SHARE_COPIED_MS",
+      "SHARE_NETWORKS",
+      "Share",
       "TITLE_FIELD",
       "asFeatureDaoList",
       "badgePresentation",
@@ -1199,6 +1278,7 @@
       "canTransition",
       "cardBadgeText",
       "cardBadgeTexts",
+      "countedTabOf",
       "createDraftBody",
       "createListingsApi",
       "createListingsRuntime",
@@ -1221,6 +1301,7 @@
       "flowEndpoints",
       "formatSpecValue",
       "hasCardBadgeContract",
+      "hasNativeShare",
       "isBatchValid",
       "isListingViewed",
       "isPubliclyVisible",
@@ -1242,8 +1323,10 @@
       "pageKey",
       "publishRefusal",
       "registerListingsI18n",
+      "resolveShareUrl",
       "retainKnownFeatureValues",
       "searchWithTab",
+      "shareLinks",
       "showsDraft",
       "tabFromSearch",
       "tabOf",
@@ -1277,6 +1360,7 @@
       "useMyListings",
       "usePublishListing",
       "useSaveDraft",
+      "useShare",
       "useTransitionListing",
       "useValidateDraft",
       "withEngagement"
@@ -1285,6 +1369,7 @@
       "CardBadgeContract",
       "CardBadgePresentation",
       "CardBadgeRow",
+      "CardBadgeStyle",
       "ComposeStage",
       "CreateListingsRuntimeOptions",
       "DeleteResponse",
@@ -1343,6 +1428,7 @@
       "MyListingCard",
       "MyListingsAddress",
       "MyListingsBag",
+      "MyListingsCountedTab",
       "MyListingsParams",
       "MyListingsSource",
       "MyListingsTab",
@@ -1354,12 +1440,18 @@
       "Remediation",
       "SaveDraftInput",
       "Schemas",
+      "ShareBag",
+      "ShareChannel",
+      "ShareLink",
+      "ShareNetwork",
+      "ShareTarget",
       "UseFavoritesOptions",
       "UseListingActionsOptions",
       "UseListingComposerOptions",
       "UseListingDetailOptions",
       "UseListingEngagementOverlayOptions",
-      "UseMyListingsOptions"
+      "UseMyListingsOptions",
+      "UseShareOptions"
     ]
   }
 }

package/nav-manifest.json

@@ -1,6 +1,6 @@
 {
   "package": "@stapel/listings-react",
-  "version": "0.25.10",
+  "version": "0.27.0",
   "entries": [
     {
       "id": "listings.detail",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@stapel/listings-react",
-  "version": "0.25.10",
+  "version": "0.27.0",
   "description": "Headless React pair for stapel-listings: a typed client over the draft twin, the composer that turns a category schema into a submittable listing, and the owner's dashboard. Two independent axes are rendered as two — lifecycle `status` decides visibility and `moderation_status` decides nothing about it, so an edit to a live listing stays live and says 'under review' instead of vanishing. Feature values are drawn and mirrored by @stapel/attributes-react; photos arrive as an injected upload bag whose `refs` ARE `images_draft` and whose `settled` gates the submit; a publish refusal is routed onto the control that caused it by slug. Zero visual opinion in the main entry; an opt-in /default subpath ships the antd skin.",
   "license": "MIT",
   "repository": {
@@ -48,24 +48,24 @@
   ],
   "size-limit": [
     {
-      "name": "index — the headless pair (client + status axes + draft model + hooks): no antd. Raised 11 -> 12 KB for the elevation gate (useElevatableMandateGate + core's useElevation): the anonymous arm can now mint an identity for a named action instead of refusing, and that is a state hook the gate did not previously carry. Raised 11.5 -> 12 KB for envelopeFieldErrors and its API-field -> control table: a save-draft/create 400 names its field in the envelope rather than in a publish batch, and without the table the refusal had nowhere to land — which is how one over-precise coordinate painted two unreadable banners and left every control clean. Thirty-six bytes of routing table is what a legible refusal costs. Raised 12 -> 13 KB for two seams the mobile wave needed in the HEADLESS half: the category-feature copy source in model/features.ts (the option table a stored select does not carry, so a published listing prints \"Second-hand\" and not \"b-u\"), and firstUnsatisfied (the field a \"10 required details are still empty\" count actually points at, in the order the form asks). Both are model, not skin: a headless host renders its own controls and needs the same two answers. Raised 13 -> 14 KB (measured 12.91) for the engagement overlay: a batch read, its normalized key, and the scope that runs it once for a page and hands every card its own entry. It is a whole new READ rather than a flag — and it is the read that makes the viewed/saved state visible at all on a feed and a SERP, which come from the search index and carry no per-viewer field. Landing at 12.91 of 13 would have been a budget passed by rounding. Raised 14 -> 15 KB (measured 14.39) for the two model modules the listing-page wave added to the HEADLESS half: model/featureText.ts, which typesets a numeric value instead of stringifying it (its unit resolved from the definition, its digits through Intl.NumberFormat — the live page read 'Power 173' and 'Mileage 20000'), and model/cardBadges.ts, the card badge contract's four presentations plus the detector that falls back to the old rendering on an older backend. Both are answers a headless host needs as much as the skin does: a container drawing its own spec rows has the same value and the same missing unit.",
+      "name": "index — the headless pair (client + status axes + draft model + hooks): no antd. Raised 11 -> 12 KB for the elevation gate (useElevatableMandateGate + core's useElevation): the anonymous arm can now mint an identity for a named action instead of refusing, and that is a state hook the gate did not previously carry. Raised 11.5 -> 12 KB for envelopeFieldErrors and its API-field -> control table: a save-draft/create 400 names its field in the envelope rather than in a publish batch, and without the table the refusal had nowhere to land — which is how one over-precise coordinate painted two unreadable banners and left every control clean. Thirty-six bytes of routing table is what a legible refusal costs. Raised 12 -> 13 KB for two seams the mobile wave needed in the HEADLESS half: the category-feature copy source in model/features.ts (the option table a stored select does not carry, so a published listing prints \"Second-hand\" and not \"b-u\"), and firstUnsatisfied (the field a \"10 required details are still empty\" count actually points at, in the order the form asks). Both are model, not skin: a headless host renders its own controls and needs the same two answers. Raised 13 -> 14 KB (measured 12.91) for the engagement overlay: a batch read, its normalized key, and the scope that runs it once for a page and hands every card its own entry. It is a whole new READ rather than a flag — and it is the read that makes the viewed/saved state visible at all on a feed and a SERP, which come from the search index and carry no per-viewer field. Landing at 12.91 of 13 would have been a budget passed by rounding. Raised 14 -> 15 KB (measured 14.39) for the two model modules the listing-page wave added to the HEADLESS half: model/featureText.ts, which typesets a numeric value instead of stringifying it (its unit resolved from the definition, its digits through Intl.NumberFormat — the live page read 'Power 173' and 'Mileage 20000'), and model/cardBadges.ts, the card badge contract's four presentations plus the detector that falls back to the old rendering on an older backend. Both are answers a headless host needs as much as the skin does: a container drawing its own spec rows has the same value and the same missing unit. Raised 15 -> 16 KB (measured 15.27) for the two model answers the desktop/mobile wave needed in the HEADLESS half: the fourth dashboard tab (D407 — `MY_LISTINGS_COUNTED_TABS` beside `MY_LISTINGS_TABS`, `countedTabOf`, the removed tab's own status set, and the tab count that comes from the takedowns' own read because `my/counters` has three integers and no fourth), and the spec-line disambiguation in model/cardBadges.ts (the caption/answer punctuation per surface, plus the pass that tells two axes wearing one unit apart). Both are answers a headless host needs as much as the skin does: a container drawing its own tab strip has the same missing count, and one drawing its own spec line has the same two axes. Raised 16 -> 17 KB (measured 15.99) for `useShare`: the canonical-URL resolution, the three networks' encoded endpoints, the clipboard write and the native-sheet capability probe. The previous ceiling was reached EXACTLY — 15.99 of 16 — and a budget passed by rounding is a budget the next sentence fails. It is in the headless half deliberately: a host drawing its own share menu needs the same three hrefs and the same rule that a canonical route beats the address bar.",
       "path": "dist/index.js",
-      "limit": "15 KB"
+      "limit": "17 KB"
     },
     {
-      "name": "default — the antd skin (three cards, detail, composer, dashboard, the named slots and the delete confirmation) must stay out of the main bundle. Raised 17 -> 19 KB for the mobile wave: <ListingSerpCard> (photo strip + price-first block + action rail), <ListingFeedCard> and <FeedGrid> are two more card surfaces on the same shared target/favourite/photo parts, not three copies of one Raised 19 -> 20 KB for the desktop wave of the detail page: layout=\"split\" is a second ASSEMBLY of the money page (the sticky buy column, the two-column spec table, the widened measure) over the same parts, and GateReasonPopover is the blocked heart's third volume — the reason and the door disclosed on interaction, with the visually-hidden copy that keeps the refusal in the accessibility tree. Both are geometry and wiring, not new widgets. Raised 20 -> 21 KB (measured 20.22) for the engagement wave, which is four small things and no new component: the disclosure became a controlled open/close so a pointer that hovers and then clicks does not shut the only explanation the control has; the heart draws a filled accent when saved and states a failed save through the shared ErrorAlert; an already-seen card dims through one rule in the sheet all three cards already hoist; and the listing page gained a view-count row. 216 bytes is what a control that reports its own outcome costs. Raised 21 -> 22 KB for the seller's board becoming a door in both directions: the transition route and useTransitionListing, OWNER_TRANSITIONS/ownerMoves as the fallback mirror, ListingActionsBag.moves drawn in a stable order, listingHref/linkComponent on the cabinet pane, the refusal that stops quoting the wire, and the row that fits a phone. Measured on a clean tree, this package's src reverted to the previous commit with dependencies held constant: 20.82 -> 21.60 KB. The old ceiling had 180 B of room and the work needs 780; none of it is copy, and a fourth axis of owner state is not a rounding error. Raised 22 -> 25 KB (measured 23.94) for the three surfaces of the same wave: <ListingSpecList>/<ListingSpecColumns>, which is a REPLACEMENT of antd's <Descriptions> with a paragraph row (an inline muted label and the value in one text flow, so a long answer wraps at the measure instead of stacking inside a third-of-a-page cell) and therefore carries its own hoisted sheet; <CardBadges>/<CardSpecLine>, one badge renderer for all three card surfaces with the pre-contract path kept whole beside it; and cardGallery.ts, the hover-scrub and swipe gestures — a segment map, a horizontal-intent threshold, the pointer-capability gate and the touch-action rule that leaves the page's vertical scroll to the browser. A gallery a card did not have and a spec list rebuilt from a table are not a rounding error.",
+      "name": "default — the antd skin (three cards, detail, composer, dashboard, the named slots and the delete confirmation) must stay out of the main bundle. Raised 17 -> 19 KB for the mobile wave: <ListingSerpCard> (photo strip + price-first block + action rail), <ListingFeedCard> and <FeedGrid> are two more card surfaces on the same shared target/favourite/photo parts, not three copies of one Raised 19 -> 20 KB for the desktop wave of the detail page: layout=\"split\" is a second ASSEMBLY of the money page (the sticky buy column, the two-column spec table, the widened measure) over the same parts, and GateReasonPopover is the blocked heart's third volume — the reason and the door disclosed on interaction, with the visually-hidden copy that keeps the refusal in the accessibility tree. Both are geometry and wiring, not new widgets. Raised 20 -> 21 KB (measured 20.22) for the engagement wave, which is four small things and no new component: the disclosure became a controlled open/close so a pointer that hovers and then clicks does not shut the only explanation the control has; the heart draws a filled accent when saved and states a failed save through the shared ErrorAlert; an already-seen card dims through one rule in the sheet all three cards already hoist; and the listing page gained a view-count row. 216 bytes is what a control that reports its own outcome costs. Raised 21 -> 22 KB for the seller's board becoming a door in both directions: the transition route and useTransitionListing, OWNER_TRANSITIONS/ownerMoves as the fallback mirror, ListingActionsBag.moves drawn in a stable order, listingHref/linkComponent on the cabinet pane, the refusal that stops quoting the wire, and the row that fits a phone. Measured on a clean tree, this package's src reverted to the previous commit with dependencies held constant: 20.82 -> 21.60 KB. The old ceiling had 180 B of room and the work needs 780; none of it is copy, and a fourth axis of owner state is not a rounding error. Raised 22 -> 25 KB (measured 23.94) for the three surfaces of the same wave: <ListingSpecList>/<ListingSpecColumns>, which is a REPLACEMENT of antd's <Descriptions> with a paragraph row (an inline muted label and the value in one text flow, so a long answer wraps at the measure instead of stacking inside a third-of-a-page cell) and therefore carries its own hoisted sheet; <CardBadges>/<CardSpecLine>, one badge renderer for all three card surfaces with the pre-contract path kept whole beside it; and cardGallery.ts, the hover-scrub and swipe gestures — a segment map, a horizontal-intent threshold, the pointer-capability gate and the touch-action rule that leaves the page's vertical scroll to the browser. A gallery a card did not have and a spec list rebuilt from a table are not a rounding error. Raised 25 -> 26 KB (measured 25.34) for three small things and no new component: the dashboard's fourth tab and the takedown notice that shrank to one line above it (D407), the delete dialog choosing its sentence from the row's own remaining moves rather than printing the archive at somebody standing in the archive, and the photo strip's \"1 of 16\" counter with its two CSS rules (D418's neighbour on the card). None of it is copy; the counter is the one thing on a phone card that says a swipe is worth making. Raised 26 -> 29 KB (measured 27.56) for the reader's two actions: <ShareAction> (the native-sheet arm, the desktop menu with its three outbound links and the clipboard row, and the copy confirmation that stands in the menu rather than only in a toast), <ListingActions> (the cluster the listing page and the cards lay out through), actionRow.ts (two hit-target tiers as a class contract — 44px on the page, 36/44 on a card — plus the overlay pin and the label's phone arm) and notice.ts (the message seam, which is antd's own App/static message and no new dependency). Measured with dependencies held constant: 25.34 -> 27.56 KB. A verb the product did not have at all is not a rounding error. Raised 29 -> 31 KB (measured 29.92) for the two seams a live container was working around with a second component and an `!important`: the MOVABLE CLUSTER (movableCluster.tsx — the portal, the slot registry, the settle that appends the container into the highest-priority mount on screen, and the pane's two slots plus the bar layer) and the GALLERY LAYOUT (detailGallery.ts — the class, the two arms and the strip's child rule, hoisted because an inline style cannot reach a child), together with `useTitleVisibility`'s IntersectionObserver. Measured with dependencies held constant, this package's src at HEAD built into a scratch tree and then this one: 27.72 -> 29.92 KB. 30 would have left 80 B, which is the budget-passed-by-rounding this entry has warned about four times; 31 leaves 1.08 KB. What was bought: a page that mounts ONE `useFavoriteToggle` instead of two, and a host stylesheet that no longer needs `!important` over a pair's own geometry.",
       "path": "dist/default/index.js",
-      "limit": "25 KB"
+      "limit": "31 KB"
     },
     {
-      "name": "i18n/ru — the Russian bundle is opt-in, not carried by the main entry",
+      "name": "i18n/ru — the Russian bundle is opt-in, not carried by the main entry. Raised 5 -> 5.5 KB (measured 5.02): three sentences the wave added — the fourth tab and its empty state, and the delete warning that does not promise the archive to a listing already in it. A bundle sitting exactly ON its limit is a limit the next sentence breaks. Raised 5.5 -> 6 KB (measured 5.48) for the three features_draft refusals the stapel-listings 0.22.3 pin brought with it: the module is locale-exempt upstream, so a code that arrives without a ru sentence renders its own key on a Russian host, and each of these three has to NAME the shape it wanted rather than say \"try again\". 5.48 of 5.5 is twenty bytes of headroom — the rounding this entry already warns about.",
       "path": "dist/i18n/ru.js",
-      "limit": "5 KB"
+      "limit": "6 KB"
     },
     {
-      "name": "i18n/es — the Spanish bundle is opt-in, not carried by the main entry. Raised 3.5 -> 4 KB: the mobile wave's four card keys landed the bundle exactly ON the old limit, and a budget a release passes by rounding is a budget that fails the next one",
+      "name": "i18n/es — the Spanish bundle is opt-in, not carried by the main entry. Raised 3.5 -> 4 KB: the mobile wave's four card keys landed the bundle exactly ON the old limit, and a budget a release passes by rounding is a budget that fails the next one. Raised 4 -> 4.5 KB (measured 3.94) for the share wave's ten sentences, which landed it on that limit again by the same 60 bytes",
       "path": "dist/i18n/es.js",
-      "limit": "4 KB"
+      "limit": "4.5 KB"
     }
   ],
   "peerDependencies": {
@@ -102,7 +102,7 @@
     "size-limit": "^11.2.0",
     "typescript": "^5.8.3",
     "vitest": "^3.2.4",
-    "@stapel/attributes-react": "^0.16.4",
+    "@stapel/attributes-react": "^0.16.5",
     "@stapel/core": "^0.25.4",
     "@stapel/currencies-react": "^0.4.0",
     "@stapel/image": "^0.4.2",

package/src/analytics/generated/events.json

@@ -1,7 +1,7 @@
 {
   "$generated": "by scripts/gen-events.mjs — do not edit; drift-gated (pnpm gen:events:check)",
   "package": "@stapel/listings-react",
-  "version": "0.25.10",
+  "version": "0.27.0",
   "defined": [],
   "flows": []
 }

package/src/api/generated/schema.ts

@@ -439,15 +439,18 @@ export interface paths {
             cookie?: never;
         };
         /**
-         * @description Listings CRUD plus owner lifecycle actions and favorites.
+         * @description One integer per cabinet tab, over the caller's own listings.
          *
-         *     Read and write live in one class, so the guest wall
-         *     (:func:`anonymous_write_refusal`, the ``ALLOW_ANONYMOUS_WRITES`` switch)
-         *     is applied per ACTION and never as a class permission: an anonymous
-         *     session must keep browsing and keep its favorites, and only the
-         *     authorship actions — ``create``, ``update``/``partial_update``,
-         *     ``save-draft``, ``publish`` — are the ones that turn a caller into a
-         *     seller.
+         *     The tab groupings are the SERVER's — ``my/listings?status=`` takes
+         *     the same sets — so a cabinet never has to re-derive which statuses
+         *     make up "active". Every lifecycle status is in exactly one group:
+         *     ``blocked`` (a moderation takedown) is its own count rather than
+         *     being folded into ``archived``, because the two tell the seller
+         *     different things and only one of them is theirs to undo.
+         *
+         *     Owner-scoped at the queryset via ``owned_by``, soft-deleted rows
+         *     excluded by the default manager — the same scope as
+         *     ``my/listings``, so a tab's rows and its count always agree.
          *
          *     **Permissions:** `IsAuthenticated`
          */
@@ -500,7 +503,7 @@ export interface paths {
          * @description The caller's OWN listings, in every status.
          *
          *     The counterpart of ``my/counters``: the same owner scope and the same
-         *     status grouping, but the rows behind the three numbers. ``list`` is
+         *     status grouping, but the rows behind the four numbers. ``list`` is
          *     the shop window (``published()``, narrowable to nobody), so this is
          *     the only route by which a person can be shown their own drafts.
          *
@@ -1056,6 +1059,7 @@ export interface components {
             lat_draft?: string | null;
             /** Format: decimal */
             lon_draft?: string | null;
+            /** @description The WRITE shape of features_draft: an object keyed by feature slug, each value a FeatureDto — e.g. {"mileage":{"type":"int","value":42000}}. A listing READ hands back features as a *list* of decorated DAOs instead (`features` / `features_title` / `features_badges` — `{slug, name, label, presentation, …}`); posting that same list back here is also accepted, e.g. [{"slug":"mileage","type":"int","value":42000}] — only `slug`, `type` and `value` are read back out, every other (decoration) key is ignored. A malformed payload of either shape gets a features_draft_shape / features_draft_value_shape / features_draft_unknown_slug 400 naming the shape that would have worked. */
             features_draft?: {
                 [key: string]: components["schemas"]["FeatureDto"];
             } | null;
@@ -1128,11 +1132,18 @@ export interface components {
          * @enum {string}
          */
         ModerationStatusEnum: "not_submitted" | "pending" | "approved" | "rejected" | "needs_review";
-        /** @description Listing counts by tab for the current user. */
+        /**
+         * @description Listing counts by tab for the current user.
+         *
+         *     One integer per cabinet tab, and every lifecycle status belongs to
+         *     exactly one of them — ``blocked`` included, so a listing a moderator
+         *     took down is counted somewhere instead of vanishing from the totals.
+         */
         MyCountersResponse: {
             active: number;
             archived: number;
             drafts: number;
+            blocked: number;
         };
         /**
          * @description The owner's own card — the public card plus what only an owner sees.
@@ -1286,6 +1297,7 @@ export interface components {
             lat_draft?: string | null;
             /** Format: decimal */
             lon_draft?: string | null;
+            /** @description The WRITE shape of features_draft: an object keyed by feature slug, each value a FeatureDto — e.g. {"mileage":{"type":"int","value":42000}}. A listing READ hands back features as a *list* of decorated DAOs instead (`features` / `features_title` / `features_badges` — `{slug, name, label, presentation, …}`); posting that same list back here is also accepted, e.g. [{"slug":"mileage","type":"int","value":42000}] — only `slug`, `type` and `value` are read back out, every other (decoration) key is ignored. A malformed payload of either shape gets a features_draft_shape / features_draft_value_shape / features_draft_unknown_slug 400 naming the shape that would have worked. */
             features_draft?: {
                 [key: string]: components["schemas"]["FeatureDto"];
             } | null;
@@ -1357,8 +1369,6 @@ export interface components {
             labels?: string[];
             vocabulary?: string | null;
             level?: string | null;
-            prefix?: string | null;
-            postfix?: string | null;
         };
         /** @description Serializer for the ref_select feature DTO. */
         RefSelectDto: {

package/src/default/CardBadges.tsx

@@ -56,7 +56,9 @@ export function CardBadges(props: CardBadgesProps): ReactElement | null {
   if (rows.length === 0) return null;
 
   if (hasCardBadgeContract(rows)) {
-    const printed = cardBadgeTexts(rows, locale);
+    // The variant is not only a layout: it decides how a caption is joined to
+    // its answer, because a chip has a border and a line has a dot (D421).
+    const printed = cardBadgeTexts(rows, locale, props.variant === "line" ? "line" : "badge");
     if (printed.length === 0) return null;
     if (props.variant === "line") {
       return (

package/src/default/ListingActions.tsx

@@ -0,0 +1,196 @@
+/**
+ * `<ListingActions>` — save it, or send it to somebody. The two verbs a
+ * classified puts beside a listing's title, in one cluster.
+ *
+ * ── Why they are one component and not two buttons in a row ───────────────
+ *
+ * Because everything that makes them usable is a property of the PAIR, not of
+ * either control: they share a hit-target tier, they share the corner of the
+ * photograph they are pinned to on a phone, and the reason they are icon-only
+ * on the listing page is that there are two of them and a price on one line.
+ * Measured against the reference (§23): our listing page drew a 152px
+ * "Save to favourites" button with a word in it at every width, where the
+ * reference draws a 44×44 glyph on a desktop and 36×36 on a phone and puts
+ * the share glyph beside it. Two components could not have been given that
+ * ruling once.
+ *
+ * ── The NAME of `<ListingActions>` and of `useListingActions` ─────────────
+ *
+ * They are different things and the collision is worth stating rather than
+ * renaming around. `useListingActions` (the headless entry) is the SELLER's
+ * lifecycle moves — archive, mark sold, delete — the owner's half of the
+ * state machine. This is the READER's two actions, and it lives in
+ * `/default` because it is a layout. Neither is exported from the other's
+ * barrel.
+ *
+ * ── The heart arrives as a node when the surface already has one ──────────
+ *
+ * The listing page's heart is driven by `useListingDetail`'s own optimistic
+ * bag (it holds the whole listing, so it flips the row it already has),
+ * while a card's is driven by `useFavoriteToggle` against a card row. Two
+ * hooks, one control — so the cluster takes {@link ListingActionsProps.favorite}
+ * as a node for a surface that already built one, and mounts the shared
+ * `<FavoriteHeart>` for everyone else. What it never does is let the two
+ * surfaces disagree about SIZE, PLACEMENT or ORDER, which is the whole job.
+ *
+ * ── There is no favourite count on the wire, and this does not invent one ─
+ *
+ * `ListingCard`/`ListingDetail` carry `is_favorited` — a per-reader boolean —
+ * and no aggregate anywhere (asserted in `test/engagementState`). So
+ * {@link ListingActionsProps.favoriteCount} is a number the HOST was given by
+ * something else, rendered when it is there and absent when it is not. Never
+ * a zero standing in for "nobody counted".
+ */
+import type { CSSProperties, ReactElement, ReactNode } from "react";
+import { Flex, Typography } from "antd";
+import type { SignInCta } from "@stapel/core";
+import { useT } from "@stapel/core";
+import { LISTINGS_I18N_KEYS } from "../i18n/keys.js";
+import type { ShareChannel } from "../headless/Share.js";
+import { FavoriteHeart } from "./favorite.js";
+import { ShareAction } from "./ShareAction.js";
+import {
+  LISTING_ACTIONS_CLASS,
+  LISTING_ACTIONS_OVERLAY_CLASS,
+  LISTING_ACTIONS_STYLE_HREF,
+  LISTING_ACTION_CLASS,
+  actionRowCss,
+} from "./actionRow.js";
+
+/**
+ * Which of the two the host wants drawn.
+ *
+ * Both default to `true`: a pair whose share button had to be switched ON
+ * would have shipped a storefront with no share button, which is the exact
+ * defect this wave answers. `{ share: false }` is for a deployment that has
+ * decided against it — a private marketplace, an internal catalogue — and
+ * `{ favorite: false }` for a surface where saving makes no sense (the
+ * owner's own listing).
+ */
+export interface ListingActionsConfig {
+  readonly favorite?: boolean;
+  readonly share?: boolean;
+}
+
+export interface ListingActionsProps {
+  readonly listingId: number;
+  /** `is_favorited` off the row — ignored when {@link favorite} is given. */
+  readonly favorited?: boolean | null | undefined;
+  /**
+   * The surface's own heart, when it has one. See the file header: the
+   * listing page's heart is driven by a different hook from a card's, and
+   * this cluster's job is the geometry, not the hook.
+   */
+  readonly favorite?: ReactNode;
+  /** How many people saved it, when the host knows. Absent draws nothing —
+   * the wire carries no such aggregate. */
+  readonly favoriteCount?: number;
+  /** The listing's canonical address — a path or an absolute URL. Given, it
+   * is what is shared and `window.location` is never read. */
+  readonly shareUrl?: string;
+  /** The listing's title: the share sheet's heading. */
+  readonly shareTitle?: string;
+  /** A line under it in the sheet — the price, typically. */
+  readonly shareText?: string;
+  readonly onShared?: (channel: ShareChannel) => void;
+  /** The container's sign-in door for the heart. */
+  readonly signIn?: SignInCta;
+  /** How loudly a blocked heart speaks — only consulted when this cluster
+   * mounts the heart itself. */
+  readonly blockedReason?: "text" | "popover";
+  /** A short toast on each successful favourite press. */
+  readonly announce?: boolean;
+  /** See {@link ListingActionsConfig}. */
+  readonly actions?: ListingActionsConfig;
+  /**
+   * `"inline"` (default) is a row wherever the surface put it.
+   *
+   * `"overlay"` pins the cluster to the TRAILING TOP corner of the media it
+   * is drawn over — the one corner of a card gallery that is free, because
+   * the dots own the bottom centre and the "3 of 16" counter owns the bottom
+   * trailing corner. The element it is pinned inside must be a containing
+   * block; every media well in this package already is.
+   */
+  readonly placement?: "inline" | "overlay";
+  /** This cluster's test id. Default `listings-actions`. */
+  readonly testId?: string;
+  /** The heart's test id, when this cluster mounts it. */
+  readonly favoriteTestId?: string;
+  readonly style?: CSSProperties;
+}
+
+export function ListingActions(props: ListingActionsProps): ReactElement | null {
+  const t = useT();
+  const testId = props.testId ?? "listings-actions";
+  const showFavorite = props.actions?.favorite !== false;
+  const showShare = props.actions?.share !== false;
+  const overlay = props.placement === "overlay";
+
+  // Nothing asked for is nothing drawn — not an empty box with a gap in it.
+  if (!showFavorite && !showShare) return null;
+
+  const heart = !showFavorite ? null : (
+    props.favorite ?? (
+      <FavoriteHeart
+        listingId={props.listingId}
+        favorited={props.favorited}
+        testId={props.favoriteTestId ?? `${testId}-favorite`}
+        className={LISTING_ACTION_CLASS}
+        {...(props.announce === true ? { announce: true } : {})}
+        {...(props.blockedReason !== undefined
+          ? { blockedReason: props.blockedReason }
+          : {})}
+        {...(props.signIn !== undefined ? { signIn: props.signIn } : {})}
+      />
+    )
+  );
+
+  return (
+    <>
+      <style href={LISTING_ACTIONS_STYLE_HREF} precedence="default">
+        {actionRowCss()}
+      </style>
+      <Flex
+        align="flex-end"
+        className={
+          overlay
+            ? `${LISTING_ACTIONS_CLASS} ${LISTING_ACTIONS_OVERLAY_CLASS}`
+            : LISTING_ACTIONS_CLASS
+        }
+        data-testid={testId}
+        data-placement={overlay ? "overlay" : "inline"}
+        {...(props.style !== undefined ? { style: props.style } : {})}
+      >
+        {heart}
+
+        {/* The count, when a host was given one. Beside the heart and not
+            inside it: the number is a fact about the listing, and a button
+            whose accessible name changed with a counter would be announced
+            differently to every reader. */}
+        {showFavorite && props.favoriteCount !== undefined ? (
+          <Typography.Text
+            type="secondary"
+            data-testid={`${testId}-favorite-count`}
+          >
+            {t(LISTINGS_I18N_KEYS.favoriteCount, { count: props.favoriteCount })}
+          </Typography.Text>
+        ) : null}
+
+        {showShare ? (
+          <ShareAction
+            testId={`${testId}-share`}
+            // Icon-only in the cluster, at both placements: two glyphs and a
+            // price share one line on a phone, and the reference draws the
+            // page's actions as glyphs on a desktop too (§23). The verb is
+            // still the control's accessible name in every arm.
+            shape="circle"
+            {...(props.shareUrl !== undefined ? { url: props.shareUrl } : {})}
+            {...(props.shareTitle !== undefined ? { title: props.shareTitle } : {})}
+            {...(props.shareText !== undefined ? { text: props.shareText } : {})}
+            {...(props.onShared !== undefined ? { onShared: props.onShared } : {})}
+          />
+        ) : null}
+      </Flex>
+    </>
+  );
+}