@stapel/listings-react 0.4.0 → 0.7.0

package/src/i18n/ru.ts

@@ -1,4 +1,5 @@
 import type { I18nDictionary, I18nEngine } from "@stapel/core";
+import { registerAttributesI18nRu } from "@stapel/attributes-react/i18n/ru";
 import { listingsErrorBundleRu } from "./generated/errors.ru.gen.js";
 
 export { listingsErrorBundleRu } from "./generated/errors.ru.gen.js";
@@ -110,6 +111,8 @@ export const listingsI18nBundleRu: I18nDictionary = {
   "listings.detail.published_at": "Опубликовано {date}",
   "listings.detail.expires_at": "В продаже до {date}",
   "listings.detail.stock": "В наличии",
+  "listings.detail.edit": "Редактировать объявление",
+  "listings.detail.take_down": "Снять с публикации",
 
   "listings.compose.new_title": "Новое объявление",
   "listings.compose.edit_title": "Редактирование объявления",
@@ -128,8 +131,8 @@ export const listingsI18nBundleRu: I18nDictionary = {
     "Введите цену числом, не более двух знаков после запятой",
   "listings.compose.currency_label": "Валюта",
   "listings.compose.location_label": "Где находится",
-  "listings.compose.lat_label": "Широта",
-  "listings.compose.lon_label": "Долгота",
+  "listings.compose.location_help":
+    "Покупатели ищут по расстоянию — объявление без места они просто не найдут",
   "listings.compose.geo_incomplete":
     "Рядом с широтой нужна долгота — половина координаты никуда не указывает",
   "listings.compose.photos": "Фотографии",
@@ -160,12 +163,13 @@ export const listingsI18nBundleRu: I18nDictionary = {
   "listings.compose.blocked.no_category":
     "Выберите категорию — от неё зависит остальная форма",
   "listings.compose.blocked.unsupported_type":
-    "Эта категория спрашивает характеристику, которую приложение пока не умеет показывать ({types}), поэтому заполнить её здесь нельзя",
+    "Эта категория спрашивает характеристику, которую приложение пока не умеет показывать, поэтому закончить объявление здесь нельзя",
   "listings.compose.blocked.photos_pending":
     "Дождитесь окончания загрузки фотографий",
   "listings.compose.blocked.no_draft": "Черновик ещё не создан",
   "listings.compose.blocked.busy":
     "Секунду — предыдущее изменение ещё сохраняется",
+  "listings.compose.blocked.incomplete": "Не заполнено обязательных деталей: {count}",
   "listings.compose.blocked.mirror": "Сначала поправьте отмеченные поля",
   "listings.compose.blocked.details_unavailable":
     "Не удалось загрузить характеристики категории, поэтому проверить форму нельзя",
@@ -184,6 +188,10 @@ export const listingsI18nBundleRu: I18nDictionary = {
   "listings.mine.empty.archived": "Пока ничего не в архиве, не снято, не истекло и не продано",
   "listings.mine.blocked.title":
     "Модерация сняла ваших объявлений: {count}",
+  "listings.mine.blocked.title.one": "Модерация сняла одно ваше объявление",
+  "listings.mine.blocked.title.few": "Модерация сняла {count} ваших объявления",
+  "listings.mine.blocked.title.many": "Модерация сняла {count} ваших объявлений",
+  "listings.mine.blocked.title.other": "Модерация сняла ваших объявлений: {count}",
   "listings.mine.blocked.load_failed":
     "Не удалось проверить, снимала ли модерация ваши объявления",
   "listings.mine.live_under_review": "Опубликовано, правки на проверке",
@@ -191,11 +199,18 @@ export const listingsI18nBundleRu: I18nDictionary = {
   "listings.mine.archive": "В архив",
   "listings.mine.complete": "Отметить проданным",
   "listings.mine.delete": "Удалить",
+  "listings.mine.delete_confirm_title": "Удалить объявление?",
+  "listings.mine.delete_confirm_body":
+    "Оно исчезнет из кабинета, и вернуть его будет нельзя. Архив сохраняет его.",
 
   "listings.favorites.title": "Избранное",
   "listings.favorites.loading": "Загружаем избранное…",
   "listings.favorites.load_failed": "Не удалось загрузить избранное",
   "listings.favorites.empty": "Вы ещё ничего не сохранили",
+  "listings.favorites.empty_hint":
+    "Нажмите на сердечко в любом объявлении — оно будет ждать здесь.",
+  "listings.favorites.sign_in_hint":
+    "Избранное хранится в аккаунте, поэтому переходит с вами на другие устройства.",
 
   "listings.blocked.sign_in": "Войдите, чтобы сделать это",
   "listings.blocked.guest":
@@ -207,9 +222,12 @@ export const listingsI18nBundleRu: I18nDictionary = {
   "listings.blocked.delete_active":
     "Сначала уберите в архив — объявление в продаже удалить нельзя",
   "listings.blocked.in_flight": "Секунду — это уже выполняется",
+  "listings.blocked.no_editor":
+    "В этом приложении пока нет экрана редактирования объявления",
 
   "listings.page.prev": "Назад",
   "listings.page.next": "Дальше",
+  "listings.page.indicator": "Страница {page}",
 
   "listings.nav.detail": "Объявление",
   "listings.nav.compose": "Подать объявление",
@@ -217,7 +235,23 @@ export const listingsI18nBundleRu: I18nDictionary = {
   "listings.nav.favorites": "Избранное",
 };
 
-/** Register the Russian bundle into a core i18n engine. */
+/**
+ * Register the Russian bundle into a core i18n engine — AND the twelve
+ * `stapel_attributes` sentences this pair deliberately does not author.
+ *
+ * The split of ownership is right and stays: two packages must not give one
+ * refusal two sentences. What was wrong was leaving the JOIN to a README. A
+ * host that registered only this bundle got twelve of the composer's most
+ * common refusals ("this value is below the minimum", "the description is too
+ * long") in English on a Russian page, and nothing failed anywhere to say so.
+ *
+ * `@stapel/attributes-react` is a peer of this pair and its editors are what
+ * RAISE those twelve, so a listings-ru host is an attributes-ru host by
+ * construction; chaining the registration states that instead of asking. It is
+ * idempotent — a host that also registers the bundle itself simply writes the
+ * same keys twice.
+ */
 export function registerListingsI18nRu(i18n: I18nEngine): void {
+  registerAttributesI18nRu(i18n);
   i18n.registerBundle("ru", listingsI18nBundleRu);
 }

package/src/model/draft.ts

@@ -29,12 +29,14 @@ import { DEFAULT_LISTING_CURRENCY } from "../api/types.js";
  * `geohash` that disagrees with the coordinates beside it is worse than no
  * geohash — the pin and the bucket point at different places.
  *
- * The pair does NOT compute `geohash` from `lat`/`lon`, and that is a
- * decision. A geohash is precision-dependent, the indexer's bucketing depends
- * on which precision was used, and a client that picked its own would put
- * listings in neighbouring cells for reasons nobody could see. It is written
- * by whatever resolved the place (a geo picker, `stapel-geo`) and carried
- * verbatim from there to the wire.
+ * `geohash` is SERVER-COMPUTED and read-only since stapel-listings 0.7.1.
+ * `Listing.save()` stamps `geohash_draft` from `lat_draft`/`lon_draft` through
+ * the `geo.geohash_encode` comm function, and `ListingDraftSerializer` marks
+ * the field `readOnly` — a value sent in the request body is silently ignored.
+ * So this member is something the composer READS BACK (a reopened draft, a
+ * published listing) and never something it sends: `draftPatchFromValues`
+ * omits it, and a picker that happens to know a geohash may keep it for its
+ * own display without expecting the wire to carry it.
  */
 export interface ListingLocation {
   /** Opaque id from whatever place directory the deployment uses. */
@@ -45,6 +47,7 @@ export interface ListingLocation {
    * `55.796100` into `55.7961` and change what was submitted. */
   readonly lat: string | null;
   readonly lon: string | null;
+  /** Read-only: the server computes it from `lat`/`lon` (0.7.1). Never sent. */
   readonly geohash: string;
 }
 
@@ -242,7 +245,9 @@ export function draftPatchFromValues(
     images_draft: [...values.images],
     location_id_draft: values.location.locationId,
     location_label_draft: values.location.locationLabel,
-    geohash_draft: values.location.geohash,
+    // No `geohash_draft`: stapel-listings 0.7.1 computes it in `Listing.save()`
+    // from the coordinates and marks the serializer field read-only, so a value
+    // sent here is discarded. Sending one would be a claim the wire ignores.
     lat_draft: values.location.lat,
     lon_draft: values.location.lon,
     features_draft: toWireFeatures(features, values.features),

package/src/model/features.ts

@@ -22,14 +22,28 @@
  * `order`, `title`, `badge`) are simply ignored by every formatter. Copying a
  * hand-picked subset instead would be a list to keep in step with ten types.
  *
- * ── What a DAO does NOT carry ──────────────────────────────────────────────
+ * ── What a DAO does NOT carry, and the one line that repairs it ────────────
  *
- * `select`'s `options`. `normalize_to_dao` stores the chosen VALUES, not the
- * option table, so `formatFeatureValue` falls back to the raw option value —
- * which is a translation KEY when the config is translatable (the default),
- * so a host whose bundle carries the catalogue's option copy still reads a
- * word. A host whose bundle does not sees the key, on purpose: a visible
- * `option.condition.used` gets fixed, an invented "Used" ships wrong.
+ * `select`'s `options`. `SelectType.dto_to_dao` stores the chosen VALUES and
+ * the ui config, never the option table — the table lives on the CATEGORY, and
+ * not needing it is the whole point of the projection.
+ *
+ * The consequence was a defect the visual pass caught on every card and every
+ * spec row: `formatFeatureValue` resolves an option's copy by looking the
+ * value up in `config.options`, and with no table it falls through to
+ * `String(value)`. The stored value of a translatable catalogue IS a
+ * translation key, so a listing page printed `demo.condition.used` and
+ * `demo.brand.bosch` at people. (The server does not have this problem: its
+ * own `format_value` has the category's config in hand.)
+ *
+ * So the split below synthesizes the IDENTITY table — `{value: v, label: v}`
+ * for each stored value — which is exactly the table a translatable catalogue
+ * would have produced, since its labels ARE the keys. `formatFeatureValue`
+ * then runs the value through the host's `t` and a bundle carrying the
+ * catalogue copy reads "Used". A bundle that does not still shows the key, on
+ * purpose: a visible `option.condition.used` gets fixed, an invented "Used"
+ * ships wrong. A NON-translatable catalogue stores literal labels, `t` returns
+ * an unknown key unchanged, and the output is what it always was.
  */
 import type { FeatureDef, FeatureValueDto } from "@stapel/attributes-react";
 import type { ListingFeatureDao, ListingFeatureView } from "../api/types.js";
@@ -37,6 +51,31 @@ import type { ListingFeatureDao, ListingFeatureView } from "../api/types.js";
 /** Keys that belong to the DAO envelope rather than to the type's config. */
 const ENVELOPE = new Set(["slug", "value", "name", "order", "title", "badge"]);
 
+/** The two types whose stored `value` is an option key rather than the thing
+ * itself. `hierarchical_select` is deliberately absent: its formatter joins
+ * the path with " / " and never consults an option table at all. */
+const OPTION_VALUED = new Set(["select"]);
+
+/**
+ * The identity option table for a stored `select` — see the module header.
+ *
+ * Returns `undefined` when there is nothing to add (another type, a config
+ * that already carries a table, a value that is not a list of strings), so the
+ * common path allocates nothing and a DAO that DOES carry options is left
+ * exactly as it arrived.
+ */
+function synthesizedOptions(
+  dao: ListingFeatureDao,
+  config: Readonly<Record<string, unknown>>
+): readonly { value: string; label: string }[] | undefined {
+  if (typeof dao.type !== "string" || !OPTION_VALUED.has(dao.type)) return undefined;
+  if (Array.isArray(config["options"])) return undefined;
+  const raw = Array.isArray(dao.value) ? dao.value : [dao.value];
+  const values = raw.filter((item): item is string => typeof item === "string");
+  if (values.length === 0) return undefined;
+  return values.map((value) => ({ value, label: value }));
+}
+
 /**
  * One DAO row → the definition/value pair the display half consumes.
  *
@@ -54,6 +93,8 @@ export function featureFromDao(
   for (const [key, value] of Object.entries(dao)) {
     if (!ENVELOPE.has(key)) config[key] = value;
   }
+  const options = synthesizedOptions(dao, config);
+  if (options !== undefined) config["options"] = options;
 
   const feature: FeatureDef = {
     slug: dao.slug,

package/dist/default/ErrorAlert.d.ts

@@ -1,9 +0,0 @@
-import type { CSSProperties, ReactElement, ReactNode } from "react";
-import type { FlowErrorDisplay } from "@stapel/core";
-export declare function ErrorAlert(props: {
-    error: FlowErrorDisplay | undefined;
-    style?: CSSProperties | undefined;
-    testId?: string | undefined;
-    action?: ReactNode;
-}): ReactElement | null;
-//# sourceMappingURL=ErrorAlert.d.ts.map

package/dist/default/ErrorAlert.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"ErrorAlert.d.ts","sourceRoot":"","sources":["../../src/default/ErrorAlert.tsx"],"names":[],"mappings":"AAeA,OAAO,KAAK,EAAE,aAAa,EAAE,YAAY,EAAE,SAAS,EAAE,MAAM,OAAO,CAAC;AACpE,OAAO,KAAK,EAAE,gBAAgB,EAAE,MAAM,cAAc,CAAC;AAErD,wBAAgB,UAAU,CAAC,KAAK,EAAE;IAChC,KAAK,EAAE,gBAAgB,GAAG,SAAS,CAAC;IACpC,KAAK,CAAC,EAAE,aAAa,GAAG,SAAS,CAAC;IAClC,MAAM,CAAC,EAAE,MAAM,GAAG,SAAS,CAAC;IAC5B,MAAM,CAAC,EAAE,SAAS,CAAC;CACpB,GAAG,YAAY,GAAG,IAAI,CAsBtB"}

package/dist/default/ErrorAlert.js

@@ -1,27 +0,0 @@
-import { jsx as _jsx } from "react/jsx-runtime";
-/**
- * The one error surface this pair's default skin renders, so the split copy
- * core produces reaches a screen the same way everywhere (mirrors the
- * docs/notifications/workspaces etalon).
- *
- * Core's `describeFlowError` splits a failure into the sentence a person
- * reads and the technical detail a support agent quotes (owner report
- * 2026-08-09: the status used to be spliced into the sentence, ending in a
- * bare `" (500)"`). The split only helps if a skin renders both halves at
- * their own weights: `message` at normal weight, `detail` muted and small.
- *
- * `undefined` in — including a `detail` core left `undefined` because there
- * was nothing worth quoting — renders nothing rather than an empty line.
- */
-import { Alert, Typography } from "antd";
-export function ErrorAlert(props) {
-    const { error } = props;
-    if (!error)
-        return null;
-    return (_jsx(Alert, { type: "error", showIcon: true, ...(props.style ? { style: props.style } : {}), ...(props.testId ? { "data-testid": props.testId } : {}), ...(props.action ? { action: props.action } : {}), message: error.message, ...(error.detail
-            ? {
-                description: (_jsx(Typography.Text, { type: "secondary", style: { fontSize: 12 }, children: error.detail })),
-            }
-            : {}) }));
-}
-//# sourceMappingURL=ErrorAlert.js.map

package/dist/default/ErrorAlert.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"ErrorAlert.js","sourceRoot":"","sources":["../../src/default/ErrorAlert.tsx"],"names":[],"mappings":";AAAA;;;;;;;;;;;;;GAaG;AACH,OAAO,EAAE,KAAK,EAAE,UAAU,EAAE,MAAM,MAAM,CAAC;AAIzC,MAAM,UAAU,UAAU,CAAC,KAK1B;IACC,MAAM,EAAE,KAAK,EAAE,GAAG,KAAK,CAAC;IACxB,IAAI,CAAC,KAAK;QAAE,OAAO,IAAI,CAAC;IACxB,OAAO,CACL,KAAC,KAAK,IACJ,IAAI,EAAC,OAAO,EACZ,QAAQ,WACJ,CAAC,KAAK,CAAC,KAAK,CAAC,CAAC,CAAC,EAAE,KAAK,EAAE,KAAK,CAAC,KAAK,EAAE,CAAC,CAAC,CAAC,EAAE,CAAC,KAC3C,CAAC,KAAK,CAAC,MAAM,CAAC,CAAC,CAAC,EAAE,aAAa,EAAE,KAAK,CAAC,MAAM,EAAE,CAAC,CAAC,CAAC,EAAE,CAAC,KACrD,CAAC,KAAK,CAAC,MAAM,CAAC,CAAC,CAAC,EAAE,MAAM,EAAE,KAAK,CAAC,MAAM,EAAE,CAAC,CAAC,CAAC,EAAE,CAAC,EAClD,OAAO,EAAE,KAAK,CAAC,OAAO,KAClB,CAAC,KAAK,CAAC,MAAM;YACf,CAAC,CAAC;gBACE,WAAW,EAAE,CACX,KAAC,UAAU,CAAC,IAAI,IAAC,IAAI,EAAC,WAAW,EAAC,KAAK,EAAE,EAAE,QAAQ,EAAE,EAAE,EAAE,YACtD,KAAK,CAAC,MAAM,GACG,CACnB;aACF;YACH,CAAC,CAAC,EAAE,CAAC,GACP,CACH,CAAC;AACJ,CAAC"}

package/dist/default/theme.d.ts

@@ -1,25 +0,0 @@
-import type { CSSProperties, ReactElement, ReactNode } from "react";
-import type { ThemeMode } from "@stapel/tokens-antd";
-export interface ListingsSkinThemeProps {
-    /**
-     * Light or dark. Defaults to the mode the host's document declares
-     * (`resolveThemeMode()`). Pass explicitly to pin a side.
-     */
-    readonly mode?: ThemeMode;
-    /** Extra styles merged onto the themed root element (layout only — colors
-     * come from the mode). */
-    readonly style?: CSSProperties;
-    readonly children: ReactNode;
-}
-/**
- * `<ListingsSkinTheme/>` — the self-theming wrapper of
- * `@stapel/listings-react/default`. Standalone use is supported (wrap any
- * composition of the skin's parts once); the shipped surfaces
- * (`ListingCard`, `ListingDetailPane`, `ListingComposerPage`,
- * `MyListingsPane`, `FavoritesPane`)
- * each already wrap themselves, and nested antd
- * `ConfigProvider`s merge, so composing them under one `ListingsSkinTheme`
- * stays correct.
- */
-export declare function ListingsSkinTheme(props: ListingsSkinThemeProps): ReactElement;
-//# sourceMappingURL=theme.d.ts.map

package/dist/default/theme.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"theme.d.ts","sourceRoot":"","sources":["../../src/default/theme.tsx"],"names":[],"mappings":"AAgBA,OAAO,KAAK,EAAE,aAAa,EAAE,YAAY,EAAE,SAAS,EAAE,MAAM,OAAO,CAAC;AAOpE,OAAO,KAAK,EAAE,SAAS,EAAE,MAAM,qBAAqB,CAAC;AAErD,MAAM,WAAW,sBAAsB;IACrC;;;OAGG;IACH,QAAQ,CAAC,IAAI,CAAC,EAAE,SAAS,CAAC;IAC1B;8BAC0B;IAC1B,QAAQ,CAAC,KAAK,CAAC,EAAE,aAAa,CAAC;IAC/B,QAAQ,CAAC,QAAQ,EAAE,SAAS,CAAC;CAC9B;AAED;;;;;;;;;GASG;AACH,wBAAgB,iBAAiB,CAAC,KAAK,EAAE,sBAAsB,GAAG,YAAY,CAmB7E"}

package/dist/default/theme.js

@@ -1,40 +0,0 @@
-import { jsx as _jsx } from "react/jsx-runtime";
-/**
- * The default skin's INTERNAL theme provider — every `/default` surface wraps
- * itself in this, so the skin is readable no matter what the host supplies
- * (tracker #26: a skin set with no internal provider once inherited a theme
- * bridge serving light-mode values inside a dark document — text on
- * background at 1.00:1). The theme derives from `@stapel/tokens` via
- * `@stapel/tokens-antd`'s `toAntdThemeConfig(mode)`; `mode` defaults to what
- * the HOST's document declares (`resolveThemeMode()` — the `data-theme`
- * attribute `tokens.css` keys its dark block on), never to a hardcoded side.
- *
- * This is also what "override styles" means for this pair: a storefront
- * retheming through the §68 token JSON regenerates its `--stapel-*` custom
- * properties and the result page follows with zero code — a far better deal
- * than a prop-per-colour API, and the reason the skin has none.
- */
-import { useMemo } from "react";
-import { ConfigProvider } from "antd";
-import { resolveThemeMode, toAntdTheme, toAntdThemeConfig, } from "@stapel/tokens-antd";
-/**
- * `<ListingsSkinTheme/>` — the self-theming wrapper of
- * `@stapel/listings-react/default`. Standalone use is supported (wrap any
- * composition of the skin's parts once); the shipped surfaces
- * (`ListingCard`, `ListingDetailPane`, `ListingComposerPage`,
- * `MyListingsPane`, `FavoritesPane`)
- * each already wrap themselves, and nested antd
- * `ConfigProvider`s merge, so composing them under one `ListingsSkinTheme`
- * stays correct.
- */
-export function ListingsSkinTheme(props) {
-    const mode = props.mode ?? resolveThemeMode();
-    const theme = useMemo(() => toAntdThemeConfig(mode), [mode]);
-    const token = useMemo(() => toAntdTheme(mode), [mode]);
-    return (_jsx(ConfigProvider, { theme: theme, children: _jsx("div", { "data-listings-skin-root": true, "data-listings-skin-mode": mode, style: {
-                color: token.colorText,
-                backgroundColor: token.colorBgContainer,
-                ...props.style,
-            }, children: props.children }) }));
-}
-//# sourceMappingURL=theme.js.map

package/dist/default/theme.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"theme.js","sourceRoot":"","sources":["../../src/default/theme.tsx"],"names":[],"mappings":";AAAA;;;;;;;;;;;;;;GAcG;AACH,OAAO,EAAE,OAAO,EAAE,MAAM,OAAO,CAAC;AAEhC,OAAO,EAAE,cAAc,EAAE,MAAM,MAAM,CAAC;AACtC,OAAO,EACL,gBAAgB,EAChB,WAAW,EACX,iBAAiB,GAClB,MAAM,qBAAqB,CAAC;AAe7B;;;;;;;;;GASG;AACH,MAAM,UAAU,iBAAiB,CAAC,KAA6B;IAC7D,MAAM,IAAI,GAAG,KAAK,CAAC,IAAI,IAAI,gBAAgB,EAAE,CAAC;IAC9C,MAAM,KAAK,GAAG,OAAO,CAAC,GAAG,EAAE,CAAC,iBAAiB,CAAC,IAAI,CAAC,EAAE,CAAC,IAAI,CAAC,CAAC,CAAC;IAC7D,MAAM,KAAK,GAAG,OAAO,CAAC,GAAG,EAAE,CAAC,WAAW,CAAC,IAAI,CAAC,EAAE,CAAC,IAAI,CAAC,CAAC,CAAC;IACvD,OAAO,CACL,KAAC,cAAc,IAAC,KAAK,EAAE,KAAK,YAC1B,0EAE2B,IAAI,EAC7B,KAAK,EAAE;gBACL,KAAK,EAAE,KAAK,CAAC,SAAS;gBACtB,eAAe,EAAE,KAAK,CAAC,gBAAgB;gBACvC,GAAG,KAAK,CAAC,KAAK;aACf,YAEA,KAAK,CAAC,QAAQ,GACX,GACS,CAClB,CAAC;AACJ,CAAC"}

package/src/default/ErrorAlert.tsx

@@ -1,46 +0,0 @@
-/**
- * The one error surface this pair's default skin renders, so the split copy
- * core produces reaches a screen the same way everywhere (mirrors the
- * docs/notifications/workspaces etalon).
- *
- * Core's `describeFlowError` splits a failure into the sentence a person
- * reads and the technical detail a support agent quotes (owner report
- * 2026-08-09: the status used to be spliced into the sentence, ending in a
- * bare `" (500)"`). The split only helps if a skin renders both halves at
- * their own weights: `message` at normal weight, `detail` muted and small.
- *
- * `undefined` in — including a `detail` core left `undefined` because there
- * was nothing worth quoting — renders nothing rather than an empty line.
- */
-import { Alert, Typography } from "antd";
-import type { CSSProperties, ReactElement, ReactNode } from "react";
-import type { FlowErrorDisplay } from "@stapel/core";
-
-export function ErrorAlert(props: {
-  error: FlowErrorDisplay | undefined;
-  style?: CSSProperties | undefined;
-  testId?: string | undefined;
-  action?: ReactNode;
-}): ReactElement | null {
-  const { error } = props;
-  if (!error) return null;
-  return (
-    <Alert
-      type="error"
-      showIcon
-      {...(props.style ? { style: props.style } : {})}
-      {...(props.testId ? { "data-testid": props.testId } : {})}
-      {...(props.action ? { action: props.action } : {})}
-      message={error.message}
-      {...(error.detail
-        ? {
-            description: (
-              <Typography.Text type="secondary" style={{ fontSize: 12 }}>
-                {error.detail}
-              </Typography.Text>
-            ),
-          }
-        : {})}
-    />
-  );
-}

package/src/default/theme.tsx

@@ -1,67 +0,0 @@
-/**
- * The default skin's INTERNAL theme provider — every `/default` surface wraps
- * itself in this, so the skin is readable no matter what the host supplies
- * (tracker #26: a skin set with no internal provider once inherited a theme
- * bridge serving light-mode values inside a dark document — text on
- * background at 1.00:1). The theme derives from `@stapel/tokens` via
- * `@stapel/tokens-antd`'s `toAntdThemeConfig(mode)`; `mode` defaults to what
- * the HOST's document declares (`resolveThemeMode()` — the `data-theme`
- * attribute `tokens.css` keys its dark block on), never to a hardcoded side.
- *
- * This is also what "override styles" means for this pair: a storefront
- * retheming through the §68 token JSON regenerates its `--stapel-*` custom
- * properties and the result page follows with zero code — a far better deal
- * than a prop-per-colour API, and the reason the skin has none.
- */
-import { useMemo } from "react";
-import type { CSSProperties, ReactElement, ReactNode } from "react";
-import { ConfigProvider } from "antd";
-import {
-  resolveThemeMode,
-  toAntdTheme,
-  toAntdThemeConfig,
-} from "@stapel/tokens-antd";
-import type { ThemeMode } from "@stapel/tokens-antd";
-
-export interface ListingsSkinThemeProps {
-  /**
-   * Light or dark. Defaults to the mode the host's document declares
-   * (`resolveThemeMode()`). Pass explicitly to pin a side.
-   */
-  readonly mode?: ThemeMode;
-  /** Extra styles merged onto the themed root element (layout only — colors
-   * come from the mode). */
-  readonly style?: CSSProperties;
-  readonly children: ReactNode;
-}
-
-/**
- * `<ListingsSkinTheme/>` — the self-theming wrapper of
- * `@stapel/listings-react/default`. Standalone use is supported (wrap any
- * composition of the skin's parts once); the shipped surfaces
- * (`ListingCard`, `ListingDetailPane`, `ListingComposerPage`,
- * `MyListingsPane`, `FavoritesPane`)
- * each already wrap themselves, and nested antd
- * `ConfigProvider`s merge, so composing them under one `ListingsSkinTheme`
- * stays correct.
- */
-export function ListingsSkinTheme(props: ListingsSkinThemeProps): ReactElement {
-  const mode = props.mode ?? resolveThemeMode();
-  const theme = useMemo(() => toAntdThemeConfig(mode), [mode]);
-  const token = useMemo(() => toAntdTheme(mode), [mode]);
-  return (
-    <ConfigProvider theme={theme}>
-      <div
-        data-listings-skin-root
-        data-listings-skin-mode={mode}
-        style={{
-          color: token.colorText,
-          backgroundColor: token.colorBgContainer,
-          ...props.style,
-        }}
-      >
-        {props.children}
-      </div>
-    </ConfigProvider>
-  );
-}