Document Waterline environment banner names and supported colors

docs/monitoring.md

@@ -254,6 +254,36 @@ backend does not migrate or combine runs.
 | A service-catalog route reports `backend_capability_unavailable` | Service mode does not mirror Waterline's embedded cross-namespace service catalog. Use the connected server's native service endpoints and API for that capability. |
 | A custom metric is missing from Waterline | Inspect the worker's metrics exporter. Waterline reports durable operator facts, not arbitrary process metrics. |
 
+### Environment banner {#waterline-environment-banner}
+
+Label production and non-production Waterline tabs with the environment banner. These variables work in embedded Laravel and standalone service mode:
+
+```dotenv
+WATERLINE_ENV_NAME=production
+WATERLINE_ENV_COLOR="#dc3545"
+```
+
+`WATERLINE_ENV_COLOR` selects a fixed CSP-compatible palette:
+
+| Accepted value | Banner color |
+| --- | --- |
+| `#0d6efd` or `#2563eb` | Blue |
+| `#198754` or `#28a745` | Green |
+| `#6f42c1` or `#7746ec` | Purple |
+| `#dc3545` | Red |
+| `#fd7e14` | Orange |
+| `#ffc107` | Yellow |
+
+Other values render neutral gray, including valid hex colors such as `#ff0000`. Use a listed palette value for the intended color.
+
+In embedded Laravel, the resolved `env_name` and `env_color` keys in `config/waterline.php` are authoritative. A published configuration can override the environment-based values. After changing environment-based configuration, rebuild the host application's configuration cache through its normal deployment:
+
+```bash
+php artisan config:cache
+```
+
+Inspect the resolved Waterline configuration when the banner differs from `.env`; cached configuration remains in effect until rebuilt. In standalone service mode, update the Waterline deployment environment and recreate or redeploy the Waterline container so it loads the new values. These are Waterline display settings; apply them to the Waterline service described above.
+
 ### Cloud Managed Waterline
 
 Cloud customers open Cloud Managed Waterline from the namespace-scoped managed

i18n/de/docusaurus-plugin-content-docs/current/monitoring.md

@@ -169,6 +169,36 @@ Waterline zeigt nur den konfigurierten Namespace und die vom verbundenen Server
 | Eine Dienstkatalogroute meldet `backend_capability_unavailable` | Der Dienstmodus spiegelt Waterlines eingebetteten Namespace-übergreifenden Dienstkatalog nicht. Verwenden Sie dafür native Dienstendpunkte und API des verbundenen Servers. |
 | Eine eigene Metrik fehlt in Waterline | Den Metrikexporter des Workers prüfen. Waterline meldet dauerhafte Operatorfakten, keine beliebigen Prozessmetriken. |
 
+### Umgebungsbanner {#waterline-environment-banner}
+
+Kennzeichnen Sie Produktions- und Nichtproduktions-Tabs mit dem Waterline-Umgebungsbanner. Diese Variablen funktionieren in eingebettetem Laravel und im eigenständigen Service-Modus:
+
+```dotenv
+WATERLINE_ENV_NAME=production
+WATERLINE_ENV_COLOR="#dc3545"
+```
+
+`WATERLINE_ENV_COLOR` wählt aus einer festen CSP-kompatiblen Palette:
+
+| Akzeptierter Wert | Bannerfarbe |
+| --- | --- |
+| `#0d6efd` oder `#2563eb` | Blau |
+| `#198754` oder `#28a745` | Grün |
+| `#6f42c1` oder `#7746ec` | Violett |
+| `#dc3545` | Rot |
+| `#fd7e14` | Orange |
+| `#ffc107` | Gelb |
+
+Andere Werte erscheinen neutral grau, auch gültige Hexfarben wie `#ff0000`. Verwenden Sie einen Tabellenwert für die gewünschte Farbe.
+
+In eingebettetem Laravel sind die aufgelösten Schlüssel `env_name` und `env_color` in `config/waterline.php` maßgeblich. Eine veröffentlichte Konfiguration kann umgebungsbasierte Werte überschreiben. Erstellen Sie nach Änderungen den Konfigurationscache der Anwendung im normalen Deployment neu:
+
+```bash
+php artisan config:cache
+```
+
+Wenn das Banner von `.env` abweicht, prüfen Sie die aufgelöste Waterline-Konfiguration. Der Cache bleibt bis zur Neuerstellung wirksam. Aktualisieren Sie im eigenständigen Service-Modus die Waterline-Deployment-Umgebung und erstellen oder deployen Sie den Waterline-Container neu, damit er die Werte lädt. Dies sind Waterline-Anzeigeeinstellungen; wenden Sie sie auf den oben beschriebenen Waterline-Service an.
+
 ### Cloud Managed Waterline {#cloud-managed-waterline}
 
 Cloud-Kunden öffnen Cloud Managed Waterline über die Namespace-bezogene verwaltete Operatoroberfläche. Sie stellen Waterline, Server, PHP oder interne Endpunkte weder bereit noch konfigurieren sie diese und pflegen keine zweite Waterline-Anmeldung. Die obigen Anweisungen zu selbst gehostetem Image, `WATERLINE_*`, Servertoken, Datenbank und äußerer Authentifizierung gelten für diesen Weg nicht.

i18n/de/source-hashes.json

@@ -62,7 +62,7 @@
   "laravel-adoption.md": "978f2333bf5ce38ebc58619ca3f50a087572a3b0c28d52bc06843bc341010684",
   "mcp-workflows.md": "1c0b5bb7f2e5c7ca835dfdfa57bbe8f6624172c855f4e225057ac2377abf360e",
   "migration.md": "53659987d64f3fc66c935bed55ec4227689185a23970f31327773fa408f5cf22",
-  "monitoring.md": "598e74fe6839ddba8c0fec969946dc1286f59d01261f5c0c745f63a38e36bc10",
+  "monitoring.md": "f71d32f731ede9d489f1c5a17168fa932022a874ac61686bac7e4ac072007b20",
   "operator-operating-envelope.md": "c106e192b3716b8e2d14ffc84b3b2837b25792a7c3a9493d14dc6dd29ae9dee5",
   "platform-conformance.md": "2eec7eba9a65c010e03c4b2eb78afe4dddd6fd8170218b3194c49e3777124c91",
   "platform-protocol-specs.md": "ba9c69adfca7fb4a0dd982464b0ca69dd5a21de1e340edbe23b075ec0fb0c35c",

i18n/es/docusaurus-plugin-content-docs/current/monitoring.md

@@ -248,6 +248,36 @@ nativas. Cambiar el backend de Waterline no migra ni combina ejecuciones.
 | Una ruta del catálogo de servicios indica `backend_capability_unavailable` | El modo servicio no refleja el catálogo integrado de Waterline entre namespaces. Usa los endpoints y API nativos de servicios del servidor conectado. |
 | Falta una métrica personalizada en Waterline | Inspecciona el exportador del worker. Waterline informa de hechos operativos duraderos, no de métricas arbitrarias de procesos. |
 
+### Banner de entorno {#waterline-environment-banner}
+
+Distinga las pestañas de producción y otros entornos con el banner de Waterline. Estas variables funcionan en Laravel integrado y en modo servicio independiente:
+
+```dotenv
+WATERLINE_ENV_NAME=production
+WATERLINE_ENV_COLOR="#dc3545"
+```
+
+`WATERLINE_ENV_COLOR` selecciona una paleta fija compatible con CSP:
+
+| Valor aceptado | Color del banner |
+| --- | --- |
+| `#0d6efd` o `#2563eb` | Azul |
+| `#198754` o `#28a745` | Verde |
+| `#6f42c1` o `#7746ec` | Morado |
+| `#dc3545` | Rojo |
+| `#fd7e14` | Naranja |
+| `#ffc107` | Amarillo |
+
+Los demás valores se muestran en gris neutro, incluidos colores hex válidos como `#ff0000`. Use un valor de la tabla para obtener el color deseado.
+
+En Laravel integrado, los valores resueltos de `env_name` y `env_color` en `config/waterline.php` son los que mandan. La configuración publicada puede sobrescribir los valores basados en entorno. Tras modificarlos, reconstruya la caché de configuración de la aplicación mediante su despliegue habitual:
+
+```bash
+php artisan config:cache
+```
+
+Si el banner difiere de `.env`, inspeccione la configuración resuelta de Waterline. La caché sigue vigente hasta reconstruirla. En modo servicio independiente, actualice el entorno del despliegue de Waterline y vuelva a crear o desplegar su contenedor para cargar los nuevos valores. Son ajustes visuales de Waterline; aplíquelos al servicio Waterline descrito arriba.
+
 ### Cloud Managed Waterline {#cloud-managed-waterline}
 
 Los clientes abren Cloud Managed Waterline desde la interfaz gestionada de

i18n/es/source-hashes.json

@@ -62,7 +62,7 @@
   "laravel-adoption.md": "978f2333bf5ce38ebc58619ca3f50a087572a3b0c28d52bc06843bc341010684",
   "mcp-workflows.md": "1c0b5bb7f2e5c7ca835dfdfa57bbe8f6624172c855f4e225057ac2377abf360e",
   "migration.md": "53659987d64f3fc66c935bed55ec4227689185a23970f31327773fa408f5cf22",
-  "monitoring.md": "598e74fe6839ddba8c0fec969946dc1286f59d01261f5c0c745f63a38e36bc10",
+  "monitoring.md": "f71d32f731ede9d489f1c5a17168fa932022a874ac61686bac7e4ac072007b20",
   "operator-operating-envelope.md": "c106e192b3716b8e2d14ffc84b3b2837b25792a7c3a9493d14dc6dd29ae9dee5",
   "platform-conformance.md": "2eec7eba9a65c010e03c4b2eb78afe4dddd6fd8170218b3194c49e3777124c91",
   "platform-protocol-specs.md": "ba9c69adfca7fb4a0dd982464b0ca69dd5a21de1e340edbe23b075ec0fb0c35c",

i18n/fr/docusaurus-plugin-content-docs/current/monitoring.md

@@ -253,6 +253,36 @@ Changer le backend Waterline ne migre ni ne combine les exécutions.
 | Une route de catalogue de services signale `backend_capability_unavailable` | Le mode service ne reproduit pas le catalogue de services interespaces de noms embarqué de Waterline. Utilisez les routes et l'API natives du serveur connecté pour cette capacité. |
 | Une métrique personnalisée manque dans Waterline | Inspectez l'exportateur du worker. Waterline expose les faits durables d'exploitation, pas les métriques arbitraires des processus. |
 
+### Bandeau d’environnement {#waterline-environment-banner}
+
+Distinguez les onglets de production et hors production avec le bandeau Waterline. Ces variables fonctionnent en Laravel embarqué et en mode service autonome :
+
+```dotenv
+WATERLINE_ENV_NAME=production
+WATERLINE_ENV_COLOR="#dc3545"
+```
+
+`WATERLINE_ENV_COLOR` sélectionne une palette fixe compatible avec la CSP :
+
+| Valeur acceptée | Couleur du bandeau |
+| --- | --- |
+| `#0d6efd` ou `#2563eb` | Bleu |
+| `#198754` ou `#28a745` | Vert |
+| `#6f42c1` ou `#7746ec` | Violet |
+| `#dc3545` | Rouge |
+| `#fd7e14` | Orange |
+| `#ffc107` | Jaune |
+
+Les autres valeurs donnent un gris neutre, y compris des couleurs hexadécimales valides comme `#ff0000`. Utilisez une valeur du tableau pour la couleur souhaitée.
+
+En Laravel embarqué, les clés résolues `env_name` et `env_color` de `config/waterline.php` font autorité. La configuration publiée peut remplacer les valeurs issues de l’environnement. Après modification, reconstruisez le cache de configuration de l’application dans son déploiement habituel :
+
+```bash
+php artisan config:cache
+```
+
+Si le bandeau diffère de `.env`, inspectez la configuration résolue de Waterline : le cache reste effectif jusqu’à sa reconstruction. En mode service autonome, mettez à jour l’environnement du déploiement Waterline puis recréez ou redéployez son conteneur pour charger les valeurs. Ce sont des réglages d’affichage Waterline ; appliquez-les au service Waterline décrit plus haut.
+
 ### Cloud Managed Waterline {#cloud-managed-waterline}
 
 Les clients Cloud ouvrent Cloud Managed Waterline depuis l'interface opérateur

i18n/fr/source-hashes.json

@@ -62,7 +62,7 @@
   "laravel-adoption.md": "978f2333bf5ce38ebc58619ca3f50a087572a3b0c28d52bc06843bc341010684",
   "mcp-workflows.md": "1c0b5bb7f2e5c7ca835dfdfa57bbe8f6624172c855f4e225057ac2377abf360e",
   "migration.md": "53659987d64f3fc66c935bed55ec4227689185a23970f31327773fa408f5cf22",
-  "monitoring.md": "598e74fe6839ddba8c0fec969946dc1286f59d01261f5c0c745f63a38e36bc10",
+  "monitoring.md": "f71d32f731ede9d489f1c5a17168fa932022a874ac61686bac7e4ac072007b20",
   "operator-operating-envelope.md": "c106e192b3716b8e2d14ffc84b3b2837b25792a7c3a9493d14dc6dd29ae9dee5",
   "platform-conformance.md": "2eec7eba9a65c010e03c4b2eb78afe4dddd6fd8170218b3194c49e3777124c91",
   "platform-protocol-specs.md": "ba9c69adfca7fb4a0dd982464b0ca69dd5a21de1e340edbe23b075ec0fb0c35c",

i18n/ja/docusaurus-plugin-content-docs/current/monitoring.md

@@ -167,6 +167,36 @@ Waterline が表示するのは、設定した名前空間と接続先 Server 
 | サービスカタログルートが `backend_capability_unavailable` を報告する | サービスモードは組み込みの名前空間横断サービスカタログを複製しません。接続先 Server のネイティブサービスエンドポイントと API を使います。 |
 | Waterline にカスタムメトリクスがない | Worker のメトリクスエクスポーターを調査。Waterline は永続的な運用の事実を報告し、任意のプロセスメトリクスは扱いません。 |
 
+### 環境バナー {#waterline-environment-banner}
+
+Waterline の環境バナーで本番と非本番のタブを区別できます。以下の変数は組み込み Laravel と独立したサービスモードの両方で使えます。
+
+```dotenv
+WATERLINE_ENV_NAME=production
+WATERLINE_ENV_COLOR="#dc3545"
+```
+
+`WATERLINE_ENV_COLOR` は CSP に対応した固定パレットから色を選びます。
+
+| 受け付ける値 | バナーの色 |
+| --- | --- |
+| `#0d6efd` または `#2563eb` | 青 |
+| `#198754` または `#28a745` | 緑 |
+| `#6f42c1` または `#7746ec` | 紫 |
+| `#dc3545` | 赤 |
+| `#fd7e14` | オレンジ |
+| `#ffc107` | 黄 |
+
+それ以外の値は、`#ff0000` のような有効な十六進数色も含めてニュートラルな灰色になります。目的の色には表の値を使ってください。
+
+組み込み Laravel では `config/waterline.php` の解決済み `env_name` と `env_color` が優先されます。公開済みの設定は環境変数に基づく値を上書きできます。環境に基づく設定を変更したら、アプリケーションの通常のデプロイ手順で設定キャッシュを再構築してください。
+
+```bash
+php artisan config:cache
+```
+
+バナーが `.env` と異なる場合は Waterline の解決済み設定を確認します。再構築までキャッシュ値が適用されます。独立サービスモードでは Waterline のデプロイ環境を更新し、コンテナーを再作成または再デプロイして新しい値を読み込ませます。これらは Waterline の表示設定なので、前述の Waterline サービスに適用してください。
+
 ### Cloud Managed Waterline {#cloud-managed-waterline}
 
 Cloud 顧客は、名前空間単位のマネージド運用インターフェースから Cloud Managed Waterline を開きます。Waterline、Server、PHP、内部エンドポイントをデプロイ・設定せず、二つ目の Waterline ログインも管理しません。上記のセルフホストイメージ、`WATERLINE_*` 設定、Server トークン、データベース、入口認証の手順は適用されません。

i18n/ja/source-hashes.json

@@ -62,7 +62,7 @@
   "laravel-adoption.md": "978f2333bf5ce38ebc58619ca3f50a087572a3b0c28d52bc06843bc341010684",
   "mcp-workflows.md": "1c0b5bb7f2e5c7ca835dfdfa57bbe8f6624172c855f4e225057ac2377abf360e",
   "migration.md": "53659987d64f3fc66c935bed55ec4227689185a23970f31327773fa408f5cf22",
-  "monitoring.md": "598e74fe6839ddba8c0fec969946dc1286f59d01261f5c0c745f63a38e36bc10",
+  "monitoring.md": "f71d32f731ede9d489f1c5a17168fa932022a874ac61686bac7e4ac072007b20",
   "operator-operating-envelope.md": "c106e192b3716b8e2d14ffc84b3b2837b25792a7c3a9493d14dc6dd29ae9dee5",
   "platform-conformance.md": "2eec7eba9a65c010e03c4b2eb78afe4dddd6fd8170218b3194c49e3777124c91",
   "platform-protocol-specs.md": "ba9c69adfca7fb4a0dd982464b0ca69dd5a21de1e340edbe23b075ec0fb0c35c",

i18n/pt-BR/docusaurus-plugin-content-docs/current/monitoring.md

@@ -259,6 +259,36 @@ Mudar o backend do Waterline não migra nem combina execuções.
 | Uma rota de catálogo de serviços informa `backend_capability_unavailable` | O modo de serviço não replica o catálogo de serviços entre namespaces do Waterline embutido. Use os endpoints e a API nativos de serviços do servidor conectado para essa capacidade. |
 | Uma métrica personalizada não aparece no Waterline | Inspecione o exportador de métricas do worker. O Waterline informa fatos duráveis de operação, não métricas arbitrárias de processo. |
 
+### Banner de ambiente {#waterline-environment-banner}
+
+Identifique abas de produção e de outros ambientes com o banner do Waterline. Estas variáveis funcionam no Laravel incorporado e no modo serviço independente:
+
+```dotenv
+WATERLINE_ENV_NAME=production
+WATERLINE_ENV_COLOR="#dc3545"
+```
+
+`WATERLINE_ENV_COLOR` seleciona uma paleta fixa compatível com CSP:
+
+| Valor aceito | Cor do banner |
+| --- | --- |
+| `#0d6efd` ou `#2563eb` | Azul |
+| `#198754` ou `#28a745` | Verde |
+| `#6f42c1` ou `#7746ec` | Roxo |
+| `#dc3545` | Vermelho |
+| `#fd7e14` | Laranja |
+| `#ffc107` | Amarelo |
+
+Os demais valores aparecem em cinza neutro, inclusive cores hex válidas como `#ff0000`. Use um valor listado para obter a cor pretendida.
+
+No Laravel incorporado, os valores resolvidos de `env_name` e `env_color` em `config/waterline.php` são a fonte efetiva. A configuração publicada pode substituir os valores baseados no ambiente. Depois de alterá-los, reconstrua o cache de configuração da aplicação pelo processo normal de deploy:
+
+```bash
+php artisan config:cache
+```
+
+Se o banner diferir de `.env`, inspecione a configuração resolvida do Waterline. O cache continua valendo até ser reconstruído. No modo serviço independente, atualize o ambiente do deploy do Waterline e recrie ou faça novo deploy do contêiner para carregar os valores. São configurações visuais do Waterline; aplique-as ao serviço Waterline descrito acima.
+
 ### Cloud Managed Waterline {#cloud-managed-waterline}
 
 Clientes Cloud abrem Cloud Managed Waterline pela interface gerenciada de

i18n/pt-BR/source-hashes.json

@@ -62,7 +62,7 @@
   "laravel-adoption.md": "978f2333bf5ce38ebc58619ca3f50a087572a3b0c28d52bc06843bc341010684",
   "mcp-workflows.md": "1c0b5bb7f2e5c7ca835dfdfa57bbe8f6624172c855f4e225057ac2377abf360e",
   "migration.md": "53659987d64f3fc66c935bed55ec4227689185a23970f31327773fa408f5cf22",
-  "monitoring.md": "598e74fe6839ddba8c0fec969946dc1286f59d01261f5c0c745f63a38e36bc10",
+  "monitoring.md": "f71d32f731ede9d489f1c5a17168fa932022a874ac61686bac7e4ac072007b20",
   "operator-operating-envelope.md": "c106e192b3716b8e2d14ffc84b3b2837b25792a7c3a9493d14dc6dd29ae9dee5",
   "platform-conformance.md": "2eec7eba9a65c010e03c4b2eb78afe4dddd6fd8170218b3194c49e3777124c91",
   "platform-protocol-specs.md": "ba9c69adfca7fb4a0dd982464b0ca69dd5a21de1e340edbe23b075ec0fb0c35c",