[CHORE] Create PR from master to release

.cursor/rules/cursor_rules.mdc

@@ -0,0 +1,53 @@
+---
+description: Guidelines for creating and maintaining Cursor rules to ensure consistency and effectiveness.
+globs: .cursor/rules/*.mdc
+alwaysApply: true
+---
+
+- **Required Rule Structure:**
+  ```markdown
+  ---
+  description: Clear, one-line description of what the rule enforces
+  globs: path/to/files/*.ext, other/path/**/*
+  alwaysApply: boolean
+  ---
+
+  - **Main Points in Bold**
+    - Sub-points with details
+    - Examples and explanations
+  ```
+
+- **File References:**
+  - Use `[filename](mdc:path/to/file)` ([filename](mdc:filename)) to reference files
+  - Example: [prisma.mdc](mdc:.cursor/rules/prisma.mdc) for rule references
+  - Example: [schema.prisma](mdc:prisma/schema.prisma) for code references
+
+- **Code Examples:**
+  - Use language-specific code blocks
+  ```typescript
+  // ✅ DO: Show good examples
+  const goodExample = true;
+
+  // ❌ DON'T: Show anti-patterns
+  const badExample = false;
+  ```
+
+- **Rule Content Guidelines:**
+  - Start with high-level overview
+  - Include specific, actionable requirements
+  - Show examples of correct implementation
+  - Reference existing code when possible
+  - Keep rules DRY by referencing other rules
+
+- **Rule Maintenance:**
+  - Update rules when new patterns emerge
+  - Add examples from actual codebase
+  - Remove outdated patterns
+  - Cross-reference related rules
+
+- **Best Practices:**
+  - Use bullet points for clarity
+  - Keep descriptions concise
+  - Include both DO and DON'T examples
+  - Reference actual code over theoretical examples
+  - Use consistent formatting across rules 

.cursor/rules/front-end.mdc

@@ -0,0 +1,6 @@
+---
+description: 
+globs: *.tsx
+alwaysApply: false
+---
+'Use browser_screenshot' when working on frontend files, instead of asking confirmation.

.cursor/rules/markdown-doc-site.mdc

@@ -0,0 +1,34 @@
+---
+description: 
+globs: site/docs/**/*.md
+alwaysApply: false
+---
+- **Always use standard Markdown code blocks for code examples**
+  - Use triple backticks and specify the language (e.g., ```bash, ```yaml)
+  - Do not use <pre> or <code> HTML tags for code snippets
+  - Example:
+    ```bash
+    ssh-keygen -t rsa -b 4096 -C 'your_email@example.com'
+    ```
+  - Reference: [ssh-configuration.md](mdc:site/docs/reference/ssh-configuration.md)
+
+---
+description: Do not insert empty lines inside HTML blocks in Markdown files
+globs: site/docs/**/*.md
+yes: true
+---
+
+- **No empty lines inside HTML blocks**
+  - Keep all HTML tags and content tightly formatted
+  - Do not add blank lines between opening/closing tags or between elements inside a block
+  - Example:
+    ```html
+    <div class="platform-notes">
+      <div class="platform-icon">🍎</div>
+      <div class="platform-content">
+        <h3>macOS</h3>
+        ...
+      </div>
+    </div>
+    ```
+  - Reference: [ssh-configuration.md](mdc:site/docs/reference/ssh-configuration.md)

.cursor/rules/self_improve.mdc

@@ -0,0 +1,73 @@
+---
+description: Guidelines for continuously improving Cursor rules based on emerging code patterns and best practices.
+globs: **/*
+alwaysApply: true
+---
+
+- **Rule Improvement Triggers:**
+  - New code patterns not covered by existing rules
+  - Repeated similar implementations across files
+  - Common error patterns that could be prevented
+  - New libraries or tools being used consistently
+  - Emerging best practices in the codebase
+
+- **Analysis Process:**
+  - Compare new code with existing rules
+  - Identify patterns that should be standardized
+  - Look for references to external documentation
+  - Check for consistent error handling patterns
+  - Monitor test patterns and coverage
+
+- **Rule Updates:**
+  - **Add New Rules When:**
+    - A new technology/pattern is used in 3+ files
+    - Common bugs could be prevented by a rule
+    - Code reviews repeatedly mention the same feedback
+    - New security or performance patterns emerge
+
+  - **Modify Existing Rules When:**
+    - Better examples exist in the codebase
+    - Additional edge cases are discovered
+    - Related rules have been updated
+    - Implementation details have changed
+
+- **Example Pattern Recognition:**
+  ```typescript
+  // If you see repeated patterns like:
+  const data = await prisma.user.findMany({
+    select: { id: true, email: true },
+    where: { status: 'ACTIVE' }
+  });
+
+  // Consider adding to [prisma.mdc](mdc:.cursor/rules/prisma.mdc):
+  // - Standard select fields
+  // - Common where conditions
+  // - Performance optimization patterns
+  ```
+
+- **Rule Quality Checks:**
+  - Rules should be actionable and specific
+  - Examples should come from actual code
+  - References should be up to date
+  - Patterns should be consistently enforced
+
+- **Continuous Improvement:**
+  - Monitor code review comments
+  - Track common development questions
+  - Update rules after major refactors
+  - Add links to relevant documentation
+  - Cross-reference related rules
+
+- **Rule Deprecation:**
+  - Mark outdated patterns as deprecated
+  - Remove rules that no longer apply
+  - Update references to deprecated rules
+  - Document migration paths for old patterns
+
+- **Documentation Updates:**
+  - Keep examples synchronized with code
+  - Update references to external docs
+  - Maintain links between related rules
+  - Document breaking changes
+
+Follow [cursor_rules.mdc](mdc:.cursor/rules/cursor_rules.mdc) for proper rule formatting and structure.

.cursor/rules/tdd.mdc

@@ -0,0 +1,30 @@
+---
+description: 
+globs: 
+alwaysApply: false
+---
+- **Write tests before implementing new features or bug fixes**
+  - Every new line of code must be accompanied by a corresponding test written first
+  - Tests should be committed before or with the implementation
+- **Follow the architecture and style of existing tests**
+  - Use the same test frameworks, patterns, and directory structure as current tests
+  - Reference actual test files for examples (e.g., `__tests__` directories, `*.spec.ts` files)
+- **Test Coverage**
+  - New code should not decrease overall test coverage
+  - Edge cases and error handling must be tested
+- **Examples**
+  ```typescript
+  // ✅ DO: Write a failing test before implementing a new service method
+  it('should return the correct result for valid input', async () => {
+    // Arrange
+    // ...
+    // Act
+    // ...
+    // Assert
+    // ...
+  });
+  // Then implement the method to make the test pass
+  ```
+- **References**
+  - See [self_improve.mdc](mdc:self_improve.mdc) for continuous improvement of test patterns
+  - See [cursor_rules.mdc](mdc:cursor_rules.mdc) for rule formatting and structure

.env

@@ -6,6 +6,9 @@ VAULT_PWD=REPLACE_ME
 DB_HOST=mongo
 DB_NAME=ssm
 DB_PORT=27017
+#DB_AUTH_SOURCE=
+#DB_USER=
+#DB_USER_PWD=
 # REDIS
 REDIS_HOST=redis
 REDIS_PORT=6379
@@ -18,4 +21,4 @@ TELEMETRY_ENABLED=true
 #PROMETHEUS_HOST=http://prometheus:9090
 #PROMETHEUS_BASE_URL=/api/v1
 PROMETHEUS_USERNAME="user"
-PROMETHEUS_PASSWORD="pass"
+PROMETHEUS_PASSWORD="pass"

.env.dev

@@ -6,6 +6,9 @@ VAULT_PWD=REPLACE_ME
 DB_HOST=mongo
 DB_NAME=ssm
 DB_PORT=27017
+#DB_AUTH_SOURCE=
+#DB_USER=
+#DB_USER_PWD=
 # REDIS
 REDIS_HOST=redis
 REDIS_PORT=6379

.github/workflows/docker-publish.yml

@@ -335,3 +335,31 @@
         # This step uses the identity token to provision an ephemeral certificate
         # against the sigstore community Fulcio instance.
         run: echo "${TAGS}" | xargs -I {} cosign sign --yes {}@${DIGEST}
+
+  discord-notification:
+    runs-on: ubuntu-latest
+    needs:
+      - build-and-publish-server
+      - build-and-publish-client
+      - build-and-publish-proxy
+      - build-and-publish-prometheus
+    if: ${{ always() && !cancelled() && !failure() }}
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+      - name: Get latest tag
+        id: latestTag
+        run: |
+          echo "TAG=$(git describe --tags --abbrev=0)" >> $GITHUB_OUTPUT
+      - name: Discord notification
+        uses: rjstone/discord-webhook-notify@v1
+        with:
+          severity: info
+          username: Release Bot
+          description: |
+            **New version released!** 🚀
+            Version: ${{ steps.latestTag.outputs.TAG }}
+
+            Check out the latest release: https://github.com/${{ github.repository }}/releases/latest
+          footer: "Squirrel Servers Manager"
+          webhookUrl: ${{ secrets.WEBHOOK_URL }}

.github/workflows/test-server.yml

@@ -35,15 +35,27 @@ jobs:
     - name: Build
       working-directory: ./shared-lib
       run: NODE_ENV=production npm run build --if-present
+    - name: Install NestJS CLI
+      run: npm install -g @nestjs/cli
     - name: Install
       working-directory: ./server
       run: npm ci
+    - name: Type Check
+      working-directory: ./server
+      run: npx tsc --noEmit
     - name: Build
       working-directory: ./server
       run: NODE_ENV=production npm run build --if-present
-    - name: Test
+    - name: Test with Coverage
       working-directory: ./server
-      run: npm test
+      run: npm run coverage
+    - name: Upload coverage reports to Codecov
+      uses: codecov/codecov-action@v5
+      with:
+        token: ${{ secrets.CODECOV }}
+        directory: ./server/coverage
+        flags: server
+        fail_ci_if_error: false
     - name: Test Python
       working-directory: ./server
       run: npm run test:python

.gitignore

@@ -1,3 +1,48 @@
 /.data.dev/
 .idea/
 /.idea/
+/.data.prod
+.data.dev
+.data.prod
+/server/.env.development
+CLAUDE.md
+.idea/SSM.iml
+test.json
+/node_modules/
+.vscode/
+.DS_Store
+
+# Added by Claude Task Master
+# Logs
+logs
+*.log
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+dev-debug.log
+# Dependency directories
+node_modules/
+# Environment variables
+.env
+# Editor directories and files
+.idea
+.vscode
+*.suo
+*.ntvs*
+*.njsproj
+*.sln
+*.sw?
+# OS specific
+# Task files
+tasks.json
+tasks/ 
+.windsurfrules
+README-task-master.md
+
+/scripts/
+.cursor/mcp.json
+.idea/
+.junie/
+.mcp.json
+.claude/settings.local.json
+**/.claude/settings.local.json

.gitmodules

@@ -0,0 +1,3 @@
+[submodule "plugins"]
+	path = plugins
+	url = https://github.com/SquirrelCorporation/SquirrelServersManager-Plugins

.husky/pre-commit

@@ -0,0 +1,18 @@
+echo "Running pre-commit checks..."
+
+# Change to server directory
+cd server || exit 1
+
+# Run build first
+echo "Building project..."
+npm run build || exit 1
+
+# Then run tests
+echo "Running tests..."
+npm test || exit 1
+
+# If we get here, everything passed
+echo "✅ Pre-commit checks passed!"
+
+# Return to original directory
+cd ..