release: bump version to 0.73.0

docs/technical/en/frontend-admin-frontend-context.md

@@ -98,6 +98,8 @@ Admin status labels should use [StatusText](/home/ray/dev/linkong/planet/fronten
 
 `StatusText` is an indicator-light pill: the pill background and border stay on the component base color, while only the dot and text use the status color. `Badge` does not carry the indicator-light meaning, so it may use a light same-tone background and border for stronger hierarchy.
 
+Status indicators must show the full state word. In lists, hierarchy groups, and detail headers, the title/description area should shrink or wrap while the status pill keeps content-sized width and does not get compressed by flex/grid layout; do not truncate state words such as `Configured` or `Available` just to save horizontal space.
+
 | Tone | Color variable | Meaning | Examples |
 | --- | --- | --- | --- |
 | `success` | `--an-success` | available, successful, connected, enabled | log source `Available`, collection `Success` |
@@ -216,7 +218,31 @@ Current constraints:
 - Prefer CSS variable overrides for colors instead of hard-coding theme colors in feature components
 - Best for a small set of mutually exclusive choices; do not use it as a long list, navigation menu, or select replacement
 
-### 6. `MarkdownRenderer`
+### 6. Console i18n
+
+Files:
+
+- [i18n/index.ts](/home/ray/dev/linkong/planet/frontend/src/i18n/index.ts)
+- [i18n/locale.ts](/home/ray/dev/linkong/planet/frontend/src/i18n/locale.ts)
+- [i18n/resources.ts](/home/ray/dev/linkong/planet/frontend/src/i18n/resources.ts)
+- [LegacyI18nBridge.tsx](/home/ray/dev/linkong/planet/frontend/src/i18n/LegacyI18nBridge.tsx)
+
+Purpose:
+
+- Share one `zh-CN` / `en-US` language state across the console, auth pages, and Docs UI
+- Store the language preference in `planet-locale` while keeping compatibility with the old `docs-lang`
+- Keep Docs API requests mapped to the backend's existing `zh` / `en` document interface
+- Provide language switchers in the console sidebar preferences panel and auth panel
+
+Current constraints:
+
+- New console copy should be added to `resources.ts`, then consumed with `useTranslation()` or `useLocale()`
+- Routes, menus, search indexes, and shared components must use explicit translation keys
+- `LegacyI18nBridge` is transitional and only handles exact static text and attributes inside admin/auth containers
+- Business data, raw logs, API field names, provider ids, commands, and Markdown body content are not translated by the legacy bridge
+- Future large-page migrations should shrink the legacy dictionary rather than grow it
+
+### 7. `MarkdownRenderer`
 
 File: