import type { I18nDictionary, I18nEngine } from "@stapel/core";
export { categoriesErrorBundleRu } from "./generated/errors.ru.gen.js";
/**
 * Russian bundle for categories-react — the `@stapel/categories-react/i18n/ru`
 * subpath (i18n-shipping.md §2) so the locale is opt-in: hosts that do not
 * register it never carry these strings (the main entry does not import this
 * module — gated by size-limit + the bundle-purity test).
 *
 * This is the storefront's DEFAULT language (storefront spec verdict F1:
 * ru-first).
 *
 * ── What comes from where ──────────────────────────────────────────────────
 *
 * `stapel-categories` 0.21.5 ships `translations/errors.ru.json`, which is
 * the line that used to say the opposite. Of the 64 registry codes:
 *
 *  - the 42 cross-cutting `stapel_core` codes are GENERATED, merged in from
 *    stapel-core's own catalogue by `pnpm gen:errors`;
 *  - the **9 `stapel_categories` codes** are GENERATED too, from the module's
 *    own catalogue — the nine 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 pairs must not give one refusal two
 *    sentences (§13.2 note 3). A host registers both bundles;
 *    `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 the two-sources problem this file just removed.
 *
 * The first two bullets are the whole generated spread below; everything after
 * it is UI copy, and this pair keeps no error-text override at all.
 *
 * PROVENANCE, stated rather than implied: the core catalogue ships
 * `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.
 *
 * And once more, because it is the fact this pair exists to be honest about:
 * **no category name is translated here.** Category and feature names arrive
 * as translation KEYS (`catalog/labels.ts`) and belong in the deployment's own
 * bundle, not in a library's.
 */
export declare const categoriesI18nBundleRu: I18nDictionary;
/** Register the `ru` bundle. Call AFTER `registerCategoriesI18n` so it
 * overrides the English floor. */
export declare function registerCategoriesI18nRu(engine: I18nEngine, locale?: string): void;
//# sourceMappingURL=ru.d.ts.map