fix: add i18n route bridges to dispatcher plugin

The createDispatcherPlugin() bridges all service domains (auth, analytics,
packages, storage, automation) from HttpDispatcher to the HTTP server, but
i18n was missing. When no explicit I18nServicePlugin is loaded (kernel uses
memory fallback i18n), no i18n HTTP routes were registered, causing 404.

Add 3 i18n route bridges consistent with all other service domains:
- GET /api/v1/i18n/locales
- GET /api/v1/i18n/translations/:locale
- GET /api/v1/i18n/labels/:object/:locale

Co-authored-by: hotlong <50353452+hotlong@users.noreply.github.com>

Author: Copilot

CHANGELOG.md

@@ -19,6 +19,11 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - `I18nServicePlugin` now accepts `registerRoutes` and `basePath` options for HTTP route control.
 - i18n endpoints now work independently of `RestServer`, enabling MSW/mock test environments
   to serve i18n routes without any REST API gateway dependency.
+- **Dispatcher i18n bridge routes** — `createDispatcherPlugin()` now registers i18n HTTP route
+  bridges (`GET /i18n/locales`, `GET /i18n/translations/:locale`, `GET /i18n/labels/:object/:locale`)
+  via `HttpDispatcher.handleI18n()`, ensuring i18n endpoints work even when only the kernel's
+  memory fallback i18n is active (no explicit `I18nServicePlugin` loaded). This is consistent with
+  how auth, analytics, packages, storage, and automation services are bridged.
 
 ### Added
 - **i18n as core built-in service** — The i18n service is now a `core` criticality service with

packages/runtime/src/dispatcher-plugin.ts

@@ -53,7 +53,7 @@ function errorResponse(err: any, res: any): void {
  *   - /graphql   (GraphQL)
  *   - /analytics (BI queries)
  *   - /packages  (package management)
-
+ *   - /i18n      (internationalization — locales, translations, field labels)
  *   - /storage   (file storage)
  *   - /automation (CRUD + triggers + runs)
  *
@@ -237,6 +237,36 @@ export function createDispatcherPlugin(config: DispatcherPluginConfig = {}): Plu
                 }
             });
 
+            // ── i18n ────────────────────────────────────────────────────
+            // Bridges to HttpDispatcher.handleI18n() which resolves the i18n
+            // service from the kernel (either I18nServicePlugin or memory fallback).
+            server.get(`${prefix}/i18n/locales`, async (req: any, res: any) => {
+                try {
+                    const result = await dispatcher.handleI18n('/locales', 'GET', req.query, { request: req });
+                    sendResult(result, res);
+                } catch (err: any) {
+                    errorResponse(err, res);
+                }
+            });
+
+            server.get(`${prefix}/i18n/translations/:locale`, async (req: any, res: any) => {
+                try {
+                    const result = await dispatcher.handleI18n(`/translations/${req.params.locale}`, 'GET', req.query, { request: req });
+                    sendResult(result, res);
+                } catch (err: any) {
+                    errorResponse(err, res);
+                }
+            });
+
+            server.get(`${prefix}/i18n/labels/:object/:locale`, async (req: any, res: any) => {
+                try {
+                    const result = await dispatcher.handleI18n(`/labels/${req.params.object}/${req.params.locale}`, 'GET', req.query, { request: req });
+                    sendResult(result, res);
+                } catch (err: any) {
+                    errorResponse(err, res);
+                }
+            });
+
             // ── Automation ──────────────────────────────────────────────
             server.get(`${prefix}/automation`, async (req: any, res: any) => {
                 try {