Release/2.69.9

.ai/README.md

@@ -0,0 +1,124 @@
+# RedisInsight AI Development Rules
+
+This directory contains the **single source of truth** for AI-assisted development rules and workflows in RedisInsight. These rules are used by multiple AI coding assistants:
+
+- **Cursor** (via symlinks: `.cursor/rules/` and `.cursor/commands/`)
+- **Augment** (via symlink: `.augment/`)
+- **Windsurf** (via symlink: `.windsurfrules`)
+- **GitHub Copilot** (via file: `.github/copilot-instructions.md`)
+
+## MCP (Model Context Protocol) Setup
+
+AI tools can access external services (JIRA, Confluence, GitHub) via MCP configuration.
+
+### Initial Setup
+
+1. **Copy the example configuration:**
+
+   ```bash
+   cp env.mcp.example .env.mcp
+   ```
+
+2. **Get your Atlassian API token:**
+
+   - Go to: https://id.atlassian.com/manage-profile/security/api-tokens
+   - Create a classic token by pressing the first "Create Token" button
+   - Copy the token
+
+3. **Edit `.env.mcp` with your credentials:**
+
+4. **Verify your setup:**
+
+   **For Cursor users:**
+
+   - Restart Cursor to load the new MCP configuration
+   - Ask the AI: "Can you list all available MCP tools and test them?"
+   - The AI should be able to access JIRA, Confluence, GitHub, and other configured services
+
+   **For Augment users:**
+
+   ```bash
+   npx @augmentcode/auggie --mcp-config mcp.json "go over all my mcp tools and make sure they work as expected"
+   ```
+
+   **For GitHub Copilot users:**
+
+   - Note: GitHub Copilot does not currently support MCP integration
+   - MCP services (JIRA, Confluence, etc.) will not be available in Copilot
+
+### Available MCP Services
+
+The `mcp.json` file configures these services:
+
+- **github** - GitHub integration (issues, PRs, repository operations)
+- **memory** - Persistent context storage across sessions
+- **sequential-thinking** - Enhanced reasoning for complex tasks
+- **context-7** - Advanced context management
+- **atlassian** - JIRA (RI-XXX tickets) and Confluence integration
+
+## Structure
+
+```
+.ai/                                  # 🎯 Single source of truth
+├── README.md                         # Overview & quick reference
+├── rules/                            # Development standards (modular)
+│   ├── code-quality.md               # Linting, TypeScript standards
+│   ├── frontend.md                   # React, Redux, UI patterns
+│   ├── backend.md                    # NestJS, API patterns
+│   ├── testing.md                    # Testing standards
+│   ├── branches.md                   # Branch naming conventions
+│   ├── commits.md                    # Commit message guidelines
+│   └── pull-requests.md              # Pull request process
+└── commands/                         # AI workflow commands
+    ├── commit-message.md             # Commit message generation
+    └── pull-request-review.md        # PR review workflow
+
+# Symlinks (all AI tools read from .ai/)
+.cursor/
+  ├── rules/ -> ../.ai/rules/         # Cursor AI (rules)
+  └── commands/ -> ../.ai/commands/   # Cursor AI (commands)
+.augment/ -> .ai/                     # Augment AI
+.windsurfrules -> .ai/                # Windsurf AI
+.github/copilot-instructions.md       # GitHub Copilot
+```
+
+## Project Overview
+
+**RedisInsight** is a desktop application for Redis database management built with:
+
+- **Frontend**: React 18, TypeScript, Redux Toolkit, Elastic UI, Monaco Editor, Vite
+- **Backend**: NestJS, TypeScript, Node.js
+- **Desktop**: Electron for cross-platform distribution
+- **Testing**: Jest, Testing Library, Playwright
+
+**Architecture**:
+
+```
+redisinsight/
+├── ui/          # React frontend (Vite + TypeScript)
+├── api/         # NestJS backend (TypeScript)
+├── desktop/     # Electron main process
+└── tests/       # E2E tests (Playwright)
+```
+
+## Detailed Guidelines
+
+All detailed development standards, coding practices, and workflows are maintained in modular files:
+
+- **Code Quality Standards**: See `.ai/rules/code-quality.md`
+- **Frontend Patterns**: See `.ai/rules/frontend.md`
+- **Backend Patterns**: See `.ai/rules/backend.md`
+- **Testing Standards**: See `.ai/rules/testing.md`
+- **Branch Naming**: See `.ai/rules/branches.md`
+- **Commit Messages**: See `.ai/rules/commits.md`
+- **Pull Request Process**: See `.ai/rules/pull-requests.md`
+
+## Updating These Rules
+
+To update AI rules:
+
+1. **Edit files in `.ai/` only** (never edit symlinked files directly)
+2. Changes automatically propagate to all AI tools
+3. Commit changes to version control
+
+**Remember**: These rules exist to maintain code quality and consistency. Follow them, but also use good judgment.

.ai/commands/commit-message.md

@@ -0,0 +1,112 @@
+# Commit Message Generation
+
+Generate concise, meaningful commit messages following RedisInsight conventions.
+
+## Format
+
+```
+<type>(<scope>): <description>
+
+[optional body]
+
+References: #RI-XXX
+```
+
+## Types & Scopes
+
+**Types**: `feat`, `fix`, `refactor`, `test`, `docs`, `chore`, `perf`, `ci`
+
+**Scopes**: `api`, `ui`, `e2e`, `deps`
+
+## Rules
+
+**DO:**
+- ✅ Always include scope: `feat(api):`, `fix(ui):`
+- ✅ Use imperative mood: "add feature" not "added feature"
+- ✅ Start with lowercase after scope
+- ✅ Keep subject under 250 characters
+- ✅ Inspect all uncommitted files before generating
+
+**DON'T:**
+- ❌ Omit scope
+- ❌ Use past tense
+- ❌ Add period at end
+- ❌ Use multiple scopes (split into separate commits)
+
+## Examples
+
+```bash
+feat(ui): add user profile editing
+fix(api): resolve memory leak in connection pool
+refactor(api): extract validation logic
+test(e2e): add authentication tests
+chore(deps): upgrade React to 18.2
+```
+
+## Issue References
+
+**JIRA**: `References: #RI-123` or `Fixes #RI-123`
+**GitHub**: `Fixes #123` or `Closes #123`
+
+## Process
+
+1. Run `git status && git diff`
+2. Identify scope: API → `api`, UI → `ui`, Both → separate commits
+3. Identify type: New → `feat`, Bug → `fix`, Improvement → `refactor`
+4. Write description (what changed and why)
+5. Add issue reference in body
+
+## Multiple Scopes
+
+Split into separate commits:
+
+```bash
+# ✅ Good
+git commit -m "feat(api): add user endpoint
+
+References: #RI-123"
+
+git commit -m "feat(ui): add user interface
+
+References: #RI-123"
+
+# ❌ Bad
+git commit -m "feat(api,ui): add user feature"
+```
+
+## Output Format
+
+Present in copyable format:
+
+```markdown
+Based on the changes, here's your commit message:
+
+\`\`\`
+feat(api): add OAuth 2.0 authentication
+
+Implements OAuth flow with token management
+and refresh token support.
+
+References: #RI-123
+\`\`\`
+```
+
+If multiple scopes:
+
+```markdown
+Changes span multiple scopes. I recommend two commits:
+
+**Commit 1:**
+\`\`\`
+feat(api): add OAuth endpoints
+
+References: #RI-123
+\`\`\`
+
+**Commit 2:**
+\`\`\`
+feat(ui): add OAuth login interface
+
+References: #RI-123
+\`\`\`
+```