i18n

To add react-i18next translation keys without hardcoding UI text, create a new flat dot-notated key like `{feature}.{context}.{action}` in `src/locales/default/{namespace}.ts` and wire the namespace in the index file.

The `pnpm i18n` command automatically generates translation files by extracting keys from the default locale definitions, ensuring zh-CN and en-US JSON files stay synchronized for development preview or release workflows.

The flat dot-notation key convention for react-i18next namespaces structures keys as `{feature}.{context}.{action}` to prevent translation key collisions and keep locale mappings maintainable across feature development.

To wire a new namespace in the default locale index, register it in `src/locales/default/index.ts` so `t()` calls resolve correctly across features without directly modifying the source JSON files.

Yes, you can use variable interpolation in translation keys by applying the `{{variable}}` syntax within your locale string definitions, allowing dynamic values to be injected into the translated text at runtime.

The `pnpm i18n` workflow modifies locale TypeScript definitions rather than editing source JSON files directly to maintain a single source of truth and prevent translation desynchronization during development or PR preparation.