@gravito/zenith 0.1.0-beta.1

package/Dockerfile.demo-worker

@@ -0,0 +1,29 @@
+# Use Bun official image
+FROM oven/bun:1.1.26 AS base
+WORKDIR /usr/src/app
+
+# ---- 1. Install Dependencies ----
+FROM base AS install
+COPY package.json bun.lock ./
+COPY packages/photon/package.json ./packages/photon/
+COPY packages/stream/package.json ./packages/stream/
+COPY packages/flux-console/package.json ./packages/flux-console/
+RUN bun install --frozen-lockfile
+
+# ---- 2. Copy Source ----
+FROM base AS build
+COPY --from=install /usr/src/app/node_modules ./node_modules
+COPY --from=install /usr/src/app/packages ./packages
+COPY . .
+
+# ---- 3. Runner ----
+FROM base AS release
+WORKDIR /usr/src/app
+COPY --from=build /usr/src/app ./
+
+# Env defaults
+ENV NODE_ENV=production
+
+# Start the demo worker
+# It uses the local packages/dist if available, but Bun can run TS directly
+CMD ["bun", "run", "packages/flux-console/scripts/demo-worker.ts"]

package/EVOLUTION_BLUEPRINT.md

@@ -0,0 +1,112 @@
+# Gravito Zenith Evolution Blueprint
+**Target**: Zenith v2.0 - The Universal Application Control Plane
+**Core Philosophy**: Lightweight, Redis-Native, Language-Agnostic.
+
+## 🧭 Strategic Vision
+
+We aim to evolve Zenith from a **Queue Manager** into a **Lightweight Application Control Plane**. We will absorb the best features from industry leaders (Laravel Pulse, Sidekiq, BullMQ) while strictly avoiding their architectural pitfalls (heavy deps, SQL locks, language coupling).
+
+---
+
+## 📅 Roadmap Structure
+
+### Phase 1: Deep Visibility (Queue Insights)
+**Focus**: Enhance the depth of information for the current Queue System.
+**Benchmarks**: Sidekiq, BullMQ.
+
+#### 1.1 Worker "X-Ray" Vision (The "Busy" State)
+-   **Concept**: Instead of just showing "Busy", show *what* the worker is doing.
+-   **Implementation**: Update Heartbeat Protocol to include `currentJobId` and `jobName`.
+-   **UI**: Workers table shows "Processing: Order #1024 (SendEmail)".
+-   **Benefit**: Instantly identify which job is hogging a worker.
+-   **Difference**: Unlike Sidekiq which uses expensive extensive locking, we use ephemeral keys.
+
+#### 1.2 Enhanced Payload Inspector
+-   **Concept**: Developer-friendly data inspection.
+-   **Implementation**:
+    -   Syntax-highlighted JSON viewer with folding.
+    -   "Copy as cURL" or "Copy to Clipboard" actions.
+    -   Display stack traces with click-to-open (if local) potential.
+-   **UX Rule**: Always lazy-load heavy payloads. Never fetch them in the list view.
+
+#### 1.3 Timeline Visualization (Gantt-lite)
+-   **Concept**: Visualize concurrency.
+-   **Implementation**: A canvas-based timeline showing job execution durations overlapping in time.
+-   **Benefit**: Spot resource contention or gaps in processing.
+
+---
+
+## Phase 2: System Pulse (Resource Monitoring)
+**Focus**: Lightweight APM (Application Performance Monitoring).
+**Benchmarks**: Laravel Pulse, PM2.
+
+#### 2.1 Gravito Pulse Protocol (GPP)
+-   **Concept**: A standardized JSON structure for services to report health.
+-   **Structure**: `pulse:{service}:{id}` (TTL 30s).
+-   **Metrics**: CPU%, RAM (RSS/Heap), Disk Usage, Uptime, Event Loop Lag.
+-   **Avoidance**: Do NOT store historical time-series data in SQL. Use Redis Lists/Streams with aggressive trimming (e.g., keep last 1 hour).
+
+#### 2.2 Grid Dashboard
+-   **Concept**: Customizable "Mission Control" view.
+-   **UI**: Drag-and-drop grid system.
+-   **Widgets**:
+    -   Host Health (CPU/RAM guages).
+    -   Queue Backlog (Sparklines).
+    -   Exception Rate (Counter).
+    -   Slowest Routes (List).
+
+#### 2.3 Cross-Language Recorders
+-   **Goal**: Provide simple SDKs.
+    -   `@gravito/recorder-node`: For Express/Hono/Nest.
+    -   `@gravito/recorder-php`: For Laravel/Symfony.
+    -   `@gravito/recorder-python`: For Django/FastAPI.
+
+---
+
+## Phase 3: Intelligent Operations (Proactive Ops)
+**Focus**: Alerting and Anomaly Detection.
+**Benchmarks**: New Relic (Lite), Oban.
+
+#### 3.1 Outlier Detection (The "Slow" & "Error" Trap)
+-   **Concept**: Only capture interesting data.
+-   **Logic**:
+    -   If `duration > threshold`: Push to `pulse:slow_jobs`.
+    -   If `status >= 500`: Push to `pulse:exceptions`.
+-   **Benefit**: Zero overhead for successful, fast requests.
+
+#### 3.2 Smart Alerting Engine
+-   **Concept**: "Don't spam me."
+-   **Features**:
+    -   **Thresholds**: "CPU > 90% for 5 minutes".
+    -   **Cooldown**: "Alert once per hour per rule".
+    -   **Channels**: Slack, Discord, Email, Webhook.
+
+---
+
+## 🎨 UI/UX Unification Strategy
+
+To prevent "Feature Bloat" (UI Clutter), we will enforce strict design rules:
+
+### 1. Navigation Hierarchy
+Refactor Sidebar into logical groups:
+-   **Dashboards** (Overview, System Pulse)
+-   **Queues** (Active, Waiting, Delayed, Failed)
+-   **Infrastructure** (Workers, Databases, Redis)
+-   **Settings** (Alerts, API Keys)
+
+### 2. Contextual Density
+-   **List View**: Minimal info (ID, Name, Status, Time).
+-   **Detail Panel**: Slide-over panel for deep inspection (Payloads, Stack Traces, Logs).
+-   **Avoidance**: Don't try to cram everything into the table rows.
+
+### 3. Unified Filters
+-   Create a shared "Filter Bar" component (Date Range, Status, Queue Name) that works consistently across Logs, Jobs, and Pulse views.
+
+---
+
+## ✅ Implementation Checklist (Next Steps)
+
+1.  **[ ] Protocol Definition**: Document `GPP` (Gravito Pulse Protocol).
+2.  **[ ] Backend Core**: Implement `SystemMonitor` service in Zenith.
+3.  **[ ] Frontend Core**: Create the `GridDashboard` component layout.
+4.  **[ ] Feature**: Implement `Worker X-Ray` (easiest win from Phase 1).

package/JOBINSPECTOR_SCROLL_FIX.md

@@ -0,0 +1,152 @@
+# JobInspector 滾動修復
+
+## 🐛 問題描述
+
+當佇列中有大量工作（例如 100+ 個）時，JobInspector 側邊欄會被撐得很高，導致：
+- 整個側邊欄超出螢幕高度
+- 無法看到底部的 "Dismiss" 按鈕
+- 需要滾動整個頁面才能查看所有內容
+- UX 體驗很差
+
+## ✅ 修復方案
+
+### 修改的 CSS 類別
+
+#### 1. 主容器 (`motion.div`)
+```tsx
+// 修改前
+className="bg-card border-l h-full w-full max-w-2xl shadow-2xl flex flex-col"
+
+// 修改後
+className="bg-card border-l h-screen max-h-screen w-full max-w-2xl shadow-2xl flex flex-col overflow-hidden"
+```
+
+**變更說明：**
+- `h-full` → `h-screen max-h-screen`: 明確限制高度為視窗高度
+- 新增 `overflow-hidden`: 防止內容溢出
+
+#### 2. 頂部標題區域
+```tsx
+// 修改前
+className="p-6 border-b flex justify-between items-center bg-muted/20"
+
+// 修改後
+className="p-6 border-b flex justify-between items-center bg-muted/20 flex-shrink-0"
+```
+
+**變更說明：**
+- 新增 `flex-shrink-0`: 防止標題區域被壓縮
+
+#### 3. 內容滾動區域
+```tsx
+// 修改前
+className="p-0 overflow-y-auto flex-1 bg-muted/5"
+
+// 修改後
+className="flex-1 overflow-y-auto bg-muted/5 min-h-0"
+```
+
+**變更說明：**
+- 移除 `p-0`（padding 由內部元素控制）
+- 新增 `min-h-0`: 允許 flex 子元素縮小到 0，確保滾動正常運作
+
+#### 4. 底部按鈕區域
+```tsx
+// 修改前
+className="p-4 border-t bg-card text-right"
+
+// 修改後
+className="p-4 border-t bg-card text-right flex-shrink-0"
+```
+
+**變更說明：**
+- 新增 `flex-shrink-0`: 防止按鈕區域被壓縮
+
+## 🎯 修復效果
+
+### 修復前
+```
+┌─────────────────────────────┐
+│ Header (標題區)              │ ← 正常
+├─────────────────────────────┤
+│ Job 1                       │
+│ Job 2                       │
+│ Job 3                       │
+│ ...                         │
+│ Job 98                      │
+│ Job 99                      │
+│ Job 100                     │ ← 超出螢幕
+├─────────────────────────────┤
+│ [Dismiss] 按鈕               │ ← 看不到
+└─────────────────────────────┘
+```
+
+### 修復後
+```
+┌─────────────────────────────┐
+│ Header (標題區)              │ ← 固定在頂部
+├─────────────────────────────┤
+│ Job 1                       │ ↕️
+│ Job 2                       │ ↕️
+│ Job 3                       │ ↕️ 可滾動區域
+│ ...                         │ ↕️
+│ Job 50                      │ ↕️
+├─────────────────────────────┤
+│ [Dismiss] 按鈕               │ ← 固定在底部
+└─────────────────────────────┘
+```
+
+## 📊 技術細節
+
+### Flexbox 佈局結構
+```
+motion.div (h-screen, flex flex-col, overflow-hidden)
+├─ Header (flex-shrink-0)          ← 不會被壓縮
+├─ Content (flex-1, overflow-y-auto, min-h-0) ← 可滾動，佔據剩餘空間
+└─ Footer (flex-shrink-0)          ← 不會被壓縮
+```
+
+### 關鍵 CSS 屬性
+
+1. **`h-screen max-h-screen`**: 限制容器高度為視窗高度
+2. **`overflow-hidden`**: 防止容器本身滾動
+3. **`flex-shrink-0`**: 防止 header 和 footer 被壓縮
+4. **`flex-1`**: 讓內容區域佔據所有剩餘空間
+5. **`overflow-y-auto`**: 只在內容區域啟用垂直滾動
+6. **`min-h-0`**: 允許 flex 子元素縮小（CSS flexbox 的特殊行為）
+
+## 🧪 測試驗證
+
+### 測試案例
+1. ✅ 打開有 100+ 工作的佇列
+2. ✅ 側邊欄高度固定為螢幕高度
+3. ✅ 工作列表可以滾動
+4. ✅ 頂部標題始終可見
+5. ✅ 底部 Dismiss 按鈕始終可見
+6. ✅ 滾動流暢，無卡頓
+
+### 測試步驟
+```bash
+# 1. 確保測試資料存在
+bun scripts/test-batch-operations.ts create
+
+# 2. 打開 Flux Console
+# http://localhost:3000
+
+# 3. 點擊 test-batch 佇列的 Inspect
+# 4. 確認可以看到頂部標題和底部按鈕
+# 5. 滾動工作列表，確認滾動流暢
+```
+
+## 📝 相關文件
+
+- `src/client/pages/QueuesPage.tsx` - JobInspector 元件
+- 修改行數: 255, 258, 294, 505
+
+## 🎉 總結
+
+這個修復確保了 JobInspector 在處理大量工作時：
+- ✅ 高度固定為螢幕高度
+- ✅ 內容區域可以獨立滾動
+- ✅ 頂部和底部區域始終可見
+- ✅ UX 體驗大幅改善

package/PULSE_IMPLEMENTATION_PLAN.md

@@ -0,0 +1,111 @@
+# Gravito Pulse Implementation Plan
+**Version**: 1.1.0 (Beta Targeted)
+**Status**: Active
+**Target**: Zenith v1.0 Beta
+
+This document outlines the implementation plan for the **System Pulse** and **Universal Queue Connector**, enabling Zenith to monitor not just Gravito Stream, but also Laravel, BullMQ, and other queue systems directly in the current Beta phase.
+
+---
+
+## 🏗 Architecture Specifications
+
+### 1. Redis Schema (Updated)
+
+| Key Pattern | Type | TTL | Description |
+| :--- | :--- | :--- | :--- |
+| `pulse:server:{app}:{id}` | `String` (JSON) | 30s | **Heartbeat**. System resources (CPU/RAM). |
+| `pulse:queues:{app}` | `String` (JSON) | 30s | **Queue Snapshot**. Metrics from external queues. |
+| `pulse:slow:{app}` | `Stream` | MaxLen 1000 | **Slow Logs**. Validated heavy requests. |
+
+### 2. Gravito Pulse Protocol (GPP) - Shared Types
+
+```typescript
+// System Heartbeat
+interface PulseHeartbeat {
+  // ... (Existing fields)
+}
+
+// Universal Queue Snapshot
+interface QueueSnapshot {
+  timestamp: number;
+  app: string;
+  queues: Array<{
+    name: string;
+    driver: 'gravito-stream' | 'laravel-horizon' | 'bullmq' | 'sqs' | 'other';
+    metrics: {
+      waiting: number;
+      active?: number | null; // Optional (some drivers can't count active)
+      delayed?: number;
+      failed?: number;
+    };
+    meta?: Record<string, any>;
+  }>;
+}
+```
+
+---
+
+## 📅 Implementation Phases (Beta Priority)
+
+### Phase 1: Foundation (Protocol & Node SDK)
+**Goal**: Define the standard so other languages can conform.
+
+- [ ] **Task 1.1: Create `packages/pulse-protocol`**
+    - Define TypeScript interfaces for Heartbeat AND QueueSnapshot.
+    - Export Redis key constants.
+
+- [ ] **Task 1.2: Create `packages/pulse-node`**
+    - Implement System Recorder (CPU/RAM).
+
+### Phase 2: Universal Queue Adapters (v1.0 Beta Target)
+**Goal**: Enable "One Dashboard, Any Queue".
+
+- [ ] **Task 2.1: Laravel Adapter Specification (Concept)**
+    - Target: `gravito/zenith-laravel` (Composer package).
+    - Logic: 
+        - Hook into Laravel Schedule.
+        - Run `Redis::llen` on queue lists or query `failed_jobs` table.
+        - Push JSON to `pulse:queues:{laravel_app}`.
+    - *Action*: Create a POC documentation/spec for PHP developers.
+
+- [ ] **Task 2.2: BullMQ Adapter (Node.js)**
+    - Create `packages/adapter-bullmq`.
+    - Wrapper that accepts a BullMQ queue instance and auto-reports metrics to Zenith.
+
+### Phase 3: Zenith Integration (Aggregated UI)
+**Goal**: Visualize mixed queue sources.
+
+- [ ] **Task 3.1: Backend Aggregation**
+    - `MonitorService` must now SCAN both `pulse:server:*` and `pulse:queues:*`.
+    - Stream consolidated data via SSE.
+
+- [ ] **Task 3.2: Unified Queue Dashboard**
+    - Update `QueuesPage` to support "External Queues".
+    - External queues might be "Read-Only" initially (Metrics only, no Retry controls yet).
+    - Add visuals to distinguish Gravito Queues vs. External Queues.
+
+---
+
+## 🔮 Future Roadmap (v2.0)
+
+### Phase 4: Full Application Monitoring (Pulse)
+**Goal**: Catch the "bad" requests and visualize deep application health.
+
+- [ ] **Task 4.1: Slow Request Interceptor**
+    - Add `httpMiddleware` to `pulse-node`.
+    - Tracks request start/end time.
+    - If > threshold (default 1s), XADD to `pulse:slow:{app}`.
+
+- [ ] **Task 4.2: Exception Tracking**
+    - Aggregated 5xx error tracking via ZSET.
+
+- [ ] **Task 4.3: Cross-Language SDKs**
+    - Python (Django/FastAPI) and Go Recorders.
+    - GPU Monitoring for AI workloads.
+
+
+---
+
+## ⚡ Development Guidelines for External Adapters
+1.  **Passive Reporting**: Adapters should strictly REPORT data. They should not rely on Zenith for commands in V1.
+2.  **Fault Tolerance**: If Redis is down, the adapter must not crash the main application.

package/QUICK_TEST_GUIDE.md

@@ -0,0 +1,72 @@
+# 🎯 Flux Console 統一測試指南
+
+## 🚀 快速開始
+
+我們已經將所有測試腳本整合為 `seed.ts` 與 `worker.ts`，以下是常用的測試流程。
+
+### 1. 初始化資料 (Seeding)
+
+根據測試需求選擇模式：
+
+```bash
+# 基本資料（Waiting, Delayed, Failed）
+bun scripts/seed.ts standard
+
+# 壓力測試（建立 15 個佇列，每個佇列有大量資料）
+bun scripts/seed.ts stress
+
+# 批次操作測試（專用大量資料）
+bun scripts/seed.ts batch
+
+# 註冊排程管理 (Cron Jobs)
+bun scripts/seed.ts cron
+
+# 懶人包：一次執行以上所有模式
+bun scripts/seed.ts all
+
+# 清理所有資料
+bun scripts/seed.ts cleanup
+```
+
+### 2. 啟動背景處理 (Workers)
+
+模擬工作正在被處理、成功或失敗的過程：
+
+```bash
+# 啟動預設佇列的處理
+bun scripts/worker.ts
+
+# 模擬高失敗率與處理延遲
+bun scripts/worker.ts orders,reports --fail=0.3 --delay=500
+```
+
+---
+
+## 🧪 核心測試情境
+
+### 測試 1：排程管理 (Schedules)
+1. 執行 `bun scripts/seed.ts cron`。
+2. 在 UI 點擊側邊欄的 **"Schedules"**。
+3. 檢查是否顯示 `cleanup-tmp`, `daily-report` 等排程。
+4. 點擊 "Run Now" 檢查工作是否立即進入 `system` 或 `reports` 佇列。
+
+### 測試 2：批次操作 (Batch Operations)
+1. 執行 `bun scripts/seed.ts batch`。
+2. 進入 `test-batch` 佇列。
+3. 使用 **Cmd+A** 全選，然後點擊 "Delete Selected"。
+4. 測試頁面底部的「刪除所有 X 個工作」警告橫幅。
+
+### 測試 3：排版與搜尋
+1. 執行 `bun scripts/seed.ts stress`。
+2. 檢查側邊欄的佇列列表是否正確收合/捲動。
+3. 使用 **Cmd+K** 開啟命令列，輸入 `billing` 跳轉至該佇列。
+
+---
+
+## 🧹 清理空間
+
+測試完成後，建議執行：
+```bash
+bun scripts/seed.ts cleanup
+```
+這會清除 Redis 中所有帶有 `queue:` 前綴的 Key，以及 Console 的日誌快取。

package/README.md

@@ -0,0 +1,33 @@
+# @gravito/flux-console
+
+Management and Monitoring UI for Gravito Stream.
+
+## Features
+
+- **Real-time Monitoring**: Throughput and error rates.
+- **Worker Health**: Live CPU and RAM metrics.
+- **Queue Management**: Pause/Resume queues, View Waiting/Delayed/Failed jobs.
+- **DLQ Operations**: Batch retry or clear failed jobs directly from the UI.
+- **Job Auditing & Search**: Permanent history via SQL (MySQL/SQLite) with global search.
+- **Operational Log Archiving**: Persistent storage for system events and worker activities with history search.
+- **Automated Alerting**: Slack notifications for failure spikes or backlog issues.
+- **Batch Actions**: Flush delayed jobs, purge queues, and bulk operations.
+- **Schedule Management**: Full UI for Cron jobs.
+- **Zero-Config**: Built-in SQLite support for local auditing without a DB server.
+
+## Development
+
+```bash
+# Start backend and frontend (proxy mode)
+bun run dev
+
+# Seed test data
+bun scripts/seed-data.ts
+
+# Start demo worker
+bun scripts/demo-worker.ts
+```
+
+## Technical Specification
+
+See [ARCHITECTURE.md](./ARCHITECTURE.md) and [DOCS_INTERNAL.md](./DOCS_INTERNAL.md) for implementation details.

package/ROADMAP.md

@@ -0,0 +1,85 @@
+# Gravito Zenith Roadmap (Control Plane)
+
+This document outlines the future development plan for **Gravito Zenith**, moving from a basic monitoring tool to a comprehensive polyglot control plane for any job processing system.
+
+## 🚀 High Priority (Immediate Next Steps)
+
+### 1. Polyglot & Framework Integration (P0)
+**Goal**: Official support for non-Node.js workers, making Zenith a universal dashboard.
+- **Tasks**:
+    - [x] **Protocol Specification**: Defined standard Redis structures for Heartbeat and Logs.
+    - [x] **Laravel Integration**: Blueprint for `ZenithServiceProvider` and `ZenithConnector` defined.
+    - [ ] **Go/Python SDK**: Create lightweight client libraries for other languages.
+
+### 2. Docker & Cloud-Native Deployment (P1)
+**Goal**: Enable "One-Click Deployment" for any environment (local, EC2, K8s).
+- **Current Blocker**: Local workspace dependencies (`workspace:*`) cause build failures in standard Docker contexts.
+- **Tasks**:
+- [x] Fix `Dockerfile` dependency resolution (via multi-stage builds).
+- [x] Create `docker-compose.yml` for a full stack setup (Console + Redis + Demo Worker).
+- [x] Implementation of Scheduled Jobs (Cron) Management.
+
+### 3. System Pulse Monitoring (Lightweight APM) (P0 - NEW)
+**Goal**: Application-Aware lightweight resource monitoring and alerting.
+**Philosophy**: "If you can connect to Redis, you are monitored." No extra agents, no Prometheus config.
+- **Features**:
+    - **Live Resource Cards**: CPU / RAM / Disk Usage per service (Node.js, PHP, Python).
+    - **Health Heartbeats**: Auto-discovery of active services via `pulse:{service}:{id}` keys.
+    - **Proactive Alerting**: Slack notifications for Disk Space < 10% or High CPU Load.
+    - **Protocol-Based**: Language-agnostic design (Gravito Pulse Protocol).
+
+
+### 3. History Persistence (SQL Archive) (Completed ✅)
+**Goal**: Store job history permanently for auditing and long-term analysis.
+- [x] Implement a `PersistenceAdapter` in `@gravito/stream`.
+- [x] Automatically archive completed/failed jobs to a SQL database.
+- [x] **Zero-Config (SQLite)**: Integrated support for local testing.
+- [x] **Time Travel Audit**: comprehensive UI for tracing job history.
+
+## ✨ Feature Enhancements (Mid-Term)
+
+### 4. Alerting & Notifications (Completed ✅)
+**Goal**: Proactive issue notification system.
+- [x] **AlertService**: Lightweight rules for failure spikes, backlog, and worker loss.
+- [x] **Cooldown Mechanism**: Prevents alerting storms.
+- [x] **Slack Integration**: Webhook support with test notification UI.
+- [x] **Real-time Monitoring**: Integrated directly into server metrics loop.
+
+### 5. Scheduled Jobs (Cron) Management (Completed ✅)
+**Goal**: UI-based management for recurring tasks.
+- [x] Dashboard to view all registered Cron jobs.
+- [x] Ability to "Trigger Now" manually.
+- [x] Ability to Pause/Resume (Delete/Register) specific Cron schedules.
+- [x] Real-time ticking via the Console server.
+
+### 6. Batch Operations (Completed ✅)
+**Goal**: Bulk management actions.
+- **Problem**: Can only retry/delete one job or "all" jobs. Hard to handle "the 50 jobs that failed due to the bug yesterday".
+- **Tasks**:
+    - [x] Multi-select checkboxes in job lists.
+    - [x] Bulk Retry / Bulk Delete.
+    - [x] Select All Matching Query (Delete/Retry ALL jobs of a type).
+    - [x] Confirmation dialogs with loading states.
+    - [x] Keyboard shortcuts (Ctrl+A, Escape).
+    - [x] Visual feedback and total count display.
+
+## 🔮 Enterprise Features (Long-Term)
+
+### 7. Role-Based Access Control (RBAC)
+**Goal**: Granular permission management for teams.
+- **Problem**: Single password for everyone. Risky for junior devs to have "Delete Queue" power.
+- **Features**:
+    - Roles: `Viewer` (Read-only), `Operator` (Retry/Pause), `Admin` (Delete/Purge).
+    - User Management system (potentially integrated with OAuth/SSO).
+
+### 8. Multi-Cluster Management
+**Goal**: Centralized control pane for multiple environments.
+- **Problem**: Need to open 3 different tabs for Dev, Staging, and Prop.
+- **Features**:
+    - Connection Switcher in the UI header.
+    - Unified view of multiple Redis instances.
+
+### 9. Enhanced Search (Indexer)
+**Goal**: Full-text search on Job Payloads.
+- **Problem**: Can only search by Job ID. Cannot search by "email: user@example.com".
+- **Solution**: Implement a lightweight search index (RedisSearch or external engine) to index payloads.