@stapel/listings-react 0.28.1 → 0.29.1

package/src/i18n/es.ts

@@ -8,39 +8,33 @@ export { listingsErrorBundleEs } from "./generated/errors.es.gen.js";
  * Spanish bundle for listings-react — the `@stapel/listings-react/i18n/es`
  * subpath (i18n-shipping.md §2), opt-in exactly like `./i18n/ru`.
  *
- * It carries the UI copy too, not only the nine module-owned error keys. The
+ * It carries the UI copy, which is now the ONLY thing it carries by hand. The
  * composer and the owner's dashboard are the surfaces a seller works in for
  * minutes at a time; a half-translated form there is visible immediately, in
  * the way a half-translated settings pane is not. Same call chat-react made
  * for the buyer↔seller thread.
  *
- * Provenance and the owner split are as in `./ru.ts`: 42 cross-cutting codes
- * generated from stapel-core's catalogue, 9 `stapel_listings` codes authored
- * here until upstream ships `translations/`, and the 12 `stapel_attributes`
- * codes deliberately left to `@stapel/attributes-react`.
+ * Provenance and the owner split are as in `./ru.ts`: of the 72 registry
+ * codes, 42 cross-cutting `stapel_core` ones are generated from core's
+ * catalogue and the 17 `stapel_listings` ones from the module's own — which
+ * stapel-listings 0.22.8 ships for the first time, and which is why the
+ * seventeen strings that used to be authored here are gone. The 13
+ * `stapel_attributes` codes stay with `@stapel/attributes-react`.
  */
 export const listingsI18nBundleEs: I18nDictionary = {
   ...listingsErrorBundleEs,
 
-  // ── the 10 stapel_listings-owned codes, pair-authored ────────────────────
-  "error.400.category_required": "Hay que elegir una categoría",
-  "error.400.image_required":
-    "Para publicar el anuncio hace falta al menos una foto",
-  "error.400.listing_feature_not_allowed":
-    "El detalle «{feature}» no pertenece a esta categoría",
-  "error.400.listing_invalid_status_filter":
-    "Estado de anuncio desconocido: «{status}»",
-  "error.400.publish_validation_failed":
-    "El anuncio no pasó la revisión y no se publicó",
-  "error.403.listing_anonymous_not_allowed":
-    "Para publicar un anuncio, inicia sesión o crea una cuenta",
-  "error.403.listing_not_owner": "Este anuncio no es tuyo",
-  "error.404.listing_not_found": "No se encontró el anuncio",
-  "error.409.already_favorited": "El anuncio ya está en favoritos",
-  "error.409.invalid_listing_transition":
-    "Desde su estado actual, el anuncio no se puede mover así",
-  "error.409.listing_cannot_delete_active":
-    "Archívalo primero — un anuncio a la venta no se puede borrar",
+  // ── stapel_listings' own refusals: NONE are authored here any more ───────
+  //
+  // stapel-listings 0.22.8 ships `translations/errors.es.json`, so all
+  // SEVENTEEN codes it owns arrive through the generated spread above and the
+  // seventeen lines that stood in for them are deleted — one string, one
+  // source. The reasoning, and the single surviving override, are spelled out
+  // once in `./ru.ts`; this is its es half.
+  //
+  // The one override that survived 0.22.8 is gone with it: stapel-listings
+  // 0.22.10 dropped the {from_status} slot from all three languages, so there
+  // is nothing left for this pair to correct.
 
   "listings.error.unknown": "Algo salió mal con este anuncio",
 
@@ -230,26 +224,6 @@ export const listingsI18nBundleEs: I18nDictionary = {
   "listings.favorites.sign_in_hint":
     "Los favoritos se guardan en tu cuenta, así que te siguen entre dispositivos.",
 
-  // Las dos comprobaciones de publicación que llegaron con el contrato 0.17.
-  "error.400.listing_location_required":
-    "Indica dónde está el artículo antes de publicarlo",
-  "error.400.listing_zero_price_not_allowed":
-    "En esta categoría no se permite un precio de 0. Deja el precio vacío para «precio no indicado».",
-
-  "error.400.listing_draft_meta_too_large":
-    "El borrador es demasiado grande (máximo {max_bytes} bytes). Quita parte de los datos y guarda de nuevo.",
-
-  // stapel-listings 0.22.3: the features_draft WRITE now accepts the shape a
-  // listing READ returns. These three are the refusals for a body that is
-  // neither — read by whoever is wiring the integration, so each names the
-  // shape it wanted instead of advising "try again".
-  "error.400.listing_features_draft_shape":
-    "features_draft debe ser un objeto con los slugs de las características como claves, o la lista de objetos de característica que devuelve la lectura del anuncio (cada uno con su propio «slug»). Llegó: {got_type}. Ejemplo de la forma de objeto aceptada: {example}",
-  "error.400.listing_features_draft_unknown_slug":
-    "Cada elemento de una lista features_draft debe llevar su propio «slug» no vacío — el que la lectura del anuncio guarda en ese elemento — para poder archivarlo bajo la característica correcta. El elemento en el índice {index} no lo tiene. Ejemplo: {example}",
-  "error.400.listing_features_draft_value_shape":
-    "features_draft['{slug}'] debe ser a su vez un objeto de la forma {{\"type\": <tipo de característica>, \"value\": <valor de característica>}}. Llegó: {got_type}. Ejemplo: {example}",
-
   "listings.blocked.sign_in": "Inicia sesión para hacer esto",
   "listings.blocked.guest":
     "Esta cuenta todavía no puede hacerlo — termina de configurarla primero",

package/src/i18n/generated/errors.es.gen.ts

@@ -8,8 +8,8 @@ import type { ListingsErrorCode } from "./errors.gen.js";
 /**
  * `es` texts for the backend error codes this catalog carries.
  *
- * PARTIAL, and deliberately typed to say so: 30 key(s) owned by
- * stapel_attributes, stapel_listings are absent, because that owner ships no locale catalog
+ * PARTIAL, and deliberately typed to say so: 13 key(s) owned by
+ * stapel_attributes are absent, because that owner ships no locale catalog
  * (ERRORS_LOCALE_EXEMPT_OWNERS). English for them still comes from the registry
  * artifact via the en bundle; the pair layers its own authored `es`
  * strings over this one until upstream ships translations. `Partial` is what
@@ -22,6 +22,7 @@ export const listingsErrorBundleEs: Partial<Record<ListingsErrorCode, string>> =
   "error.400.bad_request": "Solicitud incorrecta",
   "error.400.captcha_invalid": "La verificación del captcha ha fallado. Inténtalo de nuevo.",
   "error.400.captcha_required": "Se requiere el token del captcha.",
+  "error.400.category_required": "La categoría es obligatoria",
   "error.400.expected_list": "Se esperaba una lista de elementos",
   "error.400.field.blank": "{field} no puede estar vacío",
   "error.400.field.does_not_exist": "{field} no existe",
@@ -34,23 +35,39 @@ export const listingsErrorBundleEs: Partial<Record<ListingsErrorCode, string>> =
   "error.400.field.null": "{field} no puede ser nulo",
   "error.400.field.required": "{field} es obligatorio",
   "error.400.field.unique": "{field} debe ser único",
+  "error.400.image_required": "Se necesita al menos una imagen para publicar",
   "error.400.invalid_ad_id": "ID de anuncio no válido",
+  "error.400.listing_draft_meta_too_large": "El campo draft_meta es demasiado grande (máximo {max_bytes} bytes)",
+  "error.400.listing_feature_not_allowed": "La característica {feature} no está permitida en esta categoría",
+  "error.400.listing_features_draft_shape": "features_draft debe ser un objeto con los slugs de las características como claves, o la lista de objetos de característica que devuelve la lectura de un anuncio (cada uno con su propio «slug»); se recibió {got_type}. Ejemplo de la forma de objeto aceptada: {example}",
+  "error.400.listing_features_draft_unknown_slug": "Cada elemento de una lista features_draft debe llevar su propia cadena «slug» no vacía (el slug que la lectura de un anuncio guarda en ese elemento) para poder asignarlo a la característica correcta; el elemento con índice {index} no la tiene. Ejemplo: {example}",
+  "error.400.listing_features_draft_value_shape": "features_draft['{slug}'] debe ser a su vez un objeto de la forma {{\"type\": <tipo de característica>, \"value\": <valor de la característica>}}; se recibió {got_type}. Ejemplo: {example}",
+  "error.400.listing_invalid_status_filter": "Estado de anuncio desconocido: {status}",
+  "error.400.listing_location_required": "Indica dónde se encuentra el artículo antes de publicar",
+  "error.400.listing_zero_price_not_allowed": "No se permite un precio de 0 en esta categoría. Deja el precio vacío para indicar «precio no indicado».",
+  "error.400.publish_validation_failed": "La validación del anuncio ha fallado",
   "error.400.validation_error": "Error de validación",
   "error.400.verification_failed": "La verificación ha fallado",
   "error.400.verification_invalid_factor": "Este factor de verificación no está disponible",
   "error.401.unauthorized": "Se requiere autenticación",
   "error.402.payment_required": "Se requiere pago",
   "error.403.forbidden": "No tienes permiso para realizar esta acción",
+  "error.403.listing_anonymous_not_allowed": "Una cuenta de invitado no puede publicar anuncios",
+  "error.403.listing_not_owner": "Este anuncio no es tuyo",
   "error.403.network_blocked": "No se permiten solicitudes desde esta red.",
   "error.403.verification_enrollment_required": "Es necesario registrar un factor de verificación.",
   "error.403.verification_required": "Se requiere verificación adicional",
   "error.404.ad_not_found": "Anuncio no encontrado",
+  "error.404.listing_not_found": "Anuncio no encontrado",
   "error.404.not_found": "Recurso solicitado no encontrado",
   "error.404.verification_challenge_not_found": "Desafío de verificación no encontrado o caducado",
   "error.405.method_not_allowed": "Método no permitido",
   "error.406.not_acceptable": "No aceptable",
   "error.408.request_timeout": "Tiempo de espera de la solicitud agotado",
+  "error.409.already_favorited": "El anuncio ya está en favoritos",
   "error.409.conflict": "El recurso ya existe",
+  "error.409.invalid_listing_transition": "El anuncio no puede pasar de su estado actual al estado elegido",
+  "error.409.listing_cannot_delete_active": "No se puede eliminar un anuncio activo. Archívalo primero.",
   "error.410.gone": "El recurso se ha eliminado permanentemente",
   "error.413.payload_too_large": "El cuerpo de la solicitud es demasiado grande",
   "error.415.unsupported_media_type": "Tipo de contenido no compatible",

package/src/i18n/generated/errors.gen.ts

@@ -95,7 +95,7 @@ export const LISTINGS_ERRORS = {
   "error.408.request_timeout": { status: 408, params: [], remediation: "retry", en: "Request timeout" },
   "error.409.already_favorited": { status: 409, params: [], remediation: "fix_input", en: "Listing already favorited" },
   "error.409.conflict": { status: 409, params: [], remediation: "fix_input", en: "Resource already exists" },
-  "error.409.invalid_listing_transition": { status: 409, params: ["from_status"], remediation: "fix_input", en: "Invalid status transition for {from_status}" },
+  "error.409.invalid_listing_transition": { status: 409, params: [], remediation: "fix_input", en: "This listing cannot move to that status from the one it is in now" },
   "error.409.listing_cannot_delete_active": { status: 409, params: [], remediation: "fix_input", en: "Cannot delete an active listing. Archive it first." },
   "error.410.gone": { status: 410, params: [], remediation: "retry", en: "Resource has been permanently removed" },
   "error.413.payload_too_large": { status: 413, params: [], remediation: "retry", en: "Request body is too large" },
@@ -253,7 +253,7 @@ export const listingsErrorBundleEn: Record<ListingsErrorCode, string> = {
   "error.408.request_timeout": "Request timeout",
   "error.409.already_favorited": "Listing already favorited",
   "error.409.conflict": "Resource already exists",
-  "error.409.invalid_listing_transition": "Invalid status transition for {from_status}",
+  "error.409.invalid_listing_transition": "This listing cannot move to that status from the one it is in now",
   "error.409.listing_cannot_delete_active": "Cannot delete an active listing. Archive it first.",
   "error.410.gone": "Resource has been permanently removed",
   "error.413.payload_too_large": "Request body is too large",

package/src/i18n/generated/errors.json

@@ -490,11 +490,9 @@
   {
     "code": "error.409.invalid_listing_transition",
     "status": 409,
-    "params": [
-      "from_status"
-    ],
+    "params": [],
     "remediation": "fix_input",
-    "en": "Invalid status transition for {from_status}"
+    "en": "This listing cannot move to that status from the one it is in now"
   },
   {
     "code": "error.409.listing_cannot_delete_active",

package/src/i18n/generated/errors.ru.gen.ts

@@ -8,8 +8,8 @@ import type { ListingsErrorCode } from "./errors.gen.js";
 /**
  * `ru` texts for the backend error codes this catalog carries.
  *
- * PARTIAL, and deliberately typed to say so: 30 key(s) owned by
- * stapel_attributes, stapel_listings are absent, because that owner ships no locale catalog
+ * PARTIAL, and deliberately typed to say so: 13 key(s) owned by
+ * stapel_attributes are absent, because that owner ships no locale catalog
  * (ERRORS_LOCALE_EXEMPT_OWNERS). English for them still comes from the registry
  * artifact via the en bundle; the pair layers its own authored `ru`
  * strings over this one until upstream ships translations. `Partial` is what
@@ -22,6 +22,7 @@ export const listingsErrorBundleRu: Partial<Record<ListingsErrorCode, string>> =
   "error.400.bad_request": "Некорректный запрос",
   "error.400.captcha_invalid": "Проверка капчи не пройдена. Пожалуйста, попробуйте ещё раз.",
   "error.400.captcha_required": "Требуется токен капчи.",
+  "error.400.category_required": "Категория обязательна",
   "error.400.expected_list": "Ожидался список элементов",
   "error.400.field.blank": "Поле «{field}» не может быть пустым",
   "error.400.field.does_not_exist": "«{field}» не существует",
@@ -34,23 +35,39 @@ export const listingsErrorBundleRu: Partial<Record<ListingsErrorCode, string>> =
   "error.400.field.null": "Поле «{field}» не может быть null",
   "error.400.field.required": "Поле «{field}» обязательно",
   "error.400.field.unique": "Значение поля «{field}» должно быть уникальным",
+  "error.400.image_required": "Для публикации нужна хотя бы одна фотография",
   "error.400.invalid_ad_id": "Недопустимый идентификатор объявления",
+  "error.400.listing_draft_meta_too_large": "Поле draft_meta слишком большое (не более {max_bytes} байт)",
+  "error.400.listing_feature_not_allowed": "Характеристика «{feature}» недопустима для этой категории",
+  "error.400.listing_features_draft_shape": "features_draft должен быть объектом с ключами-слагами характеристик либо списком объектов характеристик, который возвращает чтение объявления (у каждого есть собственный «slug») — получено {got_type}. Пример допустимой формы объекта: {example}",
+  "error.400.listing_features_draft_unknown_slug": "Каждый элемент списка features_draft должен содержать собственную непустую строку «slug» (тот слаг, который чтение объявления сохраняет в этом элементе), чтобы значение вернулось к нужной характеристике — у элемента с индексом {index} его нет. Пример: {example}",
+  "error.400.listing_features_draft_value_shape": "features_draft['{slug}'] сам должен быть объектом вида {{\"type\": <тип характеристики>, \"value\": <значение характеристики>}} — получено {got_type}. Пример: {example}",
+  "error.400.listing_invalid_status_filter": "Неизвестный статус объявления «{status}»",
+  "error.400.listing_location_required": "Перед публикацией укажите, где находится товар",
+  "error.400.listing_zero_price_not_allowed": "Цена 0 в этой категории недопустима. Оставьте поле цены пустым — это означает «цена не указана».",
+  "error.400.publish_validation_failed": "Объявление не прошло проверку",
   "error.400.validation_error": "Ошибка валидации",
   "error.400.verification_failed": "Проверка не пройдена",
   "error.400.verification_invalid_factor": "Этот способ подтверждения недоступен",
   "error.401.unauthorized": "Требуется аутентификация",
   "error.402.payment_required": "Требуется оплата",
   "error.403.forbidden": "У вас нет прав для выполнения этого действия",
+  "error.403.listing_anonymous_not_allowed": "Гостевая учётная запись не может публиковать объявления",
+  "error.403.listing_not_owner": "Это не ваше объявление",
   "error.403.network_blocked": "Запросы из этой сети не разрешены.",
   "error.403.verification_enrollment_required": "Требуется регистрация фактора подтверждения.",
   "error.403.verification_required": "Требуется дополнительная проверка",
   "error.404.ad_not_found": "Объявление не найдено",
+  "error.404.listing_not_found": "Объявление не найдено",
   "error.404.not_found": "Запрошенный ресурс не найден",
   "error.404.verification_challenge_not_found": "Запрос на подтверждение не найден или истёк",
   "error.405.method_not_allowed": "Метод не разрешён",
   "error.406.not_acceptable": "Недопустимый формат ответа",
   "error.408.request_timeout": "Время ожидания запроса истекло",
+  "error.409.already_favorited": "Объявление уже в избранном",
   "error.409.conflict": "Ресурс уже существует",
+  "error.409.invalid_listing_transition": "Из текущего статуса объявление нельзя перевести в выбранный",
+  "error.409.listing_cannot_delete_active": "Активное объявление нельзя удалить. Сначала перенесите его в архив.",
   "error.410.gone": "Ресурс был безвозвратно удалён",
   "error.413.payload_too_large": "Тело запроса слишком большое",
   "error.415.unsupported_media_type": "Неподдерживаемый тип данных",

package/src/i18n/keys.ts

@@ -546,13 +546,12 @@ export const listingsI18nBundleEn: Record<string, string> = {
    * the reader needs is which MOVE is impossible, and that is the control
    * they are looking at.
    *
-   * The SERVER's own 409 (`error.409.invalid_listing_transition`) carries the
-   * same placeholder and is reworded in the ru and es bundles beside this
-   * one, where a real reader met it. It is deliberately NOT overridden in the
-   * English bundle: that bundle spreads the generated backend texts whole,
-   * and a hand-written entry for one error code makes this pair's catalogue
-   * claim a namespace it does not own — `stapel/i18n-locale-parity` says so
-   * and is right. The refusal is in any case now close to unreachable: the
+   * The SERVER's own 409 (`error.409.invalid_listing_transition`) carried the
+   * same placeholder and was reworded here, in the ru and es bundles, for the
+   * same reason. That override is GONE as of stapel-listings 0.22.10, which
+   * dropped the slot upstream in all three languages — so the refusal now
+   * arrives already free of the wire value and this pair authors nothing under
+   * `error.*` at all. The refusal is in any case close to unreachable: the
    * dashboard offers only the moves the server declared.
    */
   "listings.blocked.transition":

package/src/i18n/ru.ts

@@ -17,50 +17,48 @@ export { listingsErrorBundleRu } from "./generated/errors.ru.gen.js";
  *
  * ── What comes from where ──────────────────────────────────────────────────
  *
- * `stapel-listings` ships **no `translations/` directory at all**, so 21 of
- * the 63 registry codes can never come from an upstream catalogue. They split
- * by owner:
+ * `stapel-listings` 0.22.8 ships `translations/errors.ru.json`, which is the
+ * line that used to say the opposite. Of the 72 registry codes:
  *
  *  - the 42 cross-cutting `stapel_core` codes are GENERATED, merged in from
- *    stapel-core's own catalogue by `pnpm gen:errors` (spread first below);
- *  - the **9 `stapel_listings` codes** are authored here — and when upstream
- *    ships a catalogue, nine lines are deleted and no key or text moves;
- *  - the **12 `stapel_attributes` codes** are NOT here. They belong to
+ *    stapel-core's own catalogue by `pnpm gen:errors`;
+ *  - the **17 `stapel_listings` codes** are GENERATED too, from the module's
+ *    own catalogue — the seventeen hand-authored lines that stood in for it
+ *    are deleted, so each of those strings has exactly one source and the
+ *    drift gate owns it;
+ *  - the **13 `stapel_attributes` codes** are NOT here. They belong to
  *    `@stapel/attributes-react`, which already translates them and which is a
  *    peer of this pair anyway. Two packages must not give one refusal two
  *    sentences (spec §13.2, note 3). A host registers both bundles;
- *    `test/i18n.test.ts` proves the union covers the registry.
+ *    `test/i18n.test.ts` proves the union covers the registry. stapel-attributes
+ *    0.9.3 ships a catalogue of its own now, and merging it in HERE would
+ *    recreate exactly the two-sources problem this file just removed — the
+ *    place to consume it is that pair, not this one.
+ *
+ * The first two bullets are the whole generated spread below; what follows it
+ * by hand is UI copy plus one deliberate override, called out where it sits.
  *
  * PROVENANCE, stated rather than implied: the core catalogue ships
- * `origin=seed:authored` and is UNREVIEWED; the pair-authored strings below
- * are the same grade. Neither is a claim of review.
+ * `origin=seed:authored` and is UNREVIEWED; the module's own catalogue and the
+ * pair-authored UI copy below are the same grade. None of it is a claim of
+ * review.
  */
 export const listingsI18nBundleRu: I18nDictionary = {
   ...listingsErrorBundleRu,
 
-  // ── the 10 stapel_listings-owned codes, pair-authored ────────────────────
-  "error.400.category_required": "Нужно выбрать категорию",
-  "error.400.image_required":
-    "Чтобы опубликовать объявление, добавьте хотя бы одно фото",
-  "error.400.listing_feature_not_allowed":
-    "Характеристика «{feature}» не относится к этой категории",
-  "error.400.listing_invalid_status_filter":
-    "Неизвестный статус объявления: «{status}»",
-  "error.400.publish_validation_failed":
-    "Объявление не прошло проверку и не опубликовано",
-  "error.403.listing_anonymous_not_allowed":
-    "Чтобы подать объявление, войдите или зарегистрируйтесь",
-  "error.403.listing_not_owner": "Это не ваше объявление",
-  "error.404.listing_not_found": "Объявление не найдено",
-  "error.409.already_favorited": "Объявление уже в избранном",
-  // No `{from_status}`: what landed in that slot was the wire value
-  // ('draft', 'archived'), and the status is already named in the reader's
-  // own words beside the control. See the note on this pair of keys in
-  // keys.ts.
-  "error.409.invalid_listing_transition":
-    "Из текущего состояния объявление так перевести нельзя",
-  "error.409.listing_cannot_delete_active":
-    "Сначала снимите объявление с публикации — активное удалить нельзя",
+  // ── stapel_listings' own refusals: NONE are authored here any more ───────
+  //
+  // The module ships `translations/errors.ru.json` as of 0.22.8, so all
+  // SEVENTEEN codes it owns arrive through the generated spread above. The
+  // seventeen lines that used to sit here are deleted rather than kept beside
+  // it: a key with two sources drifts, and nothing in this file could tell a
+  // reader which of the two a screen had shown them.
+  //
+  // The ONE override this pair kept at 0.22.8 is gone too, as its own note
+  // said it should be: upstream's text interpolated {from_status} — the WIRE
+  // value ('draft', 'archived') — into translated prose, and stapel-listings
+  // 0.22.10 dropped the placeholder from all three languages. The pair now
+  // authors nothing at all under `error.*`.
 
   "listings.error.unknown": "Что-то пошло не так с этим объявлением",
 
@@ -253,30 +251,6 @@ export const listingsI18nBundleRu: I18nDictionary = {
   "listings.favorites.sign_in_hint":
     "Избранное хранится в аккаунте, поэтому переходит с вами на другие устройства.",
 
-  // The two publish checks the 0.17 contract brought with it: a place is
-  // required, and a zero price in such a category is an empty field rather
-  // than "free".
-  "error.400.listing_location_required":
-    "Перед публикацией укажите, где находится товар",
-  "error.400.listing_zero_price_not_allowed":
-    "В этой категории цена 0 недопустима. Оставьте поле пустым — это и есть «цена не указана».",
-
-  // stapel-listings 0.21.2: the composer's per-field provenance sidecar has a
-  // size ceiling, and the number is the server's own — never restated here.
-  "error.400.listing_draft_meta_too_large":
-    "Черновик слишком большой (не больше {max_bytes} байт). Уберите часть данных и сохраните ещё раз.",
-
-  // stapel-listings 0.22.3: the features_draft WRITE now accepts the shape a
-  // listing READ returns. These three are the refusals for a body that is
-  // neither — read by whoever is wiring the integration, so each names the
-  // shape it wanted instead of advising "try again".
-  "error.400.listing_features_draft_shape":
-    "features_draft должен быть объектом со слагами признаков в ключах — или тем списком объектов признаков, который возвращает чтение объявления (у каждого свой «slug»). Пришло: {got_type}. Пример принимаемой формы объекта: {example}",
-  "error.400.listing_features_draft_unknown_slug":
-    "У каждого элемента списка features_draft должен быть свой непустой «slug» — тот, который чтение объявления хранит на этом элементе, иначе значение некуда положить. У элемента с индексом {index} его нет. Пример: {example}",
-  "error.400.listing_features_draft_value_shape":
-    "features_draft['{slug}'] сам должен быть объектом вида {{\"type\": <тип признака>, \"value\": <значение признака>}}. Пришло: {got_type}. Пример: {example}",
-
   "listings.blocked.sign_in": "Войдите, чтобы сделать это",
   "listings.blocked.guest":
     "Этот аккаунт пока так не может — сначала завершите настройку",
@@ -303,17 +277,17 @@ export const listingsI18nBundleRu: I18nDictionary = {
 };
 
 /**
- * Register the Russian bundle into a core i18n engine — AND the twelve
+ * Register the Russian bundle into a core i18n engine — AND the thirteen
  * `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
+ * host that registered only this bundle got thirteen 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
+ * RAISE those thirteen, 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.