fix: use -p never shorthand for electron-builder

The --publish never format wasn't being parsed correctly. Using -p never shorthand instead.

.coderabbit.yaml

@@ -1,65 +0,0 @@
-# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json
-
-# CodeRabbit Configuration
-# Documentation: https://docs.coderabbit.ai/reference/configuration
-
-language: "en-US"
-
-reviews:
-  # Review profile: "chill" for fewer comments, "assertive" for more thorough feedback
-  profile: "assertive"
-
-  # Generate high-level summary in PR description
-  high_level_summary: true
-
-  # Automatic review settings
-  auto_review:
-    enabled: true
-    auto_incremental_review: true
-    # Target branches for review (in addition to default branch)
-    base_branches:
-      - develop
-      - "release/*"
-      - "hotfix/*"
-    # Skip review for PRs with these title keywords (case-insensitive)
-    ignore_title_keywords:
-      - "[WIP]"
-      - "WIP:"
-      - "DO NOT MERGE"
-    # Don't review draft PRs
-    drafts: false
-
-  # Path filters - exclude generated/vendor files
-  path_filters:
-    - "!**/node_modules/**"
-    - "!**/.venv/**"
-    - "!**/dist/**"
-    - "!**/build/**"
-    - "!**/*.lock"
-    - "!**/package-lock.json"
-    - "!**/*.min.js"
-    - "!**/*.min.css"
-
-  # Path-specific review instructions
-  path_instructions:
-    - path: "apps/backend/**/*.py"
-      instructions: |
-        Focus on Python best practices, type hints, and async patterns.
-        Check for proper error handling and security considerations.
-        Verify compatibility with Python 3.12+.
-    - path: "apps/frontend/**/*.{ts,tsx}"
-      instructions: |
-        Review React patterns and TypeScript type safety.
-        Check for proper state management and component composition.
-    - path: "tests/**"
-      instructions: |
-        Ensure tests are comprehensive and follow pytest conventions.
-        Check for proper mocking and test isolation.
-
-chat:
-  auto_reply: true
-
-knowledge_base:
-  opt_out: false
-  learnings:
-    scope: "auto"

.github/FUNDING.yml

@@ -1,3 +0,0 @@
-# These are supported funding model platforms
-
-github: AndyMik90

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -1,27 +1,75 @@
-name: 🐛 Bug Report
-description: Something isn't working
-labels: ["bug", "needs-triage"]
+name: Bug Report
+description: Report a bug or unexpected behavior
+labels: ["bug", "triage"]
 body:
-  - type: checkboxes
-    id: checklist
+  - type: markdown
     attributes:
-      label: Checklist
-      options:
-        - label: I searched existing issues and this hasn't been reported
-          required: true
+      value: |
+        Thanks for taking the time to report a bug! Please fill out the sections below.
+
+  - type: textarea
+    id: description
+    attributes:
+      label: Bug Description
+      description: A clear and concise description of the bug.
+      placeholder: What happened?
+    validations:
+      required: true
+
+  - type: textarea
+    id: expected
+    attributes:
+      label: Expected Behavior
+      description: What did you expect to happen?
+      placeholder: What should have happened?
+    validations:
+      required: true
+
+  - type: textarea
+    id: reproduce
+    attributes:
+      label: Steps to Reproduce
+      description: Steps to reproduce the behavior.
+      placeholder: |
+        1. Run command '...'
+        2. Click on '...'
+        3. See error
+    validations:
+      required: true
+
+  - type: textarea
+    id: logs
+    attributes:
+      label: Error Messages / Logs
+      description: If applicable, paste any error messages or logs.
+      render: shell
+
+  - type: textarea
+    id: screenshots
+    attributes:
+      label: Screenshots
+      description: If applicable, add screenshots to help explain the problem.
 
   - type: dropdown
-    id: area
+    id: component
     attributes:
-      label: Area
+      label: Component
+      description: Which part of Auto Claude is affected?
       options:
-        - Frontend
-        - Backend
-        - Fullstack
+        - Python Backend (auto-claude/)
+        - Electron UI (auto-claude-ui/)
+        - Both
         - Not sure
     validations:
       required: true
 
+  - type: input
+    id: version
+    attributes:
+      label: Auto Claude Version
+      description: What version are you running? (check package.json or git tag)
+      placeholder: "v2.0.1"
+
   - type: dropdown
     id: os
     attributes:
@@ -30,47 +78,26 @@ body:
         - macOS
         - Windows
         - Linux
+        - Other
     validations:
       required: true
 
   - type: input
-    id: version
+    id: python-version
     attributes:
-      label: Version
-      placeholder: "e.g., 2.5.5"
-    validations:
-      required: true
+      label: Python Version
+      description: Output of `python --version`
+      placeholder: "3.12.0"
+
+  - type: input
+    id: node-version
+    attributes:
+      label: Node.js Version (for UI issues)
+      description: Output of `node --version`
+      placeholder: "20.10.0"
 
   - type: textarea
-    id: description
+    id: additional
     attributes:
-      label: What happened?
-      placeholder: Describe the bug clearly and concisely. Include any error messages you encountered.
-    validations:
-      required: true
-
-  - type: textarea
-    id: steps
-    attributes:
-      label: Steps to reproduce
-      placeholder: |
-        1. Run command '...' or click on '...'
-        2. Observe behavior '...'
-        3. See error or unexpected result
-    validations:
-      required: true
-
-  - type: textarea
-    id: expected
-    attributes:
-      label: Expected behavior
-      placeholder: What did you expect to happen instead? Describe the correct behavior.
-    validations:
-      required: true
-
-  - type: textarea
-    id: logs
-    attributes:
-      label: Logs / Screenshots
-      description: Required for UI bugs. Attach relevant logs, screenshots, or error output.
-      render: shell
+      label: Additional Context
+      description: Any other context about the problem.

.github/ISSUE_TEMPLATE/config.yml

@@ -1,8 +1,8 @@
 blank_issues_enabled: false
 contact_links:
-  - name: 💡 Feature Request
+  - name: Questions & Discussions
     url: https://github.com/AndyMik90/Auto-Claude/discussions
-    about: Suggest new features in GitHub Discussions
-  - name: 💬 Discord Community
-    url: https://discord.gg/QhRnz9m5HE
-    about: Questions and discussions - join our Discord!
+    about: Ask questions and discuss ideas with the community
+  - name: Documentation
+    url: https://github.com/AndyMik90/Auto-Claude#readme
+    about: Check the documentation before opening an issue

.github/ISSUE_TEMPLATE/docs.yml

@@ -1,37 +0,0 @@
-name: 📚 Documentation
-description: Improvements or additions to documentation
-labels: ["documentation", "needs-triage", "help wanted"]
-body:
-  - type: dropdown
-    id: type
-    attributes:
-      label: Type
-      options:
-        - Missing documentation
-        - Incorrect/outdated info
-        - Improvement suggestion
-        - Typo/grammar fix
-    validations:
-      required: true
-
-  - type: input
-    id: location
-    attributes:
-      label: Location
-      description: Which file or page?
-      placeholder: "e.g., README.md or guides/setup.md"
-
-  - type: textarea
-    id: description
-    attributes:
-      label: Description
-      description: What needs to change?
-    validations:
-      required: true
-
-  - type: checkboxes
-    id: contribute
-    attributes:
-      label: Contribution
-      options:
-        - label: I'm willing to submit a PR for this

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,70 @@
+name: Feature Request
+description: Suggest a new feature or enhancement
+labels: ["enhancement", "triage"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for suggesting a feature! Please describe your idea below.
+
+  - type: textarea
+    id: problem
+    attributes:
+      label: Problem Statement
+      description: What problem does this feature solve? Is this related to a frustration?
+      placeholder: I'm always frustrated when...
+    validations:
+      required: true
+
+  - type: textarea
+    id: solution
+    attributes:
+      label: Proposed Solution
+      description: Describe the solution you'd like to see.
+      placeholder: I would like Auto Claude to...
+    validations:
+      required: true
+
+  - type: textarea
+    id: alternatives
+    attributes:
+      label: Alternatives Considered
+      description: Have you considered any alternative solutions or workarounds?
+      placeholder: I've tried...
+
+  - type: dropdown
+    id: component
+    attributes:
+      label: Component
+      description: Which part of Auto Claude would this affect?
+      options:
+        - Python Backend (auto-claude/)
+        - Electron UI (auto-claude-ui/)
+        - Both
+        - New component
+        - Not sure
+    validations:
+      required: true
+
+  - type: dropdown
+    id: priority
+    attributes:
+      label: How important is this feature to you?
+      options:
+        - Nice to have
+        - Important for my workflow
+        - Critical / Blocking my use
+
+  - type: checkboxes
+    id: contribution
+    attributes:
+      label: Contribution
+      description: Would you be willing to help implement this?
+      options:
+        - label: I'm willing to submit a PR for this feature
+
+  - type: textarea
+    id: additional
+    attributes:
+      label: Additional Context
+      description: Add any other context, mockups, or screenshots about the feature request.

.github/ISSUE_TEMPLATE/question.yml

@@ -1,61 +0,0 @@
-name: ❓ Question
-description: Needs clarification
-labels: ["question", "needs-triage"]
-body:
-  - type: markdown
-    attributes:
-      value: |
-        **Before asking:** Check [Discord](https://discord.gg/QhRnz9m5HE) - your question may already be answered there!
-
-  - type: checkboxes
-    id: checklist
-    attributes:
-      label: Checklist
-      options:
-        - label: I searched existing issues and Discord for similar questions
-          required: true
-
-  - type: dropdown
-    id: area
-    attributes:
-      label: Area
-      options:
-        - Setup/Installation
-        - Frontend
-        - Backend
-        - Configuration
-        - Other
-    validations:
-      required: true
-
-  - type: input
-    id: version
-    attributes:
-      label: Version
-      description: Which version are you using?
-      placeholder: "e.g., 2.7.1"
-    validations:
-      required: true
-
-  - type: textarea
-    id: question
-    attributes:
-      label: Question
-      placeholder: "Describe your question in detail..."
-    validations:
-      required: true
-
-  - type: textarea
-    id: context
-    attributes:
-      label: Context
-      description: What are you trying to achieve?
-    validations:
-      required: true
-
-  - type: textarea
-    id: attempts
-    attributes:
-      label: What have you already tried?
-      description: What steps have you taken to resolve this?
-      placeholder: "e.g., I tried reading the docs, searched for..."

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,76 +1,44 @@
-## Base Branch
+## Summary
 
-- [ ] This PR targets the `develop` branch (required for all feature/fix PRs)
-- [ ] This PR targets `main` (hotfix only - maintainers)
-
-## Description
-
-<!-- What does this PR do? 2-3 sentences -->
-
-## Related Issue
-
-Closes #
+<!-- Brief description of what this PR does -->
 
 ## Type of Change
 
-- [ ] 🐛 Bug fix
-- [ ] ✨ New feature
-- [ ] 📚 Documentation
-- [ ] ♻️ Refactor
-- [ ] 🧪 Test
+- [ ] Bug fix (non-breaking change that fixes an issue)
+- [ ] New feature (non-breaking change that adds functionality)
+- [ ] Breaking change (fix or feature that would cause existing functionality to change)
+- [ ] Documentation update
+- [ ] Refactoring (no functional changes)
+- [ ] Tests (adding or updating tests)
 
-## Area
+## Related Issues
 
-- [ ] Frontend
-- [ ] Backend
-- [ ] Fullstack
+<!-- Link any related issues: Fixes #123, Closes #456 -->
 
-## Commit Message Format
+## Changes Made
 
-Follow conventional commits: `<type>: <subject>`
+<!-- List the main changes in this PR -->
 
-**Types:** feat, fix, docs, style, refactor, test, chore
-
-**Example:** `feat: add user authentication system`
-
-## Checklist
-
-- [ ] I've synced with `develop` branch
-- [ ] I've tested my changes locally
-- [ ] I've followed the code principles (SOLID, DRY, KISS)
-- [ ] My PR is small and focused (< 400 lines ideally)
-
-## CI/Testing Requirements
-
-- [ ] All CI checks pass
-- [ ] All existing tests pass
-- [ ] New features include test coverage
-- [ ] Bug fixes include regression tests
+-
+-
+-
 
 ## Screenshots
 
-<!-- Required for UI changes. Delete if not applicable. -->
+<!-- If applicable, add screenshots for UI changes -->
 
-| Before | After |
-|--------|-------|
-|        |       |
+## Checklist
 
-## Feature Toggle
+- [ ] I have run `pre-commit run --all-files` and fixed any issues
+- [ ] I have added tests for my changes (if applicable)
+- [ ] All existing tests pass locally
+- [ ] I have updated documentation (if applicable)
+- [ ] My code follows the project's code style
 
-<!-- If feature is incomplete or experimental, how is it hidden from users? -->
-<!-- This ensures incomplete work can be merged without affecting production. -->
+## Testing
 
-- [ ] Behind localStorage flag: `use_feature_name`
-- [ ] Behind settings toggle
-- [ ] Behind environment variable/config
-- [ ] N/A - Feature is complete and ready for all users
+<!-- Describe how you tested these changes -->
 
-## Breaking Changes
+## Additional Notes
 
-<!-- Does this PR introduce breaking changes? If yes, describe what breaks and migration steps. -->
-<!-- Delete this section if not applicable. -->
-
-**Breaking:** Yes / No
-
-**Details:**
-<!-- What breaks? What do users/developers need to change? -->
+<!-- Any additional context or notes for reviewers -->

.github/dependabot.yml

@@ -1,37 +0,0 @@
-version: 2
-updates:
-  # Python dependencies
-  - package-ecosystem: pip
-    directory: /apps/backend
-    schedule:
-      interval: weekly
-    open-pull-requests-limit: 5
-    labels:
-      - dependencies
-      - python
-    commit-message:
-      prefix: "chore(deps)"
-
-  # npm dependencies
-  - package-ecosystem: npm
-    directory: /apps/frontend
-    schedule:
-      interval: weekly
-    open-pull-requests-limit: 5
-    labels:
-      - dependencies
-      - javascript
-    commit-message:
-      prefix: "chore(deps)"
-
-  # GitHub Actions
-  - package-ecosystem: github-actions
-    directory: /
-    schedule:
-      interval: weekly
-    open-pull-requests-limit: 5
-    labels:
-      - dependencies
-      - ci
-    commit-message:
-      prefix: "ci(deps)"

.github/workflows/beta-release.yml

@@ -1,629 +0,0 @@
-name: Beta Release
-
-# Manual trigger for beta releases from develop branch
-on:
-  workflow_dispatch:
-    inputs:
-      version:
-        description: 'Beta version (e.g., 2.8.0-beta.1)'
-        required: true
-        type: string
-      dry_run:
-        description: 'Test build without creating release'
-        required: false
-        default: false
-        type: boolean
-
-jobs:
-  validate-version:
-    name: Validate beta version format
-    runs-on: ubuntu-latest
-    steps:
-      - name: Validate version format
-        run: |
-          VERSION="${{ github.event.inputs.version }}"
-
-          # Check if version matches beta semver pattern
-          if [[ ! "$VERSION" =~ ^[0-9]+\.[0-9]+\.[0-9]+-(beta|alpha|rc)\.[0-9]+$ ]]; then
-            echo "::error::Invalid version format: $VERSION"
-            echo "Version must match pattern: X.Y.Z-beta.N (e.g., 2.8.0-beta.1)"
-            exit 1
-          fi
-
-          echo "Valid beta version: $VERSION"
-
-  create-tag:
-    name: Create beta tag
-    needs: validate-version
-    runs-on: ubuntu-latest
-    permissions:
-      contents: write
-    outputs:
-      version: ${{ github.event.inputs.version }}
-    steps:
-      - uses: actions/checkout@v4
-        with:
-          ref: develop
-
-      - name: Create and push tag
-        if: ${{ github.event.inputs.dry_run != 'true' }}
-        run: |
-          VERSION="${{ github.event.inputs.version }}"
-          git config user.name "github-actions[bot]"
-          git config user.email "github-actions[bot]@users.noreply.github.com"
-          git tag -a "v$VERSION" -m "Beta release v$VERSION"
-          git push origin "v$VERSION"
-          echo "Created tag v$VERSION"
-
-      - name: Create tag only (dry run)
-        if: ${{ github.event.inputs.dry_run == 'true' }}
-        run: |
-          VERSION="${{ github.event.inputs.version }}"
-          echo "DRY RUN: Would create tag v$VERSION"
-
-  # Intel build on Intel runner for native compilation
-  build-macos-intel:
-    needs: create-tag
-    runs-on: macos-15-intel
-    steps:
-      - uses: actions/checkout@v4
-        with:
-          # Use tag for real releases, develop branch for dry runs
-          ref: ${{ github.event.inputs.dry_run == 'true' && 'develop' || format('v{0}', needs.create-tag.outputs.version) }}
-
-      - name: Setup Python
-        uses: actions/setup-python@v5
-        with:
-          python-version: '3.11'
-
-      - name: Setup Node.js
-        uses: actions/setup-node@v4
-        with:
-          node-version: '24'
-
-      - name: Get npm cache directory
-        id: npm-cache
-        run: echo "dir=$(npm config get cache)" >> $GITHUB_OUTPUT
-
-      - uses: actions/cache@v4
-        with:
-          path: ${{ steps.npm-cache.outputs.dir }}
-          key: ${{ runner.os }}-npm-${{ hashFiles('**/package-lock.json') }}
-          restore-keys: ${{ runner.os }}-npm-
-
-      - name: Install dependencies
-        run: cd apps/frontend && npm ci
-
-      - name: Install Rust toolchain (for building native Python packages)
-        uses: dtolnay/rust-toolchain@stable
-
-      - name: Cache pip wheel cache (for compiled packages like real_ladybug)
-        uses: actions/cache@v4
-        with:
-          path: ~/Library/Caches/pip
-          key: pip-wheel-${{ runner.os }}-x64-${{ hashFiles('apps/backend/requirements.txt') }}
-          restore-keys: |
-            pip-wheel-${{ runner.os }}-x64-
-
-      - name: Cache bundled Python
-        uses: actions/cache@v4
-        with:
-          path: apps/frontend/python-runtime
-          key: python-bundle-${{ runner.os }}-x64-3.12.8-rust-${{ hashFiles('apps/backend/requirements.txt') }}
-          restore-keys: |
-            python-bundle-${{ runner.os }}-x64-3.12.8-rust-
-
-      - name: Build application
-        run: cd apps/frontend && npm run build
-        env:
-          SENTRY_DSN: ${{ secrets.SENTRY_DSN }}
-          SENTRY_TRACES_SAMPLE_RATE: ${{ secrets.SENTRY_TRACES_SAMPLE_RATE }}
-          SENTRY_PROFILES_SAMPLE_RATE: ${{ secrets.SENTRY_PROFILES_SAMPLE_RATE }}
-
-      - name: Package macOS (Intel)
-        run: |
-          VERSION="${{ needs.create-tag.outputs.version }}"
-          cd apps/frontend && npm run package:mac -- --x64 --config.extraMetadata.version="$VERSION"
-        env:
-          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-          CSC_LINK: ${{ secrets.MAC_CERTIFICATE }}
-          CSC_KEY_PASSWORD: ${{ secrets.MAC_CERTIFICATE_PASSWORD }}
-          SENTRY_DSN: ${{ secrets.SENTRY_DSN }}
-          SENTRY_TRACES_SAMPLE_RATE: ${{ secrets.SENTRY_TRACES_SAMPLE_RATE }}
-          SENTRY_PROFILES_SAMPLE_RATE: ${{ secrets.SENTRY_PROFILES_SAMPLE_RATE }}
-
-      - name: Notarize macOS Intel app
-        env:
-          APPLE_ID: ${{ secrets.APPLE_ID }}
-          APPLE_APP_SPECIFIC_PASSWORD: ${{ secrets.APPLE_APP_SPECIFIC_PASSWORD }}
-          APPLE_TEAM_ID: ${{ secrets.APPLE_TEAM_ID }}
-        run: |
-          if [ -z "$APPLE_ID" ]; then
-            echo "Skipping notarization: APPLE_ID not configured"
-            exit 0
-          fi
-          cd apps/frontend
-          for dmg in dist/*.dmg; do
-            echo "Notarizing $dmg..."
-            xcrun notarytool submit "$dmg" \
-              --apple-id "$APPLE_ID" \
-              --password "$APPLE_APP_SPECIFIC_PASSWORD" \
-              --team-id "$APPLE_TEAM_ID" \
-              --wait
-            xcrun stapler staple "$dmg"
-            echo "Successfully notarized and stapled $dmg"
-          done
-
-      - name: Upload artifacts
-        uses: actions/upload-artifact@v4
-        with:
-          name: macos-intel-builds
-          path: |
-            apps/frontend/dist/*.dmg
-            apps/frontend/dist/*.zip
-            apps/frontend/dist/*.yml
-
-  # Apple Silicon build on ARM64 runner for native compilation
-  build-macos-arm64:
-    needs: create-tag
-    runs-on: macos-15
-    steps:
-      - uses: actions/checkout@v4
-        with:
-          # Use tag for real releases, develop branch for dry runs
-          ref: ${{ github.event.inputs.dry_run == 'true' && 'develop' || format('v{0}', needs.create-tag.outputs.version) }}
-
-      - name: Setup Python
-        uses: actions/setup-python@v5
-        with:
-          python-version: '3.11'
-
-      - name: Setup Node.js
-        uses: actions/setup-node@v4
-        with:
-          node-version: '24'
-
-      - name: Get npm cache directory
-        id: npm-cache
-        run: echo "dir=$(npm config get cache)" >> $GITHUB_OUTPUT
-
-      - uses: actions/cache@v4
-        with:
-          path: ${{ steps.npm-cache.outputs.dir }}
-          key: ${{ runner.os }}-npm-${{ hashFiles('**/package-lock.json') }}
-          restore-keys: ${{ runner.os }}-npm-
-
-      - name: Install dependencies
-        run: cd apps/frontend && npm ci
-
-      - name: Cache pip wheel cache
-        uses: actions/cache@v4
-        with:
-          path: ~/Library/Caches/pip
-          key: pip-wheel-${{ runner.os }}-arm64-${{ hashFiles('apps/backend/requirements.txt') }}
-          restore-keys: |
-            pip-wheel-${{ runner.os }}-arm64-
-
-      - name: Cache bundled Python
-        uses: actions/cache@v4
-        with:
-          path: apps/frontend/python-runtime
-          key: python-bundle-${{ runner.os }}-arm64-3.12.8-${{ hashFiles('apps/backend/requirements.txt') }}
-          restore-keys: |
-            python-bundle-${{ runner.os }}-arm64-3.12.8-
-
-      - name: Build application
-        run: cd apps/frontend && npm run build
-        env:
-          SENTRY_DSN: ${{ secrets.SENTRY_DSN }}
-          SENTRY_TRACES_SAMPLE_RATE: ${{ secrets.SENTRY_TRACES_SAMPLE_RATE }}
-          SENTRY_PROFILES_SAMPLE_RATE: ${{ secrets.SENTRY_PROFILES_SAMPLE_RATE }}
-
-      - name: Package macOS (Apple Silicon)
-        run: |
-          VERSION="${{ needs.create-tag.outputs.version }}"
-          cd apps/frontend && npm run package:mac -- --arm64 --config.extraMetadata.version="$VERSION"
-        env:
-          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-          CSC_LINK: ${{ secrets.MAC_CERTIFICATE }}
-          CSC_KEY_PASSWORD: ${{ secrets.MAC_CERTIFICATE_PASSWORD }}
-          SENTRY_DSN: ${{ secrets.SENTRY_DSN }}
-          SENTRY_TRACES_SAMPLE_RATE: ${{ secrets.SENTRY_TRACES_SAMPLE_RATE }}
-          SENTRY_PROFILES_SAMPLE_RATE: ${{ secrets.SENTRY_PROFILES_SAMPLE_RATE }}
-
-      - name: Notarize macOS ARM64 app
-        env:
-          APPLE_ID: ${{ secrets.APPLE_ID }}
-          APPLE_APP_SPECIFIC_PASSWORD: ${{ secrets.APPLE_APP_SPECIFIC_PASSWORD }}
-          APPLE_TEAM_ID: ${{ secrets.APPLE_TEAM_ID }}
-        run: |
-          if [ -z "$APPLE_ID" ]; then
-            echo "Skipping notarization: APPLE_ID not configured"
-            exit 0
-          fi
-          cd apps/frontend
-          for dmg in dist/*.dmg; do
-            echo "Notarizing $dmg..."
-            xcrun notarytool submit "$dmg" \
-              --apple-id "$APPLE_ID" \
-              --password "$APPLE_APP_SPECIFIC_PASSWORD" \
-              --team-id "$APPLE_TEAM_ID" \
-              --wait
-            xcrun stapler staple "$dmg"
-            echo "Successfully notarized and stapled $dmg"
-          done
-
-      - name: Upload artifacts
-        uses: actions/upload-artifact@v4
-        with:
-          name: macos-arm64-builds
-          path: |
-            apps/frontend/dist/*.dmg
-            apps/frontend/dist/*.zip
-            apps/frontend/dist/*.yml
-
-  build-windows:
-    needs: create-tag
-    runs-on: windows-latest
-    permissions:
-      id-token: write  # Required for OIDC authentication with Azure
-      contents: read
-    env:
-      # Job-level env so AZURE_CLIENT_ID is available for step-level if conditions
-      AZURE_CLIENT_ID: ${{ secrets.AZURE_CLIENT_ID }}
-    steps:
-      - uses: actions/checkout@v4
-        with:
-          # Use tag for real releases, develop branch for dry runs
-          ref: ${{ github.event.inputs.dry_run == 'true' && 'develop' || format('v{0}', needs.create-tag.outputs.version) }}
-
-      - name: Setup Python
-        uses: actions/setup-python@v5
-        with:
-          python-version: '3.11'
-
-      - name: Setup Node.js
-        uses: actions/setup-node@v4
-        with:
-          node-version: '24'
-
-      - name: Get npm cache directory
-        id: npm-cache
-        shell: bash
-        run: echo "dir=$(npm config get cache)" >> $GITHUB_OUTPUT
-
-      - uses: actions/cache@v4
-        with:
-          path: ${{ steps.npm-cache.outputs.dir }}
-          key: ${{ runner.os }}-npm-${{ hashFiles('**/package-lock.json') }}
-          restore-keys: ${{ runner.os }}-npm-
-
-      - name: Install dependencies
-        run: cd apps/frontend && npm ci
-
-      - name: Cache pip wheel cache
-        uses: actions/cache@v4
-        with:
-          path: ~\AppData\Local\pip\Cache
-          key: pip-wheel-${{ runner.os }}-x64-${{ hashFiles('apps/backend/requirements.txt') }}
-          restore-keys: |
-            pip-wheel-${{ runner.os }}-x64-
-
-      - name: Cache bundled Python
-        uses: actions/cache@v4
-        with:
-          path: apps/frontend/python-runtime
-          key: python-bundle-${{ runner.os }}-x64-3.12.8-${{ hashFiles('apps/backend/requirements.txt') }}
-          restore-keys: |
-            python-bundle-${{ runner.os }}-x64-3.12.8-
-
-      - name: Build application
-        run: cd apps/frontend && npm run build
-        env:
-          SENTRY_DSN: ${{ secrets.SENTRY_DSN }}
-          SENTRY_TRACES_SAMPLE_RATE: ${{ secrets.SENTRY_TRACES_SAMPLE_RATE }}
-          SENTRY_PROFILES_SAMPLE_RATE: ${{ secrets.SENTRY_PROFILES_SAMPLE_RATE }}
-
-      - name: Package Windows
-        shell: bash
-        run: |
-          VERSION="${{ needs.create-tag.outputs.version }}"
-          cd apps/frontend && npm run package:win -- --config.extraMetadata.version="$VERSION"
-        env:
-          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-          # Disable electron-builder's built-in signing (we use Azure Trusted Signing instead)
-          CSC_IDENTITY_AUTO_DISCOVERY: false
-          SENTRY_DSN: ${{ secrets.SENTRY_DSN }}
-          SENTRY_TRACES_SAMPLE_RATE: ${{ secrets.SENTRY_TRACES_SAMPLE_RATE }}
-          SENTRY_PROFILES_SAMPLE_RATE: ${{ secrets.SENTRY_PROFILES_SAMPLE_RATE }}
-
-      - name: Azure Login (OIDC)
-        if: env.AZURE_CLIENT_ID != ''
-        uses: azure/login@v2
-        with:
-          client-id: ${{ secrets.AZURE_CLIENT_ID }}
-          tenant-id: ${{ secrets.AZURE_TENANT_ID }}
-          subscription-id: ${{ secrets.AZURE_SUBSCRIPTION_ID }}
-
-      - name: Sign Windows executable with Azure Trusted Signing
-        if: env.AZURE_CLIENT_ID != ''
-        uses: azure/trusted-signing-action@v0.5.11
-        with:
-          endpoint: https://neu.codesigning.azure.net/
-          trusted-signing-account-name: ${{ secrets.AZURE_SIGNING_ACCOUNT }}
-          certificate-profile-name: ${{ secrets.AZURE_CERTIFICATE_PROFILE }}
-          files-folder: apps/frontend/dist
-          files-folder-filter: exe
-          file-digest: SHA256
-          timestamp-rfc3161: http://timestamp.acs.microsoft.com
-          timestamp-digest: SHA256
-
-      - name: Verify Windows executable is signed
-        if: env.AZURE_CLIENT_ID != ''
-        shell: pwsh
-        run: |
-          cd apps/frontend/dist
-          $exeFile = Get-ChildItem -Filter "*.exe" | Select-Object -First 1
-          if ($exeFile) {
-            Write-Host "Verifying signature on $($exeFile.Name)..."
-            $sig = Get-AuthenticodeSignature -FilePath $exeFile.FullName
-            if ($sig.Status -ne 'Valid') {
-              Write-Host "::error::Signature verification failed: $($sig.Status)"
-              Write-Host "::error::Status Message: $($sig.StatusMessage)"
-              exit 1
-            }
-            Write-Host "✅ Signature verified successfully"
-            Write-Host "  Subject: $($sig.SignerCertificate.Subject)"
-            Write-Host "  Issuer: $($sig.SignerCertificate.Issuer)"
-            Write-Host "  Thumbprint: $($sig.SignerCertificate.Thumbprint)"
-          } else {
-            Write-Host "::error::No .exe file found to verify"
-            exit 1
-          }
-
-      - name: Regenerate checksums after signing
-        if: env.AZURE_CLIENT_ID != ''
-        shell: pwsh
-        run: |
-          $ErrorActionPreference = "Stop"
-          cd apps/frontend/dist
-
-          # Find the installer exe (electron-builder names it with "Setup" or just the app name)
-          # electron-builder produces one installer exe per build
-          $exeFiles = Get-ChildItem -Filter "*.exe"
-          if ($exeFiles.Count -eq 0) {
-            Write-Host "::error::No .exe files found in dist folder"
-            exit 1
-          }
-
-          Write-Host "Found $($exeFiles.Count) exe file(s): $($exeFiles.Name -join ', ')"
-
-          $ymlFile = "latest.yml"
-          if (-not (Test-Path $ymlFile)) {
-            Write-Host "::error::$ymlFile not found - cannot update checksums"
-            exit 1
-          }
-
-          $content = Get-Content $ymlFile -Raw
-          $originalContent = $content
-
-          # Process each exe file and update its hash in latest.yml
-          foreach ($exeFile in $exeFiles) {
-            Write-Host "Processing $($exeFile.Name)..."
-
-            # Compute SHA512 hash and convert to base64 (electron-builder format)
-            $bytes = [System.IO.File]::ReadAllBytes($exeFile.FullName)
-            $sha512 = [System.Security.Cryptography.SHA512]::Create()
-            $hashBytes = $sha512.ComputeHash($bytes)
-            $hash = [System.Convert]::ToBase64String($hashBytes)
-            $size = $exeFile.Length
-
-            Write-Host "  Hash: $hash"
-            Write-Host "  Size: $size"
-          }
-
-          # For electron-builder, latest.yml has a single file entry for the installer
-          # Update the sha512 and size for the primary exe (first one, typically the installer)
-          $primaryExe = $exeFiles | Select-Object -First 1
-          $bytes = [System.IO.File]::ReadAllBytes($primaryExe.FullName)
-          $sha512 = [System.Security.Cryptography.SHA512]::Create()
-          $hashBytes = $sha512.ComputeHash($bytes)
-          $hash = [System.Convert]::ToBase64String($hashBytes)
-          $size = $primaryExe.Length
-
-          # Update sha512 hash (base64 pattern: alphanumeric, +, /, =)
-          $content = $content -replace 'sha512: [A-Za-z0-9+/=]+', "sha512: $hash"
-          # Update size
-          $content = $content -replace 'size: \d+', "size: $size"
-
-          if ($content -eq $originalContent) {
-            Write-Host "::error::Checksum replacement failed - content unchanged. Check if latest.yml format has changed."
-            exit 1
-          }
-
-          Set-Content -Path $ymlFile -Value $content -NoNewline
-          Write-Host "✅ Updated $ymlFile with new base64 hash and size for $($primaryExe.Name)"
-
-      - name: Skip signing notice
-        if: env.AZURE_CLIENT_ID == ''
-        run: echo "::warning::Windows signing skipped - AZURE_CLIENT_ID not configured. The .exe will be unsigned."
-
-      - name: Upload artifacts
-        uses: actions/upload-artifact@v4
-        with:
-          name: windows-builds
-          path: |
-            apps/frontend/dist/*.exe
-            apps/frontend/dist/*.yml
-
-  build-linux:
-    needs: create-tag
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-        with:
-          # Use tag for real releases, develop branch for dry runs
-          ref: ${{ github.event.inputs.dry_run == 'true' && 'develop' || format('v{0}', needs.create-tag.outputs.version) }}
-
-      - name: Setup Python
-        uses: actions/setup-python@v5
-        with:
-          python-version: '3.11'
-
-      - name: Setup Node.js
-        uses: actions/setup-node@v4
-        with:
-          node-version: '24'
-
-      - name: Get npm cache directory
-        id: npm-cache
-        run: echo "dir=$(npm config get cache)" >> $GITHUB_OUTPUT
-
-      - uses: actions/cache@v4
-        with:
-          path: ${{ steps.npm-cache.outputs.dir }}
-          key: ${{ runner.os }}-npm-${{ hashFiles('**/package-lock.json') }}
-          restore-keys: ${{ runner.os }}-npm-
-
-      - name: Install dependencies
-        run: cd apps/frontend && npm ci
-
-      - name: Setup Flatpak
-        run: |
-          set -e
-          sudo apt-get update
-          sudo apt-get install -y flatpak flatpak-builder
-          flatpak remote-add --user --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepo
-          flatpak install -y --user flathub org.freedesktop.Platform//25.08 org.freedesktop.Sdk//25.08
-          flatpak install -y --user flathub org.electronjs.Electron2.BaseApp//25.08
-
-      - name: Cache pip wheel cache
-        uses: actions/cache@v4
-        with:
-          path: ~/.cache/pip
-          key: pip-wheel-${{ runner.os }}-x64-${{ hashFiles('apps/backend/requirements.txt') }}
-          restore-keys: |
-            pip-wheel-${{ runner.os }}-x64-
-
-      - name: Cache bundled Python
-        uses: actions/cache@v4
-        with:
-          path: apps/frontend/python-runtime
-          key: python-bundle-${{ runner.os }}-x64-3.12.8-${{ hashFiles('apps/backend/requirements.txt') }}
-          restore-keys: |
-            python-bundle-${{ runner.os }}-x64-3.12.8-
-
-      - name: Build application
-        run: cd apps/frontend && npm run build
-        env:
-          SENTRY_DSN: ${{ secrets.SENTRY_DSN }}
-          SENTRY_TRACES_SAMPLE_RATE: ${{ secrets.SENTRY_TRACES_SAMPLE_RATE }}
-          SENTRY_PROFILES_SAMPLE_RATE: ${{ secrets.SENTRY_PROFILES_SAMPLE_RATE }}
-
-      - name: Package Linux
-        run: |
-          VERSION="${{ needs.create-tag.outputs.version }}"
-          cd apps/frontend && npm run package:linux -- --config.extraMetadata.version="$VERSION"
-        env:
-          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-          SENTRY_DSN: ${{ secrets.SENTRY_DSN }}
-          SENTRY_TRACES_SAMPLE_RATE: ${{ secrets.SENTRY_TRACES_SAMPLE_RATE }}
-          SENTRY_PROFILES_SAMPLE_RATE: ${{ secrets.SENTRY_PROFILES_SAMPLE_RATE }}
-
-      - name: Upload artifacts
-        uses: actions/upload-artifact@v4
-        with:
-          name: linux-builds
-          path: |
-            apps/frontend/dist/*.AppImage
-            apps/frontend/dist/*.deb
-            apps/frontend/dist/*.flatpak
-            apps/frontend/dist/*.yml
-
-  create-release:
-    needs: [create-tag, build-macos-intel, build-macos-arm64, build-windows, build-linux]
-    runs-on: ubuntu-latest
-    if: ${{ github.event.inputs.dry_run != 'true' }}
-    permissions:
-      contents: write
-    steps:
-      - uses: actions/checkout@v4
-        with:
-          ref: v${{ needs.create-tag.outputs.version }}
-          fetch-depth: 0
-
-      - name: Download all artifacts
-        uses: actions/download-artifact@v4
-        with:
-          path: dist
-
-      - name: Flatten and validate artifacts
-        run: |
-          mkdir -p release-assets
-          find dist -type f \( -name "*.dmg" -o -name "*.zip" -o -name "*.exe" -o -name "*.AppImage" -o -name "*.deb" -o -name "*.flatpak" -o -name "*.yml" \) -exec cp {} release-assets/ \;
-
-          # Validate that at least one artifact was copied
-          artifact_count=$(find release-assets -type f \( -name "*.dmg" -o -name "*.zip" -o -name "*.exe" -o -name "*.AppImage" -o -name "*.deb" -o -name "*.flatpak" \) | wc -l)
-          if [ "$artifact_count" -eq 0 ]; then
-            echo "::error::No build artifacts found! Expected .dmg, .zip, .exe, .AppImage, .deb, or .flatpak files."
-            exit 1
-          fi
-
-          echo "Found $artifact_count artifact(s):"
-          ls -la release-assets/
-
-      - name: Generate checksums
-        run: |
-          cd release-assets
-          sha256sum ./* > checksums.sha256
-          cat checksums.sha256
-
-      - name: Create Beta Release
-        uses: softprops/action-gh-release@v2
-        with:
-          tag_name: v${{ needs.create-tag.outputs.version }}
-          name: v${{ needs.create-tag.outputs.version }} (Beta)
-          body: |
-            ## Beta Release v${{ needs.create-tag.outputs.version }}
-
-            This is a **beta release** for testing new features. It may contain bugs or incomplete functionality.
-
-            ### How to opt-in to beta updates
-            1. Open Auto Claude
-            2. Go to Settings > Updates
-            3. Enable "Beta Updates" toggle
-
-            ### Reporting Issues
-            Please report any issues at https://github.com/AndyMik90/Auto-Claude/issues
-
-            ---
-
-            **Full Changelog**: https://github.com/${{ github.repository }}/compare/main...v${{ needs.create-tag.outputs.version }}
-          files: release-assets/*
-          draft: false
-          prerelease: true
-        env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-
-  dry-run-summary:
-    needs: [create-tag, build-macos-intel, build-macos-arm64, build-windows, build-linux]
-    runs-on: ubuntu-latest
-    if: ${{ github.event.inputs.dry_run == 'true' }}
-    steps:
-      - name: Download all artifacts
-        uses: actions/download-artifact@v4
-        with:
-          path: dist
-
-      - name: Dry run summary
-        run: |
-          echo "## Beta Release Dry Run Complete" >> $GITHUB_STEP_SUMMARY
-          echo "" >> $GITHUB_STEP_SUMMARY
-          echo "**Version:** ${{ needs.create-tag.outputs.version }}" >> $GITHUB_STEP_SUMMARY
-          echo "" >> $GITHUB_STEP_SUMMARY
-          echo "Build artifacts created successfully:" >> $GITHUB_STEP_SUMMARY
-          echo "\`\`\`" >> $GITHUB_STEP_SUMMARY
-          find dist -type f \( -name "*.dmg" -o -name "*.zip" -o -name "*.exe" -o -name "*.AppImage" -o -name "*.deb" -o -name "*.flatpak" \) >> $GITHUB_STEP_SUMMARY
-          echo "\`\`\`" >> $GITHUB_STEP_SUMMARY
-          echo "" >> $GITHUB_STEP_SUMMARY
-          echo "To create a real release, run this workflow again with dry_run unchecked." >> $GITHUB_STEP_SUMMARY

.github/workflows/build-prebuilds.yml

@@ -32,17 +32,22 @@ jobs:
       - name: Setup Node.js
         uses: actions/setup-node@v4
         with:
-          node-version: '24'
+          node-version: '20'
+
+      - name: Setup pnpm
+        uses: pnpm/action-setup@v4
+        with:
+          version: 9
 
       - name: Install Visual Studio Build Tools
         uses: microsoft/setup-msbuild@v2
 
       - name: Install node-pty and rebuild for Electron
-        working-directory: apps/frontend
+        working-directory: auto-claude-ui
         shell: pwsh
         run: |
           # Install only node-pty
-          npm install node-pty@1.1.0-beta42
+          pnpm add node-pty@1.1.0-beta42
 
           # Get Electron ABI version
           $electronAbi = (npx electron-abi $env:ELECTRON_VERSION)
@@ -52,7 +57,7 @@ jobs:
           npx @electron/rebuild --version $env:ELECTRON_VERSION --module-dir node_modules/node-pty --arch ${{ matrix.arch }}
 
       - name: Package prebuilt binaries
-        working-directory: apps/frontend
+        working-directory: auto-claude-ui
         shell: pwsh
         run: |
           $electronAbi = (npx electron-abi $env:ELECTRON_VERSION)
@@ -78,7 +83,7 @@ jobs:
           Get-ChildItem $prebuildDir
 
       - name: Create archive
-        working-directory: apps/frontend
+        working-directory: auto-claude-ui
         shell: pwsh
         run: |
           $electronAbi = (npx electron-abi $env:ELECTRON_VERSION)
@@ -93,14 +98,14 @@ jobs:
         uses: actions/upload-artifact@v4
         with:
           name: node-pty-win32-${{ matrix.arch }}
-          path: apps/frontend/node-pty-*.zip
+          path: auto-claude-ui/node-pty-*.zip
           retention-days: 90
 
       - name: Upload to release
         if: github.event_name == 'release'
         uses: softprops/action-gh-release@v1
         with:
-          files: apps/frontend/node-pty-*.zip
+          files: auto-claude-ui/node-pty-*.zip
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
 

.github/workflows/ci.yml

@@ -2,17 +2,9 @@ name: CI
 
 on:
   push:
-    branches: [main, develop]
+    branches: [main]
   pull_request:
-    branches: [main, develop]
-
-concurrency:
-  group: ci-${{ github.event.pull_request.number || github.ref }}
-  cancel-in-progress: true
-
-permissions:
-  contents: read
-  actions: read
+    branches: [main]
 
 jobs:
   # Python tests
@@ -37,34 +29,30 @@ jobs:
           version: "latest"
 
       - name: Install dependencies
-        working-directory: apps/backend
+        working-directory: auto-claude
         run: |
           uv venv
           uv pip install -r requirements.txt
-          uv pip install -r ../../tests/requirements-test.txt
+          uv pip install -r ../tests/requirements-test.txt
 
       - name: Run tests
-        working-directory: apps/backend
-        env:
-          PYTHONPATH: ${{ github.workspace }}/apps/backend
+        working-directory: auto-claude
         run: |
           source .venv/bin/activate
-          pytest ../../tests/ -v --tb=short -x
+          pytest ../tests/ -v --tb=short -x
 
       - name: Run tests with coverage
         if: matrix.python-version == '3.12'
-        working-directory: apps/backend
-        env:
-          PYTHONPATH: ${{ github.workspace }}/apps/backend
+        working-directory: auto-claude
         run: |
           source .venv/bin/activate
-          pytest ../../tests/ -v --cov=. --cov-report=xml --cov-report=term-missing --cov-fail-under=20
+          pytest ../tests/ -v --cov=. --cov-report=xml --cov-report=term-missing
 
       - name: Upload coverage reports
         if: matrix.python-version == '3.12'
         uses: codecov/codecov-action@v4
         with:
-          file: ./apps/backend/coverage.xml
+          file: ./auto-claude/coverage.xml
           fail_ci_if_error: false
         env:
           CODECOV_TOKEN: ${{ secrets.CODECOV_TOKEN }}
@@ -79,34 +67,39 @@ jobs:
       - name: Setup Node.js
         uses: actions/setup-node@v4
         with:
-          node-version: '24'
+          node-version: '20'
 
-      - name: Get npm cache directory
-        id: npm-cache
-        run: echo "dir=$(npm config get cache)" >> "$GITHUB_OUTPUT"
+      - name: Setup pnpm
+        uses: pnpm/action-setup@v4
+        with:
+          version: 10
+
+      - name: Get pnpm store directory
+        id: pnpm-cache
+        run: echo "dir=$(pnpm store path)" >> "$GITHUB_OUTPUT"
 
       - uses: actions/cache@v4
         with:
-          path: ${{ steps.npm-cache.outputs.dir }}
-          key: ${{ runner.os }}-npm-${{ hashFiles('**/package-lock.json') }}
-          restore-keys: ${{ runner.os }}-npm-
+          path: ${{ steps.pnpm-cache.outputs.dir }}
+          key: ${{ runner.os }}-pnpm-${{ hashFiles('**/pnpm-lock.yaml') }}
+          restore-keys: ${{ runner.os }}-pnpm-
 
       - name: Install dependencies
-        working-directory: apps/frontend
-        run: npm ci --ignore-scripts
+        working-directory: auto-claude-ui
+        run: pnpm install --frozen-lockfile --ignore-scripts
 
       - name: Lint
-        working-directory: apps/frontend
-        run: npm run lint
+        working-directory: auto-claude-ui
+        run: pnpm run lint
 
       - name: Type check
-        working-directory: apps/frontend
-        run: npm run typecheck
+        working-directory: auto-claude-ui
+        run: pnpm run typecheck
 
       - name: Run tests
-        working-directory: apps/frontend
-        run: npm run test
+        working-directory: auto-claude-ui
+        run: pnpm run test
 
       - name: Build
-        working-directory: apps/frontend
-        run: npm run build
+        working-directory: auto-claude-ui
+        run: pnpm run build

.github/workflows/issue-auto-label.yml

@@ -1,53 +0,0 @@
-name: Issue Auto Label
-
-on:
-  issues:
-    types: [opened]
-
-jobs:
-  label-area:
-    runs-on: ubuntu-latest
-    permissions:
-      issues: write
-    steps:
-      - name: Add area label from form
-        uses: actions/github-script@v7
-        with:
-          script: |
-            const issue = context.payload.issue;
-            const body = issue.body || '';
-
-            console.log(`Processing issue #${issue.number}: ${issue.title}`);
-
-            // Map form selection to label
-            const areaMap = {
-              'Frontend': 'area/frontend',
-              'Backend': 'area/backend',
-              'Fullstack': 'area/fullstack'
-            };
-
-            const labels = [];
-
-            for (const [key, label] of Object.entries(areaMap)) {
-              if (body.includes(key)) {
-                console.log(`Found area: ${key}, adding label: ${label}`);
-                labels.push(label);
-                break;
-              }
-            }
-
-            if (labels.length > 0) {
-              try {
-                await github.rest.issues.addLabels({
-                  owner: context.repo.owner,
-                  repo: context.repo.repo,
-                  issue_number: issue.number,
-                  labels: labels
-                });
-                console.log(`Successfully added labels: ${labels.join(', ')}`);
-              } catch (error) {
-                core.setFailed(`Failed to add labels: ${error.message}`);
-              }
-            } else {
-              console.log('No matching area found in issue body');
-            }

.github/workflows/lint.yml

@@ -2,13 +2,9 @@ name: Lint
 
 on:
   push:
-    branches: [main, develop]
+    branches: [main]
   pull_request:
-    branches: [main, develop]
-
-concurrency:
-  group: lint-${{ github.event.pull_request.number || github.ref }}
-  cancel-in-progress: true
+    branches: [main]
 
 jobs:
   # Python linting
@@ -23,12 +19,40 @@ jobs:
         with:
           python-version: '3.12'
 
-      # Pin ruff version to match .pre-commit-config.yaml (astral-sh/ruff-pre-commit rev)
       - name: Install ruff
-        run: pip install ruff==0.14.10
+        run: pip install ruff
 
       - name: Run ruff check
-        run: ruff check apps/backend/ --output-format=github
+        run: ruff check auto-claude/ --output-format=github
 
       - name: Run ruff format check
-        run: ruff format apps/backend/ --check --diff
+        run: ruff format auto-claude/ --check --diff
+
+  # TypeScript/React linting
+  frontend:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: '20'
+
+      - name: Setup pnpm
+        uses: pnpm/action-setup@v4
+        with:
+          version: 9
+
+      - name: Install dependencies
+        working-directory: auto-claude-ui
+        run: pnpm install --frozen-lockfile --ignore-scripts
+
+      - name: Run ESLint
+        working-directory: auto-claude-ui
+        run: pnpm lint
+
+      - name: Run TypeScript check
+        working-directory: auto-claude-ui
+        run: pnpm typecheck

.github/workflows/pr-labeler.yml

@@ -1,320 +0,0 @@
-name: PR Labeler
-
-on:
-  pull_request:
-    types: [opened, synchronize, reopened]
-
-concurrency:
-  group: pr-labeler-${{ github.event.pull_request.number }}
-  cancel-in-progress: true
-
-permissions:
-  contents: read
-  pull-requests: write
-
-jobs:
-  label:
-    name: Auto Label PR
-    runs-on: ubuntu-latest
-    # Security: Prevent fork PRs from modifying labels (they don't have write access)
-    if: github.event.pull_request.head.repo.full_name == github.repository
-    timeout-minutes: 5
-
-    steps:
-      - name: Label PR
-        uses: actions/github-script@v7
-        with:
-          retries: 3
-          retry-exempt-status-codes: 400,401,403,404,422
-          script: |
-            // ═══════════════════════════════════════════════════════════════
-            // CONFIGURATION - Single source of truth for all settings
-            // ═══════════════════════════════════════════════════════════════
-
-            const CONFIG = {
-              // Size thresholds (lines changed)
-              SIZE_THRESHOLDS: {
-                XS: 10,
-                S: 100,
-                M: 500,
-                L: 1000
-              },
-
-              // Conventional commit type mappings
-              TYPE_MAP: Object.freeze({
-                'feat': 'feature',
-                'fix': 'bug',
-                'docs': 'documentation',
-                'refactor': 'refactor',
-                'test': 'test',
-                'ci': 'ci',
-                'chore': 'chore',
-                'perf': 'performance',
-                'style': 'style',
-                'build': 'build'
-              }),
-
-              // Area detection paths
-              AREA_PATHS: Object.freeze({
-                frontend: 'apps/frontend/',
-                backend: 'apps/backend/',
-                ci: '.github/'
-              }),
-
-              // Label definitions
-              LABELS: Object.freeze({
-                SIZE: ['size/XS', 'size/S', 'size/M', 'size/L', 'size/XL'],
-                AREA: ['area/frontend', 'area/backend', 'area/fullstack', 'area/ci'],
-                STATUS: ['🔄 Checking', '✅ Ready for Review', '❌ Checks Failed'],
-                REVIEW: ['Missing AC Approval', 'AC: Approved', 'AC: Changes Requested', 'AC: Needs Re-review']
-              }),
-
-              // Pagination
-              MAX_FILES_PER_PAGE: 100
-            };
-
-            // ═══════════════════════════════════════════════════════════════
-            // HELPER FUNCTIONS - Small, focused, single responsibility
-            // ═══════════════════════════════════════════════════════════════
-
-            /**
-             * Safely parse conventional commit type from PR title
-             * @param {string} title - PR title
-             * @returns {{type: string|null, isBreaking: boolean}}
-             */
-            function parseConventionalCommit(title) {
-              if (!title || typeof title !== 'string') {
-                return { type: null, isBreaking: false };
-              }
-
-              // Limit input length to prevent ReDoS attacks
-              const safeTitle = title.slice(0, 200);
-              const match = safeTitle.match(/^(\w{1,20})(\([^)]{0,50}\))?(!)?:/);
-
-              if (!match) {
-                return { type: null, isBreaking: false };
-              }
-
-              return {
-                type: match[1].toLowerCase(),
-                isBreaking: match[3] === '!'
-              };
-            }
-
-            /**
-             * Determine size label based on lines changed
-             * @param {number} totalLines - Total lines changed
-             * @returns {string} Size label
-             */
-            function determineSizeLabel(totalLines) {
-              const { SIZE_THRESHOLDS } = CONFIG;
-
-              if (totalLines < SIZE_THRESHOLDS.XS) return 'size/XS';
-              if (totalLines < SIZE_THRESHOLDS.S) return 'size/S';
-              if (totalLines < SIZE_THRESHOLDS.M) return 'size/M';
-              if (totalLines < SIZE_THRESHOLDS.L) return 'size/L';
-              return 'size/XL';
-            }
-
-            /**
-             * Detect areas affected by file changes
-             * @param {Array} files - List of changed files
-             * @returns {{frontend: boolean, backend: boolean, ci: boolean}}
-             */
-            function detectAreas(files) {
-              const areas = { frontend: false, backend: false, ci: false };
-              const { AREA_PATHS } = CONFIG;
-
-              for (const file of files) {
-                const path = file.filename || '';
-                if (path.startsWith(AREA_PATHS.frontend)) areas.frontend = true;
-                if (path.startsWith(AREA_PATHS.backend)) areas.backend = true;
-                if (path.startsWith(AREA_PATHS.ci)) areas.ci = true;
-              }
-
-              return areas;
-            }
-
-            /**
-             * Determine area label based on detected areas
-             * @param {{frontend: boolean, backend: boolean, ci: boolean}} areas
-             * @returns {string|null} Area label or null
-             */
-            function determineAreaLabel(areas) {
-              if (areas.frontend && areas.backend) return 'area/fullstack';
-              if (areas.frontend) return 'area/frontend';
-              if (areas.backend) return 'area/backend';
-              if (areas.ci) return 'area/ci';
-              return null;
-            }
-
-            /**
-             * Remove labels from PR (with error handling)
-             * @param {Array} labels - Labels to remove
-             * @param {number} prNumber - PR number
-             */
-            async function removeLabels(labels, prNumber) {
-              const { owner, repo } = context.repo;
-
-              await Promise.allSettled(labels.map(async (label) => {
-                try {
-                  await github.rest.issues.removeLabel({
-                    owner,
-                    repo,
-                    issue_number: prNumber,
-                    name: label
-                  });
-                  console.log(`  ✓ Removed: ${label}`);
-                } catch (e) {
-                  // 404 means label wasn't present - that's fine
-                  if (e.status !== 404) {
-                    console.log(`  ⚠ Failed to remove ${label}: ${e.message}`);
-                  }
-                }
-              }));
-            }
-
-            /**
-             * Add labels to PR (with error handling)
-             * @param {Array} labels - Labels to add
-             * @param {number} prNumber - PR number
-             */
-            async function addLabels(labels, prNumber) {
-              if (labels.length === 0) return;
-
-              const { owner, repo } = context.repo;
-
-              try {
-                await github.rest.issues.addLabels({
-                  owner,
-                  repo,
-                  issue_number: prNumber,
-                  labels
-                });
-                console.log(`  ✓ Added: ${labels.join(', ')}`);
-              } catch (e) {
-                if (e.status === 404) {
-                  core.warning(`One or more labels do not exist. Create them in repository settings.`);
-                } else {
-                  throw e;
-                }
-              }
-            }
-
-            /**
-             * Fetch PR files with full pagination support
-             * @param {number} prNumber - PR number
-             * @returns {Array} List of all files (paginated)
-             */
-            async function fetchPRFiles(prNumber) {
-              const { owner, repo } = context.repo;
-
-              try {
-                // Use paginate to fetch ALL files, not just first 100
-                const files = await github.paginate(
-                  github.rest.pulls.listFiles,
-                  { owner, repo, pull_number: prNumber, per_page: CONFIG.MAX_FILES_PER_PAGE }
-                );
-                return files;
-              } catch (e) {
-                console.log(`  ⚠ Could not fetch files: ${e.message}`);
-                return [];
-              }
-            }
-
-            // ═══════════════════════════════════════════════════════════════
-            // MAIN LOGIC - Orchestrates the labeling process
-            // ═══════════════════════════════════════════════════════════════
-
-            const { owner, repo } = context.repo;
-            const pr = context.payload.pull_request;
-            const prNumber = pr.number;
-            const title = pr.title || '';
-            const isNewPR = context.payload.action === 'opened' || context.payload.action === 'reopened';
-
-            console.log(`::group::PR #${prNumber} - Auto-labeling`);
-            console.log(`Title: ${title.slice(0, 100)}${title.length > 100 ? '...' : ''}`);
-            console.log(`Action: ${context.payload.action}`);
-
-            const labelsToAdd = new Set();
-            const labelsToRemove = new Set();
-
-            // 1. Parse conventional commit type
-            const { type, isBreaking } = parseConventionalCommit(title);
-            if (type && CONFIG.TYPE_MAP[type]) {
-              labelsToAdd.add(CONFIG.TYPE_MAP[type]);
-              console.log(`  📝 Type: ${type} → ${CONFIG.TYPE_MAP[type]}`);
-            } else {
-              console.log(`  ℹ️ No conventional commit prefix detected`);
-            }
-
-            if (isBreaking) {
-              labelsToAdd.add('breaking-change');
-              console.log(`  ⚠️ Breaking change detected`);
-            }
-
-            // 2. Detect areas from changed files
-            const files = await fetchPRFiles(prNumber);
-            const areas = detectAreas(files);
-            const areaLabel = determineAreaLabel(areas);
-
-            if (areaLabel) {
-              labelsToAdd.add(areaLabel);
-              CONFIG.LABELS.AREA.filter(l => l !== areaLabel).forEach(l => labelsToRemove.add(l));
-              console.log(`  📁 Area: ${areaLabel.replace('area/', '')}`);
-            }
-
-            // 3. Calculate size label
-            const totalLines = (pr.additions || 0) + (pr.deletions || 0);
-            const sizeLabel = determineSizeLabel(totalLines);
-            labelsToAdd.add(sizeLabel);
-            CONFIG.LABELS.SIZE.filter(l => l !== sizeLabel).forEach(l => labelsToRemove.add(l));
-            console.log(`  📏 Size: ${sizeLabel} (${totalLines} lines)`);
-
-            // 4. Set status label (only on new PRs - let pr-status-gate handle updates on pushes)
-            // Note: On synchronize events, CI workflows will trigger pr-status-gate when they complete
-            if (isNewPR) {
-              labelsToAdd.add('🔄 Checking');
-              CONFIG.LABELS.STATUS.filter(l => l !== '🔄 Checking').forEach(l => labelsToRemove.add(l));
-              console.log(`  🔄 Status: Checking`);
-            } else {
-              console.log(`  ℹ️ Status: Unchanged (will be updated by pr-status-gate)`);
-            }
-
-            // 5. Add review label for new PRs only
-            if (isNewPR) {
-              labelsToAdd.add('Missing AC Approval');
-              console.log(`  ⏳ Review: Missing AC Approval`);
-            }
-
-            console.log('::endgroup::');
-
-            // 6. Apply label changes
-            console.log(`::group::Applying labels`);
-
-            // Remove labels that should be replaced (exclude ones we're adding)
-            const removeList = [...labelsToRemove].filter(l => !labelsToAdd.has(l));
-            await removeLabels(removeList, prNumber);
-
-            // Add new labels
-            await addLabels([...labelsToAdd], prNumber);
-
-            console.log('::endgroup::');
-            console.log(`✅ PR #${prNumber} labeled successfully`);
-
-            // 7. Write job summary
-            const summaryType = type ? CONFIG.TYPE_MAP[type] || 'unknown' : 'none';
-            const summaryArea = areaLabel ? areaLabel.replace('area/', '') : 'other';
-
-            await core.summary
-              .addHeading(`PR #${prNumber} Auto-Labels`, 3)
-              .addTable([
-                [{ data: 'Category', header: true }, { data: 'Label', header: true }],
-                ['Type', summaryType],
-                ['Area', summaryArea],
-                ['Size', sizeLabel],
-                ['Status', isNewPR ? '🔄 Checking' : '(unchanged)'],
-                ['Review', isNewPR ? 'Missing AC Approval' : '(unchanged)']
-              ])
-              .addRaw(`\n**Files:** ${files.length} | **Lines:** +${pr.additions || 0} / -${pr.deletions || 0}\n`)
-              .write();

.github/workflows/pr-status-gate.yml

@@ -1,585 +0,0 @@
-name: PR Status Gate
-
-on:
-  workflow_run:
-    workflows: [CI, Lint, Quality Security]
-    types: [completed]
-
-  issue_comment:
-    types: [created, edited]
-
-  pull_request:
-    types: [synchronize]
-
-concurrency:
-  group: pr-status-gate-${{ github.event.workflow_run.pull_requests[0].number || github.event.issue.number || github.event.pull_request.number || github.run_id }}
-  cancel-in-progress: true
-
-permissions:
-  pull-requests: write
-  checks: read
-
-env:
-  # Shared configuration - single source of truth
-  REQUIRED_CHECKS: |
-    CI / test-frontend
-    CI / test-python (3.12)
-    CI / test-python (3.13)
-    Lint / python
-    Quality Security / CodeQL (javascript-typescript)
-    Quality Security / CodeQL (python)
-    Quality Security / Python Security (Bandit)
-    Quality Security / Security Summary
-
-jobs:
-  # ═══════════════════════════════════════════════════════════════════════════
-  # JOB 1: CI STATUS (triggered by workflow_run)
-  # Updates CI status labels when monitored workflows complete
-  # ═══════════════════════════════════════════════════════════════════════════
-  update-ci-status:
-    name: Update CI Status
-    runs-on: ubuntu-latest
-    if: github.event_name == 'workflow_run' && github.event.workflow_run.pull_requests[0] != null
-    timeout-minutes: 5
-
-    steps:
-      - name: Check all required checks and update label
-        uses: actions/github-script@v7
-        env:
-          REQUIRED_CHECKS: ${{ env.REQUIRED_CHECKS }}
-        with:
-          retries: 3
-          retry-exempt-status-codes: 400,401,403,404,422
-          script: |
-            // NOTE: STATUS_LABELS is intentionally duplicated across jobs.
-            // GitHub Actions jobs run in isolated contexts and cannot share runtime constants.
-            // If label values change, update ALL occurrences: update-ci-status, check-status-command
-            const STATUS_LABELS = Object.freeze({
-              CHECKING: '🔄 Checking',
-              PASSED: '✅ Ready for Review',
-              FAILED: '❌ Checks Failed'
-            });
-
-            const REQUIRED_CHECKS = process.env.REQUIRED_CHECKS
-              .split('\n')
-              .map(s => s.trim())
-              .filter(Boolean);
-
-            async function fetchCheckRuns(sha) {
-              const { owner, repo } = context.repo;
-              // Let the configured retries (retries: 3) handle transient failures
-              // Don't catch errors - allow them to propagate for retry logic
-              const checkRuns = await github.paginate(
-                github.rest.checks.listForRef,
-                { owner, repo, ref: sha, per_page: 100 },
-                (response) => response.data
-              );
-              return checkRuns;
-            }
-
-            function analyzeChecks(checkRuns) {
-              const results = [];
-              let allComplete = true;
-              let anyFailed = false;
-
-              for (const checkName of REQUIRED_CHECKS) {
-                const check = checkRuns.find(c => c.name === checkName);
-
-                if (!check) {
-                  results.push({ name: checkName, status: '⏳ Pending', complete: false });
-                  allComplete = false;
-                } else if (check.status !== 'completed') {
-                  results.push({ name: checkName, status: '🔄 Running', complete: false });
-                  allComplete = false;
-                } else if (check.conclusion === 'success') {
-                  results.push({ name: checkName, status: '✅ Passed', complete: true });
-                } else if (check.conclusion === 'skipped') {
-                  results.push({ name: checkName, status: '⏭️ Skipped', complete: true, skipped: true });
-                } else {
-                  results.push({ name: checkName, status: '❌ Failed', complete: true, failed: true });
-                  anyFailed = true;
-                }
-              }
-              return { allComplete, anyFailed, results };
-            }
-
-            async function updateStatusLabels(prNumber, newLabel) {
-              const { owner, repo } = context.repo;
-              const allLabels = Object.values(STATUS_LABELS);
-
-              // Remove all status labels first - throw on non-404 errors to prevent conflicting labels
-              for (const label of allLabels) {
-                try {
-                  await github.rest.issues.removeLabel({ owner, repo, issue_number: prNumber, name: label });
-                } catch (e) {
-                  if (e && e.status !== 404) {
-                    // Throw to prevent adding new label if removal failed (could cause conflicting labels)
-                    throw new Error(`Failed to remove label '${label}': ${e.message}`);
-                  }
-                }
-              }
-
-              try {
-                await github.rest.issues.addLabels({ owner, repo, issue_number: prNumber, labels: [newLabel] });
-              } catch (e) {
-                if (e && e.status === 404) {
-                  core.warning(`Label '${newLabel}' does not exist`);
-                } else {
-                  throw e;
-                }
-              }
-            }
-
-            // Main logic
-            const prNumber = context.payload.workflow_run.pull_requests[0].number;
-            const headSha = context.payload.workflow_run.head_sha;
-            const triggerWorkflow = context.payload.workflow_run.name;
-
-            console.log(`PR #${prNumber} - Triggered by: ${triggerWorkflow}, SHA: ${headSha.slice(0, 8)}`);
-
-            const checkRuns = await fetchCheckRuns(headSha);
-            console.log(`Found ${checkRuns.length} check runs`);
-            const { allComplete, anyFailed, results } = analyzeChecks(checkRuns);
-
-            for (const r of results) {
-              console.log(`  ${r.status} ${r.name}`);
-            }
-
-            if (!allComplete) {
-              const pending = results.filter(r => !r.complete).length;
-              console.log(`⏳ ${pending}/${REQUIRED_CHECKS.length} checks pending`);
-              // Update to CHECKING status if checks are still running (prevents stale Ready/Failed status)
-              await updateStatusLabels(prNumber, STATUS_LABELS.CHECKING);
-              return;
-            }
-
-            const newLabel = anyFailed ? STATUS_LABELS.FAILED : STATUS_LABELS.PASSED;
-            await updateStatusLabels(prNumber, newLabel);
-
-            const passedCount = results.filter(r => r.status === '✅ Passed').length;
-            const failedCount = results.filter(r => r.failed).length;
-
-            if (anyFailed) {
-              console.log(`❌ PR #${prNumber}: ${failedCount} check(s) failed`);
-            } else {
-              console.log(`✅ PR #${prNumber}: Ready for review (${passedCount}/${REQUIRED_CHECKS.length} passed)`);
-            }
-
-  # ═══════════════════════════════════════════════════════════════════════════
-  # JOB 2: /check-status COMMAND
-  # Manual status check - anyone can trigger by commenting /check-status
-  # ═══════════════════════════════════════════════════════════════════════════
-  check-status-command:
-    name: Check Status Command
-    runs-on: ubuntu-latest
-    if: |
-      github.event_name == 'issue_comment' &&
-      github.event.issue.pull_request &&
-      contains(github.event.comment.body, '/check-status')
-    timeout-minutes: 5
-
-    steps:
-      - name: Run status check and post report
-        uses: actions/github-script@v7
-        env:
-          REQUIRED_CHECKS: ${{ env.REQUIRED_CHECKS }}
-        with:
-          retries: 3
-          retry-exempt-status-codes: 400,401,403,404,422
-          script: |
-            // NOTE: STATUS_LABELS is intentionally duplicated across jobs.
-            // GitHub Actions jobs run in isolated contexts and cannot share runtime constants.
-            // If label values change, update ALL occurrences: update-ci-status, check-status-command
-            const STATUS_LABELS = Object.freeze({
-              CHECKING: '🔄 Checking',
-              PASSED: '✅ Ready for Review',
-              FAILED: '❌ Checks Failed'
-            });
-
-            // NOTE: REVIEW_LABELS is intentionally duplicated across jobs.
-            // If label values change, update ALL occurrences: check-status-command, update-review-status
-            const REVIEW_LABELS = Object.freeze([
-              'Missing AC Approval',
-              'AC: Approved',
-              'AC: Changes Requested',
-              'AC: Blocked',
-              'AC: Needs Re-review',
-              'AC: Reviewed'
-            ]);
-
-            const REQUIRED_CHECKS = process.env.REQUIRED_CHECKS
-              .split('\n')
-              .map(s => s.trim())
-              .filter(Boolean);
-
-            const { owner, repo } = context.repo;
-            const prNumber = context.payload.issue.number;
-            const requestedBy = context.payload.comment.user.login;
-
-            // Get PR details
-            const { data: pr } = await github.rest.pulls.get({
-              owner, repo, pull_number: prNumber
-            });
-            const headSha = pr.head.sha;
-
-            console.log(`PR #${prNumber} - /check-status by @${requestedBy}, SHA: ${headSha.slice(0, 8)}`);
-
-            // Fetch check runs with pagination to handle >100 checks
-            const checkRuns = await github.paginate(
-              github.rest.checks.listForRef,
-              { owner, repo, ref: headSha, per_page: 100 },
-              (response) => response.data
-            );
-            console.log(`Found ${checkRuns.length} check runs`);
-
-            // Analyze results
-            const results = [];
-            let allComplete = true;
-            let anyFailed = false;
-
-            for (const checkName of REQUIRED_CHECKS) {
-              const check = checkRuns.find(c => c.name === checkName);
-
-              if (!check) {
-                results.push({ name: checkName, emoji: '⏳', complete: false });
-                allComplete = false;
-              } else if (check.status !== 'completed') {
-                results.push({ name: checkName, emoji: '🔄', complete: false });
-                allComplete = false;
-              } else if (check.conclusion === 'success') {
-                results.push({ name: checkName, emoji: '✅', complete: true });
-              } else if (check.conclusion === 'skipped') {
-                results.push({ name: checkName, emoji: '⏭️', complete: true, skipped: true });
-              } else {
-                results.push({ name: checkName, emoji: '❌', complete: true, failed: true });
-                anyFailed = true;
-              }
-            }
-
-            // Get current labels
-            const { data: currentLabels } = await github.rest.issues.listLabelsOnIssue({
-              owner, repo, issue_number: prNumber
-            });
-            const labelNames = currentLabels.map(l => l.name);
-            const currentStatusLabel = Object.values(STATUS_LABELS).find(l => labelNames.includes(l)) || 'None';
-            const currentReviewLabel = REVIEW_LABELS.find(l => labelNames.includes(l)) || 'None';
-
-            // Update label if all checks complete
-            let newStatusLabel = STATUS_LABELS.CHECKING;
-            let statusChanged = false;
-
-            if (allComplete) {
-              newStatusLabel = anyFailed ? STATUS_LABELS.FAILED : STATUS_LABELS.PASSED;
-
-              if (newStatusLabel !== currentStatusLabel) {
-                statusChanged = true;
-                // Remove all status labels first - throw on non-404 errors to prevent conflicting labels
-                for (const label of Object.values(STATUS_LABELS)) {
-                  try {
-                    await github.rest.issues.removeLabel({ owner, repo, issue_number: prNumber, name: label });
-                  } catch (e) {
-                    if (e && e.status !== 404) {
-                      throw new Error(`Failed to remove label '${label}': ${e.message}`);
-                    }
-                  }
-                }
-                await github.rest.issues.addLabels({ owner, repo, issue_number: prNumber, labels: [newStatusLabel] });
-              }
-            }
-
-            // Build status report
-            const passedCount = results.filter(r => r.emoji === '✅').length;
-            let statusEmoji = '🔄';
-            if (allComplete && !anyFailed) statusEmoji = '✅';
-            else if (allComplete && anyFailed) statusEmoji = '❌';
-
-            const checksTable = results.map(r => `| ${r.emoji} | ${r.name} |`).join('\n');
-
-            const lines = [
-              `## ${statusEmoji} PR Status Report`,
-              '',
-              `| Label | Value |`,
-              `|-------|-------|`,
-              `| CI Status | ${newStatusLabel} |`,
-              `| AC Review | ${currentReviewLabel} |`,
-              ''
-            ];
-
-            if (statusChanged) {
-              lines.push(`> Status updated: \`${currentStatusLabel}\` → \`${newStatusLabel}\``);
-              lines.push('');
-            }
-
-            lines.push(`### CI Checks (${passedCount}/${REQUIRED_CHECKS.length} passed)`);
-            lines.push('');
-            lines.push('| Status | Check |');
-            lines.push('|--------|-------|');
-            lines.push(checksTable);
-            lines.push('');
-            lines.push('---');
-            lines.push(`<sub>Triggered by \`/check-status\` from @${requestedBy}</sub>`);
-
-            await github.rest.issues.createComment({
-              owner, repo, issue_number: prNumber, body: lines.join('\n')
-            });
-
-            console.log(`✅ Posted status report to PR #${prNumber}`);
-
-  # ═══════════════════════════════════════════════════════════════════════════
-  # JOB 3: AUTO-CLAUDE REVIEW
-  # Processes Auto-Claude review comments from trusted sources
-  # Security: Only bots and collaborators can update labels
-  # ═══════════════════════════════════════════════════════════════════════════
-  update-review-status:
-    name: Update Review Status
-    runs-on: ubuntu-latest
-    if: |
-      github.event_name == 'issue_comment' &&
-      github.event.issue.pull_request &&
-      !contains(github.event.comment.body, '/check-status')
-    timeout-minutes: 5
-
-    steps:
-      - name: Check for Auto-Claude review
-        uses: actions/github-script@v7
-        with:
-          retries: 3
-          retry-exempt-status-codes: 400,401,403,404,422
-          script: |
-            // Security configuration
-            // SECURITY: Only [bot] suffixed accounts are protected by GitHub.
-            // Regular usernames can be registered by anyone and are NOT trusted.
-            const TRUSTED_BOT_ACCOUNTS = Object.freeze([
-              'github-actions[bot]',
-              'auto-claude[bot]'
-            ]);
-
-            const TRUSTED_AUTHOR_ASSOCIATIONS = Object.freeze([
-              'COLLABORATOR',
-              'MEMBER',
-              'OWNER'
-            ]);
-
-            const IDENTIFIER_PATTERNS = Object.freeze([
-              '🤖 Auto Claude PR Review',
-              'Auto Claude Review',
-              'Auto-Claude Review'
-            ]);
-
-            // SECURITY: Regex patterns are tightened to prevent false matches
-            // Using \s* instead of .* and requiring specific emoji + verdict format
-            const VERDICTS = Object.freeze({
-              APPROVED: {
-                patterns: ['Auto Claude Review - APPROVED', '✅ Auto Claude Review - APPROVED'],
-                // Match: "Merge Verdict:" followed by whitespace/emoji, then ✅, then APPROVED/READY TO MERGE
-                regex: /Merge Verdict:\s*✅\s*(?:APPROVED|READY TO MERGE)/i,
-                label: 'AC: Approved'
-              },
-              CHANGES_REQUESTED: {
-                patterns: ['NEEDS REVISION', 'Needs Revision'],
-                // Match: "Merge Verdict:" followed by whitespace/emoji, then 🟠
-                regex: /Merge Verdict:\s*🟠/,
-                label: 'AC: Changes Requested'
-              },
-              BLOCKED: {
-                patterns: ['BLOCKED'],
-                // Match: "Merge Verdict:" followed by whitespace/emoji, then 🔴
-                regex: /Merge Verdict:\s*🔴/,
-                label: 'AC: Blocked'
-              }
-            });
-
-            // NOTE: REVIEW_LABELS is intentionally duplicated across jobs.
-            // GitHub Actions jobs run in isolated contexts and cannot share runtime constants.
-            // If label values change, update ALL occurrences: check-status-command, update-review-status
-            const REVIEW_LABELS = Object.freeze([
-              'Missing AC Approval',
-              'AC: Approved',
-              'AC: Changes Requested',
-              'AC: Blocked',
-              'AC: Needs Re-review',
-              'AC: Reviewed'
-            ]);
-
-            // Helper functions
-            // SECURITY: Verify both username AND account type to prevent spoofing
-            function isTrustedBot(username, userType) {
-              const isKnownBot = TRUSTED_BOT_ACCOUNTS.some(t => username.toLowerCase() === t.toLowerCase());
-              // Only trust if it's a known bot account AND GitHub confirms it's a Bot type
-              return isKnownBot && userType === 'Bot';
-            }
-
-            function isTrustedAssociation(assoc) {
-              return TRUSTED_AUTHOR_ASSOCIATIONS.includes(assoc);
-            }
-
-            function isAutoClaudeComment(body) {
-              return IDENTIFIER_PATTERNS.some(p => body.includes(p));
-            }
-
-            function parseVerdict(body) {
-              const safeBody = body.slice(0, 5000);
-              for (const [key, config] of Object.entries(VERDICTS)) {
-                const patternMatch = config.patterns.some(p => safeBody.includes(p));
-                const regexMatch = config.regex && config.regex.test(safeBody);
-                if (patternMatch || regexMatch) {
-                  return { verdict: key, label: config.label };
-                }
-              }
-              return null;
-            }
-
-            async function updateReviewLabels(prNumber, newLabel) {
-              const { owner, repo } = context.repo;
-
-              // Remove all review labels first - throw on non-404 errors to prevent conflicting labels
-              for (const label of REVIEW_LABELS) {
-                try {
-                  await github.rest.issues.removeLabel({ owner, repo, issue_number: prNumber, name: label });
-                  console.log(`  Removed: ${label}`);
-                } catch (e) {
-                  if (e && e.status !== 404) {
-                    // Throw to prevent adding new label if removal failed (could cause conflicting labels)
-                    throw new Error(`Failed to remove label '${label}': ${e.message}`);
-                  }
-                }
-              }
-
-              try {
-                await github.rest.issues.addLabels({ owner, repo, issue_number: prNumber, labels: [newLabel] });
-                console.log(`  Added: ${newLabel}`);
-              } catch (e) {
-                if (e && e.status === 404) {
-                  core.warning(`Label '${newLabel}' does not exist`);
-                } else {
-                  throw e;
-                }
-              }
-            }
-
-            // Main logic
-            const prNumber = context.payload.issue.number;
-            const comment = context.payload.comment;
-            const commenter = comment.user.login;
-            const commenterType = comment.user.type;
-            const authorAssociation = comment.author_association;
-            const body = comment.body || '';
-
-            console.log(`PR #${prNumber} - Comment by: ${commenter} (type: ${commenterType}, assoc: ${authorAssociation})`);
-
-            // Security checks
-            // SECURITY: Bot status requires BOTH username match AND verified Bot type
-            const isBot = isTrustedBot(commenter, commenterType);
-            const isCollaborator = isTrustedAssociation(authorAssociation);
-            const isACComment = isAutoClaudeComment(body);
-
-            console.log(`  Trusted bot: ${isBot}, Collaborator: ${isCollaborator}, AC comment: ${isACComment}`);
-
-            if (!isBot && !isCollaborator) {
-              console.log('Skipping: Not a trusted bot or collaborator');
-              return;
-            }
-
-            if (!isACComment) {
-              console.log('Skipping: Not an Auto-Claude comment');
-              return;
-            }
-
-            const verdictResult = parseVerdict(body);
-            if (!verdictResult) {
-              console.log('Skipping: Could not parse verdict');
-              return;
-            }
-
-            console.log(`Verdict: ${verdictResult.verdict} → ${verdictResult.label}`);
-            await updateReviewLabels(prNumber, verdictResult.label);
-            console.log(`✅ PR #${prNumber} review status updated`);
-
-  # ═══════════════════════════════════════════════════════════════════════════
-  # JOB 4: RE-REVIEW ON PUSH
-  # When new commits pushed after AC approval, require re-review
-  # ═══════════════════════════════════════════════════════════════════════════
-  require-re-review:
-    name: Require Re-review on Push
-    runs-on: ubuntu-latest
-    if: github.event_name == 'pull_request' && github.event.action == 'synchronize'
-    timeout-minutes: 5
-
-    steps:
-      - name: Check and reset AC approval if needed
-        uses: actions/github-script@v7
-        with:
-          retries: 3
-          retry-exempt-status-codes: 400,401,403,404,422
-          script: |
-            const { owner, repo } = context.repo;
-            const prNumber = context.payload.pull_request.number;
-            const pusher = context.payload.sender.login;
-
-            console.log(`PR #${prNumber} - New commits by: ${pusher}`);
-
-            // Get current labels
-            const { data: labels } = await github.rest.issues.listLabelsOnIssue({
-              owner, repo, issue_number: prNumber
-            });
-            const labelNames = labels.map(l => l.name);
-
-            // Check if PR was approved
-            const wasApproved = labelNames.includes('AC: Approved');
-
-            if (!wasApproved) {
-              console.log('PR was not AC-approved, no action needed');
-              return;
-            }
-
-            console.log('PR was AC-approved, resetting to require re-review');
-
-            // Remove AC: Approved - throw on non-404 errors to prevent conflicting labels
-            try {
-              await github.rest.issues.removeLabel({
-                owner, repo, issue_number: prNumber, name: 'AC: Approved'
-              });
-              console.log('  Removed: AC: Approved');
-            } catch (e) {
-              if (e && e.status !== 404) {
-                // Throw to prevent adding 'AC: Needs Re-review' if removal failed (could cause conflicting labels)
-                core.error(`Failed to remove 'AC: Approved' label: ${e.message}`);
-                throw e;
-              }
-            }
-
-            // Add AC: Needs Re-review
-            try {
-              await github.rest.issues.addLabels({
-                owner, repo, issue_number: prNumber, labels: ['AC: Needs Re-review']
-              });
-              console.log('  Added: AC: Needs Re-review');
-            } catch (e) {
-              if (e && e.status === 404) {
-                core.warning("Label 'AC: Needs Re-review' does not exist");
-              } else {
-                throw e;
-              }
-            }
-
-            // Post notification comment
-            const commentLines = [
-              '## 🔄 Re-review Required',
-              '',
-              'New commits were pushed after Auto-Claude approval.',
-              '',
-              '| Previous | Current |',
-              '|----------|---------|',
-              '| `AC: Approved` | `AC: Needs Re-review` |',
-              '',
-              'Please run Auto-Claude review again or request a manual review.',
-              '',
-              '---',
-              `<sub>Triggered by push from @${pusher}</sub>`
-            ];
-
-            await github.rest.issues.createComment({
-              owner, repo, issue_number: prNumber, body: commentLines.join('\n')
-            });
-
-            console.log(`✅ Posted re-review notification to PR #${prNumber}`);

.github/workflows/prepare-release.yml

@@ -1,238 +0,0 @@
-name: Prepare Release
-
-# Triggers when code is pushed to main (e.g., merging develop → main)
-# If package.json version is newer than the latest tag:
-# 1. Validates CHANGELOG.md has an entry for this version (FAILS if missing)
-# 2. Extracts release notes from CHANGELOG.md
-# 3. Creates a new tag which triggers release.yml
-
-on:
-  push:
-    branches: [main]
-    paths:
-      - 'apps/frontend/package.json'
-      - 'package.json'
-  workflow_dispatch:
-    inputs:
-      force:
-        description: 'Force release even if version check fails (use with caution)'
-        required: false
-        default: false
-        type: boolean
-
-jobs:
-  check-and-tag:
-    runs-on: ubuntu-latest
-    permissions:
-      contents: write
-    outputs:
-      should_release: ${{ steps.check.outputs.should_release }}
-      new_version: ${{ steps.check.outputs.new_version }}
-    steps:
-      - uses: actions/checkout@v4
-        with:
-          fetch-depth: 0
-          token: ${{ secrets.GITHUB_TOKEN }}
-
-      - name: Get package version
-        id: package
-        run: |
-          VERSION=$(node -p "require('./apps/frontend/package.json').version")
-          echo "version=$VERSION" >> $GITHUB_OUTPUT
-          echo "Package version: $VERSION"
-
-      - name: Get latest tag version
-        id: latest_tag
-        run: |
-          # Get the latest version tag (v*)
-          LATEST_TAG=$(git tag -l 'v*' --sort=-version:refname | head -n1)
-          if [ -z "$LATEST_TAG" ]; then
-            echo "No existing tags found"
-            echo "version=0.0.0" >> $GITHUB_OUTPUT
-          else
-            # Remove 'v' prefix
-            LATEST_VERSION=${LATEST_TAG#v}
-            echo "version=$LATEST_VERSION" >> $GITHUB_OUTPUT
-            echo "Latest tag: $LATEST_TAG (version: $LATEST_VERSION)"
-          fi
-
-      - name: Check if release needed
-        id: check
-        run: |
-          PACKAGE_VERSION="${{ steps.package.outputs.version }}"
-          LATEST_VERSION="${{ steps.latest_tag.outputs.version }}"
-          FORCE="${{ github.event.inputs.force }}"
-
-          echo "Comparing: package=$PACKAGE_VERSION vs latest_tag=$LATEST_VERSION"
-
-          # Use npx semver for proper semantic version comparison
-          # This correctly handles pre-release versions (2.7.3 > 2.7.3-beta.1)
-          if npx -y semver "$PACKAGE_VERSION" -r ">$LATEST_VERSION" > /dev/null 2>&1; then
-            echo "should_release=true" >> $GITHUB_OUTPUT
-            echo "new_version=$PACKAGE_VERSION" >> $GITHUB_OUTPUT
-            echo "✅ New release needed: v$PACKAGE_VERSION"
-          elif [ "$FORCE" = "true" ]; then
-            echo "should_release=true" >> $GITHUB_OUTPUT
-            echo "new_version=$PACKAGE_VERSION" >> $GITHUB_OUTPUT
-            echo "⚠️ Force release enabled: v$PACKAGE_VERSION"
-          else
-            echo "should_release=false" >> $GITHUB_OUTPUT
-            echo "⏭️ No release needed (package version not newer than latest tag)"
-          fi
-
-      # CRITICAL: Validate CHANGELOG.md has entry for this version BEFORE creating tag
-      - name: Validate and extract changelog
-        if: steps.check.outputs.should_release == 'true'
-        id: changelog
-        run: |
-          VERSION="${{ steps.check.outputs.new_version }}"
-          CHANGELOG_FILE="CHANGELOG.md"
-
-          echo "🔍 Validating CHANGELOG.md for version $VERSION..."
-
-          if [ ! -f "$CHANGELOG_FILE" ]; then
-            echo "::error::CHANGELOG.md not found! Please create CHANGELOG.md with release notes."
-            exit 1
-          fi
-
-          # Extract changelog section for this version
-          # Looks for "## X.Y.Z" header and captures until next "## " or "---" or end
-          CHANGELOG_CONTENT=$(awk -v ver="$VERSION" '
-            BEGIN { found=0; content="" }
-            /^## / {
-              if (found) exit
-              # Match version at start of header (e.g., "## 2.7.3 -" or "## 2.7.3")
-              if ($2 == ver || $2 ~ "^"ver"[[:space:]]*-") {
-                found=1
-                # Skip the header line itself, we will add our own
-                next
-              }
-            }
-            /^---$/ { if (found) exit }
-            found { content = content $0 "\n" }
-            END {
-              if (!found) {
-                print "NOT_FOUND"
-                exit 1
-              }
-              # Trim leading/trailing whitespace
-              gsub(/^[[:space:]]+|[[:space:]]+$/, "", content)
-              print content
-            }
-          ' "$CHANGELOG_FILE")
-
-          if [ "$CHANGELOG_CONTENT" = "NOT_FOUND" ] || [ -z "$CHANGELOG_CONTENT" ]; then
-            echo ""
-            echo "::error::═══════════════════════════════════════════════════════════════════════"
-            echo "::error::  CHANGELOG VALIDATION FAILED"
-            echo "::error::═══════════════════════════════════════════════════════════════════════"
-            echo "::error::"
-            echo "::error::  Version $VERSION not found in CHANGELOG.md!"
-            echo "::error::"
-            echo "::error::  Before releasing, please update CHANGELOG.md with an entry like:"
-            echo "::error::"
-            echo "::error::    ## $VERSION - Your Release Title"
-            echo "::error::"
-            echo "::error::    ### ✨ New Features"
-            echo "::error::    - Feature description"
-            echo "::error::"
-            echo "::error::    ### 🐛 Bug Fixes"
-            echo "::error::    - Fix description"
-            echo "::error::"
-            echo "::error::═══════════════════════════════════════════════════════════════════════"
-            echo ""
-
-            # Also add to job summary for visibility
-            echo "## ❌ Release Blocked: Missing Changelog" >> $GITHUB_STEP_SUMMARY
-            echo "" >> $GITHUB_STEP_SUMMARY
-            echo "Version **$VERSION** was not found in CHANGELOG.md." >> $GITHUB_STEP_SUMMARY
-            echo "" >> $GITHUB_STEP_SUMMARY
-            echo "### How to fix:" >> $GITHUB_STEP_SUMMARY
-            echo "1. Update CHANGELOG.md with release notes for version $VERSION" >> $GITHUB_STEP_SUMMARY
-            echo "2. Commit and push the changes" >> $GITHUB_STEP_SUMMARY
-            echo "3. The release will automatically retry" >> $GITHUB_STEP_SUMMARY
-            echo "" >> $GITHUB_STEP_SUMMARY
-            echo "### Expected format:" >> $GITHUB_STEP_SUMMARY
-            echo "\`\`\`markdown" >> $GITHUB_STEP_SUMMARY
-            echo "## $VERSION - Release Title" >> $GITHUB_STEP_SUMMARY
-            echo "" >> $GITHUB_STEP_SUMMARY
-            echo "### ✨ New Features" >> $GITHUB_STEP_SUMMARY
-            echo "- Feature description" >> $GITHUB_STEP_SUMMARY
-            echo "" >> $GITHUB_STEP_SUMMARY
-            echo "### 🐛 Bug Fixes" >> $GITHUB_STEP_SUMMARY
-            echo "- Fix description" >> $GITHUB_STEP_SUMMARY
-            echo "\`\`\`" >> $GITHUB_STEP_SUMMARY
-
-            exit 1
-          fi
-
-          echo "✅ Found changelog entry for version $VERSION"
-          echo ""
-          echo "--- Extracted Release Notes ---"
-          echo "$CHANGELOG_CONTENT"
-          echo "--- End Release Notes ---"
-
-          # Save changelog to file for artifact upload
-          echo "$CHANGELOG_CONTENT" > changelog-extract.md
-
-          # Also save to output (for short changelogs)
-          # Using heredoc for multiline output
-          {
-            echo "content<<CHANGELOG_EOF"
-            echo "$CHANGELOG_CONTENT"
-            echo "CHANGELOG_EOF"
-          } >> $GITHUB_OUTPUT
-
-          echo "changelog_valid=true" >> $GITHUB_OUTPUT
-
-      # Upload changelog as artifact for release.yml to use
-      - name: Upload changelog artifact
-        if: steps.check.outputs.should_release == 'true' && steps.changelog.outputs.changelog_valid == 'true'
-        uses: actions/upload-artifact@v4
-        with:
-          name: changelog-${{ steps.check.outputs.new_version }}
-          path: changelog-extract.md
-          retention-days: 1
-
-      - name: Create and push tag
-        if: steps.check.outputs.should_release == 'true' && steps.changelog.outputs.changelog_valid == 'true'
-        run: |
-          VERSION="${{ steps.check.outputs.new_version }}"
-          TAG="v$VERSION"
-
-          git config user.name "github-actions[bot]"
-          git config user.email "github-actions[bot]@users.noreply.github.com"
-
-          echo "Creating tag: $TAG"
-          git tag -a "$TAG" -m "Release $TAG"
-          git push origin "$TAG"
-
-          echo "✅ Tag $TAG created and pushed"
-          echo "🚀 This will trigger the release workflow"
-
-      - name: Summary
-        run: |
-          if [ "${{ steps.check.outputs.should_release }}" = "true" ] && [ "${{ steps.changelog.outputs.changelog_valid }}" = "true" ]; then
-            echo "## 🚀 Release Triggered" >> $GITHUB_STEP_SUMMARY
-            echo "" >> $GITHUB_STEP_SUMMARY
-            echo "**Version:** v${{ steps.check.outputs.new_version }}" >> $GITHUB_STEP_SUMMARY
-            echo "" >> $GITHUB_STEP_SUMMARY
-            echo "✅ Changelog validated and extracted from CHANGELOG.md" >> $GITHUB_STEP_SUMMARY
-            echo "" >> $GITHUB_STEP_SUMMARY
-            echo "The release workflow has been triggered and will:" >> $GITHUB_STEP_SUMMARY
-            echo "1. Build binaries for all platforms" >> $GITHUB_STEP_SUMMARY
-            echo "2. Use changelog from CHANGELOG.md" >> $GITHUB_STEP_SUMMARY
-            echo "3. Create GitHub release" >> $GITHUB_STEP_SUMMARY
-            echo "4. Update README with new version" >> $GITHUB_STEP_SUMMARY
-          elif [ "${{ steps.check.outputs.should_release }}" = "false" ]; then
-            echo "## ⏭️ No Release Needed" >> $GITHUB_STEP_SUMMARY
-            echo "" >> $GITHUB_STEP_SUMMARY
-            echo "**Package version:** ${{ steps.package.outputs.version }}" >> $GITHUB_STEP_SUMMARY
-            echo "**Latest tag:** v${{ steps.latest_tag.outputs.version }}" >> $GITHUB_STEP_SUMMARY
-            echo "" >> $GITHUB_STEP_SUMMARY
-            echo "The package version is not newer than the latest tag." >> $GITHUB_STEP_SUMMARY
-            echo "To trigger a release, bump the version using:" >> $GITHUB_STEP_SUMMARY
-            echo "\`\`\`bash" >> $GITHUB_STEP_SUMMARY
-            echo "node scripts/bump-version.js patch  # or minor/major" >> $GITHUB_STEP_SUMMARY
-            echo "\`\`\`" >> $GITHUB_STEP_SUMMARY
-          fi

.github/workflows/quality-security.yml

@@ -1,178 +0,0 @@
-name: Quality Security
-
-on:
-  push:
-    branches: [main, develop]
-  pull_request:
-    branches: [main, develop]
-  schedule:
-    - cron: '0 0 * * 1' # Weekly on Monday at midnight UTC
-
-# Cancel in-progress runs for the same branch/PR
-concurrency:
-  group: security-${{ github.workflow }}-${{ github.ref }}
-  cancel-in-progress: true
-
-permissions:
-  contents: read
-  security-events: write
-  actions: read
-
-jobs:
-  codeql:
-    name: CodeQL (${{ matrix.language }})
-    runs-on: ubuntu-latest
-    timeout-minutes: 30
-    strategy:
-      fail-fast: false
-      matrix:
-        language: [python, javascript-typescript]
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v4
-
-      - name: Initialize CodeQL
-        uses: github/codeql-action/init@v3
-        with:
-          languages: ${{ matrix.language }}
-          queries: +security-extended,security-and-quality
-
-      - name: Autobuild
-        uses: github/codeql-action/autobuild@v3
-
-      - name: Perform CodeQL Analysis
-        uses: github/codeql-action/analyze@v3
-        with:
-          category: "/language:${{ matrix.language }}"
-
-  python-security:
-    name: Python Security (Bandit)
-    runs-on: ubuntu-latest
-    timeout-minutes: 10
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v4
-
-      - name: Set up Python
-        uses: actions/setup-python@v5
-        with:
-          python-version: '3.12'
-
-      - name: Install Bandit
-        run: pip install bandit
-
-      - name: Run Bandit security scan
-        id: bandit
-        run: |
-          echo "::group::Running Bandit security scan"
-          # Run Bandit; exit code 1 means issues found (expected), other codes are errors
-          # Flags: -r=recursive, -ll=severity LOW+, -ii=confidence LOW+, -f=format, -o=output
-          bandit -r apps/backend/ -ll -ii -f json -o bandit-report.json || BANDIT_EXIT=$?
-          if [ "${BANDIT_EXIT:-0}" -gt 1 ]; then
-            echo "::error::Bandit scan failed with exit code $BANDIT_EXIT"
-            exit 1
-          fi
-          echo "::endgroup::"
-
-      - name: Analyze Bandit results
-        uses: actions/github-script@v7
-        with:
-          script: |
-            const fs = require('fs');
-
-            // Check if report exists
-            if (!fs.existsSync('bandit-report.json')) {
-              core.setFailed('Bandit report not found - scan may have failed');
-              return;
-            }
-
-            const report = JSON.parse(fs.readFileSync('bandit-report.json', 'utf8'));
-            const results = report.results || [];
-
-            // Categorize by severity
-            const high = results.filter(r => r.issue_severity === 'HIGH');
-            const medium = results.filter(r => r.issue_severity === 'MEDIUM');
-            const low = results.filter(r => r.issue_severity === 'LOW');
-
-            console.log(`::group::Bandit Security Scan Results`);
-            console.log(`Found ${results.length} issues:`);
-            console.log(`  🔴 HIGH:   ${high.length}`);
-            console.log(`  🟡 MEDIUM: ${medium.length}`);
-            console.log(`  🟢 LOW:    ${low.length}`);
-            console.log('');
-
-            // Print high severity issues
-            if (high.length > 0) {
-              console.log('High Severity Issues:');
-              console.log('─'.repeat(60));
-              for (const issue of high) {
-                console.log(`  ${issue.filename}:${issue.line_number}`);
-                console.log(`    ${issue.issue_text}`);
-                console.log(`    Test: ${issue.test_id} (${issue.test_name})`);
-                console.log('');
-              }
-            }
-            console.log('::endgroup::');
-
-            // Build summary
-            let summary = `## 🔒 Python Security Scan (Bandit)\n\n`;
-            summary += `| Severity | Count |\n`;
-            summary += `|----------|-------|\n`;
-            summary += `| 🔴 High | ${high.length} |\n`;
-            summary += `| 🟡 Medium | ${medium.length} |\n`;
-            summary += `| 🟢 Low | ${low.length} |\n\n`;
-
-            if (high.length > 0) {
-              summary += `### High Severity Issues\n\n`;
-              for (const issue of high) {
-                summary += `- **${issue.filename}:${issue.line_number}**\n`;
-                summary += `  - ${issue.issue_text}\n`;
-                summary += `  - Test: \`${issue.test_id}\` (${issue.test_name})\n\n`;
-              }
-            }
-
-            core.summary.addRaw(summary);
-            await core.summary.write();
-
-            // Fail if high severity issues found
-            if (high.length > 0) {
-              core.setFailed(`Found ${high.length} high severity security issue(s)`);
-            } else {
-              console.log('✅ No high severity security issues found');
-            }
-
-  # Summary job that waits for all security checks
-  security-summary:
-    name: Security Summary
-    runs-on: ubuntu-latest
-    needs: [codeql, python-security]
-    if: always()
-    timeout-minutes: 5
-    steps:
-      - name: Check security results
-        uses: actions/github-script@v7
-        with:
-          script: |
-            const codeql = '${{ needs.codeql.result }}';
-            const bandit = '${{ needs.python-security.result }}';
-
-            console.log('Security Check Results:');
-            console.log(`  CodeQL:        ${codeql}`);
-            console.log(`  Bandit:        ${bandit}`);
-
-            // Only 'failure' is a real failure; 'skipped' is acceptable (e.g., path filters)
-            const acceptable = ['success', 'skipped'];
-            const codeqlOk = acceptable.includes(codeql);
-            const banditOk = acceptable.includes(bandit);
-            const allPassed = codeqlOk && banditOk;
-
-            if (allPassed) {
-              console.log('\n✅ All security checks passed');
-              core.summary.addRaw('## ✅ Security Checks Passed\n\nAll security scans completed successfully.');
-            } else {
-              console.log('\n❌ Some security checks failed');
-              core.summary.addRaw('## ❌ Security Checks Failed\n\nOne or more security scans found issues.');
-              core.setFailed('Security checks failed');
-            }
-
-            await core.summary.write();

.github/workflows/release.yml

@@ -1,5 +1,4 @@
 name: Release
-# Triggers on version tags (v*) to build and publish releases
 
 on:
   push:
@@ -21,64 +20,38 @@ jobs:
     steps:
       - uses: actions/checkout@v4
 
-      - name: Setup Python
-        uses: actions/setup-python@v5
-        with:
-          python-version: '3.11'
-
       - name: Setup Node.js
         uses: actions/setup-node@v4
         with:
-          node-version: '24'
+          node-version: '20'
 
-      - name: Get npm cache directory
-        id: npm-cache
-        run: echo "dir=$(npm config get cache)" >> $GITHUB_OUTPUT
+      - name: Setup pnpm
+        uses: pnpm/action-setup@v4
+        with:
+          version: 10
+
+      - name: Get pnpm store directory
+        id: pnpm-cache
+        run: echo "dir=$(pnpm store path)" >> $GITHUB_OUTPUT
 
       - uses: actions/cache@v4
         with:
-          path: ${{ steps.npm-cache.outputs.dir }}
-          key: ${{ runner.os }}-npm-${{ hashFiles('**/package-lock.json') }}
-          restore-keys: ${{ runner.os }}-npm-
+          path: ${{ steps.pnpm-cache.outputs.dir }}
+          key: ${{ runner.os }}-x64-pnpm-${{ hashFiles('**/pnpm-lock.yaml') }}
+          restore-keys: ${{ runner.os }}-x64-pnpm-
 
       - name: Install dependencies
-        run: cd apps/frontend && npm ci
-
-      - name: Install Rust toolchain (for building native Python packages)
-        uses: dtolnay/rust-toolchain@stable
-
-      - name: Cache pip wheel cache (for compiled packages like real_ladybug)
-        uses: actions/cache@v4
-        with:
-          path: ~/Library/Caches/pip
-          key: pip-wheel-${{ runner.os }}-x64-${{ hashFiles('apps/backend/requirements.txt') }}
-          restore-keys: |
-            pip-wheel-${{ runner.os }}-x64-
-
-      - name: Cache bundled Python
-        uses: actions/cache@v4
-        with:
-          path: apps/frontend/python-runtime
-          key: python-bundle-${{ runner.os }}-x64-3.12.8-rust-${{ hashFiles('apps/backend/requirements.txt') }}
-          restore-keys: |
-            python-bundle-${{ runner.os }}-x64-3.12.8-rust-
+        run: cd auto-claude-ui && pnpm install --frozen-lockfile
 
       - name: Build application
-        run: cd apps/frontend && npm run build
-        env:
-          SENTRY_DSN: ${{ secrets.SENTRY_DSN }}
-          SENTRY_TRACES_SAMPLE_RATE: ${{ secrets.SENTRY_TRACES_SAMPLE_RATE }}
-          SENTRY_PROFILES_SAMPLE_RATE: ${{ secrets.SENTRY_PROFILES_SAMPLE_RATE }}
+        run: cd auto-claude-ui && pnpm run build
 
       - name: Package macOS (Intel)
-        run: cd apps/frontend && npm run package:mac -- --x64
+        run: cd auto-claude-ui && pnpm run package:mac -- --arch=x64 -p never
         env:
           GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
           CSC_LINK: ${{ secrets.MAC_CERTIFICATE }}
           CSC_KEY_PASSWORD: ${{ secrets.MAC_CERTIFICATE_PASSWORD }}
-          SENTRY_DSN: ${{ secrets.SENTRY_DSN }}
-          SENTRY_TRACES_SAMPLE_RATE: ${{ secrets.SENTRY_TRACES_SAMPLE_RATE }}
-          SENTRY_PROFILES_SAMPLE_RATE: ${{ secrets.SENTRY_PROFILES_SAMPLE_RATE }}
 
       - name: Notarize macOS Intel app
         env:
@@ -90,7 +63,7 @@ jobs:
             echo "Skipping notarization: APPLE_ID not configured"
             exit 0
           fi
-          cd apps/frontend
+          cd auto-claude-ui
           for dmg in dist/*.dmg; do
             echo "Notarizing $dmg..."
             xcrun notarytool submit "$dmg" \
@@ -107,10 +80,8 @@ jobs:
         with:
           name: macos-intel-builds
           path: |
-            apps/frontend/dist/*.dmg
-            apps/frontend/dist/*.zip
-            apps/frontend/dist/*.yml
-            apps/frontend/dist/*.blockmap
+            auto-claude-ui/dist/*.dmg
+            auto-claude-ui/dist/*.zip
 
   # Apple Silicon build on ARM64 runner for native compilation
   build-macos-arm64:
@@ -118,61 +89,38 @@ jobs:
     steps:
       - uses: actions/checkout@v4
 
-      - name: Setup Python
-        uses: actions/setup-python@v5
-        with:
-          python-version: '3.11'
-
       - name: Setup Node.js
         uses: actions/setup-node@v4
         with:
-          node-version: '24'
+          node-version: '20'
 
-      - name: Get npm cache directory
-        id: npm-cache
-        run: echo "dir=$(npm config get cache)" >> $GITHUB_OUTPUT
+      - name: Setup pnpm
+        uses: pnpm/action-setup@v4
+        with:
+          version: 10
+
+      - name: Get pnpm store directory
+        id: pnpm-cache
+        run: echo "dir=$(pnpm store path)" >> $GITHUB_OUTPUT
 
       - uses: actions/cache@v4
         with:
-          path: ${{ steps.npm-cache.outputs.dir }}
-          key: ${{ runner.os }}-npm-${{ hashFiles('**/package-lock.json') }}
-          restore-keys: ${{ runner.os }}-npm-
+          path: ${{ steps.pnpm-cache.outputs.dir }}
+          key: ${{ runner.os }}-arm64-pnpm-${{ hashFiles('**/pnpm-lock.yaml') }}
+          restore-keys: ${{ runner.os }}-arm64-pnpm-
 
       - name: Install dependencies
-        run: cd apps/frontend && npm ci
-
-      - name: Cache pip wheel cache
-        uses: actions/cache@v4
-        with:
-          path: ~/Library/Caches/pip
-          key: pip-wheel-${{ runner.os }}-arm64-${{ hashFiles('apps/backend/requirements.txt') }}
-          restore-keys: |
-            pip-wheel-${{ runner.os }}-arm64-
-
-      - name: Cache bundled Python
-        uses: actions/cache@v4
-        with:
-          path: apps/frontend/python-runtime
-          key: python-bundle-${{ runner.os }}-arm64-3.12.8-${{ hashFiles('apps/backend/requirements.txt') }}
-          restore-keys: |
-            python-bundle-${{ runner.os }}-arm64-3.12.8-
+        run: cd auto-claude-ui && pnpm install --frozen-lockfile
 
       - name: Build application
-        run: cd apps/frontend && npm run build
-        env:
-          SENTRY_DSN: ${{ secrets.SENTRY_DSN }}
-          SENTRY_TRACES_SAMPLE_RATE: ${{ secrets.SENTRY_TRACES_SAMPLE_RATE }}
-          SENTRY_PROFILES_SAMPLE_RATE: ${{ secrets.SENTRY_PROFILES_SAMPLE_RATE }}
+        run: cd auto-claude-ui && pnpm run build
 
       - name: Package macOS (Apple Silicon)
-        run: cd apps/frontend && npm run package:mac -- --arm64
+        run: cd auto-claude-ui && pnpm run package:mac -- --arch=arm64 -p never
         env:
           GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
           CSC_LINK: ${{ secrets.MAC_CERTIFICATE }}
           CSC_KEY_PASSWORD: ${{ secrets.MAC_CERTIFICATE_PASSWORD }}
-          SENTRY_DSN: ${{ secrets.SENTRY_DSN }}
-          SENTRY_TRACES_SAMPLE_RATE: ${{ secrets.SENTRY_TRACES_SAMPLE_RATE }}
-          SENTRY_PROFILES_SAMPLE_RATE: ${{ secrets.SENTRY_PROFILES_SAMPLE_RATE }}
 
       - name: Notarize macOS ARM64 app
         env:
@@ -184,7 +132,7 @@ jobs:
             echo "Skipping notarization: APPLE_ID not configured"
             exit 0
           fi
-          cd apps/frontend
+          cd auto-claude-ui
           for dmg in dist/*.dmg; do
             echo "Notarizing $dmg..."
             xcrun notarytool submit "$dmg" \
@@ -201,276 +149,98 @@ jobs:
         with:
           name: macos-arm64-builds
           path: |
-            apps/frontend/dist/*.dmg
-            apps/frontend/dist/*.zip
-            apps/frontend/dist/*.yml
-            apps/frontend/dist/*.blockmap
+            auto-claude-ui/dist/*.dmg
+            auto-claude-ui/dist/*.zip
 
   build-windows:
     runs-on: windows-latest
-    permissions:
-      id-token: write  # Required for OIDC authentication with Azure
-      contents: read
-    env:
-      # Job-level env so AZURE_CLIENT_ID is available for step-level if conditions
-      AZURE_CLIENT_ID: ${{ secrets.AZURE_CLIENT_ID }}
     steps:
       - uses: actions/checkout@v4
 
-      - name: Setup Python
-        uses: actions/setup-python@v5
-        with:
-          python-version: '3.11'
-
       - name: Setup Node.js
         uses: actions/setup-node@v4
         with:
-          node-version: '24'
+          node-version: '20'
 
-      - name: Get npm cache directory
-        id: npm-cache
+      - name: Setup pnpm
+        uses: pnpm/action-setup@v4
+        with:
+          version: 10
+
+      - name: Get pnpm store directory
+        id: pnpm-cache
         shell: bash
-        run: echo "dir=$(npm config get cache)" >> $GITHUB_OUTPUT
+        run: echo "dir=$(pnpm store path)" >> $GITHUB_OUTPUT
 
       - uses: actions/cache@v4
         with:
-          path: ${{ steps.npm-cache.outputs.dir }}
-          key: ${{ runner.os }}-npm-${{ hashFiles('**/package-lock.json') }}
-          restore-keys: ${{ runner.os }}-npm-
+          path: ${{ steps.pnpm-cache.outputs.dir }}
+          key: ${{ runner.os }}-pnpm-${{ hashFiles('**/pnpm-lock.yaml') }}
+          restore-keys: ${{ runner.os }}-pnpm-
 
       - name: Install dependencies
-        run: cd apps/frontend && npm ci
-
-      - name: Cache pip wheel cache
-        uses: actions/cache@v4
-        with:
-          path: ~\AppData\Local\pip\Cache
-          key: pip-wheel-${{ runner.os }}-x64-${{ hashFiles('apps/backend/requirements.txt') }}
-          restore-keys: |
-            pip-wheel-${{ runner.os }}-x64-
-
-      - name: Cache bundled Python
-        uses: actions/cache@v4
-        with:
-          path: apps/frontend/python-runtime
-          key: python-bundle-${{ runner.os }}-x64-3.12.8-${{ hashFiles('apps/backend/requirements.txt') }}
-          restore-keys: |
-            python-bundle-${{ runner.os }}-x64-3.12.8-
+        run: cd auto-claude-ui && pnpm install --frozen-lockfile
 
       - name: Build application
-        run: cd apps/frontend && npm run build
-        env:
-          SENTRY_DSN: ${{ secrets.SENTRY_DSN }}
-          SENTRY_TRACES_SAMPLE_RATE: ${{ secrets.SENTRY_TRACES_SAMPLE_RATE }}
-          SENTRY_PROFILES_SAMPLE_RATE: ${{ secrets.SENTRY_PROFILES_SAMPLE_RATE }}
+        run: cd auto-claude-ui && pnpm run build
 
       - name: Package Windows
-        run: cd apps/frontend && npm run package:win
+        run: cd auto-claude-ui && pnpm run package:win -- -p never
         env:
           GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-          # Disable electron-builder's built-in signing (we use Azure Trusted Signing instead)
-          CSC_IDENTITY_AUTO_DISCOVERY: false
-          SENTRY_DSN: ${{ secrets.SENTRY_DSN }}
-          SENTRY_TRACES_SAMPLE_RATE: ${{ secrets.SENTRY_TRACES_SAMPLE_RATE }}
-          SENTRY_PROFILES_SAMPLE_RATE: ${{ secrets.SENTRY_PROFILES_SAMPLE_RATE }}
-
-      - name: Azure Login (OIDC)
-        if: env.AZURE_CLIENT_ID != ''
-        uses: azure/login@v2
-        with:
-          client-id: ${{ secrets.AZURE_CLIENT_ID }}
-          tenant-id: ${{ secrets.AZURE_TENANT_ID }}
-          subscription-id: ${{ secrets.AZURE_SUBSCRIPTION_ID }}
-
-      - name: Sign Windows executable with Azure Trusted Signing
-        if: env.AZURE_CLIENT_ID != ''
-        uses: azure/trusted-signing-action@v0.5.11
-        with:
-          endpoint: https://neu.codesigning.azure.net/
-          trusted-signing-account-name: ${{ secrets.AZURE_SIGNING_ACCOUNT }}
-          certificate-profile-name: ${{ secrets.AZURE_CERTIFICATE_PROFILE }}
-          files-folder: apps/frontend/dist
-          files-folder-filter: exe
-          file-digest: SHA256
-          timestamp-rfc3161: http://timestamp.acs.microsoft.com
-          timestamp-digest: SHA256
-
-      - name: Verify Windows executable is signed
-        if: env.AZURE_CLIENT_ID != ''
-        shell: pwsh
-        run: |
-          cd apps/frontend/dist
-          $exeFile = Get-ChildItem -Filter "*.exe" | Select-Object -First 1
-          if ($exeFile) {
-            Write-Host "Verifying signature on $($exeFile.Name)..."
-            $sig = Get-AuthenticodeSignature -FilePath $exeFile.FullName
-            if ($sig.Status -ne 'Valid') {
-              Write-Host "::error::Signature verification failed: $($sig.Status)"
-              Write-Host "::error::Status Message: $($sig.StatusMessage)"
-              exit 1
-            }
-            Write-Host "✅ Signature verified successfully"
-            Write-Host "  Subject: $($sig.SignerCertificate.Subject)"
-            Write-Host "  Issuer: $($sig.SignerCertificate.Issuer)"
-            Write-Host "  Thumbprint: $($sig.SignerCertificate.Thumbprint)"
-          } else {
-            Write-Host "::error::No .exe file found to verify"
-            exit 1
-          }
-
-      - name: Regenerate checksums after signing
-        if: env.AZURE_CLIENT_ID != ''
-        shell: pwsh
-        run: |
-          $ErrorActionPreference = "Stop"
-          cd apps/frontend/dist
-
-          # Find the installer exe (electron-builder names it with "Setup" or just the app name)
-          # electron-builder produces one installer exe per build
-          $exeFiles = Get-ChildItem -Filter "*.exe"
-          if ($exeFiles.Count -eq 0) {
-            Write-Host "::error::No .exe files found in dist folder"
-            exit 1
-          }
-
-          Write-Host "Found $($exeFiles.Count) exe file(s): $($exeFiles.Name -join ', ')"
-
-          $ymlFile = "latest.yml"
-          if (-not (Test-Path $ymlFile)) {
-            Write-Host "::error::$ymlFile not found - cannot update checksums"
-            exit 1
-          }
-
-          $content = Get-Content $ymlFile -Raw
-          $originalContent = $content
-
-          # Process each exe file and update its hash in latest.yml
-          foreach ($exeFile in $exeFiles) {
-            Write-Host "Processing $($exeFile.Name)..."
-
-            # Compute SHA512 hash and convert to base64 (electron-builder format)
-            $bytes = [System.IO.File]::ReadAllBytes($exeFile.FullName)
-            $sha512 = [System.Security.Cryptography.SHA512]::Create()
-            $hashBytes = $sha512.ComputeHash($bytes)
-            $hash = [System.Convert]::ToBase64String($hashBytes)
-            $size = $exeFile.Length
-
-            Write-Host "  Hash: $hash"
-            Write-Host "  Size: $size"
-          }
-
-          # For electron-builder, latest.yml has a single file entry for the installer
-          # Update the sha512 and size for the primary exe (first one, typically the installer)
-          $primaryExe = $exeFiles | Select-Object -First 1
-          $bytes = [System.IO.File]::ReadAllBytes($primaryExe.FullName)
-          $sha512 = [System.Security.Cryptography.SHA512]::Create()
-          $hashBytes = $sha512.ComputeHash($bytes)
-          $hash = [System.Convert]::ToBase64String($hashBytes)
-          $size = $primaryExe.Length
-
-          # Update sha512 hash (base64 pattern: alphanumeric, +, /, =)
-          $content = $content -replace 'sha512: [A-Za-z0-9+/=]+', "sha512: $hash"
-          # Update size
-          $content = $content -replace 'size: \d+', "size: $size"
-
-          if ($content -eq $originalContent) {
-            Write-Host "::error::Checksum replacement failed - content unchanged. Check if latest.yml format has changed."
-            exit 1
-          }
-
-          Set-Content -Path $ymlFile -Value $content -NoNewline
-          Write-Host "✅ Updated $ymlFile with new base64 hash and size for $($primaryExe.Name)"
-
-      - name: Skip signing notice
-        if: env.AZURE_CLIENT_ID == ''
-        run: echo "::warning::Windows signing skipped - AZURE_CLIENT_ID not configured. The .exe will be unsigned."
+          CSC_LINK: ${{ secrets.WIN_CERTIFICATE }}
+          CSC_KEY_PASSWORD: ${{ secrets.WIN_CERTIFICATE_PASSWORD }}
 
       - name: Upload artifacts
         uses: actions/upload-artifact@v4
         with:
           name: windows-builds
           path: |
-            apps/frontend/dist/*.exe
-            apps/frontend/dist/*.yml
-            apps/frontend/dist/*.blockmap
+            auto-claude-ui/dist/*.exe
 
   build-linux:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v4
 
-      - name: Setup Python
-        uses: actions/setup-python@v5
-        with:
-          python-version: '3.11'
-
       - name: Setup Node.js
         uses: actions/setup-node@v4
         with:
-          node-version: '24'
+          node-version: '20'
 
-      - name: Get npm cache directory
-        id: npm-cache
-        run: echo "dir=$(npm config get cache)" >> $GITHUB_OUTPUT
+      - name: Setup pnpm
+        uses: pnpm/action-setup@v4
+        with:
+          version: 10
+
+      - name: Get pnpm store directory
+        id: pnpm-cache
+        run: echo "dir=$(pnpm store path)" >> $GITHUB_OUTPUT
 
       - uses: actions/cache@v4
         with:
-          path: ${{ steps.npm-cache.outputs.dir }}
-          key: ${{ runner.os }}-npm-${{ hashFiles('**/package-lock.json') }}
-          restore-keys: ${{ runner.os }}-npm-
+          path: ${{ steps.pnpm-cache.outputs.dir }}
+          key: ${{ runner.os }}-pnpm-${{ hashFiles('**/pnpm-lock.yaml') }}
+          restore-keys: ${{ runner.os }}-pnpm-
 
       - name: Install dependencies
-        run: cd apps/frontend && npm ci
-
-      - name: Setup Flatpak
-        run: |
-          sudo apt-get update
-          sudo apt-get install -y flatpak flatpak-builder
-          flatpak remote-add --user --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepo
-          flatpak install -y --user flathub org.freedesktop.Platform//25.08 org.freedesktop.Sdk//25.08
-          flatpak install -y --user flathub org.electronjs.Electron2.BaseApp//25.08
-
-      - name: Cache pip wheel cache
-        uses: actions/cache@v4
-        with:
-          path: ~/.cache/pip
-          key: pip-wheel-${{ runner.os }}-x64-${{ hashFiles('apps/backend/requirements.txt') }}
-          restore-keys: |
-            pip-wheel-${{ runner.os }}-x64-
-
-      - name: Cache bundled Python
-        uses: actions/cache@v4
-        with:
-          path: apps/frontend/python-runtime
-          key: python-bundle-${{ runner.os }}-x64-3.12.8-${{ hashFiles('apps/backend/requirements.txt') }}
-          restore-keys: |
-            python-bundle-${{ runner.os }}-x64-3.12.8-
+        run: cd auto-claude-ui && pnpm install --frozen-lockfile
 
       - name: Build application
-        run: cd apps/frontend && npm run build
-        env:
-          SENTRY_DSN: ${{ secrets.SENTRY_DSN }}
-          SENTRY_TRACES_SAMPLE_RATE: ${{ secrets.SENTRY_TRACES_SAMPLE_RATE }}
-          SENTRY_PROFILES_SAMPLE_RATE: ${{ secrets.SENTRY_PROFILES_SAMPLE_RATE }}
+        run: cd auto-claude-ui && pnpm run build
 
       - name: Package Linux
-        run: cd apps/frontend && npm run package:linux
+        run: cd auto-claude-ui && pnpm run package:linux -- -p never
         env:
           GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-          SENTRY_DSN: ${{ secrets.SENTRY_DSN }}
-          SENTRY_TRACES_SAMPLE_RATE: ${{ secrets.SENTRY_TRACES_SAMPLE_RATE }}
-          SENTRY_PROFILES_SAMPLE_RATE: ${{ secrets.SENTRY_PROFILES_SAMPLE_RATE }}
 
       - name: Upload artifacts
         uses: actions/upload-artifact@v4
         with:
           name: linux-builds
           path: |
-            apps/frontend/dist/*.AppImage
-            apps/frontend/dist/*.deb
-            apps/frontend/dist/*.flatpak
-            apps/frontend/dist/*.yml
-            apps/frontend/dist/*.blockmap
+            auto-claude-ui/dist/*.AppImage
+            auto-claude-ui/dist/*.deb
 
   create-release:
     needs: [build-macos-intel, build-macos-arm64, build-windows, build-linux]
@@ -490,30 +260,16 @@ jobs:
       - name: Flatten and validate artifacts
         run: |
           mkdir -p release-assets
-          find dist -type f \( -name "*.dmg" -o -name "*.zip" -o -name "*.exe" -o -name "*.AppImage" -o -name "*.deb" -o -name "*.flatpak" -o -name "*.yml" -o -name "*.blockmap" \) -exec cp {} release-assets/ \;
+          find dist -type f \( -name "*.dmg" -o -name "*.zip" -o -name "*.exe" -o -name "*.AppImage" -o -name "*.deb" \) -exec cp {} release-assets/ \;
 
-          # Validate that installer files exist (not just manifests)
-          installer_count=$(find release-assets -type f \( -name "*.dmg" -o -name "*.zip" -o -name "*.exe" -o -name "*.AppImage" -o -name "*.deb" -o -name "*.flatpak" \) | wc -l)
-          if [ "$installer_count" -eq 0 ]; then
-            echo "::error::No installer artifacts found! Expected .dmg, .zip, .exe, .AppImage, .deb, or .flatpak files."
+          # Validate that at least one artifact was copied
+          artifact_count=$(find release-assets -type f \( -name "*.dmg" -o -name "*.zip" -o -name "*.exe" -o -name "*.AppImage" -o -name "*.deb" \) | wc -l)
+          if [ "$artifact_count" -eq 0 ]; then
+            echo "::error::No build artifacts found! Expected .dmg, .zip, .exe, .AppImage, or .deb files."
             exit 1
           fi
 
-          echo "Found $installer_count installer(s):"
-          find release-assets -type f \( -name "*.dmg" -o -name "*.zip" -o -name "*.exe" -o -name "*.AppImage" -o -name "*.deb" -o -name "*.flatpak" \) -exec basename {} \;
-
-          # Validate that electron-updater manifest files are present (required for auto-updates)
-          yml_count=$(find release-assets -type f -name "*.yml" | wc -l)
-          if [ "$yml_count" -eq 0 ]; then
-            echo "::error::No update manifest (.yml) files found! Auto-update architecture detection will not work."
-            exit 1
-          fi
-
-          echo "Found $yml_count manifest file(s):"
-          find release-assets -type f -name "*.yml" -exec basename {} \;
-
-          echo ""
-          echo "All release assets:"
+          echo "Found $artifact_count artifact(s):"
           ls -la release-assets/
 
       - name: Generate checksums
@@ -522,6 +278,144 @@ jobs:
           sha256sum ./* > checksums.sha256
           cat checksums.sha256
 
+      - name: Scan with VirusTotal
+        id: virustotal
+        continue-on-error: true
+        if: ${{ github.event_name == 'push' || (github.event_name == 'workflow_dispatch' && inputs.dry_run != true) }}
+        env:
+          VT_API_KEY: ${{ secrets.VIRUSTOTAL_API_KEY }}
+        run: |
+          if [ -z "$VT_API_KEY" ]; then
+            echo "::warning::VIRUSTOTAL_API_KEY not configured, skipping scan"
+            echo "vt_results=" >> $GITHUB_OUTPUT
+            exit 0
+          fi
+
+          echo "## VirusTotal Scan Results" > vt_results.md
+          echo "" >> vt_results.md
+
+          for file in release-assets/*.{exe,dmg,AppImage,deb}; do
+            [ -f "$file" ] || continue
+            filename=$(basename "$file")
+            filesize=$(stat -c%s "$file" 2>/dev/null || stat -f%z "$file")
+            echo "Scanning $filename (${filesize} bytes)..."
+
+            # For files > 32MB, get a special upload URL first
+            if [ "$filesize" -gt 33554432 ]; then
+              echo "  Large file detected, requesting upload URL..."
+              upload_url_response=$(curl -s --request GET \
+                --url "https://www.virustotal.com/api/v3/files/upload_url" \
+                --header "x-apikey: $VT_API_KEY")
+
+              upload_url=$(echo "$upload_url_response" | jq -r '.data // empty')
+              if [ -z "$upload_url" ]; then
+                echo "::warning::Failed to get upload URL for large file $filename"
+                echo "Response: $upload_url_response"
+                echo "- $filename - ⚠️ Upload failed (large file)" >> vt_results.md
+                continue
+              fi
+              api_url="$upload_url"
+            else
+              api_url="https://www.virustotal.com/api/v3/files"
+            fi
+
+            # Upload file to VirusTotal
+            response=$(curl -s --request POST \
+              --url "$api_url" \
+              --header "x-apikey: $VT_API_KEY" \
+              --form "file=@$file")
+
+            # Check if response is valid JSON before parsing
+            if ! echo "$response" | jq -e . >/dev/null 2>&1; then
+              echo "::warning::VirusTotal returned invalid JSON for $filename"
+              echo "Response (first 500 chars): ${response:0:500}"
+              echo "- $filename - ⚠️ Scan failed (invalid response)" >> vt_results.md
+              continue
+            fi
+
+            # Check for API error response
+            error_code=$(echo "$response" | jq -r '.error.code // empty')
+            if [ -n "$error_code" ]; then
+              error_msg=$(echo "$response" | jq -r '.error.message // "Unknown error"')
+              echo "::warning::VirusTotal API error for $filename: $error_code - $error_msg"
+              echo "- $filename - ⚠️ Scan failed ($error_code)" >> vt_results.md
+              continue
+            fi
+
+            # Extract analysis ID
+            analysis_id=$(echo "$response" | jq -r '.data.id // empty')
+
+            if [ -z "$analysis_id" ]; then
+              echo "::warning::Failed to upload $filename to VirusTotal"
+              echo "Response: $response"
+              echo "- $filename - ⚠️ Upload failed" >> vt_results.md
+              continue
+            fi
+
+            echo "Uploaded $filename, analysis ID: $analysis_id"
+
+            # Wait for analysis to complete (max 5 minutes per file)
+            analysis=""
+            for i in {1..30}; do
+              sleep 10
+              analysis=$(curl -s --request GET \
+                --url "https://www.virustotal.com/api/v3/analyses/$analysis_id" \
+                --header "x-apikey: $VT_API_KEY")
+
+              # Validate JSON response
+              if ! echo "$analysis" | jq -e . >/dev/null 2>&1; then
+                echo "  Warning: Invalid JSON response on attempt $i, retrying..."
+                continue
+              fi
+
+              status=$(echo "$analysis" | jq -r '.data.attributes.status // "unknown"')
+              echo "  Status: $status (attempt $i/30)"
+
+              if [ "$status" = "completed" ]; then
+                break
+              fi
+            done
+
+            # Final validation that we have valid analysis data
+            if ! echo "$analysis" | jq -e '.data.attributes.stats' >/dev/null 2>&1; then
+              echo "::warning::Could not get complete analysis for $filename, using local hash"
+              file_hash=$(sha256sum "$file" | cut -d' ' -f1)
+              echo "- [$filename](https://www.virustotal.com/gui/file/$file_hash) - ⚠️ Analysis incomplete" >> vt_results.md
+              continue
+            fi
+
+            # Get file hash for permanent URL
+            file_hash=$(echo "$analysis" | jq -r '.meta.file_info.sha256 // empty')
+
+            if [ -z "$file_hash" ]; then
+              # Fallback: calculate hash locally
+              file_hash=$(sha256sum "$file" | cut -d' ' -f1)
+            fi
+
+            # Get detection stats
+            malicious=$(echo "$analysis" | jq -r '.data.attributes.stats.malicious // 0')
+            suspicious=$(echo "$analysis" | jq -r '.data.attributes.stats.suspicious // 0')
+            undetected=$(echo "$analysis" | jq -r '.data.attributes.stats.undetected // 0')
+
+            vt_url="https://www.virustotal.com/gui/file/$file_hash"
+
+            if [ "$malicious" -gt 0 ] || [ "$suspicious" -gt 0 ]; then
+              echo "::warning::$filename has $malicious malicious and $suspicious suspicious detections (likely false positives)"
+              echo "- [$filename]($vt_url) - ⚠️ **$malicious malicious, $suspicious suspicious** detections (review recommended)" >> vt_results.md
+            else
+              echo "$filename is clean ($undetected engines, 0 detections)"
+              echo "- [$filename]($vt_url) - ✅ Clean ($undetected engines, 0 detections)" >> vt_results.md
+            fi
+          done
+
+          echo "" >> vt_results.md
+
+          # Save results for release notes
+          cat vt_results.md
+          echo "vt_results<<EOF" >> $GITHUB_OUTPUT
+          cat vt_results.md >> $GITHUB_OUTPUT
+          echo "EOF" >> $GITHUB_OUTPUT
+
       - name: Dry run summary
         if: ${{ github.event_name == 'workflow_dispatch' && inputs.dry_run == true }}
         run: |
@@ -535,219 +429,25 @@ jobs:
           cat release-assets/checksums.sha256 >> $GITHUB_STEP_SUMMARY
           echo "\`\`\`" >> $GITHUB_STEP_SUMMARY
 
-      - name: Extract changelog from CHANGELOG.md
-        if: ${{ github.event_name == 'push' }}
+      - name: Generate changelog
+        if: ${{ github.event_name == 'push' || (github.event_name == 'workflow_dispatch' && inputs.dry_run != true) }}
         id: changelog
-        run: |
-          # Extract version from tag (v2.7.2 -> 2.7.2)
-          VERSION=${GITHUB_REF_NAME#v}
-          CHANGELOG_FILE="CHANGELOG.md"
-
-          echo "📋 Extracting release notes for version $VERSION from CHANGELOG.md..."
-
-          if [ ! -f "$CHANGELOG_FILE" ]; then
-            echo "::warning::CHANGELOG.md not found, using minimal release notes"
-            echo "body=Release v$VERSION" >> $GITHUB_OUTPUT
-            exit 0
-          fi
-
-          # Extract changelog section for this version
-          # Looks for "## X.Y.Z" header and captures until next "## " or "---"
-          CHANGELOG_CONTENT=$(awk -v ver="$VERSION" '
-            BEGIN { found=0; content="" }
-            /^## / {
-              if (found) exit
-              # Match version at start of header (e.g., "## 2.7.3 -" or "## 2.7.3")
-              if ($2 == ver || $2 ~ "^"ver"[[:space:]]*-") {
-                found=1
-                next
-              }
-            }
-            /^---$/ { if (found) exit }
-            found { content = content $0 "\n" }
-            END {
-              if (!found) {
-                print "NOT_FOUND"
-                exit 0
-              }
-              # Trim leading/trailing whitespace
-              gsub(/^[[:space:]]+|[[:space:]]+$/, "", content)
-              print content
-            }
-          ' "$CHANGELOG_FILE")
-
-          if [ "$CHANGELOG_CONTENT" = "NOT_FOUND" ] || [ -z "$CHANGELOG_CONTENT" ]; then
-            echo "::warning::Version $VERSION not found in CHANGELOG.md, using minimal release notes"
-            REPO="${{ github.repository }}"
-            CHANGELOG_CONTENT="Release v$VERSION"$'\n\n'"See [CHANGELOG.md](https://github.com/${REPO}/blob/main/CHANGELOG.md) for details."
-          fi
-
-          echo "✅ Extracted changelog content"
-
-          # Save to file first (more reliable for multiline)
-          echo "$CHANGELOG_CONTENT" > changelog-body.md
-
-          # Use file-based output for multiline content
-          {
-            echo "body<<CHANGELOG_EOF"
-            cat changelog-body.md
-            echo "CHANGELOG_EOF"
-          } >> $GITHUB_OUTPUT
+        uses: release-drafter/release-drafter@v6
+        with:
+          config-name: release-drafter.yml
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
 
       - name: Create Release
-        if: ${{ github.event_name == 'push' }}
+        if: ${{ github.event_name == 'push' || (github.event_name == 'workflow_dispatch' && inputs.dry_run != true) }}
         uses: softprops/action-gh-release@v2
         with:
           body: |
             ${{ steps.changelog.outputs.body }}
 
-            ---
-
-            **Full Changelog**: https://github.com/${{ github.repository }}/blob/main/CHANGELOG.md
-
-            _VirusTotal scan results will be added automatically after release._
+            ${{ steps.virustotal.outputs.vt_results }}
           files: release-assets/*
           draft: false
           prerelease: ${{ contains(github.ref, 'beta') || contains(github.ref, 'alpha') }}
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-
-  # Update README with new version after successful release
-  update-readme:
-    needs: [create-release]
-    runs-on: ubuntu-latest
-    # Only update README on actual releases (tag push), not dry runs
-    if: ${{ github.event_name == 'push' }}
-    permissions:
-      contents: write
-    steps:
-      - uses: actions/checkout@v4
-        with:
-          ref: main
-          token: ${{ secrets.GITHUB_TOKEN }}
-
-      - name: Extract version and detect release type
-        id: version
-        run: |
-          # Extract version from tag (v2.7.2 -> 2.7.2)
-          VERSION=${GITHUB_REF_NAME#v}
-          echo "version=$VERSION" >> $GITHUB_OUTPUT
-
-          # Detect if this is a prerelease (contains - after version, e.g., 2.7.2-beta.10)
-          if [[ "$VERSION" == *-* ]]; then
-            echo "is_prerelease=true" >> $GITHUB_OUTPUT
-            echo "Detected PRERELEASE: $VERSION"
-          else
-            echo "is_prerelease=false" >> $GITHUB_OUTPUT
-            echo "Detected STABLE release: $VERSION"
-          fi
-
-      - name: Update README.md
-        run: |
-          python3 << 'EOF'
-          import re
-          import sys
-
-          version = "${{ steps.version.outputs.version }}"
-          is_prerelease = "${{ steps.version.outputs.is_prerelease }}" == "true"
-
-          # Shields.io escapes hyphens as --
-          version_badge = version.replace("-", "--")
-
-          # Read README
-          with open("README.md", "r") as f:
-              content = f.read()
-
-          # Semver pattern: matches X.Y.Z or X.Y.Z-prerelease (e.g., 2.7.2, 2.7.2-beta.10)
-          # Prerelease MUST contain a dot (beta.10, alpha.1, rc.1) to avoid matching platform suffixes (win32, darwin)
-          semver = r'\d+\.\d+\.\d+(?:-[a-zA-Z]+\.[a-zA-Z0-9.]+)?'
-          # Shields.io escaped pattern (hyphens as --)
-          semver_badge = r'\d+\.\d+\.\d+(?:--[a-zA-Z]+\.[a-zA-Z0-9.]+)?'
-
-          def update_section(text, start_marker, end_marker, replacements):
-              """Update content between markers with given replacements."""
-              pattern = f'({re.escape(start_marker)})(.*?)({re.escape(end_marker)})'
-              def replace_section(match):
-                  section = match.group(2)
-                  for old_pattern, new_value in replacements:
-                      section = re.sub(old_pattern, new_value, section)
-                  return match.group(1) + section + match.group(3)
-              return re.sub(pattern, replace_section, text, flags=re.DOTALL)
-
-          if is_prerelease:
-              print(f"Updating BETA section to {version} (badge: {version_badge})")
-
-              # Update beta badge
-              content = re.sub(
-                  rf'beta-{semver_badge}-orange',
-                  f'beta-{version_badge}-orange',
-                  content
-              )
-
-              # Update beta version badge link
-              content = update_section(content,
-                  '<!-- BETA_VERSION_BADGE -->', '<!-- BETA_VERSION_BADGE_END -->',
-                  [(rf'tag/v{semver}\)', f'tag/v{version})')])
-
-              # Update beta downloads
-              content = update_section(content,
-                  '<!-- BETA_DOWNLOADS -->', '<!-- BETA_DOWNLOADS_END -->',
-                  [
-                      (rf'Auto-Claude-{semver}', f'Auto-Claude-{version}'),
-                      (rf'download/v{semver}/', f'download/v{version}/'),
-                  ])
-          else:
-              print(f"Updating STABLE section to {version} (badge: {version_badge})")
-
-              # Update top version badge
-              content = update_section(content,
-                  '<!-- TOP_VERSION_BADGE -->', '<!-- TOP_VERSION_BADGE_END -->',
-                  [
-                      (rf'version-{semver_badge}-blue', f'version-{version_badge}-blue'),
-                      (rf'tag/v{semver}\)', f'tag/v{version})'),
-                  ])
-
-              # Update stable badge
-              content = re.sub(
-                  rf'stable-{semver_badge}-blue',
-                  f'stable-{version_badge}-blue',
-                  content
-              )
-
-              # Update stable version badge link
-              content = update_section(content,
-                  '<!-- STABLE_VERSION_BADGE -->', '<!-- STABLE_VERSION_BADGE_END -->',
-                  [(rf'tag/v{semver}\)', f'tag/v{version})')])
-
-              # Update stable downloads
-              content = update_section(content,
-                  '<!-- STABLE_DOWNLOADS -->', '<!-- STABLE_DOWNLOADS_END -->',
-                  [
-                      (rf'Auto-Claude-{semver}', f'Auto-Claude-{version}'),
-                      (rf'download/v{semver}/', f'download/v{version}/'),
-                  ])
-
-          # Write updated README
-          with open("README.md", "w") as f:
-              f.write(content)
-
-          print(f"README.md updated for {version} (prerelease={is_prerelease})")
-          EOF
-
-          echo "--- Verifying update ---"
-          grep -E "(stable-|beta-|version-)[0-9]" README.md | head -5
-
-      - name: Commit and push README update
-        run: |
-          git config user.name "github-actions[bot]"
-          git config user.email "github-actions[bot]@users.noreply.github.com"
-
-          # Check if there are changes to commit
-          if git diff --quiet README.md; then
-            echo "No changes to README.md, skipping commit"
-            exit 0
-          fi
-
-          git add README.md
-          git commit -m "docs: update README to v${{ steps.version.outputs.version }} [skip ci]"
-          git push origin main

.github/workflows/stale.yml

@@ -1,25 +0,0 @@
-name: Stale Issues
-
-on:
-  schedule:
-    - cron: '0 0 * * 0'  # Every Sunday
-  workflow_dispatch:
-
-jobs:
-  stale:
-    runs-on: ubuntu-latest
-    permissions:
-      issues: write
-    steps:
-      - uses: actions/stale@v9
-        with:
-          stale-issue-message: |
-            This issue has been inactive for 60 days. It will be closed in 14 days if there's no activity.
-
-            - If this is still relevant, please comment or update the issue
-            - If you're working on this, add the `in-progress` label
-          close-issue-message: 'Closed due to inactivity. Feel free to reopen if still relevant.'
-          stale-issue-label: 'stale'
-          days-before-stale: 60
-          days-before-close: 14
-          exempt-issue-labels: 'priority/critical,priority/high,in-progress,blocked'

.github/workflows/test-azure-auth.yml

@@ -1,21 +0,0 @@
-name: Test Azure Auth
-
-on:
-  workflow_dispatch:
-
-jobs:
-  test-auth:
-    runs-on: windows-latest
-    permissions:
-      id-token: write
-      contents: read
-    steps:
-      - name: Azure Login (OIDC)
-        uses: azure/login@v2
-        with:
-          client-id: ${{ secrets.AZURE_CLIENT_ID }}
-          tenant-id: ${{ secrets.AZURE_TENANT_ID }}
-          subscription-id: ${{ secrets.AZURE_SUBSCRIPTION_ID }}
-
-      - name: Success
-        run: echo "Azure authentication successful!"

.github/workflows/test-on-tag.yml

@@ -28,19 +28,17 @@ jobs:
           version: "latest"
 
       - name: Install dependencies
-        working-directory: apps/backend
+        working-directory: auto-claude
         run: |
           uv venv
           uv pip install -r requirements.txt
-          uv pip install -r ../../tests/requirements-test.txt
+          uv pip install -r ../tests/requirements-test.txt
 
       - name: Run tests
-        working-directory: apps/backend
-        env:
-          PYTHONPATH: ${{ github.workspace }}/apps/backend
+        working-directory: auto-claude
         run: |
           source .venv/bin/activate
-          pytest ../../tests/ -v --tb=short
+          pytest ../tests/ -v --tb=short
 
   # Frontend tests
   test-frontend:
@@ -52,12 +50,17 @@ jobs:
       - name: Setup Node.js
         uses: actions/setup-node@v4
         with:
-          node-version: '24'
+          node-version: '20'
+
+      - name: Setup pnpm
+        uses: pnpm/action-setup@v4
+        with:
+          version: 9
 
       - name: Install dependencies
-        working-directory: apps/frontend
-        run: npm ci --ignore-scripts
+        working-directory: auto-claude-ui
+        run: pnpm install --frozen-lockfile --ignore-scripts
 
       - name: Run tests
-        working-directory: apps/frontend
-        run: npm run test
+        working-directory: auto-claude-ui
+        run: pnpm test

.github/workflows/validate-version.yml

@@ -26,7 +26,7 @@ jobs:
         id: package_version
         run: |
           # Read version from package.json
-          PACKAGE_VERSION=$(node -p "require('./apps/frontend/package.json').version")
+          PACKAGE_VERSION=$(node -p "require('./auto-claude-ui/package.json').version")
           echo "version=$PACKAGE_VERSION" >> $GITHUB_OUTPUT
           echo "Package.json version: $PACKAGE_VERSION"
 

.github/workflows/virustotal-scan.yml

@@ -1,343 +0,0 @@
-name: VirusTotal Scan
-
-# Runs AFTER release is published to avoid blocking release creation
-# VirusTotal scans can take 5+ minutes per file, which delays releases
-
-on:
-  release:
-    types: [published]
-  workflow_dispatch:
-    inputs:
-      tag:
-        description: 'Release tag to scan (e.g., v2.8.0)'
-        required: true
-        type: string
-
-# Prevent TOCTOU race condition when updating release notes
-# If two runs target the same tag, queue them instead of running in parallel
-concurrency:
-  group: virustotal-${{ github.event.inputs.tag || github.event.release.tag_name }}
-  cancel-in-progress: false
-
-jobs:
-  scan:
-    name: Scan release assets
-    runs-on: ubuntu-latest
-    permissions:
-      contents: write  # Required to update release notes
-    steps:
-      - name: Determine release tag
-        id: tag
-        run: |
-          if [ "${{ github.event_name }}" = "workflow_dispatch" ]; then
-            echo "tag=${{ github.event.inputs.tag }}" >> $GITHUB_OUTPUT
-          else
-            echo "tag=${{ github.event.release.tag_name }}" >> $GITHUB_OUTPUT
-          fi
-
-      - name: Check for API key
-        id: check-key
-        env:
-          VT_KEY: ${{ secrets.VIRUSTOTAL_API_KEY }}
-        run: |
-          if [ -z "$VT_KEY" ]; then
-            echo "::warning::VIRUSTOTAL_API_KEY not configured, skipping scan"
-            echo "has_key=false" >> $GITHUB_OUTPUT
-          else
-            echo "has_key=true" >> $GITHUB_OUTPUT
-          fi
-
-      - name: Download release assets
-        if: steps.check-key.outputs.has_key == 'true'
-        env:
-          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-        run: |
-          TAG="${{ steps.tag.outputs.tag }}"
-          echo "Downloading assets for release $TAG..."
-
-          mkdir -p release-assets
-
-          # First verify the release exists
-          if ! gh release view "$TAG" --repo "${{ github.repository }}" >/dev/null 2>&1; then
-            echo "::error::Release $TAG not found"
-            exit 1
-          fi
-
-          # Download assets, distinguishing between "no matching assets" and real errors
-          set +e
-          gh release download "$TAG" \
-            --repo "${{ github.repository }}" \
-            --pattern "*.exe" \
-            --pattern "*.dmg" \
-            --pattern "*.AppImage" \
-            --pattern "*.deb" \
-            --pattern "*.flatpak" \
-            --dir release-assets 2>&1
-          exit_code=$?
-          set -e
-
-          if [ $exit_code -ne 0 ]; then
-            # Check if it's just "no assets matched" vs a real error
-            asset_count=$(gh release view "$TAG" --repo "${{ github.repository }}" --json assets -q '.assets | length')
-            if [ "$asset_count" -eq 0 ]; then
-              echo "Release has no assets yet (this is OK for new releases)"
-            else
-              # Check if any scannable assets exist that should have been downloaded
-              scannable_assets=$(gh release view "$TAG" --repo "${{ github.repository }}" --json assets \
-                -q '.assets[].name | select(test("\\.(exe|dmg|AppImage|deb|flatpak)$"))' | wc -l)
-              if [ "$scannable_assets" -gt 0 ]; then
-                echo "::error::Download failed - $scannable_assets scannable asset(s) exist but download failed"
-                exit 1
-              fi
-              echo "No assets matched the patterns (exe, dmg, AppImage, deb, flatpak)"
-            fi
-          fi
-
-          echo "Downloaded assets:"
-          ls -la release-assets/ || echo "No assets found"
-
-      - name: Scan with VirusTotal
-        if: steps.check-key.outputs.has_key == 'true'
-        id: virustotal
-        env:
-          VT_API_KEY: ${{ secrets.VIRUSTOTAL_API_KEY }}
-        run: |
-          echo "## VirusTotal Scan Results" > vt_results.md
-          echo "" >> vt_results.md
-
-          # Check if there are any files to scan
-          shopt -s nullglob
-          files=(release-assets/*.{exe,dmg,AppImage,deb,flatpak})
-          if [ ${#files[@]} -eq 0 ]; then
-            echo "No scannable files found in release assets"
-            echo "- No executable files found in release" >> vt_results.md
-            echo "vt_results<<EOF" >> $GITHUB_OUTPUT
-            cat vt_results.md >> $GITHUB_OUTPUT
-            echo "EOF" >> $GITHUB_OUTPUT
-            exit 0
-          fi
-
-          for file in "${files[@]}"; do
-            [ -f "$file" ] || continue
-            filename=$(basename "$file")
-            filesize=$(stat -c%s "$file" 2>/dev/null || stat -f%z "$file")
-            echo "Scanning $filename (${filesize} bytes)..."
-
-            # VirusTotal requires special upload URL for files > 32MB
-            LARGE_FILE_THRESHOLD=33554432  # 32 MB in bytes
-            if [ "$filesize" -gt "$LARGE_FILE_THRESHOLD" ]; then
-              echo "  Large file detected, requesting upload URL..."
-              upload_http_response=$(curl -s -w '\n%{http_code}' --request GET \
-                --url "https://www.virustotal.com/api/v3/files/upload_url" \
-                --header "x-apikey: $VT_API_KEY")
-              upload_http_code=$(echo "$upload_http_response" | tail -1)
-              upload_url_response=$(echo "$upload_http_response" | sed '$d')
-
-              if [ "$upload_http_code" != "200" ]; then
-                echo "::warning::Failed to get upload URL for large file $filename (HTTP $upload_http_code)"
-                echo "- $filename - ⚠️ Upload failed (large file, HTTP $upload_http_code)" >> vt_results.md
-                continue
-              fi
-
-              upload_url=$(echo "$upload_url_response" | jq -r '.data // empty')
-              if [ -z "$upload_url" ]; then
-                echo "::warning::Failed to get upload URL for large file $filename"
-                echo "Response: $upload_url_response"
-                echo "- $filename - ⚠️ Upload failed (large file)" >> vt_results.md
-                continue
-              fi
-              api_url="$upload_url"
-            else
-              api_url="https://www.virustotal.com/api/v3/files"
-            fi
-
-            # Upload file to VirusTotal (capture HTTP status code)
-            http_response=$(curl -s -w '\n%{http_code}' --request POST \
-              --url "$api_url" \
-              --header "x-apikey: $VT_API_KEY" \
-              --form "file=@$file")
-            http_code=$(echo "$http_response" | tail -1)
-            response=$(echo "$http_response" | sed '$d')
-
-            # Check HTTP status code first
-            if [ "$http_code" != "200" ]; then
-              echo "::warning::VirusTotal returned HTTP $http_code for $filename"
-              if [ "$http_code" = "429" ]; then
-                echo "- $filename - ⚠️ Scan failed (rate limited)" >> vt_results.md
-              elif [ "$http_code" = "403" ]; then
-                echo "- $filename - ⚠️ Scan failed (forbidden - check API key)" >> vt_results.md
-              else
-                echo "- $filename - ⚠️ Scan failed (HTTP $http_code)" >> vt_results.md
-              fi
-              continue
-            fi
-
-            # Check if response is valid JSON before parsing
-            if ! echo "$response" | jq -e . >/dev/null 2>&1; then
-              echo "::warning::VirusTotal returned invalid JSON for $filename"
-              echo "Response (first 500 chars): ${response:0:500}"
-              echo "- $filename - ⚠️ Scan failed (invalid response)" >> vt_results.md
-              continue
-            fi
-
-            # Check for API error response
-            error_code=$(echo "$response" | jq -r '.error.code // empty')
-            if [ -n "$error_code" ]; then
-              error_msg=$(echo "$response" | jq -r '.error.message // "Unknown error"')
-              echo "::warning::VirusTotal API error for $filename: $error_code - $error_msg"
-              echo "- $filename - ⚠️ Scan failed ($error_code)" >> vt_results.md
-              continue
-            fi
-
-            # Extract analysis ID
-            analysis_id=$(echo "$response" | jq -r '.data.id // empty')
-
-            if [ -z "$analysis_id" ]; then
-              echo "::warning::Failed to upload $filename to VirusTotal"
-              echo "Response: $response"
-              echo "- $filename - ⚠️ Upload failed" >> vt_results.md
-              continue
-            fi
-
-            echo "Uploaded $filename, analysis ID: $analysis_id"
-
-            # Wait for analysis to complete (max 5 minutes per file)
-            analysis=""
-            for i in {1..30}; do
-              sleep 10
-              analysis_http_response=$(curl -s -w '\n%{http_code}' --request GET \
-                --url "https://www.virustotal.com/api/v3/analyses/$analysis_id" \
-                --header "x-apikey: $VT_API_KEY")
-              analysis_http_code=$(echo "$analysis_http_response" | tail -1)
-              analysis=$(echo "$analysis_http_response" | sed '$d')
-
-              # Check HTTP status code
-              if [ "$analysis_http_code" != "200" ]; then
-                echo "  Warning: HTTP $analysis_http_code on attempt $i, retrying..."
-                if [ "$analysis_http_code" = "429" ]; then
-                  echo "  Rate limited, waiting longer..."
-                  sleep 30
-                fi
-                continue
-              fi
-
-              # Validate JSON response
-              if ! echo "$analysis" | jq -e . >/dev/null 2>&1; then
-                echo "  Warning: Invalid JSON response on attempt $i, retrying..."
-                continue
-              fi
-
-              status=$(echo "$analysis" | jq -r '.data.attributes.status // "unknown"')
-              echo "  Status: $status (attempt $i/30)"
-
-              if [ "$status" = "completed" ]; then
-                break
-              fi
-            done
-
-            # Handle analysis timeout - if loop completed without status=completed
-            if [ "$status" != "completed" ]; then
-              echo "::warning::Analysis timed out for $filename (status: $status after 5 minutes)"
-              file_hash=$(sha256sum "$file" | cut -d' ' -f1)
-              echo "- [$filename](https://www.virustotal.com/gui/file/$file_hash) - ⚠️ Analysis timed out" >> vt_results.md
-              continue
-            fi
-
-            # Final validation that we have valid analysis data
-            if ! echo "$analysis" | jq -e '.data.attributes.stats' >/dev/null 2>&1; then
-              echo "::warning::Could not get complete analysis for $filename, using local hash"
-              file_hash=$(sha256sum "$file" | cut -d' ' -f1)
-              echo "- [$filename](https://www.virustotal.com/gui/file/$file_hash) - ⚠️ Analysis incomplete" >> vt_results.md
-              continue
-            fi
-
-            # Get file hash for permanent URL
-            file_hash=$(echo "$analysis" | jq -r '.meta.file_info.sha256 // empty')
-
-            if [ -z "$file_hash" ]; then
-              # Fallback: calculate hash locally
-              file_hash=$(sha256sum "$file" | cut -d' ' -f1)
-            fi
-
-            # Get detection stats
-            malicious=$(echo "$analysis" | jq -r '.data.attributes.stats.malicious // 0')
-            suspicious=$(echo "$analysis" | jq -r '.data.attributes.stats.suspicious // 0')
-            undetected=$(echo "$analysis" | jq -r '.data.attributes.stats.undetected // 0')
-
-            vt_url="https://www.virustotal.com/gui/file/$file_hash"
-
-            if [ "$malicious" -gt 0 ] || [ "$suspicious" -gt 0 ]; then
-              echo "::warning::$filename has $malicious malicious and $suspicious suspicious detections (likely false positives)"
-              echo "- [$filename]($vt_url) - ⚠️ **$malicious malicious, $suspicious suspicious** detections (review recommended)" >> vt_results.md
-            else
-              echo "$filename is clean ($undetected engines, 0 detections)"
-              echo "- [$filename]($vt_url) - ✅ Clean ($undetected engines, 0 detections)" >> vt_results.md
-            fi
-          done
-
-          echo "" >> vt_results.md
-
-          # Save results for next step
-          cat vt_results.md
-          echo "vt_results<<EOF" >> $GITHUB_OUTPUT
-          cat vt_results.md >> $GITHUB_OUTPUT
-          echo "EOF" >> $GITHUB_OUTPUT
-
-      - name: Update release notes with scan results
-        if: steps.check-key.outputs.has_key == 'true' && steps.virustotal.outputs.vt_results != ''
-        env:
-          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-        run: |
-          TAG="${{ steps.tag.outputs.tag }}"
-
-          # Get current release body with error checking
-          if ! current_body=$(gh release view "$TAG" --repo "${{ github.repository }}" --json body -q '.body'); then
-            echo "::error::Failed to fetch current release body for $TAG"
-            exit 1
-          fi
-
-          # Additional safeguard for empty body
-          if [ -z "$current_body" ]; then
-            echo "::warning::Release body is empty, this may indicate a problem"
-          fi
-
-          # Check if VirusTotal results already exist in the body
-          if echo "$current_body" | grep -q "## VirusTotal Scan Results"; then
-            echo "VirusTotal results already in release notes, skipping update"
-            exit 0
-          fi
-
-          # Use file-based approach to avoid shell expansion issues
-          # First, write current body to file
-          echo "$current_body" > release-body.md
-
-          # Remove placeholder text if present (portable sed approach)
-          sed '/_VirusTotal scan results will be added automatically after release\./d' release-body.md > release-body.tmp && mv release-body.tmp release-body.md
-
-          # Append separator and VT results
-          echo "" >> release-body.md
-          echo "---" >> release-body.md
-          echo "" >> release-body.md
-          cat vt_results.md >> release-body.md
-
-          # Update release using --notes-file to avoid shell quoting issues
-          gh release edit "$TAG" \
-            --repo "${{ github.repository }}" \
-            --notes-file release-body.md
-
-          echo "✅ Updated release notes with VirusTotal scan results"
-
-      - name: Summary
-        if: always()
-        run: |
-          echo "## VirusTotal Scan Summary" >> $GITHUB_STEP_SUMMARY
-          echo "" >> $GITHUB_STEP_SUMMARY
-          echo "**Release:** ${{ steps.tag.outputs.tag }}" >> $GITHUB_STEP_SUMMARY
-          echo "" >> $GITHUB_STEP_SUMMARY
-          if [ "${{ steps.check-key.outputs.has_key }}" = "false" ]; then
-            echo "⚠️ Scan skipped: VIRUSTOTAL_API_KEY not configured" >> $GITHUB_STEP_SUMMARY
-          elif [ -f vt_results.md ]; then
-            cat vt_results.md >> $GITHUB_STEP_SUMMARY
-          else
-            echo "No scan results available" >> $GITHUB_STEP_SUMMARY
-          fi

.github/workflows/welcome.yml

@@ -1,33 +0,0 @@
-name: Welcome
-
-on:
-  pull_request_target:
-    types: [opened]
-  issues:
-    types: [opened]
-
-jobs:
-  welcome:
-    runs-on: ubuntu-latest
-    permissions:
-      issues: write
-      pull-requests: write
-    steps:
-      - uses: actions/first-interaction@v1
-        with:
-          repo-token: ${{ secrets.GITHUB_TOKEN }}
-          issue-message: |
-            👋 Thanks for opening your first issue!
-
-            A maintainer will triage this soon. In the meantime:
-            - Make sure you've provided all the requested info
-            - Join our [Discord](https://discord.gg/QhRnz9m5HE) for faster help
-          pr-message: |
-            🎉 Thanks for your first PR!
-
-            A maintainer will review it soon. Please make sure:
-            - Your branch is synced with `develop`
-            - CI checks pass
-            - You've followed our [contribution guide](https://github.com/AndyMik90/Auto-Claude/blob/develop/CONTRIBUTING.md)
-
-            Welcome to the Auto Claude community!

.gitignore

@@ -1,70 +1,31 @@
-# ===========================
-# OS Files
-# ===========================
+# OS
 .DS_Store
-.DS_Store?
-._*
 Thumbs.db
-ehthumbs.db
-Desktop.ini
 
-# ===========================
-# Security - Environment & Secrets
-# ===========================
+# Environment files (contain API keys)
 .env
-.env.*
-!.env.example
-/config.json
-*.pem
-*.key
-*.crt
-*.p12
-*.pfx
-.secrets
-secrets/
-credentials/
+.env.local
 
-# ===========================
-# IDE & Editors
-# ===========================
+# Git worktrees (used by auto-build parallel mode)
+.worktrees/
+
+# IDE
 .idea/
 .vscode/
 *.swp
 *.swo
-*.sublime-workspace
-*.sublime-project
-.project
-.classpath
-.settings/
 
-# ===========================
 # Logs
-# ===========================
 logs/
 *.log
-npm-debug.log*
-yarn-debug.log*
-yarn-error.log*
-lerna-debug.log*
 
-# ===========================
-# Git Worktrees (parallel builds)
-# ===========================
-.worktrees/
+# Personal notes
+OPUS_ANALYSIS_AND_IDEAS.md
 
-# ===========================
-# Auto Claude Generated
-# ===========================
-.auto-claude/
-.auto-build-security.json
-.auto-claude-security.json
-.auto-claude-status
-.claude_settings.json
-.update-metadata.json
+# Documentation
+docs/
 
-# ===========================
-# Python (apps/backend)
-# ===========================
+# Python
 __pycache__/
 *.py[cod]
 *$py.class
@@ -72,19 +33,25 @@ __pycache__/
 .Python
 build/
 develop-eggs/
+dist/
+downloads/
 eggs/
 .eggs/
+/lib/
+/lib64/
+parts/
+sdist/
+var/
+wheels/
 *.egg-info/
 .installed.cfg
 *.egg
-MANIFEST
 
 # Virtual environments
 .venv/
 venv/
 ENV/
 env/
-.conda/
 
 # Testing
 .pytest_cache/
@@ -97,75 +64,26 @@ coverage.xml
 *.py,cover
 .hypothesis/
 
-# Type checking
+# mypy
 .mypy_cache/
 .dmypy.json
 dmypy.json
-.pytype/
-.pyre/
 
-# ===========================
-# Node.js (apps/frontend)
-# ===========================
-node_modules/
-.npm
-.yarn/
-.pnp.*
+# Auto-build generated files
+.auto-build-security.json
+.auto-claude-security.json
+.auto-claude-status
+.claude_settings.json
+.update-metadata.json
 
-# Build output
-dist/
-out/
-*.tsbuildinfo
-apps/frontend/python-runtime/
-
-# Cache
-.cache/
-.parcel-cache/
-.turbo/
-.eslintcache
-.prettiercache
-
-# ===========================
-# Electron
-# ===========================
-apps/frontend/dist/
-apps/frontend/out/
-*.asar
-*.blockmap
-*.snap
-*.deb
-*.rpm
-*.AppImage
-*.dmg
-*.exe
-*.msi
-
-# ===========================
-# Testing
-# ===========================
-coverage/
-.nyc_output/
-test-results/
-playwright-report/
-playwright/.cache/
-
-# ===========================
-# Misc
-# ===========================
-*.local
-*.bak
-*.tmp
-*.temp
-
-# Development
+# Development of Auto Build with Auto Build
 dev/
-_bmad/
-_bmad-output/
-.claude/
-/docs
-OPUS_ANALYSIS_AND_IDEAS.md
-/.github/agents
 
-# Auto Claude generated files
-.security-key
-/shared_docs
+.auto-claude/
+
+/docs
+
+_bmad
+_bmad-output
+
+.claude

.husky/commit-msg

@@ -1,81 +0,0 @@
-#!/bin/sh
-
-# Commit message validation
-# Enforces conventional commit format: type(scope)!?: description
-#
-# Valid types: feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert
-# Scope allows: letters, numbers, hyphens, underscores, slashes, dots
-# Optional ! for breaking changes
-# Examples:
-#   feat(tasks): add drag and drop support
-#   fix(terminal): resolve scroll position issue
-#   feat!: breaking change without scope
-#   feat(api)!: breaking change with scope
-#   docs: update README with setup instructions
-#   chore: update dependencies
-
-commit_msg_file=$1
-commit_msg=$(cat "$commit_msg_file")
-
-# Regex for conventional commits
-# Format: type(optional-scope)!?: description
-# Scope allows: letters, numbers, hyphens, underscores, slashes, dots (consistent with GitHub workflow)
-# Optional ! for breaking changes: feat!: or feat(scope)!:
-pattern="^(feat|fix|docs|style|refactor|perf|test|build|ci|chore|revert)(\([a-zA-Z0-9_/.-]+\))?!?: .{1,100}$"
-
-# Allow merge commits
-if echo "$commit_msg" | grep -qE "^Merge "; then
-  exit 0
-fi
-
-# Allow revert commits
-if echo "$commit_msg" | grep -qE "^Revert "; then
-  exit 0
-fi
-
-# Check first line against pattern
-first_line=$(echo "$commit_msg" | head -n 1)
-
-if ! echo "$first_line" | grep -qE "$pattern"; then
-  echo ""
-  echo "ERROR: Invalid commit message format!"
-  echo ""
-  echo "Your message: $first_line"
-  echo ""
-  echo "Expected format: type(scope)!?: description"
-  echo ""
-  echo "Valid types:"
-  echo "  feat     - A new feature"
-  echo "  fix      - A bug fix"
-  echo "  docs     - Documentation changes"
-  echo "  style    - Code style changes (formatting, semicolons, etc.)"
-  echo "  refactor - Code refactoring (no feature/fix)"
-  echo "  perf     - Performance improvements"
-  echo "  test     - Adding or updating tests"
-  echo "  build    - Build system or dependencies"
-  echo "  ci       - CI/CD configuration"
-  echo "  chore    - Other changes (maintenance)"
-  echo "  revert   - Reverting a previous commit"
-  echo ""
-  echo "Examples:"
-  echo "  feat(tasks): add drag and drop support"
-  echo "  fix(terminal): resolve scroll position issue"
-  echo "  feat!: breaking change without scope"
-  echo "  feat(api)!: breaking change with scope"
-  echo "  docs: update README"
-  echo "  chore: update dependencies"
-  echo ""
-  exit 1
-fi
-
-# Check description length (max 100 chars for first line)
-if [ ${#first_line} -gt 100 ]; then
-  echo ""
-  echo "ERROR: Commit message first line is too long!"
-  echo "Maximum: 100 characters"
-  echo "Current: ${#first_line} characters"
-  echo ""
-  exit 1
-fi
-
-exit 0

.husky/pre-commit

@@ -1,214 +1,6 @@
 #!/bin/sh
 
-# Preserve git worktree context - prevent HEAD corruption in worktrees
-if [ -f ".git" ]; then
-  WORKTREE_GIT_DIR=$(cat .git | sed 's/gitdir: //')
-  if [ -n "$WORKTREE_GIT_DIR" ]; then
-    export GIT_DIR="$WORKTREE_GIT_DIR"
-    export GIT_WORK_TREE="$(pwd)"
-  fi
+# Run lint-staged in auto-claude-ui if there are staged files there
+if git diff --cached --name-only | grep -q "^auto-claude-ui/"; then
+  cd auto-claude-ui && pnpm exec lint-staged
 fi
-
-echo "Running pre-commit checks..."
-
-# =============================================================================
-# VERSION SYNC - Keep all version references in sync with root package.json
-# =============================================================================
-
-# Check if package.json is staged
-if git diff --cached --name-only | grep -q "^package.json$"; then
-  echo "package.json changed, syncing version to all files..."
-
-  # Extract version from root package.json
-  VERSION=$(node -p "require('./package.json').version")
-
-  if [ -n "$VERSION" ]; then
-    # Sync to apps/frontend/package.json
-    if [ -f "apps/frontend/package.json" ]; then
-      node -e "
-        const fs = require('fs');
-        const pkg = require('./apps/frontend/package.json');
-        if (pkg.version !== '$VERSION') {
-          pkg.version = '$VERSION';
-          fs.writeFileSync('./apps/frontend/package.json', JSON.stringify(pkg, null, 2) + '\n');
-          console.log('  Updated apps/frontend/package.json to $VERSION');
-        }
-      "
-      git add apps/frontend/package.json
-    fi
-
-    # Sync to apps/backend/__init__.py
-    if [ -f "apps/backend/__init__.py" ]; then
-      sed -i.bak "s/__version__ = \"[^\"]*\"/__version__ = \"$VERSION\"/" apps/backend/__init__.py
-      rm -f apps/backend/__init__.py.bak
-      git add apps/backend/__init__.py
-      echo "  Updated apps/backend/__init__.py to $VERSION"
-    fi
-
-    # Sync to README.md - section-aware updates (stable vs beta)
-    if [ -f "README.md" ]; then
-      # Escape hyphens for shields.io badge format (shields.io uses -- for literal hyphens)
-      ESCAPED_VERSION=$(echo "$VERSION" | sed 's/-/--/g')
-
-      # Detect if this is a prerelease (contains - after base version, e.g., 2.7.2-beta.10)
-      if echo "$VERSION" | grep -q '-'; then
-        # PRERELEASE: Update only beta sections
-        echo "  Detected PRERELEASE version: $VERSION"
-
-        # Update beta version badge (orange)
-        sed -i.bak "s/beta-[0-9]*\.[0-9]*\.[0-9]*\(--[a-z]*\.[0-9]*\)*-orange/beta-$ESCAPED_VERSION-orange/g" README.md
-
-        # Update beta version badge link (within BETA_VERSION_BADGE section)
-        sed -i.bak '/<!-- BETA_VERSION_BADGE -->/,/<!-- BETA_VERSION_BADGE_END -->/s|releases/tag/v[0-9.a-z-]*)|releases/tag/v'"$VERSION"')|g' README.md
-
-        # Update beta download links (within BETA_DOWNLOADS section only)
-        for SUFFIX in "win32-x64.exe" "darwin-arm64.dmg" "darwin-x64.dmg" "linux-x86_64.AppImage" "linux-amd64.deb" "linux-x86_64.flatpak"; do
-          sed -i.bak '/<!-- BETA_DOWNLOADS -->/,/<!-- BETA_DOWNLOADS_END -->/{s|Auto-Claude-[0-9.a-z-]*-'"$SUFFIX"'](https://github.com/AndyMik90/Auto-Claude/releases/download/v[^/]*/Auto-Claude-[^)]*-'"$SUFFIX"')|Auto-Claude-'"$VERSION"'-'"$SUFFIX"'](https://github.com/AndyMik90/Auto-Claude/releases/download/v'"$VERSION"'/Auto-Claude-'"$VERSION"'-'"$SUFFIX"')|g}' README.md
-        done
-      else
-        # STABLE: Update stable sections and top badge
-        echo "  Detected STABLE version: $VERSION"
-
-        # Update top version badge (blue) - within TOP_VERSION_BADGE section
-        sed -i.bak '/<!-- TOP_VERSION_BADGE -->/,/<!-- TOP_VERSION_BADGE_END -->/s/version-[0-9]*\.[0-9]*\.[0-9]*\(--[a-z]*\.[0-9]*\)*-blue/version-'"$ESCAPED_VERSION"'-blue/g' README.md
-        sed -i.bak '/<!-- TOP_VERSION_BADGE -->/,/<!-- TOP_VERSION_BADGE_END -->/s|releases/tag/v[0-9.a-z-]*)|releases/tag/v'"$VERSION"')|g' README.md
-
-        # Update stable version badge (blue) - within STABLE_VERSION_BADGE section
-        sed -i.bak '/<!-- STABLE_VERSION_BADGE -->/,/<!-- STABLE_VERSION_BADGE_END -->/s/stable-[0-9]*\.[0-9]*\.[0-9]*\(--[a-z]*\.[0-9]*\)*-blue/stable-'"$ESCAPED_VERSION"'-blue/g' README.md
-        sed -i.bak '/<!-- STABLE_VERSION_BADGE -->/,/<!-- STABLE_VERSION_BADGE_END -->/s|releases/tag/v[0-9.a-z-]*)|releases/tag/v'"$VERSION"')|g' README.md
-
-        # Update stable download links (within STABLE_DOWNLOADS section only)
-        for SUFFIX in "win32-x64.exe" "darwin-arm64.dmg" "darwin-x64.dmg" "linux-x86_64.AppImage" "linux-amd64.deb"; do
-          sed -i.bak '/<!-- STABLE_DOWNLOADS -->/,/<!-- STABLE_DOWNLOADS_END -->/{s|Auto-Claude-[0-9.a-z-]*-'"$SUFFIX"'](https://github.com/AndyMik90/Auto-Claude/releases/download/v[^/]*/Auto-Claude-[^)]*-'"$SUFFIX"')|Auto-Claude-'"$VERSION"'-'"$SUFFIX"'](https://github.com/AndyMik90/Auto-Claude/releases/download/v'"$VERSION"'/Auto-Claude-'"$VERSION"'-'"$SUFFIX"')|g}' README.md
-        done
-      fi
-
-      rm -f README.md.bak
-      git add README.md
-      echo "  Updated README.md to $VERSION"
-    fi
-
-    echo "Version sync complete: $VERSION"
-  fi
-fi
-
-# =============================================================================
-# BACKEND CHECKS (Python) - Run first, before frontend
-# =============================================================================
-
-# Check if there are staged Python files in apps/backend
-if git diff --cached --name-only | grep -q "^apps/backend/.*\.py$"; then
-  echo "Python changes detected, running backend checks..."
-
-  # Determine ruff command (venv or global)
-  RUFF=""
-  if [ -f "apps/backend/.venv/bin/ruff" ]; then
-    RUFF="apps/backend/.venv/bin/ruff"
-  elif [ -f "apps/backend/.venv/Scripts/ruff.exe" ]; then
-    RUFF="apps/backend/.venv/Scripts/ruff.exe"
-  elif command -v ruff >/dev/null 2>&1; then
-    RUFF="ruff"
-  fi
-
-  if [ -n "$RUFF" ]; then
-    # Get only staged Python files in apps/backend (process only what's being committed)
-    STAGED_PY_FILES=$(git diff --cached --name-only --diff-filter=ACM | grep "^apps/backend/.*\.py$" || true)
-
-    if [ -n "$STAGED_PY_FILES" ]; then
-      # Run ruff linting (auto-fix) only on staged files
-      echo "Running ruff lint on staged files..."
-      echo "$STAGED_PY_FILES" | xargs $RUFF check --fix
-      if [ $? -ne 0 ]; then
-        echo "Ruff lint failed. Please fix Python linting errors before committing."
-        exit 1
-      fi
-
-      # Run ruff format (auto-fix) only on staged files
-      echo "Running ruff format on staged files..."
-      echo "$STAGED_PY_FILES" | xargs $RUFF format
-
-      # Re-stage only the files that were originally staged (in case ruff modified them)
-      echo "$STAGED_PY_FILES" | xargs git add
-    fi
-  else
-    echo "Warning: ruff not found, skipping Python linting. Install with: uv pip install ruff"
-  fi
-
-  # Run pytest (skip slow/integration tests and Windows-incompatible tests for pre-commit speed)
-  # Use subshell to isolate directory changes and prevent worktree corruption
-  echo "Running Python tests..."
-  (
-    cd apps/backend
-    # Tests to skip: graphiti (external deps), merge_file_tracker/service_orchestrator/worktree/workspace (Windows path/git issues)
-    IGNORE_TESTS="--ignore=../../tests/test_graphiti.py --ignore=../../tests/test_merge_file_tracker.py --ignore=../../tests/test_service_orchestrator.py --ignore=../../tests/test_worktree.py --ignore=../../tests/test_workspace.py"
-    if [ -d ".venv" ]; then
-      # Use venv if it exists
-      if [ -f ".venv/bin/pytest" ]; then
-        PYTHONPATH=. .venv/bin/pytest ../../tests/ -v --tb=short -x -m "not slow and not integration" $IGNORE_TESTS
-      elif [ -f ".venv/Scripts/pytest.exe" ]; then
-        # Windows
-        PYTHONPATH=. .venv/Scripts/pytest.exe ../../tests/ -v --tb=short -x -m "not slow and not integration" $IGNORE_TESTS
-      else
-        PYTHONPATH=. python -m pytest ../../tests/ -v --tb=short -x -m "not slow and not integration" $IGNORE_TESTS
-      fi
-    else
-      PYTHONPATH=. python -m pytest ../../tests/ -v --tb=short -x -m "not slow and not integration" $IGNORE_TESTS
-    fi
-  )
-  if [ $? -ne 0 ]; then
-    echo "Python tests failed. Please fix failing tests before committing."
-    exit 1
-  fi
-
-  echo "Backend checks passed!"
-fi
-
-# =============================================================================
-# FRONTEND CHECKS (TypeScript/React)
-# =============================================================================
-
-# Check if there are staged files in apps/frontend
-if git diff --cached --name-only | grep -q "^apps/frontend/"; then
-  echo "Frontend changes detected, running frontend checks..."
-  # Use subshell to isolate directory changes and prevent worktree corruption
-  (
-    cd apps/frontend
-
-    # Run lint-staged (handles staged .ts/.tsx files)
-    npm exec lint-staged
-    if [ $? -ne 0 ]; then
-      echo "lint-staged failed. Please fix linting errors before committing."
-      exit 1
-    fi
-
-    # Run TypeScript type check
-    echo "Running type check..."
-    npm run typecheck
-    if [ $? -ne 0 ]; then
-      echo "Type check failed. Please fix TypeScript errors before committing."
-      exit 1
-    fi
-
-    # Run linting
-    echo "Running lint..."
-    npm run lint
-    if [ $? -ne 0 ]; then
-      echo "Lint failed. Run 'npm run lint:fix' to auto-fix issues."
-      exit 1
-    fi
-
-    # Check for vulnerabilities (only high severity)
-    echo "Checking for vulnerabilities..."
-    npm audit --audit-level=high
-    if [ $? -ne 0 ]; then
-      echo "High severity vulnerabilities found. Run 'npm audit fix' to resolve."
-      exit 1
-    fi
-  )
-  if [ $? -ne 0 ]; then
-    exit 1
-  fi
-  echo "Frontend checks passed!"
-fi
-
-echo "All pre-commit checks passed!"

.pre-commit-config.yaml

@@ -1,170 +1,34 @@
 repos:
-  # Version sync - propagate root package.json version to all files
-  # NOTE: Skip in worktrees - version sync modifies root files which don't exist in worktree
-  - repo: local
-    hooks:
-      - id: version-sync
-        name: Version Sync
-        entry: bash
-        args:
-          - -c
-          - |
-            # Skip in worktrees - .git is a file pointing to main repo, not a directory
-            # Version sync modifies root-level files that may not exist in worktree context
-            if [ -f ".git" ]; then
-              echo "Skipping version-sync in worktree (root files not accessible)"
-              exit 0
-            fi
-            VERSION=$(node -p "require('./package.json').version")
-            if [ -n "$VERSION" ]; then
-
-              # Sync to apps/frontend/package.json
-              node -e "
-                const fs = require('fs');
-                const p = require('./apps/frontend/package.json');
-                const v = process.argv[1];
-                if (p.version !== v) {
-                  p.version = v;
-                  fs.writeFileSync('./apps/frontend/package.json', JSON.stringify(p, null, 2) + '\n');
-                }
-              " "$VERSION"
-
-              # Sync to apps/backend/__init__.py
-              sed -i.bak "s/__version__ = \"[^\"]*\"/__version__ = \"$VERSION\"/" apps/backend/__init__.py && rm -f apps/backend/__init__.py.bak
-
-              # Sync to README.md - section-aware updates (stable vs beta)
-              ESCAPED_VERSION=$(echo "$VERSION" | sed 's/-/--/g')
-
-              # Detect if this is a prerelease (contains - after base version)
-              if echo "$VERSION" | grep -q '-'; then
-                # PRERELEASE: Update only beta sections
-                echo "  Detected PRERELEASE version: $VERSION"
-
-                # Update beta version badge (orange)
-                sed -i.bak "s/beta-[0-9]*\.[0-9]*\.[0-9]*\(--[a-z]*\.[0-9]*\)*-orange/beta-$ESCAPED_VERSION-orange/g" README.md
-
-                # Update beta version badge link
-                sed -i.bak '/<!-- BETA_VERSION_BADGE -->/,/<!-- BETA_VERSION_BADGE_END -->/s|releases/tag/v[0-9.a-z-]*)|releases/tag/v'"$VERSION"')|g' README.md
-
-                # Update beta download links (within BETA_DOWNLOADS section only)
-                for SUFFIX in "win32-x64.exe" "darwin-arm64.dmg" "darwin-x64.dmg" "linux-x86_64.AppImage" "linux-amd64.deb" "linux-x86_64.flatpak"; do
-                  sed -i.bak '/<!-- BETA_DOWNLOADS -->/,/<!-- BETA_DOWNLOADS_END -->/{s|Auto-Claude-[0-9.a-z-]*-'"$SUFFIX"'](https://github.com/AndyMik90/Auto-Claude/releases/download/v[^/]*/Auto-Claude-[^)]*-'"$SUFFIX"')|Auto-Claude-'"$VERSION"'-'"$SUFFIX"'](https://github.com/AndyMik90/Auto-Claude/releases/download/v'"$VERSION"'/Auto-Claude-'"$VERSION"'-'"$SUFFIX"')|g}' README.md
-                done
-              else
-                # STABLE: Update stable sections and top badge
-                echo "  Detected STABLE version: $VERSION"
-
-                # Update top version badge (blue)
-                sed -i.bak '/<!-- TOP_VERSION_BADGE -->/,/<!-- TOP_VERSION_BADGE_END -->/s/version-[0-9]*\.[0-9]*\.[0-9]*\(--[a-z]*\.[0-9]*\)*-blue/version-'"$ESCAPED_VERSION"'-blue/g' README.md
-                sed -i.bak '/<!-- TOP_VERSION_BADGE -->/,/<!-- TOP_VERSION_BADGE_END -->/s|releases/tag/v[0-9.a-z-]*)|releases/tag/v'"$VERSION"')|g' README.md
-
-                # Update stable version badge (blue)
-                sed -i.bak '/<!-- STABLE_VERSION_BADGE -->/,/<!-- STABLE_VERSION_BADGE_END -->/s/stable-[0-9]*\.[0-9]*\.[0-9]*\(--[a-z]*\.[0-9]*\)*-blue/stable-'"$ESCAPED_VERSION"'-blue/g' README.md
-                sed -i.bak '/<!-- STABLE_VERSION_BADGE -->/,/<!-- STABLE_VERSION_BADGE_END -->/s|releases/tag/v[0-9.a-z-]*)|releases/tag/v'"$VERSION"')|g' README.md
-
-                # Update stable download links (within STABLE_DOWNLOADS section only)
-                for SUFFIX in "win32-x64.exe" "darwin-arm64.dmg" "darwin-x64.dmg" "linux-x86_64.AppImage" "linux-amd64.deb"; do
-                  sed -i.bak '/<!-- STABLE_DOWNLOADS -->/,/<!-- STABLE_DOWNLOADS_END -->/{s|Auto-Claude-[0-9.a-z-]*-'"$SUFFIX"'](https://github.com/AndyMik90/Auto-Claude/releases/download/v[^/]*/Auto-Claude-[^)]*-'"$SUFFIX"')|Auto-Claude-'"$VERSION"'-'"$SUFFIX"'](https://github.com/AndyMik90/Auto-Claude/releases/download/v'"$VERSION"'/Auto-Claude-'"$VERSION"'-'"$SUFFIX"')|g}' README.md
-                done
-              fi
-              rm -f README.md.bak
-
-              # Stage changes
-              git add apps/frontend/package.json apps/backend/__init__.py README.md 2>/dev/null || true
-            fi
-        language: system
-        files: ^package\.json$
-        pass_filenames: false
-
-  # Python linting (apps/backend/)
+  # Python linting (auto-claude/)
   - repo: https://github.com/astral-sh/ruff-pre-commit
-    rev: v0.14.10
+    rev: v0.8.3
     hooks:
       - id: ruff
         args: [--fix]
-        files: ^apps/backend/
+        files: ^auto-claude/
       - id: ruff-format
-        files: ^apps/backend/
+        files: ^auto-claude/
 
-  # Python tests (apps/backend/) - skip slow/integration tests for pre-commit speed
-  # Tests to skip: graphiti (external deps), merge_file_tracker/service_orchestrator/worktree/workspace (Windows path/git issues)
-  # NOTE: Skip this hook in worktrees (where .git is a file, not a directory)
-  - repo: local
-    hooks:
-      - id: pytest
-        name: Python Tests
-        entry: bash
-        args:
-          - -c
-          - |
-            # Skip in worktrees - .git is a file pointing to main repo, not a directory
-            # This prevents path resolution issues with ../../tests/ in worktree context
-            if [ -f ".git" ]; then
-              echo "Skipping pytest in worktree (path resolution would fail)"
-              exit 0
-            fi
-            cd apps/backend
-            if [ -f ".venv/bin/pytest" ]; then
-              PYTEST_CMD=".venv/bin/pytest"
-            elif [ -f ".venv/Scripts/pytest.exe" ]; then
-              PYTEST_CMD=".venv/Scripts/pytest.exe"
-            else
-              PYTEST_CMD="python -m pytest"
-            fi
-            PYTHONPATH=. $PYTEST_CMD \
-              ../../tests/ \
-              -v \
-              --tb=short \
-              -x \
-              -m "not slow and not integration" \
-              --ignore=../../tests/test_graphiti.py \
-              --ignore=../../tests/test_merge_file_tracker.py \
-              --ignore=../../tests/test_service_orchestrator.py \
-              --ignore=../../tests/test_worktree.py \
-              --ignore=../../tests/test_workspace.py
-        language: system
-        files: ^(apps/backend/.*\.py$|tests/.*\.py$)
-        pass_filenames: false
-
-  # Frontend linting (apps/frontend/)
-  # NOTE: These hooks check for worktree context to avoid npm/node_modules issues
+  # Frontend linting (auto-claude-ui/)
   - repo: local
     hooks:
       - id: eslint
         name: ESLint
-        entry: bash
-        args:
-          - -c
-          - |
-            # Skip in worktrees if node_modules doesn't exist (dependencies not installed)
-            if [ -f ".git" ] && [ ! -d "apps/frontend/node_modules" ]; then
-              echo "Skipping ESLint in worktree (node_modules not found)"
-              exit 0
-            fi
-            cd apps/frontend && npm run lint
+        entry: bash -c 'cd auto-claude-ui && pnpm lint'
         language: system
-        files: ^apps/frontend/.*\.(ts|tsx|js|jsx)$
+        files: ^auto-claude-ui/.*\.(ts|tsx|js|jsx)$
         pass_filenames: false
 
       - id: typecheck
         name: TypeScript Check
-        entry: bash
-        args:
-          - -c
-          - |
-            # Skip in worktrees if node_modules doesn't exist (dependencies not installed)
-            if [ -f ".git" ] && [ ! -d "apps/frontend/node_modules" ]; then
-              echo "Skipping TypeScript check in worktree (node_modules not found)"
-              exit 0
-            fi
-            cd apps/frontend && npm run typecheck
+        entry: bash -c 'cd auto-claude-ui && pnpm typecheck'
         language: system
-        files: ^apps/frontend/.*\.(ts|tsx)$
+        files: ^auto-claude-ui/.*\.(ts|tsx)$
         pass_filenames: false
 
   # General checks
   - repo: https://github.com/pre-commit/pre-commit-hooks
-    rev: v6.0.0
+    rev: v5.0.0
     hooks:
       - id: trailing-whitespace
       - id: end-of-file-fixer

CHANGELOG.md

@@ -1,948 +1,3 @@
-## 2.7.4 - Terminal & Workflow Enhancements
-
-### ✨ New Features
-
-- Added task worktrees section in terminal with ability to invoke Claude with YOLO mode (--dangerously-skip-permissions)
-
-- Added searchable branch combobox to worktree creation dialog for easier branch selection
-
-- Added Claude Code version rollback feature to switch between installed versions
-
-- Embedded Sentry DSN at build time for better error tracking in packaged apps
-
-### 🛠️ Improvements
-
-- Made worktree isolation prominent in UI to help users understand workspace isolation
-
-- Enhanced terminal recreation logic with retry mechanism for more reliable terminal recovery
-
-- Improved worktree name input UX for better user experience
-
-- Improved Claude CLI detection with installation selector when multiple versions found
-
-- Enhanced terminal drag and drop reordering with collision detection
-
-- Synced worktree config to renderer on terminal restoration for consistency
-
-### 🐛 Bug Fixes
-
-- Fixed Windows claude.cmd validation in GUI to work reliably across different setups
-
-- Fixed profile manager initialization timing issue before auth checks
-
-- Fixed terminal recreation and label reset when user closes Claude
-
-- Fixed duplicate Kanban task creation that occurred on rapid button clicks
-
-- Fixed GitHub PR preloading to prevent loading PRs currently under review
-
-- Fixed UI to display actual base branch name instead of hardcoded "main"
-
-- Fixed Claude CLI detection to properly identify available installations
-
-- Fixed broken pipe errors in backend with Sentry integration
-
-- Fixed app update state persistence for Install button visibility
-
-- Fixed merge logic to include files with content changes even when semantic analysis is empty
-
-- Fixed security profile inheritance in worktrees and shell -c command validation
-
-- Fixed auth auto-switch on 401 errors and improved OAuth-only profile handling
-
-- Fixed "already up to date" case handling in worktree operations
-
-- Resolved circular import issues in GitHub context gatherer and services
-
----
-
-## What's Changed
-
-- fix: validate Windows claude.cmd reliably in GUI by @Umaru in 1ae3359b
-- fix: await profile manager initialization before auth check by @StillKnotKnown in c8374bc1
-- feat: add file/screenshot upload to QA feedback interface by @Andy in 88277f84
-- feat(terminal): add task worktrees section and remove terminal limit by @Andy in 17118b07
-- fix(terminal): enhance terminal recreation logic with retry mechanism by @Andy in df1b8a3f
-- fix(terminal): improve worktree name input UX by @Andy in 54e9f228
-- feat(ui): make worktree isolation prominent in UI by @Andy in 4dbb7ee4
-- feat(terminal): add YOLO mode to invoke Claude with --dangerously-skip-permissions by @Andy in d48e5f68
-- fix(ui): prevent duplicate Kanban task creation on rapid button clicks by @Andy in 2d1d3ef1
-- feat(sentry): embed Sentry DSN at build time for packaged apps by @Andy in aed28c5f
-- fix(github): resolve circular import issues in context_gatherer and services by @Andy in 0307a4a9
-- fix(github-prs): prevent preloading of PRs currently under review by @Andy in 1babcc86
-- fix(ui): display actual base branch name instead of hardcoded main by @Andy in 5d07d5f1
-- ci(release): move VirusTotal scan to separate post-release workflow by @Andy in 553d1e8d
-- fix: improve Claude CLI detection and add installation selector by @Andy in e07a0dbd
-- fix(backend): add Sentry integration and fix broken pipe errors by @Andy in aa9fbe9d
-- fix(app-update): persist downloaded update state for Install button visibility by @Andy in 6f059bb5
-- fix(terminal): detect Claude exit and reset label when user closes Claude by @Andy in 14982e66
-- fix(merge): include files with content changes even when semantic analysis is empty by @Andy in 4736b6b6
-- fix(frontend): sync worktree config to renderer on terminal restoration by @Andy in 68fe0860
-- feat(frontend): add searchable branch combobox to worktree creation dialog by @Andy in 2a2dc3b8
-- fix(security): inherit security profiles in worktrees and validate shell -c commands by @Andy in 750ea8d1
-- feat(frontend): add Claude Code version rollback feature by @Andy in 8d21978f
-- fix(ACS-181): enable auto-switch on 401 auth errors & OAuth-only profiles by @Michael Ludlow in e7427321
-- fix(terminal): add collision detection for terminal drag and drop reordering by @Andy in 1701160b
-- fix(worktree): handle "already up to date" case correctly by @StillKnotKnown in 74ed4320
-
-## Thanks to all contributors
-
-@Umaru, @StillKnotKnown, @Andy, @Michael Ludlow, @AndyMik90
-
-## 2.7.3 - Reliability & Stability Focus
-
-### ✨ New Features
-
-- Add terminal copy/paste keyboard shortcuts for Windows/Linux
-
-- Add Sentry environment variables to CI build workflows for error monitoring
-
-- Add Claude Code changelog link to version notifiers
-
-- Enhance PR merge readiness checks with branch state validation
-
-- Add PR creation workflow for task worktrees
-
-- Add prominent verdict summary to PR review comments
-
-- Add Dart/Flutter/Melos support to security profiles
-
-- Custom Anthropic compatible API profile management
-
-- Add terminal dropdown with inbuilt and external options in task review
-
-- Centralize CLI tool path management
-
-- Add terminal support for worktrees
-
-- Add Files tab to task details panel
-
-- Enhance PR review page to include PRs filters
-
-- Add GitLab integration
-
-- Add Flatpak packaging support for Linux
-
-- Bundle Python 3.12 with packaged Electron app
-
-- Add iOS/Swift project detection
-
-- Add automated PR review with follow-up support
-
-- Add i18n internationalization system
-
-- Add OpenRouter as LLM/embedding provider
-
-- Add UI scale feature with 75-200% range
-
-### 🛠️ Improvements
-
-- Extract shared task form components for consistent modals
-
-- Simplify task description handling and improve modal layout
-
-- Replace confidence scoring with evidence-based validation in GitHub reviews
-
-- Convert synchronous I/O to async operations in worktree handlers
-
-- Remove top bars from UI
-
-- Improve task card title readability
-
-- Add path-aware AI merge resolution and device code streaming
-
-- Increase Claude SDK JSON buffer size to 10MB
-
-- Improve performance by removing projectTabs from useEffect dependencies
-
-- Normalize feature status values for Kanban display
-
-- Improve GLM presets, ideation auth, and Insights env
-
-- Detect and clear cross-platform CLI paths in settings
-
-- Improve CLI tool detection and add Claude CLI path settings
-
-- Multiple bug fixes including binary file handling and semantic tracking
-
-- Centralize Claude CLI invocation across the application
-
-- Improve PR review with structured outputs and fork support
-
-- Improve task card description truncation for better display
-
-- Improve GitHub PR review with better evidence-based findings
-
-### 🐛 Bug Fixes
-
-- Implement atomic JSON writes to prevent file corruption
-
-- Prevent "Render frame was disposed" crash in frontend
-
-- Strip ANSI escape codes from roadmap/ideation progress messages
-
-- Resolve integrations freeze and improve rate limit handling
-
-- Use shared project-wide memory for cross-spec learning
-
-- Add isinstance(dict) validation to Graphiti to prevent AttributeError
-
-- Enforce implementation_plan schema in planner
-
-- Remove obsolete @lydell/node-pty extraResources entry from build
-
-- Add Post Clean Review button for clean PR reviews
-
-- Fix Kanban status flip-flop and phase state inconsistency
-
-- Resolve multiple merge-related issues affecting worktree operations
-
-- Show running review state when switching back to PR with in-progress review
-
-- Properly quote Windows .cmd/.bat paths in spawn() calls
-
-- Improve Claude CLI detection on Windows with space-containing paths
-
-- Display subtask titles instead of UUIDs in UI
-
-- Use HTTP for Azure Trusted Signing timestamp URL in CI
-
-- Fix Kanban state transitions and status flip-flop bug
-
-- Use selectedPR from hook to restore Files changed list
-
-- Automate auto labeling based on comments
-
-- Fix subtasks tab not updating on Linux
-
-- Add PYTHONPATH to subprocess environment for bundled packages
-
-- Prevent crash after worktree creation in terminal
-
-- Ensure PATH includes system directories when launched from Electron
-
-- Grant worktree access to original project directories
-
-- Filter task IPC events by project to prevent cross-project interference
-
-- Verify critical packages exist, not just marker file during Python bundling
-
-- Await async sendMessage to prevent race condition in insights
-
-- Add pywin32 dependency for LadybugDB on Windows
-
-- Handle Ollama version errors during model pull
-
-- Add helpful error message when Python dependencies are missing
-
-- Prevent app freeze by making Claude CLI detection non-blocking
-
-- Use Homebrew for Ollama installation on macOS
-
-- Use --continue instead of --resume for Claude session restoration
-
-- Add context menu for keyboard-accessible task status changes
-
-- Security allowlist now works correctly in worktree mode
-
-- Fix InvestigationDialog overflow issue
-
-- Auto-create .env from .env.example during backend install
-
-- Show OAuth terminal during profile authentication
-
-- Pass augmented env to Claude CLI validation on macOS
-
-- Fix Git bash path detection on Windows
-
-- Support API profiles in auth check and model resolution
-
-- Window size adjustment on Hi-DPI displays
-
-- Centralize Claude CLI invocation
-
-- Pass OAuth token to Python runner subprocesses for GitHub operations
-
-- Resolve React Fast Refresh hook error in usePtyProcess
-
-- Detect @lydell/node-pty prebuilts in postinstall
-
-- Detect Claude CLI installed via NVM on Linux/macOS
-
-- Allow toggle deselection and improve embedding model name matching
-
-- Sanitize environment to prevent PYTHONHOME contamination
-
-- Check .claude.json for OAuth auth in profile scorer
-
-- Use shell mode for Windows command spawning in MCP
-
-- Update TaskCard description truncation for improved display
-
-- Change hardcoded Opus defaults to Sonnet
-
-- Include update manifests for architecture-specific auto-updates
-
-- Fix security hook cwd extraction and PATH issues
-
-- Filter empty env vars to prevent OAuth token override
-
-- Persist human_review status (worktree plan path fix)
-
-- Resolve PATH and PYTHONPATH issues in insights and changelog services
-
-- Pass electron version explicitly to electron-rebuild on Windows
-
-- Complete refresh button implementation for Kanban
-
-- Fixed version-specific links in readme and pre-commit hook
-
-- Preserve terminal state when switching projects
-
-- Close parent modal when Edit dialog opens
-
-- Solve LadybugDB problem on Windows during npm install
-
-- Handle Windows CRLF line endings in regex fallback
-
-- Respect preferred terminal setting for Windows PTY shell
-
-- Detect and clear cross-platform CLI paths in settings
-
-- Preserve original task description after spec creation
-
-- Fix learning loop to retrieve patterns and gotchas
-
-- Resolve frontend lag and update dependencies
-
-- Allow external HTTPS images in Content-Security-Policy
-
-- Use temporary worktree for PR review isolation
-
-- Prefer versioned Homebrew Python over system python3
-
-- Support bun.lock text format for Bun 1.2.0+
-
-- Create spec.md during roadmap-to-task conversion
-
-- Treat LOW-only findings as ready to merge in PR review
-
-- Prevent infinite re-render loop in task selection
-
-- Accept Python 3.12+ in install-backend.js
-
-- Infinite loop in useTaskDetail merge preview loading
-
-- Resolve EINVAL error when opening worktree in VS Code on Windows
-
-- Add fallback to prevent tasks stuck in ai_review status
-
-- Add spec_dir to SDK permissions
-
-- Add --base-branch argument support to spec_runner
-
-- Allow Windows to run PR Reviewer
-
-- Respect task_metadata.json model selection
-
-- Add .js extension to electron-log/main imports
-
-- Move Swift detection before Ruby detection in analyzer
-
-- Prevent TaskEditDialog from unmounting when opened
-
-- Add iOS/Swift project detection
-
-- Memory Status card respects configured embedding provider
-
-- Remove projectTabs from useEffect dependencies to fix re-render loop
-
-- Invalidate profile cache when file is created/modified
-
-- Handle Python paths with spaces in subprocess
-
-- Preserve terminal state when switching projects
-
-- Add C#/Java/Swift/Kotlin project files to security hash
-
-- Make backend tests pass on Windows
-
-- Stop tracking spec files in git
-
-- Sync status to worktree implementation plan to prevent reset
-
-- Fix task status persistence reverting on refresh
-
-- Proper semver comparison for pre-release versions
-
-- Use venv Python for all services to fix dotenv errors
-
-- Use explicit Windows System32 tar path in build
-
-- Use PowerShell for tar extraction on Windows
-
-- Add --force-local flag to tar on Windows
-
-- Add explicit GET method to gh api comment fetches
-
-- Support archiving tasks across all worktree locations
-
-- Validate backend source path before using it
-
-- Resolve spawn python ENOENT error on Linux
-
-- Resolve CodeQL file system race conditions and unused variables
-
-- Use correct electron-builder arch flags
-
-- Use develop branch for dry-run builds in beta-release workflow
-
-- Accept bug_fix workflow_type alias during planning
-
-- Normalize relative paths to posix
-
-- Update path resolution for ollama_model_detector.py in memory handlers
-
-- Resolve Python detection and backend packaging issues
-
-- Add future annotations import to discovery.py
-
-- Add global spec numbering lock to prevent collisions
-
-- Add Python 3.10+ version validation and GitHub Actions Python setup
-
-- Correct welcome workflow PR message
-
-- Hide status badge when execution phase badge is showing
-
-- Stop running process when task status changes away from in_progress
-
-- Remove legacy path from auto-claude source detection
-
-- Resolve Python environment race condition
-
-- Persist staged task state across app restarts
-
-- Update progress calculation to include just-completed ideation type
-
-- Add missing ARIA attributes for screen reader accessibility
-
-- Restore missing aria-label attributes on icon buttons
-
-- Enable scrolling in Project Files list in Task Creation Wizard
-
----
-
-## What's Changed
-
-- chore: bump version to 2.7.3 by @Test User in 53e2ef6c
-- fix(core): implement atomic JSON writes to prevent file corruption (ACS-209) (#915) by @StillKnotKnown in 3c56a1ba
-- fix(frontend): prevent "Render frame was disposed" crash (ACS-211) (#918) by @StillKnotKnown in 179744e2
-- fix(frontend): strip ANSI escape codes from roadmap/ideation progress messages (ACS-219) (#933) by @StillKnotKnown in 9e86de76
-- fix(ACS-175): Resolve integrations freeze and improve rate limit handling (#839) by @Michael Ludlow in 3ca15e1c
-- fix(memory): use shared project-wide memory for cross-spec learning (#905) by @StillKnotKnown in 0c139add
-- fix(graphiti): add isinstance(dict) validation to prevent AttributeError (ACS-215) (#924) by @StillKnotKnown in d9e3b286
-- fix(planner): enforce implementation_plan schema (issue #884) (#912) by @Umaru in 29d28bf0
-- fix(build): remove obsolete @lydell/node-pty extraResources entry by @Test User in c4e08aee
-- fix(ui): add Post Clean Review button for clean PR reviews (ACS-201) (#894) by @StillKnotKnown in f43c7c51
-- fix(ACS-203): Fix Kanban status flip-flop and phase state inconsistency (#898) by @StillKnotKnown in 96fc6129
-- fix(merge): resolve multiple merge-related issues (ACS-194, ACS-179, ACS-174, ACS-163) (#885) by @StillKnotKnown in d024eec1
-- fix(github-prs): show running review state when switching back to PR with in-progress review (ACS-200) (#890) by @StillKnotKnown in d9ed8179
-- fix: properly quote Windows .cmd/.bat paths in spawn() calls (#889) by @StillKnotKnown in 6dc538c8
-- Fix/worktree branch selection (#854) by @Andy in a6bd8842
-- refactor(ui): extract shared task form components for consistent modals (#765) by @Andy in df540ec5
-- fix(ui): persist staged task state across app restarts (#800) by @Andy in 91bd2401
-- fix: improve Claude CLI detection on Windows with space-containing paths (#827) by @Umaru in 11710c55
-- fix(ui): display subtask titles instead of UUIDs (#844) (#849) by @Andy in 660e1ada
-- fix(ci): use HTTP for Azure Trusted Signing timestamp URL (#843) by @Andy in 152678bd
-- fix(ACS-51, ACS-55, ACS-71): Fix Kanban state transitions and status flip-flop bug (#824) by @Adam Slaker in dc29794e
-- fix(github): use selectedPR from hook to restore Files changed list (#822) by @StillKnotKnown in c623ab00
-- ci(release): add Azure Trusted Signing for Windows builds (#805) by @Andy in 20458849
-- feat: Add Sentry environment variables to CI build workflows (#803) by @Andy in 63e142ae
-- Fix pydantic_core missing module error during packaging (#806) by @Maxim Kosterin in 07ae1ef7
-- feat: add Claude Code changelog link to version notifiers (#820) by @StillKnotKnown in ada91fb1
-- feat(github): enhance PR merge readiness checks with branch state validation (#751) by @Andy in cbb1cb81
-- fix: automate auto labeling based on comments (#812) by @Alex in 32e8fee3
-- feat: add PR creation workflow for task worktrees (#677) by @ThrownLemon in a74bd865
-- fix: increase Claude SDK JSON buffer size to 10MB (#815) by @StillKnotKnown in e310d56f
-- fix(a11y): restore missing aria-label attributes on icon buttons (#808) by @Orinks in ab3149fc
-- feat: Add terminal copy/paste keyboard shortcuts for Windows/Linux (#786) by @StillKnotKnown in a6ffd0e1
-- fix(ui): enable scrolling in Project Files list in Task Creation Wizard (#757) (#785) by @Ashwinhegde19 in 05c652e4
-- fix: resolve subtasks tab not updating on Linux (#794) by @StillKnotKnown in 29ef46d7
-- fix: add PYTHONPATH to subprocess environment for bundled packages (#139) (#777) by @Andy in a47354b4
-- fix(terminal): prevent crash after worktree creation (#771) by @Andy in 40fc7e4d
-- feat(pr-review): add prominent verdict summary to PR review comments (#780) by @Andy in 63766f76
-- fix(frontend): ensure PATH includes system directories when launched (#748) by @Marcelo Czerewacz in 4cc9198a
-- fix(permissions): grant worktree access to original project directories (#385) (#776) by @Andy in 42033412
-- fix(multi-project): filter task IPC events by project to prevent cross-project interference (#723) (#775) by @Andy in cc78d7ae
-- fix(python-bundling): verify critical packages exist, not just marker file (#416) (#774) by @Andy in 061411d7
-- fix(insights): await async sendMessage to prevent race condition (#613) (#773) by @Andy in cbd47f2c
-- fix(windows): add pywin32 dependency for LadybugDB (#627) (#778) by @Andy in fbaf2e7a
-- fix(memory): handle Ollama version errors during model pull (#760) by @Brett Bonner in 01decaeb
-- ACS-103 Windows can finish a task (#739) by @Alex in 96b7eb4a
-- fix(roadmap): normalize feature status values for Kanban display [ACS-115] (#763) by @Michael Ludlow in 5e783908
-- fix: add helpful error message when Python dependencies are missing (ACS-145) (#755) by @StillKnotKnown in 31519c2a
-- fix(startup): prevent app freeze by making Claude CLI detection non-blocking (#680 regression) (#720) by @Adam Slaker in f4069590
-- refactor: simplify task description handling and improve modal layout (#750) by @Andy in e3d72d64
-- fix(memory): use Homebrew for Ollama installation on macOS (#742) by @Michael Ludlow in e9c859cc
-- fix: use --continue instead of --resume for Claude session restoration (#699) by @Andy in 7fda36ad
-- fix: Multiple bug fixes including binary file handling and semantic tracking (#732) by @Andy in 78b80bca
-- fix(a11y): Add context menu for keyboard-accessible task status changes (#710) by @Orinks in 724ad827
-- Fix: Security allowlist not working in worktree mode (#646) by @arcker in 2f321fb2
-- fix: InvestigationDialog overflow issue (#669) by @Masanori Uehara in df57fbf8
-- fix(setup): auto-create .env from .env.example during backend install (#713) by @Crimson341 in 84bc5226
-- fix: show OAuth terminal during profile authentication (#671) by @Bogdan Dragomir in 8a4b5066
-- fix: pass augmented env to Claude CLI validation on macOS (#640) by @tallinn102 in 574cd117
-- fix: WIndows not finding the gith bash path (#724) by @Alex in 09aa4f4f
-- fix(profiles): support API profiles in auth check and model resolution (#608) by @Ginanjar Noviawan in 78aceaed
-- Fix Window Size on Hi-DPI Displays (#696) by @aaronson2012 in 5005e56e
-- fix: centralize Claude CLI invocation (#680) by @StillKnotKnown in ec4441c1
-- fix(github): pass OAuth token to Python runner subprocesses (fixes #563) (#698) by @Michael Ludlow in 97f34496
-- chore: Update Linux app icon to use multiple resolution sizes and fix .deb icon (#672) by @Rooki in 2c9fcbf4
-- fix(a11y): Add missing ARIA attributes for screen reader accessibility (#634) by @Orinks in 3930b12c
-- docs: add stars badge and star history chart to README (#675) by @eddie333016 in e2937320
-- fix(terminal): resolve React Fast Refresh hook error in usePtyProcess by @AndyMik90 in 81afc3d2
-- sentry dev support + sessions handling in terminals by @AndyMik90 in 63f46173
-- fix(frontend): detect @lydell/node-pty prebuilts in postinstall (#673) by @Vinícius Santos in 35573fd5
-- Fix/small fixes all around (#645) by @Andy in 7b4993e9
-- fix: detect Claude CLI installed via NVM on Linux/macOS (#623) by @StillKnotKnown in c2713543
-- fix: improve GLM presets, ideation auth, and Insights env (#648) by @StillKnotKnown in 6fb2d484
-- Fix/update app (#594) by @Andy in 1e3e8bda
-- feat(sentry): add anonymous error reporting with privacy controls (#636) by @Andy in 8be0e6ff
-- fix(settings): allow toggle deselection and improve embedding model name matching (#661) by @Michael Ludlow in 234d44f6
-- fix(python): sanitize environment to prevent PYTHONHOME contamination (#664) by @Michael Ludlow in 65f60898
-- fix: check .claude.json for OAuth auth in profile scorer (#652) by @Michael Ludlow in eeef8a3d
-- fix(mcp): use shell mode for Windows command spawning (#572) by @Andy in e1e89430
-- fix(ui): update TaskCard description truncation for improved display (#637) by @Andy in b7203124
-- fix: change hardcoded Opus defaults to Sonnet (fix #433) (#633) by @Michael Ludlow in 46c41f8f
-- Fix/small fixes 2.7.3 (#631) by @Andy in 39da8193
-- fix(ci): include update manifests for architecture-specific auto-updates (#611) by @Hunter Luisi in f7b02e87
-- fix: security hook cwd extraction and PATH issues (#555, #556) (#587) by @Hunter Luisi in 4ec9db8c
-- fix(frontend): filter empty env vars to prevent OAuth token override (#520) by @Ashwinhegde19 in 556f0b21
-- refactor(github-review): replace confidence scoring with evidence-based validation (#628) by @Andy in acdd7d9b
-- feat(terminal): add worktree support for terminals (#625) by @Andy in 13535f1b
-- fix: human_review status persistence bug (worktree plan path fix) (#605) by @Michael Ludlow in 7177c799
-- fix(frontend): resolve PATH and PYTHONPATH issues in insights and changelog services (#558) (#610) by @Hunter Luisi in f5be7943
-- fix: pass electron version explicitly to electron-rebuild on Windows (#622) by @Vinícius Santos in 14b3db56
-- fix(kanban): complete refresh button implementation (#584) by @Michael Ludlow in 6c855905
-- feat: add Dart/Flutter/Melos support to security profiles (#583) by @Mitsu in 4a833048
-- docs: update stable download links to v2.7.2 (#579) by @Alex in 5efc2c56
-- Improving Task Card Title Readability (#461) by @Vinícius Santos in 3086233f
-- feat: custom Anthropic compatible API profile management (#181) by @Ginanjar Noviawan in d278963b
-- 2.7.2 release by @AndyMik90 in 6ac3012f
-- fix: Solve ladybug problem on running npm install all on windows (#576) by @Alex in effaa681
-- fix(merge): handle Windows CRLF line endings in regex fallback by @AndyMik90 in 04de8c78
-- ci(release): add CHANGELOG.md validation and fix release workflow by @AndyMik90 in 6d4231ed
-- 🔥 hotfix(electron): restore app functionality on Windows broken by GPU cache errors (#569) by @sniggl in dedd0757
-- fix(ci): cache pip wheels to speed up Intel Mac builds by @AndyMik90 in 90dddc28
-- feat(terminal): respect preferred terminal setting for Windows PTY shell by @AndyMik90 in 90a20320
-- fix(ci): add Python setup to beta-release and fix PR status gate checks (#565) by @Andy in c2148bb9
-- fix: detect and clear cross-platform CLI paths in settings (#535) by @Andy in 29e45505
-- fix(ui): preserve original task description after spec creation (#536) by @Andy in 7990dcb4
-- fix(memory): fix learning loop to retrieve patterns and gotchas (#530) by @Andy in f58c2578
-- fix: resolve frontend lag and update dependencies (#526) by @Andy in 30f7951a
-- fix(csp): allow external HTTPS images in Content-Security-Policy (#549) by @Michael Ludlow in 3db02c5d
-- fix(pr-review): use temporary worktree for PR review isolation (#532) by @Andy in 344ec65e
-- fix: prefer versioned Homebrew Python over system python3 (#494) by @Navid in 8d58dd6f
-- fix(detection): support bun.lock text format for Bun 1.2.0+ (#525) by @Andy in 4da8cd66
-- chore: bump version to 2.7.2-beta.12 (#460) by @Andy in 8e5c11ac
-- Fix/windows issues (#471) by @Andy in 72106109
-- fix(ci): add Rust toolchain for Intel Mac builds (#459) by @Andy in 52a4fcc6
-- fix: create spec.md during roadmap-to-task conversion (#446) by @Mulaveesala Pranaveswar in fb6b7fc6
-- fix(pr-review): treat LOW-only findings as ready to merge (#455) by @Andy in 0f9c5b84
-- Fix/2.7.2 beta12 (#424) by @Andy in 5d8ede23
-- feat: remove top bars (#386) by @Vinícius Santos in da31b687
-- fix: prevent infinite re-render loop in task selection useEffect (#442) by @Abe Diaz in 2effa535
-- fix: accept Python 3.12+ in install-backend.js (#443) by @Abe Diaz in c15bb311
-- fix: infinite loop in useTaskDetail merge preview loading (#444) by @Abe Diaz in 203a970a
-- fix(windows): resolve EINVAL error when opening worktree in VS Code (#434) by @Vinícius Santos in 3c0708b7
-- feat(frontend): Add Files tab to task details panel (#430) by @Mitsu in 666794b5
-- refactor: remove deprecated TaskDetailPanel component (#432) by @Mitsu in ac8dfcac
-- fix(ui): add fallback to prevent tasks stuck in ai_review status (#397) by @Michael Ludlow in 798ca79d
-- feat: Enhance the look of the PR Detail area (#427) by @Alex in bdb01549
-- ci: remove conventional commits PR title validation workflow by @AndyMik90 in 515b73b5
-- fix(client): add spec_dir to SDK permissions (#429) by @Mitsu in 88c76059
-- fix(spec_runner): add --base-branch argument support (#428) by @Mitsu in 62a75515
-- feat: enhance pr review page to include PRs filters (#423) by @Alex in 717fba04
-- feat: add gitlab integration (#254) by @Mitsu in 0a571d3a
-- fix: Allow windows to run CC PR Reviewer (#406) by @Alex in 2f662469
-- fix(model): respect task_metadata.json model selection (#415) by @Andy in e7e6b521
-- feat(build): add Flatpak packaging support for Linux (#404) by @Mitsu in 230de5fc
-- fix(github): pass repo parameter to GHClient for explicit PR resolution (#413) by @Andy in 4bdf7a0c
-- chore(ci): remove redundant CLA GitHub Action workflow by @AndyMik90 in a39ea49d
-- fix(frontend): add .js extension to electron-log/main imports by @AndyMik90 in 9aef0dd0
-- fix: 2.7.2 bug fixes and improvements (#388) by @Andy in 05131217
-- fix(analyzer): move Swift detection before Ruby detection (#401) by @Michael Ludlow in 321c9712
-- fix(ui): prevent TaskEditDialog from unmounting when opened (#395) by @Michael Ludlow in 98b12ed8
-- fix: improve CLI tool detection and add Claude CLI path settings (#393) by @Joe in aaa83131
-- feat(analyzer): add iOS/Swift project detection (#389) by @Michael Ludlow in 68548e33
-- fix(github): improve PR review with structured outputs and fork support (#363) by @Andy in 7751588e
-- fix(ideation): update progress calculation to include just-completed ideation type (#381) by @Illia Filippov in 8b4ce58c
-- Fixes failing spec - "gh CLI Check Handler - should return installed: true when gh CLI is found" (#370) by @Ian in bc220645
-- fix: Memory Status card respects configured embedding provider (#336) (#373) by @Michael Ludlow in db0cbea3
-- fix: fixed version-specific links in readme and pre-commit hook that updates them (#378) by @Ian in 0ca2e3f6
-- docs: add security research documentation (#361) by @Brian in 2d3b7fb4
-- fix/Improving UX for Display/Scaling Changes (#332) by @Kevin Rajan in 9bbdef09
-- fix(perf): remove projectTabs from useEffect deps to fix re-render loop (#362) by @Michael Ludlow in 753dc8bb
-- fix(security): invalidate profile cache when file is created/modified (#355) by @Michael Ludlow in 20f20fa3
-- fix(subprocess): handle Python paths with spaces (#352) by @Michael Ludlow in eabe7c7d
-- fix: Resolve pre-commit hook failures with version sync, pytest path, ruff version, and broken quality-dco workflow (#334) by @Ian in 1fa7a9c7
-- fix(terminal): preserve terminal state when switching projects (#358) by @Andy in 7881b2d1
-- fix(analyzer): add C#/Java/Swift/Kotlin project files to security hash (#351) by @Michael Ludlow in 4e71361b
-- fix: make backend tests pass on Windows (#282) by @Oluwatosin Oyeladun in 4dcc5afa
-- fix(ui): close parent modal when Edit dialog opens (#354) by @Michael Ludlow in e9782db0
-- chore: bump version to 2.7.2-beta.10 by @AndyMik90 in 40d04d7c
-- feat: add terminal dropdown with inbuilt and external options in task review (#347) by @JoshuaRileyDev in fef07c95
-- refactor: remove deprecated code across backend and frontend (#348) by @Mitsu in 9d43abed
-- feat: centralize CLI tool path management (#341) by @HSSAINI Saad in d51f4562
-- refactor(components): remove deprecated TaskDetailPanel re-export (#344) by @Mitsu in 787667e9
-- chore: Refactor/kanban realtime status sync (#249) by @souky-byte in 9734b70b
-- refactor(settings): remove deprecated ProjectSettings modal and hooks (#343) by @Mitsu in fec6b9f3
-- perf: convert synchronous I/O to async operations in worktree handlers (#337) by @JoshuaRileyDev in d3a63b09
-- feat: bump version (#329) by @Alex in 50e3111a
-- fix(ci): remove version bump to fix branch protection conflict (#325) by @Michael Ludlow in 8a80b1d5
-- fix(tasks): sync status to worktree implementation plan to prevent reset (#243) (#323) by @Alex in cb6b2165
-- fix(ci): add auto-updater manifest files and version auto-update (#317) by @Michael Ludlow in 661e47c3
-- fix(project): fix task status persistence reverting on refresh (#246) (#318) by @Michael Ludlow in e80ef79d
-- fix(updater): proper semver comparison for pre-release versions (#313) by @Michael Ludlow in e1b0f743
-- fix(python): use venv Python for all services to fix dotenv errors (#311) by @Alex in 92c6f278
-- chore(ci): cancel in-progress runs (#302) by @Oluwatosin Oyeladun in 1c142273
-- fix(build): use explicit Windows System32 tar path (#308) by @Andy in c0a02a45
-- fix(github): add augmented PATH env to all gh CLI calls by @AndyMik90 in 086429cb
-- fix(build): use PowerShell for tar extraction on Windows by @AndyMik90 in d9fb8f29
-- fix(build): add --force-local flag to tar on Windows (#303) by @Andy in d0b0b3df
-- fix: stop tracking spec files in git (#295) by @Andy in 937a60f8
-- Fix/2.7.2 fixes (#300) by @Andy in 7a51cbd5
-- feat(merge,oauth): add path-aware AI merge resolution and device code streaming (#296) by @Andy in 26beefe3
-- feat: enhance the logs for the commit linting stage (#293) by @Alex in 8416f307
-- fix(github): add explicit GET method to gh api comment fetches (#294) by @Andy in 217249c8
-- fix(frontend): support archiving tasks across all worktree locations (#286) by @Andy in 8bb3df91
-- Potential fix for code scanning alert no. 224: Uncontrolled command line (#285) by @Andy in 5106c6e9
-- fix(frontend): validate backend source path before using it (#287) by @Andy in 3ff61274
-- feat(python): bundle Python 3.12 with packaged Electron app (#284) by @Andy in 7f19c2e1
-- fix: resolve spawn python ENOENT error on Linux by using getAugmentedEnv() (#281) by @Todd W. Bucy in d98e2830
-- fix(ci): add write permissions to beta-release update-version job by @AndyMik90 in 0b874d4b
-- chore(deps): bump @xterm/xterm from 5.5.0 to 6.0.0 in /apps/frontend (#270) by @dependabot[bot] in 50dd1078
-- fix(github): resolve follow-up review API issues by @AndyMik90 in f1cc5a09
-- fix(security): resolve CodeQL file system race conditions and unused variables (#277) by @Andy in b005fa5c
-- fix(ci): use correct electron-builder arch flags (#278) by @Andy in d79f2da4
-- chore(deps): bump jsdom from 26.1.0 to 27.3.0 in /apps/frontend (#268) by @dependabot[bot] in 5ac566e2
-- chore(deps): bump typescript-eslint in /apps/frontend (#269) by @dependabot[bot] in f49d4817
-- fix(ci): use develop branch for dry-run builds in beta-release workflow (#276) by @Andy in 1e1d7d9b
-- fix: accept bug_fix workflow_type alias during planning (#240) by @Daniel Frey in e74a3dff
-- fix(paths): normalize relative paths to posix (#239) by @Daniel Frey in 6ac8250b
-- chore(deps): bump @electron/rebuild in /apps/frontend (#271) by @dependabot[bot] in a2cee694
-- chore(deps): bump vitest from 4.0.15 to 4.0.16 in /apps/frontend (#272) by @dependabot[bot] in d4cad80a
-- feat(github): add automated PR review with follow-up support (#252) by @Andy in 596e9513
-- ci: implement enterprise-grade PR quality gates and security scanning (#266) by @Alex in d42041c5
-- fix: update path resolution for ollama_model_detector.py in memory handlers (#263) by @delyethan in a3f87540
-- feat: add i18n internationalization system (#248) by @Mitsu in f8438112
-- Revert "Feat/Auto Fix Github issues and do extensive AI PR reviews (#250)" (#251) by @Andy in 5e8c5308
-- Feat/Auto Fix Github issues and do extensive AI PR reviews (#250) by @Andy in 348de6df
-- fix: resolve Python detection and backend packaging issues (#241) by @HSSAINI Saad in 0f7d6e05
-- fix: add future annotations import to discovery.py (#229) by @Joris Slagter in 5ccdb6ab
-- Fix/ideation status sync (#212) by @souky-byte in 6ec8549f
-- fix(core): add global spec numbering lock to prevent collisions (#209) by @Andy in 53527293
-- feat: Add OpenRouter as LLM/embedding provider (#162) by @Fernando Possebon in 02bef954
-- fix: Add Python 3.10+ version validation and GitHub Actions Python setup (#180 #167) (#208) by @Fernando Possebon in f168bdc3
-- fix(ci): correct welcome workflow PR message (#206) by @Andy in e3eec68a
-- Feat/beta release (#193) by @Andy in 407a0bee
-- feat/beta-release (#190) by @Andy in 8f766ad1
-- fix/PRs from old main setup to apps structure (#185) by @Andy in ced2ad47
-- fix: hide status badge when execution phase badge is showing (#154) by @Andy in 05f5d303
-- feat: Add UI scale feature with 75-200% range (#125) by @Enes Cingöz in 6951251b
-- fix(task): stop running process when task status changes away from in_progress by @AndyMik90 in 30e7536b
-- Fix/linear 400 error by @Andy in 220faf0f
-- fix: remove legacy path from auto-claude source detection (#148) by @Joris Slagter in f96c6301
-- fix: resolve Python environment race condition (#142) by @Joris Slagter in ebd8340d
-- Feat: Ollama download progress tracking with new apps structure (#141) by @rayBlock in df779530
-- Feature/apps restructure v2.7.2 (#138) by @Andy in 0adaddac
-- docs: Add Git Flow branching strategy to CONTRIBUTING.md by @AndyMik90 in 91f7051d
-
-## Thanks to all contributors
-
-@Test User, @StillKnotKnown, @Umaru, @Andy, @Adam Slaker, @Michael Ludlow, @Maxim Kosterin, @ThrownLemon, @Ashwinhegde19, @Orinks, @Marcelo Czerewacz, @Brett Bonner, @Alex, @Rooki, @eddie333016, @AndyMik90, @Vinícius Santos, @arcker, @Masanori Uehara, @Crimson341, @Bogdan Dragomir, @tallinn102, @Ginanjar Noviawan, @aaronson2012, @Hunter Luisi, @Navid, @Mulaveesala Pranaveswar, @sniggl, @Abe Diaz, @Mitsu, @Joe, @Illia Filippov, @Ian, @Brian, @Kevin Rajan, @HSSAINI Saad, @JoshuaRileyDev, @souky-byte, @Alex, @Oluwatosin Oyeladun, @Daniel Frey, @delyethan, @Joris Slagter, @Fernando Possebon, @Enes Cingöz, @Todd W. Bucy, @dependabot[bot], @rayBlock
-
-## 2.7.2 - Stability & Performance Enhancements
-
-### ✨ New Features
-
-- Added refresh button to Kanban board for manually reloading tasks
-
-- Terminal dropdown with built-in and external options in task review
-
-- Centralized CLI tool path management with customizable settings
-
-- Files tab in task details panel for better file organization
-
-- Enhanced PR review page with filtering capabilities
-
-- GitLab integration support
-
-- Automated PR review with follow-up support and structured outputs
-
-- UI scale feature with 75-200% range for accessibility
-
-- Python 3.12 bundled with packaged Electron app
-
-- OpenRouter support as LLM/embedding provider
-
-- Internationalization (i18n) system for multi-language support
-
-- Flatpak packaging support for Linux
-
-- Path-aware AI merge resolution with device code streaming
-
-### 🛠️ Improvements
-
-- Improved terminal experience with persistent state when switching projects
-
-- Enhanced PR review with structured outputs and fork support
-
-- Better UX for display and scaling changes
-
-- Convert synchronous I/O to async operations in worktree handlers
-
-- Enhanced logs for commit linting stage
-
-- Remove top navigation bars for cleaner UI
-
-- Enhanced PR detail area visual design
-
-- Improved CLI tool detection with more language support
-
-- Added iOS/Swift project detection
-
-- Optimize performance by removing projectTabs from useEffect dependencies
-
-- Improved Python detection and version validation for compatibility
-
-### 🐛 Bug Fixes
-
-- Fixed CI Python setup and PR status gate checks
-
-- Fixed cross-platform CLI path detection and clearing in settings
-
-- Preserve original task description after spec creation
-
-- Fixed learning loop to retrieve patterns and gotchas from memory
-
-- Resolved frontend lag and updated dependencies
-
-- Fixed Content-Security-Policy to allow external HTTPS images
-
-- Fixed PR review isolation by using temporary worktree
-
-- Fixed Homebrew Python detection to prefer versioned Python over system python3
-
-- Added support for Bun 1.2.0+ lock file format detection
-
-- Fixed infinite re-render loop in task selection
-
-- Fixed infinite loop in task detail merge preview loading
-
-- Resolved Windows EINVAL error when opening worktree in VS Code
-
-- Fixed fallback to prevent tasks stuck in ai_review status
-
-- Fixed SDK permissions to include spec_dir
-
-- Added --base-branch argument support to spec_runner
-
-- Allow Windows to run CC PR Reviewer
-
-- Fixed model selection to respect task_metadata.json
-
-- Improved GitHub PR review by passing repo parameter explicitly
-
-- Fixed electron-log imports with .js extension
-
-- Fixed Swift detection order in project analyzer
-
-- Prevent TaskEditDialog from unmounting when opened
-
-- Fixed subprocess handling for Python paths with spaces
-
-- Fixed file system race conditions and unused variables in security scanning
-
-- Resolved Python detection and backend packaging issues
-
-- Fixed version-specific links in README and pre-commit hooks
-
-- Fixed task status persistence reverting on refresh
-
-- Proper semver comparison for pre-release versions
-
-- Use virtual environment Python for all services to fix dotenv errors
-
-- Fixed explicit Windows System32 tar path for builds
-
-- Added augmented PATH environment to all GitHub CLI calls
-
-- Use PowerShell for tar extraction on Windows
-
-- Added --force-local flag to tar on Windows
-
-- Stop tracking spec files in git
-
-- Fixed GitHub API calls with explicit GET method for comment fetches
-
-- Support archiving tasks across all worktree locations
-
-- Validated backend source path before using it
-
-- Resolved spawn Python ENOENT error on Linux
-
-- Fixed CodeQL alerts for uncontrolled command line
-
-- Resolved GitHub follow-up review API issues
-
-- Fixed relative path normalization to POSIX format
-
-- Accepted bug_fix workflow_type alias during planning
-
-- Added global spec numbering lock to prevent collisions
-
-- Fixed ideation status sync
-
-- Stopped running process when task status changes away from in_progress
-
-- Removed legacy path from auto-claude source detection
-
-- Resolved Python environment race condition
-
----
-
-## What's Changed
-
-- fix(ci): add Python setup to beta-release and fix PR status gate checks (#565) by @Andy in c2148bb9
-- fix: detect and clear cross-platform CLI paths in settings (#535) by @Andy in 29e45505
-- fix(ui): preserve original task description after spec creation (#536) by @Andy in 7990dcb4
-- fix(memory): fix learning loop to retrieve patterns and gotchas (#530) by @Andy in f58c2578
-- fix: resolve frontend lag and update dependencies (#526) by @Andy in 30f7951a
-- feat(kanban): add refresh button to manually reload tasks (#548) by @Adryan Serage in 252242f9
-- fix(csp): allow external HTTPS images in Content-Security-Policy (#549) by @Michael Ludlow in 3db02c5d
-- fix(pr-review): use temporary worktree for PR review isolation (#532) by @Andy in 344ec65e
-- fix: prefer versioned Homebrew Python over system python3 (#494) by @Navid in 8d58dd6f
-- fix(detection): support bun.lock text format for Bun 1.2.0+ (#525) by @Andy in 4da8cd66
-- chore: bump version to 2.7.2-beta.12 (#460) by @Andy in 8e5c11ac
-- Fix/windows issues (#471) by @Andy in 72106109
-- fix(ci): add Rust toolchain for Intel Mac builds (#459) by @Andy in 52a4fcc6
-- fix: create spec.md during roadmap-to-task conversion (#446) by @Mulaveesala Pranaveswar in fb6b7fc6
-- fix(pr-review): treat LOW-only findings as ready to merge (#455) by @Andy in 0f9c5b84
-- Fix/2.7.2 beta12 (#424) by @Andy in 5d8ede23
-- feat: remove top bars (#386) by @Vinícius Santos in da31b687
-- fix: prevent infinite re-render loop in task selection useEffect (#442) by @Abe Diaz in 2effa535
-- fix: accept Python 3.12+ in install-backend.js (#443) by @Abe Diaz in c15bb311
-- fix: infinite loop in useTaskDetail merge preview loading (#444) by @Abe Diaz in 203a970a
-- fix(windows): resolve EINVAL error when opening worktree in VS Code (#434) by @Vinícius Santos in 3c0708b7
-- feat(frontend): Add Files tab to task details panel (#430) by @Mitsu in 666794b5
-- refactor: remove deprecated TaskDetailPanel component (#432) by @Mitsu in ac8dfcac
-- fix(ui): add fallback to prevent tasks stuck in ai_review status (#397) by @Michael Ludlow in 798ca79d
-- feat: Enhance the look of the PR Detail area (#427) by @Alex in bdb01549
-- ci: remove conventional commits PR title validation workflow by @AndyMik90 in 515b73b5
-- fix(client): add spec_dir to SDK permissions (#429) by @Mitsu in 88c76059
-- fix(spec_runner): add --base-branch argument support (#428) by @Mitsu in 62a75515
-- feat: enhance pr review page to include PRs filters (#423) by @Alex in 717fba04
-- feat: add gitlab integration (#254) by @Mitsu in 0a571d3a
-- fix: Allow windows to run CC PR Reviewer (#406) by @Alex in 2f662469
-- fix(model): respect task_metadata.json model selection (#415) by @Andy in e7e6b521
-- feat(build): add Flatpak packaging support for Linux (#404) by @Mitsu in 230de5fc
-- fix(github): pass repo parameter to GHClient for explicit PR resolution (#413) by @Andy in 4bdf7a0c
-- chore(ci): remove redundant CLA GitHub Action workflow by @AndyMik90 in a39ea49d
-- fix(frontend): add .js extension to electron-log/main imports by @AndyMik90 in 9aef0dd0
-- fix: 2.7.2 bug fixes and improvements (#388) by @Andy in 05131217
-- fix(analyzer): move Swift detection before Ruby detection (#401) by @Michael Ludlow in 321c9712
-- fix(ui): prevent TaskEditDialog from unmounting when opened (#395) by @Michael Ludlow in 98b12ed8
-- fix: improve CLI tool detection and add Claude CLI path settings (#393) by @Joe in aaa83131
-- feat(analyzer): add iOS/Swift project detection (#389) by @Michael Ludlow in 68548e33
-- fix(github): improve PR review with structured outputs and fork support (#363) by @Andy in 7751588e
-- fix(ideation): update progress calculation to include just-completed ideation type (#381) by @Illia Filippov in 8b4ce58c
-- Fixes failing spec - "gh CLI Check Handler - should return installed: true when gh CLI is found" (#370) by @Ian in bc220645
-- fix: Memory Status card respects configured embedding provider (#336) (#373) by @Michael Ludlow in db0cbea3
-- fix: fixed version-specific links in readme and pre-commit hook that updates them (#378) by @Ian in 0ca2e3f6
-- docs: add security research documentation (#361) by @Brian in 2d3b7fb4
-- fix/Improving UX for Display/Scaling Changes (#332) by @Kevin Rajan in 9bbdef09
-- fix(perf): remove projectTabs from useEffect deps to fix re-render loop (#362) by @Michael Ludlow in 753dc8bb
-- fix(security): invalidate profile cache when file is created/modified (#355) by @Michael Ludlow in 20f20fa3
-- fix(subprocess): handle Python paths with spaces (#352) by @Michael Ludlow in eabe7c7d
-- fix: Resolve pre-commit hook failures with version sync, pytest path, ruff version, and broken quality-dco workflow (#334) by @Ian in 1fa7a9c7
-- fix(terminal): preserve terminal state when switching projects (#358) by @Andy in 7881b2d1
-- fix(analyzer): add C#/Java/Swift/Kotlin project files to security hash (#351) by @Michael Ludlow in 4e71361b
-- fix: make backend tests pass on Windows (#282) by @Oluwatosin Oyeladun in 4dcc5afa
-- fix(ui): close parent modal when Edit dialog opens (#354) by @Michael Ludlow in e9782db0
-- chore: bump version to 2.7.2-beta.10 by @AndyMik90 in 40d04d7c
-- feat: add terminal dropdown with inbuilt and external options in task review (#347) by @JoshuaRileyDev in fef07c95
-- refactor: remove deprecated code across backend and frontend (#348) by @Mitsu in 9d43abed
-- feat: centralize CLI tool path management (#341) by @HSSAINI Saad in d51f4562
-- refactor(components): remove deprecated TaskDetailPanel re-export (#344) by @Mitsu in 787667e9
-- chore: Refactor/kanban realtime status sync (#249) by @souky-byte in 9734b70b
-- refactor(settings): remove deprecated ProjectSettings modal and hooks (#343) by @Mitsu in fec6b9f3
-- perf: convert synchronous I/O to async operations in worktree handlers (#337) by @JoshuaRileyDev in d3a63b09
-- feat: bump version (#329) by @Alex in 50e3111a
-- fix(ci): remove version bump to fix branch protection conflict (#325) by @Michael Ludlow in 8a80b1d5
-- fix(tasks): sync status to worktree implementation plan to prevent reset (#243) (#323) by @Alex in cb6b2165
-- fix(ci): add auto-updater manifest files and version auto-update (#317) by @Michael Ludlow in 661e47c3
-- fix(project): fix task status persistence reverting on refresh (#246) (#318) by @Michael Ludlow in e80ef79d
-- fix(updater): proper semver comparison for pre-release versions (#313) by @Michael Ludlow in e1b0f743
-- fix(python): use venv Python for all services to fix dotenv errors (#311) by @Alex in 92c6f278
-- chore(ci): cancel in-progress runs (#302) by @Oluwatosin Oyeladun in 1c142273
-- fix(build): use explicit Windows System32 tar path (#308) by @Andy in c0a02a45
-- fix(github): add augmented PATH env to all gh CLI calls by @AndyMik90 in 086429cb
-- fix(build): use PowerShell for tar extraction on Windows by @AndyMik90 in d9fb8f29
-- fix(build): add --force-local flag to tar on Windows (#303) by @Andy in d0b0b3df
-- fix: stop tracking spec files in git (#295) by @Andy in 937a60f8
-- Fix/2.7.2 fixes (#300) by @Andy in 7a51cbd5
-- feat(merge,oauth): add path-aware AI merge resolution and device code streaming (#296) by @Andy in 26beefe3
-- feat: enhance the logs for the commit linting stage (#293) by @Alex in 8416f307
-- fix(github): add explicit GET method to gh api comment fetches (#294) by @Andy in 217249c8
-- fix(frontend): support archiving tasks across all worktree locations (#286) by @Andy in 8bb3df91
-- Potential fix for code scanning alert no. 224: Uncontrolled command line (#285) by @Andy in 5106c6e9
-- fix(frontend): validate backend source path before using it (#287) by @Andy in 3ff61274
-- feat(python): bundle Python 3.12 with packaged Electron app (#284) by @Andy in 7f19c2e1
-- fix: resolve spawn python ENOENT error on Linux by using getAugmentedEnv() (#281) by @Todd W. Bucy in d98e2830
-- fix(ci): add write permissions to beta-release update-version job by @AndyMik90 in 0b874d4b
-- chore(deps): bump @xterm/xterm from 5.5.0 to 6.0.0 in /apps/frontend (#270) by @dependabot[bot] in 50dd1078
-- fix(github): resolve follow-up review API issues by @AndyMik90 in f1cc5a09
-- fix(security): resolve CodeQL file system race conditions and unused variables (#277) by @Andy in b005fa5c
-- fix(ci): use correct electron-builder arch flags (#278) by @Andy in d79f2da4
-- chore(deps): bump jsdom from 26.1.0 to 27.3.0 in /apps/frontend (#268) by @dependabot[bot] in 5ac566e2
-- chore(deps): bump typescript-eslint in /apps/frontend (#269) by @dependabot[bot] in f49d4817
-- fix(ci): use develop branch for dry-run builds in beta-release workflow (#276) by @Andy in 1e1d7d9b
-- fix: accept bug_fix workflow_type alias during planning (#240) by @Daniel Frey in e74a3dff
-- fix(paths): normalize relative paths to posix (#239) by @Daniel Frey in 6ac8250b
-- chore(deps): bump @electron/rebuild in /apps/frontend (#271) by @dependabot[bot] in a2cee694
-- chore(deps): bump vitest from 4.0.15 to 4.0.16 in /apps/frontend (#272) by @dependabot[bot] in d4cad80a
-- feat(github): add automated PR review with follow-up support (#252) by @Andy in 596e9513
-- ci: implement enterprise-grade PR quality gates and security scanning (#266) by @Alex in d42041c5
-- fix: update path resolution for ollama_model_detector.py in memory handlers (#263) by @delyethan in a3f87540
-- feat: add i18n internationalization system (#248) by @Mitsu in f8438112
-- Revert "Feat/Auto Fix Github issues and do extensive AI PR reviews (#250)" (#251) by @Andy in 5e8c5308
-- Feat/Auto Fix Github issues and do extensive AI PR reviews (#250) by @Andy in 348de6df
-- fix: resolve Python detection and backend packaging issues (#241) by @HSSAINI Saad in 0f7d6e05
-- fix: add future annotations import to discovery.py (#229) by @Joris Slagter in 5ccdb6ab
-- Fix/ideation status sync (#212) by @souky-byte in 6ec8549f
-- fix(core): add global spec numbering lock to prevent collisions (#209) by @Andy in 53527293
-- feat: Add OpenRouter as LLM/embedding provider (#162) by @Fernando Possebon in 02bef954
-- fix: Add Python 3.10+ version validation and GitHub Actions Python setup (#180 #167) (#208) by @Fernando Possebon in f168bdc3
-- fix(ci): correct welcome workflow PR message (#206) by @Andy in e3eec68a
-- Feat/beta release (#193) by @Andy in 407a0bee
-- feat/beta-release (#190) by @Andy in 8f766ad1
-- fix/PRs from old main setup to apps structure (#185) by @Andy in ced2ad47
-- fix: hide status badge when execution phase badge is showing (#154) by @Andy in 05f5d303
-- feat: Add UI scale feature with 75-200% range (#125) by @Enes Cingöz in 6951251b
-- fix(task): stop running process when task status changes away from in_progress by @AndyMik90 in 30e7536b
-- Fix/linear 400 error by @Andy in 220faf0f
-- fix: remove legacy path from auto-claude source detection (#148) by @Joris Slagter in f96c6301
-- fix: resolve Python environment race condition (#142) by @Joris Slagter in ebd8340d
-- Feat: Ollama download progress tracking with new apps structure (#141) by @rayBlock in df779530
-- Feature/apps restructure v2.7.2 (#138) by @Andy in 0adaddac
-- docs: Add Git Flow branching strategy to CONTRIBUTING.md by @AndyMik90 in 91f7051d
-
-## Thanks to all contributors
-
-@Andy, @Adryan Serage, @Michael Ludlow, @Navid, @Mulaveesala Pranaveswar, @Vinícius Santos, @Abe Diaz, @Mitsu, @Alex, @AndyMik90, @Joe, @Illia Filippov, @Ian, @Brian, @Kevin Rajan, @Oluwatosin Oyeladun, @JoshuaRileyDev, @HSSAINI Saad, @souky-byte, @Todd W. Bucy, @dependabot[bot], @Daniel Frey, @delyethan, @Joris Slagter, @Fernando Possebon, @Enes Cingöz, @rayBlock
-
 ## 2.7.1 - Build Pipeline Enhancements
 
 ### 🛠️ Improvements

CLA.md

@@ -1,76 +0,0 @@
-# Auto Claude Individual Contributor License Agreement
-
-Thank you for your interest in contributing to Auto Claude. This Contributor License Agreement ("Agreement") documents the rights granted by contributors to the Project.
-
-By signing this Agreement, you accept and agree to the following terms and conditions for your present and future Contributions submitted to the Project.
-
-## 1. Definitions
-
-**"You" (or "Your")** means the individual who submits a Contribution to the Project.
-
-**"Contribution"** means any original work of authorship, including any modifications or additions to an existing work, that is intentionally submitted by You to the Project for inclusion in, or documentation of, the Project. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Project or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Project for the purpose of discussing and improving the Project.
-
-**"Project"** means Auto Claude, a multi-agent autonomous coding framework, currently available at https://github.com/AndyMik90/Auto-Claude.
-
-**"Project Owner"** means Andre Mikalsen and any designated successors or assignees.
-
-## 2. Grant of Copyright License
-
-Subject to the terms and conditions of this Agreement, You hereby grant to the Project Owner and to recipients of software distributed by the Project Owner a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to:
-
-- Reproduce, prepare derivative works of, publicly display, publicly perform, and distribute Your Contributions and such derivative works
-- Sublicense any or all of the foregoing rights to third parties
-
-## 3. Grant of Patent License
-
-Subject to the terms and conditions of this Agreement, You hereby grant to the Project Owner and to recipients of software distributed by the Project Owner a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer Your Contributions, where such license applies only to those patent claims licensable by You that are necessarily infringed by Your Contribution(s) alone or by combination of Your Contribution(s) with the Project to which such Contribution(s) was submitted.
-
-## 4. Future Licensing Flexibility
-
-You understand and agree that the Project Owner may, in the future, license the Project, including Your Contributions, under additional licenses beyond the current GNU Affero General Public License version 3.0 (AGPL-3.0). Such additional licenses may include commercial or enterprise licenses.
-
-This provision ensures the Project has proper licensing flexibility should such licensing options be introduced in the future. The open source version of the Project will continue to be available under AGPL-3.0.
-
-## 5. Representations
-
-You represent that:
-
-(a) You are legally entitled to grant the above licenses. If your employer(s) has rights to intellectual property that you create that includes your Contributions, you represent that you have received permission to make Contributions on behalf of that employer, or that your employer has waived such rights for your Contributions to the Project.
-
-(b) Each of Your Contributions is Your original creation. You represent that Your Contribution submissions include complete details of any third-party license or other restriction (including, but not limited to, related patents and trademarks) of which you are personally aware and which are associated with any part of Your Contributions.
-
-(c) Your Contribution does not violate any third-party rights, including but not limited to intellectual property rights, privacy rights, or contractual obligations.
-
-## 6. Support and Warranty Disclaimer
-
-You are not expected to provide support for Your Contributions, except to the extent You desire to provide support. You may provide support for free, for a fee, or not at all.
-
-UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING, YOU PROVIDE YOUR CONTRIBUTIONS ON AN "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, WITHOUT LIMITATION, ANY WARRANTIES OR CONDITIONS OF TITLE, NON-INFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.
-
-## 7. No Obligation to Use
-
-You understand that the decision to include Your Contribution in any project or source repository is entirely at the discretion of the Project Owner, and this Agreement does not guarantee that Your Contributions will be included in any product.
-
-## 8. Contributor Rights
-
-You retain full copyright ownership of Your Contributions. Nothing in this Agreement shall be interpreted to prohibit you from licensing Your Contributions under different terms to third parties or from using Your Contributions for any other purpose.
-
-## 9. Notification
-
-You agree to notify the Project Owner of any facts or circumstances of which you become aware that would make these representations inaccurate in any respect.
-
----
-
-## How to Sign
-
-To sign this CLA, comment on your Pull Request with:
-
-```
-I have read the CLA Document and I hereby sign the CLA
-```
-
-Your signature will be recorded automatically.
-
----
-
-*This CLA is based on the Apache Software Foundation Individual Contributor License Agreement v2.0.*

CLAUDE.md

@@ -4,150 +4,94 @@ This file provides guidance to Claude Code (claude.ai/code) when working with co
 
 ## Project Overview
 
-Auto Claude is a multi-agent autonomous coding framework that builds software through coordinated AI agent sessions. It uses the Claude Agent SDK to run agents in isolated workspaces with security controls.
-
-**CRITICAL: All AI interactions use the Claude Agent SDK (`claude-agent-sdk` package), NOT the Anthropic API directly.**
-
-## Project Structure
-
-```
-autonomous-coding/
-├── apps/
-│   ├── backend/           # Python backend/CLI - ALL agent logic lives here
-│   │   ├── core/          # Client, auth, security
-│   │   ├── agents/        # Agent implementations
-│   │   ├── spec_agents/   # Spec creation agents
-│   │   ├── integrations/  # Graphiti, Linear, GitHub
-│   │   └── prompts/       # Agent system prompts
-│   └── frontend/          # Electron desktop UI
-├── guides/                # Documentation
-├── tests/                 # Test suite
-└── scripts/               # Build and utility scripts
-```
-
-**When working with AI/LLM code:**
-- Look in `apps/backend/core/client.py` for the Claude SDK client setup
-- Reference `apps/backend/agents/` for working agent implementations
-- Check `apps/backend/spec_agents/` for spec creation agent examples
-- NEVER use `anthropic.Anthropic()` directly - always use `create_client()` from `core.client`
-
-**Frontend (Electron Desktop App):**
-- Built with Electron, React, TypeScript
-- AI agents can perform E2E testing using the Electron MCP server
-- When bug fixing or implementing features, use the Electron MCP server for automated testing
-- See "End-to-End Testing" section below for details
+Auto Claude is a multi-agent autonomous coding framework that builds software through coordinated AI agent sessions. It uses the Claude Code SDK to run agents in isolated workspaces with security controls.
 
 ## Commands
 
 ### Setup
-
-**Requirements:**
-- Python 3.12+ (required for backend)
-- Node.js (for frontend)
-
 ```bash
-# Install all dependencies from root
-npm run install:all
-
-# Or install separately:
-# Backend (from apps/backend/)
-cd apps/backend && uv venv && uv pip install -r requirements.txt
-
-# Frontend (from apps/frontend/)
-cd apps/frontend && npm install
+# Install dependencies (from auto-claude/)
+uv venv && uv pip install -r requirements.txt
+# Or: python3 -m venv .venv && source .venv/bin/activate && pip install -r requirements.txt
 
 # Set up OAuth token
 claude setup-token
-# Add to apps/backend/.env: CLAUDE_CODE_OAUTH_TOKEN=your-token
+# Add to auto-claude/.env: CLAUDE_CODE_OAUTH_TOKEN=your-token
 ```
 
 ### Creating and Running Specs
 ```bash
-cd apps/backend
-
 # Create a spec interactively
-python spec_runner.py --interactive
+python auto-claude/spec_runner.py --interactive
 
 # Create spec from task description
-python spec_runner.py --task "Add user authentication"
+python auto-claude/spec_runner.py --task "Add user authentication"
 
 # Force complexity level (simple/standard/complex)
-python spec_runner.py --task "Fix button" --complexity simple
+python auto-claude/spec_runner.py --task "Fix button" --complexity simple
 
 # Run autonomous build
-python run.py --spec 001
+python auto-claude/run.py --spec 001
 
 # List all specs
-python run.py --list
+python auto-claude/run.py --list
 ```
 
 ### Workspace Management
 ```bash
-cd apps/backend
-
 # Review changes in isolated worktree
-python run.py --spec 001 --review
+python auto-claude/run.py --spec 001 --review
 
 # Merge completed build into project
-python run.py --spec 001 --merge
+python auto-claude/run.py --spec 001 --merge
 
 # Discard build
-python run.py --spec 001 --discard
+python auto-claude/run.py --spec 001 --discard
 ```
 
 ### QA Validation
 ```bash
-cd apps/backend
-
 # Run QA manually
-python run.py --spec 001 --qa
+python auto-claude/run.py --spec 001 --qa
 
 # Check QA status
-python run.py --spec 001 --qa-status
+python auto-claude/run.py --spec 001 --qa-status
 ```
 
 ### Testing
 ```bash
 # Install test dependencies (required first time)
-cd apps/backend && uv pip install -r ../../tests/requirements-test.txt
+cd auto-claude && uv pip install -r ../tests/requirements-test.txt
 
 # Run all tests (use virtual environment pytest)
-apps/backend/.venv/bin/pytest tests/ -v
+auto-claude/.venv/bin/pytest tests/ -v
 
 # Run single test file
-apps/backend/.venv/bin/pytest tests/test_security.py -v
+auto-claude/.venv/bin/pytest tests/test_security.py -v
 
 # Run specific test
-apps/backend/.venv/bin/pytest tests/test_security.py::test_bash_command_validation -v
+auto-claude/.venv/bin/pytest tests/test_security.py::test_bash_command_validation -v
 
 # Skip slow tests
-apps/backend/.venv/bin/pytest tests/ -m "not slow"
-
-# Or from root
-npm run test:backend
+auto-claude/.venv/bin/pytest tests/ -m "not slow"
 ```
 
 ### Spec Validation
 ```bash
-python apps/backend/validate_spec.py --spec-dir apps/backend/specs/001-feature --checkpoint all
+python auto-claude/validate_spec.py --spec-dir auto-claude/specs/001-feature --checkpoint all
 ```
 
 ### Releases
 ```bash
-# 1. Bump version on your branch (creates commit, no tag)
-node scripts/bump-version.js patch   # 2.8.0 -> 2.8.1
-node scripts/bump-version.js minor   # 2.8.0 -> 2.9.0
-node scripts/bump-version.js major   # 2.8.0 -> 3.0.0
+# Automated version bump and release (recommended)
+node scripts/bump-version.js patch   # 2.5.5 -> 2.5.6
+node scripts/bump-version.js minor   # 2.5.5 -> 2.6.0
+node scripts/bump-version.js major   # 2.5.5 -> 3.0.0
+node scripts/bump-version.js 2.6.0   # Set specific version
 
-# 2. Push and create PR to main
-git push origin your-branch
-gh pr create --base main
-
-# 3. Merge PR → GitHub Actions automatically:
-#    - Creates tag
-#    - Builds all platforms
-#    - Creates release with changelog
-#    - Updates README
+# Then push to trigger GitHub release workflows
+git push origin main
+git push origin v2.6.0
 ```
 
 See [RELEASE.md](RELEASE.md) for detailed release process documentation.
@@ -164,43 +108,21 @@ See [RELEASE.md](RELEASE.md) for detailed release process documentation.
 **Implementation (run.py → agent.py)** - Multi-session build:
 1. Planner Agent creates subtask-based implementation plan
 2. Coder Agent implements subtasks (can spawn subagents for parallel work)
-3. QA Reviewer validates acceptance criteria (can perform E2E testing via Electron MCP for frontend changes)
-4. QA Fixer resolves issues in a loop (with E2E testing to verify fixes)
+3. QA Reviewer validates acceptance criteria
+4. QA Fixer resolves issues in a loop
 
-### Key Components (apps/backend/)
+### Key Components
 
-**Core Infrastructure:**
-- **core/client.py** - Claude Agent SDK client factory with security hooks and tool permissions
-- **core/security.py** - Dynamic command allowlisting based on detected project stack
-- **core/auth.py** - OAuth token management for Claude SDK authentication
-- **agents/** - Agent implementations (planner, coder, qa_reviewer, qa_fixer)
-- **spec_agents/** - Spec creation agents (gatherer, researcher, writer, critic)
-
-**Memory & Context:**
-- **integrations/graphiti/** - Graphiti memory system (mandatory)
-  - `queries_pkg/graphiti.py` - Main GraphitiMemory class
-  - `queries_pkg/client.py` - LadybugDB client wrapper
-  - `queries_pkg/queries.py` - Graph query operations
-  - `queries_pkg/search.py` - Semantic search logic
-  - `queries_pkg/schema.py` - Graph schema definitions
+- **client.py** - Claude SDK client with security hooks and tool permissions
+- **security.py** + **project_analyzer.py** - Dynamic command allowlisting based on detected project stack
+- **worktree.py** - Git worktree isolation for safe feature development
+- **memory.py** - File-based session memory (primary, always-available storage)
+- **graphiti_memory.py** - Optional graph-based cross-session memory with semantic search
+- **graphiti_providers.py** - Multi-provider factory for Graphiti (OpenAI, Anthropic, Azure, Ollama, Google AI)
 - **graphiti_config.py** - Configuration and validation for Graphiti integration
-- **graphiti_providers.py** - Multi-provider factory (OpenAI, Anthropic, Azure, Ollama, Google AI)
-- **agents/memory_manager.py** - Session memory orchestration
-
-**Workspace & Security:**
-- **cli/worktree.py** - Git worktree isolation for safe feature development
-- **context/project_analyzer.py** - Project stack detection for dynamic tooling
-- **auto_claude_tools.py** - Custom MCP tools integration
-
-**Integrations:**
 - **linear_updater.py** - Optional Linear integration for progress tracking
-- **runners/github/** - GitHub Issues & PRs automation
-- **Electron MCP** - E2E testing integration for QA agents (Chrome DevTools Protocol)
-  - Enabled with `ELECTRON_MCP_ENABLED=true` in `.env`
-  - Allows QA agents to interact with running Electron app
-  - See "End-to-End Testing" section for details
 
-### Agent Prompts (apps/backend/prompts/)
+### Agent Prompts (auto-claude/prompts/)
 
 | Prompt | Purpose |
 |--------|---------|
@@ -217,7 +139,7 @@ See [RELEASE.md](RELEASE.md) for detailed release process documentation.
 
 ### Spec Directory Structure
 
-Each spec in `.auto-claude/specs/XXX-name/` contains:
+Each spec in `auto-claude/specs/XXX-name/` contains:
 - `spec.md` - Feature specification
 - `requirements.json` - Structured user requirements
 - `context.json` - Discovered codebase context
@@ -248,23 +170,6 @@ main (user's branch)
 4. User runs `--merge` to add to their project
 5. User pushes to remote when ready
 
-### Contributing to Upstream
-
-**CRITICAL: When submitting PRs to AndyMik90/Auto-Claude, always target the `develop` branch, NOT `main`.**
-
-**Correct workflow for contributions:**
-1. Fetch upstream: `git fetch upstream`
-2. Create feature branch from upstream/develop: `git checkout -b fix/my-fix upstream/develop`
-3. Make changes and commit with sign-off: `git commit -s -m "fix: description"`
-4. Push to your fork: `git push origin fix/my-fix`
-5. Create PR targeting `develop`: `gh pr create --repo AndyMik90/Auto-Claude --base develop`
-
-**Verify before PR:**
-```bash
-# Ensure only your commits are included
-git log --oneline upstream/develop..HEAD
-```
-
 ### Security Model
 
 Three-layer defense:
@@ -274,236 +179,44 @@ Three-layer defense:
 
 Security profile cached in `.auto-claude-security.json`.
 
-### Claude Agent SDK Integration
-
-**CRITICAL: Auto Claude uses the Claude Agent SDK for ALL AI interactions. Never use the Anthropic API directly.**
-
-**Client Location:** `apps/backend/core/client.py`
-
-The `create_client()` function creates a configured `ClaudeSDKClient` instance with:
-- Multi-layered security (sandbox, permissions, security hooks)
-- Agent-specific tool permissions (planner, coder, qa_reviewer, qa_fixer)
-- Dynamic MCP server integration based on project capabilities
-- Extended thinking token budget control
-
-**Example usage in agents:**
-```python
-from core.client import create_client
-
-# Create SDK client (NOT raw Anthropic API client)
-client = create_client(
-    project_dir=project_dir,
-    spec_dir=spec_dir,
-    model="claude-sonnet-4-5-20250929",
-    agent_type="coder",
-    max_thinking_tokens=None  # or 5000/10000/16000
-)
-
-# Run agent session
-response = client.create_agent_session(
-    name="coder-agent-session",
-    starting_message="Implement the authentication feature"
-)
-```
-
-**Why use the SDK:**
-- Pre-configured security (sandbox, allowlists, hooks)
-- Automatic MCP server integration (Context7, Linear, Graphiti, Electron, Puppeteer)
-- Tool permissions based on agent role
-- Session management and recovery
-- Unified API across all agent types
-
-**Where to find working examples:**
-- `apps/backend/agents/planner.py` - Planner agent
-- `apps/backend/agents/coder.py` - Coder agent
-- `apps/backend/agents/qa_reviewer.py` - QA reviewer
-- `apps/backend/agents/qa_fixer.py` - QA fixer
-- `apps/backend/spec_agents/` - Spec creation agents
-
 ### Memory System
 
-**Graphiti Memory (Mandatory)** - `integrations/graphiti/`
+Dual-layer memory architecture:
 
-Auto Claude uses Graphiti as its primary memory system with embedded LadybugDB (no Docker required):
+**File-Based Memory (Primary)** - `memory.py`
+- Zero dependencies, always available
+- Human-readable files in `specs/XXX/memory/`
+- Session insights, patterns, gotchas, codebase map
 
-- **Graph database with semantic search** - Knowledge graph for cross-session context
-- **Session insights** - Patterns, gotchas, discoveries automatically extracted
-- **Multi-provider support:**
+**Graphiti Memory (Optional Enhancement)** - `graphiti_memory.py`
+- Graph database with semantic search (LadybugDB - embedded, no Docker)
+- Cross-session context retrieval
+- Requires Python 3.12+
+- Multi-provider support:
   - LLM: OpenAI, Anthropic, Azure OpenAI, Ollama, Google AI (Gemini)
   - Embedders: OpenAI, Voyage AI, Azure OpenAI, Ollama, Google AI
-- **Modular architecture:** (`integrations/graphiti/queries_pkg/`)
-  - `graphiti.py` - Main GraphitiMemory class
-  - `client.py` - LadybugDB client wrapper
-  - `queries.py` - Graph query operations
-  - `search.py` - Semantic search logic
-  - `schema.py` - Graph schema definitions
 
-**Configuration:**
-- Set provider credentials in `apps/backend/.env` (see `.env.example`)
-- Required env vars: `GRAPHITI_ENABLED=true`, `ANTHROPIC_API_KEY` or other provider keys
-- Memory data stored in `.auto-claude/specs/XXX/graphiti/`
-
-**Usage in agents:**
-```python
-from integrations.graphiti.memory import get_graphiti_memory
-
-memory = get_graphiti_memory(spec_dir, project_dir)
-context = memory.get_context_for_session("Implementing feature X")
-memory.add_session_insight("Pattern: use React hooks for state")
-```
-
-## Development Guidelines
-
-### Frontend Internationalization (i18n)
-
-**CRITICAL: Always use i18n translation keys for all user-facing text in the frontend.**
-
-The frontend uses `react-i18next` for internationalization. All labels, buttons, messages, and user-facing text MUST use translation keys.
-
-**Translation file locations:**
-- `apps/frontend/src/shared/i18n/locales/en/*.json` - English translations
-- `apps/frontend/src/shared/i18n/locales/fr/*.json` - French translations
-
-**Translation namespaces:**
-- `common.json` - Shared labels, buttons, common terms
-- `navigation.json` - Sidebar navigation items, sections
-- `settings.json` - Settings page content
-- `dialogs.json` - Dialog boxes and modals
-- `tasks.json` - Task/spec related content
-- `errors.json` - Error messages (structured error information with substitution support)
-- `onboarding.json` - Onboarding wizard content
-- `welcome.json` - Welcome screen content
-
-**Usage pattern:**
-```tsx
-import { useTranslation } from 'react-i18next';
-
-// In component
-const { t } = useTranslation(['navigation', 'common']);
-
-// Use translation keys, NOT hardcoded strings
-<span>{t('navigation:items.githubPRs')}</span>  // ✅ CORRECT
-<span>GitHub PRs</span>                          // ❌ WRONG
-```
-
-**Error messages with substitution:**
-
-```tsx
-// For error messages with dynamic content, use interpolation
-const { t } = useTranslation(['errors']);
-
-// errors.json: { "task": { "parseError": "Failed to parse: {{error}}" } }
-<span>{t('errors:task.parseError', { error: errorMessage })}</span>
-```
-
-**When adding new UI text:**
-1. Add the translation key to ALL language files (at minimum: `en/*.json` and `fr/*.json`)
-2. Use `namespace:section.key` format (e.g., `navigation:items.githubPRs`)
-3. Never use hardcoded strings in JSX/TSX files
-
-### End-to-End Testing (Electron App)
-
-**IMPORTANT: When bug fixing or implementing new features in the frontend, AI agents can perform automated E2E testing using the Electron MCP server.**
-
-The Electron MCP server allows QA agents to interact with the running Electron app via Chrome DevTools Protocol:
-
-**Setup:**
-1. Start the Electron app with remote debugging enabled:
-   ```bash
-   npm run dev  # Already configured with --remote-debugging-port=9222
-   ```
-
-2. Enable Electron MCP in `apps/backend/.env`:
-   ```bash
-   ELECTRON_MCP_ENABLED=true
-   ELECTRON_DEBUG_PORT=9222  # Default port
-   ```
-
-**Available Testing Capabilities:**
-
-QA agents (`qa_reviewer` and `qa_fixer`) automatically get access to Electron MCP tools:
-
-1. **Window Management**
-   - `mcp__electron__get_electron_window_info` - Get info about running windows
-   - `mcp__electron__take_screenshot` - Capture screenshots for visual verification
-
-2. **UI Interaction**
-   - `mcp__electron__send_command_to_electron` with commands:
-     - `click_by_text` - Click buttons/links by visible text
-     - `click_by_selector` - Click elements by CSS selector
-     - `fill_input` - Fill form fields by placeholder or selector
-     - `select_option` - Select dropdown options
-     - `send_keyboard_shortcut` - Send keyboard shortcuts (Enter, Ctrl+N, etc.)
-     - `navigate_to_hash` - Navigate to hash routes (#settings, #create, etc.)
-
-3. **Page Inspection**
-   - `get_page_structure` - Get organized overview of page elements
-   - `debug_elements` - Get debugging info about buttons and forms
-   - `verify_form_state` - Check form state and validation
-   - `eval` - Execute custom JavaScript code
-
-4. **Logging**
-   - `mcp__electron__read_electron_logs` - Read console logs for debugging
-
-**Example E2E Test Flow:**
-
-```python
-# 1. Agent takes screenshot to see current state
-agent: "Take a screenshot to see the current UI"
-# Uses: mcp__electron__take_screenshot
-
-# 2. Agent inspects page structure
-agent: "Get page structure to find available buttons"
-# Uses: mcp__electron__send_command_to_electron (command: "get_page_structure")
-
-# 3. Agent clicks a button to navigate
-agent: "Click the 'Create New Spec' button"
-# Uses: mcp__electron__send_command_to_electron (command: "click_by_text", args: {text: "Create New Spec"})
-
-# 4. Agent fills out a form
-agent: "Fill the task description field"
-# Uses: mcp__electron__send_command_to_electron (command: "fill_input", args: {placeholder: "Describe your task", value: "Add login feature"})
-
-# 5. Agent submits and verifies
-agent: "Click Submit and verify success"
-# Uses: click_by_text → take_screenshot → verify result
-```
-
-**When to Use E2E Testing:**
-
-- **Bug Fixes**: Reproduce the bug, apply fix, verify it's resolved
-- **New Features**: Implement feature, test the UI flow end-to-end
-- **UI Changes**: Verify visual changes and interactions work correctly
-- **Form Validation**: Test form submission, validation, error handling
-
-**Configuration in `core/client.py`:**
-
-The client automatically enables Electron MCP tools for QA agents when:
-- Project is detected as Electron (`is_electron` capability)
-- `ELECTRON_MCP_ENABLED=true` is set
-- Agent type is `qa_reviewer` or `qa_fixer`
-
-**Note:** Screenshots are automatically compressed (1280x720, quality 60, JPEG) to stay under Claude SDK's 1MB JSON message buffer limit.
-
-## Running the Application
-
-**As a standalone CLI tool**:
 ```bash
-cd apps/backend
-python run.py --spec 001
+# Setup (requires Python 3.12+)
+pip install real_ladybug graphiti-core
 ```
 
-**With the Electron frontend**:
+Enable with: `GRAPHITI_ENABLED=true` + provider credentials. See `.env.example`.
+
+## Project Structure
+
+Auto Claude can be used in two ways:
+
+**As a standalone CLI tool** (original project):
 ```bash
-npm start        # Build and run desktop app
-npm run dev      # Run in development mode (includes --remote-debugging-port=9222 for E2E testing)
+python auto-claude/run.py --spec 001
 ```
 
-**For E2E Testing with QA Agents:**
-1. Start the Electron app: `npm run dev`
-2. Enable Electron MCP in `apps/backend/.env`: `ELECTRON_MCP_ENABLED=true`
-3. Run QA: `python run.py --spec 001 --qa`
-4. QA agents will automatically interact with the running app for testing
+**With the optional Electron frontend** (`auto-claude-ui/`):
+- Provides a GUI for task management and progress tracking
+- Wraps the CLI commands - the backend works independently
 
-**Project data storage:**
-- `.auto-claude/specs/` - Per-project data (specs, plans, QA reports, memory) - gitignored
+**Directory layout:**
+- `auto-claude/` - Python backend/CLI (the framework code)
+- `auto-claude-ui/` - Optional Electron frontend
+- `.auto-claude/specs/` - Per-project data (specs, plans, QA reports) - gitignored

CONTRIBUTING.md

@@ -4,9 +4,7 @@ Thank you for your interest in contributing to Auto Claude! This document provid
 
 ## Table of Contents
 
-- [Contributor License Agreement (CLA)](#contributor-license-agreement-cla)
 - [Prerequisites](#prerequisites)
-- [Quick Start](#quick-start)
 - [Development Setup](#development-setup)
   - [Python Backend](#python-backend)
   - [Electron Frontend](#electron-frontend)
@@ -16,164 +14,47 @@ Thank you for your interest in contributing to Auto Claude! This document provid
 - [Testing](#testing)
 - [Continuous Integration](#continuous-integration)
 - [Git Workflow](#git-workflow)
-  - [Branch Overview](#branch-overview)
-  - [Main Branches](#main-branches)
-  - [Supporting Branches](#supporting-branches)
   - [Branch Naming](#branch-naming)
-  - [Where to Branch From](#where-to-branch-from)
-  - [Pull Request Targets](#pull-request-targets)
-  - [Release Process](#release-process-maintainers)
   - [Commit Messages](#commit-messages)
-  - [PR Hygiene](#pr-hygiene)
 - [Pull Request Process](#pull-request-process)
 - [Issue Reporting](#issue-reporting)
 - [Architecture Overview](#architecture-overview)
 
-## Contributor License Agreement (CLA)
-
-All contributors must sign our Contributor License Agreement (CLA) before contributions can be accepted.
-
-### Why We Require a CLA
-
-Auto Claude is currently licensed under AGPL-3.0. The CLA ensures the project has proper licensing flexibility should we introduce additional licensing options (such as commercial/enterprise licenses) in the future.
-
-You retain full copyright ownership of your contributions.
-
-### How to Sign
-
-1. Open a Pull Request
-2. The CLA bot will automatically comment with instructions
-3. Comment on the PR with: `I have read the CLA Document and I hereby sign the CLA`
-4. Done - you only need to sign once, and it applies to all future contributions
-
-Read the full CLA here: [CLA.md](CLA.md)
-
 ## Prerequisites
 
 Before contributing, ensure you have the following installed:
 
-- **Python 3.12+** - For the backend framework
-- **Node.js 24+** - For the Electron frontend
-- **npm 10+** - Package manager for the frontend (comes with Node.js)
+- **Python 3.8+** - For the backend framework
+- **Node.js 18+** - For the Electron frontend
+- **pnpm** - Package manager for the frontend (`npm install -g pnpm`)
 - **uv** (recommended) or **pip** - Python package manager
-- **CMake** - Required for building native dependencies (e.g., LadybugDB)
 - **Git** - Version control
 
-### Installing Python 3.12
-
-**Windows:**
-```bash
-winget install Python.Python.3.12
-```
-
-**macOS:**
-```bash
-brew install python@3.12
-```
-
-**Linux (Ubuntu/Debian):**
-```bash
-sudo apt install python3.12 python3.12-venv
-```
-
-**Linux (Fedora):**
-```bash
-sudo dnf install python3.12
-```
-
-### Installing Node.js 24+
-
-**Windows:**
-```bash
-winget install OpenJS.NodeJS.LTS
-```
-
-**macOS:**
-```bash
-brew install node@24
-```
-
-**Linux (Ubuntu/Debian):**
-```bash
-curl -fsSL https://deb.nodesource.com/setup_24.x | sudo -E bash -
-sudo apt install -y nodejs
-```
-
-**Linux (Fedora):**
-```bash
-sudo dnf install nodejs npm
-```
-
-### Installing CMake
-
-**Windows:**
-```bash
-winget install Kitware.CMake
-```
-
-**macOS:**
-```bash
-brew install cmake
-```
-
-**Linux (Ubuntu/Debian):**
-```bash
-sudo apt install cmake
-```
-
-**Linux (Fedora):**
-```bash
-sudo dnf install cmake
-```
-
-## Quick Start
-
-The fastest way to get started:
-
-```bash
-# Clone the repository
-git clone https://github.com/AndyMik90/Auto-Claude.git
-cd Auto-Claude
-
-# Install all dependencies (cross-platform)
-npm run install:all
-
-# Run in development mode
-npm run dev
-
-# Or build and run production
-npm start
-```
-
 ## Development Setup
 
 The project consists of two main components:
 
-1. **Python Backend** (`apps/backend/`) - The core autonomous coding framework
-2. **Electron Frontend** (`apps/frontend/`) - Optional desktop UI
+1. **Python Backend** (`auto-claude/`) - The core autonomous coding framework
+2. **Electron Frontend** (`auto-claude-ui/`) - Optional desktop UI
 
 ### Python Backend
 
-The recommended way is to use `npm run install:backend`, but you can also set up manually:
-
 ```bash
-# Navigate to the backend directory
-cd apps/backend
+# Navigate to the auto-claude directory
+cd auto-claude
 
-# Create virtual environment
-# Windows:
-py -3.12 -m venv .venv
-.venv\Scripts\activate
+# Create virtual environment (using uv - recommended)
+uv venv
+source .venv/bin/activate  # On Windows: .venv\Scripts\activate
+uv pip install -r requirements.txt
 
-# macOS/Linux:
-python3.12 -m venv .venv
+# Or using standard Python
+python3 -m venv .venv
 source .venv/bin/activate
-
-# Install dependencies
 pip install -r requirements.txt
 
 # Install test dependencies
-pip install -r ../../tests/requirements-test.txt
+pip install -r ../tests/requirements-test.txt
 
 # Set up environment
 cp .env.example .env
@@ -183,31 +64,31 @@ cp .env.example .env
 ### Electron Frontend
 
 ```bash
-# Navigate to the frontend directory
-cd apps/frontend
+# Navigate to the UI directory
+cd auto-claude-ui
 
 # Install dependencies
-npm install
+pnpm install
 
 # Start development server
-npm run dev
+pnpm dev
 
 # Build for production
-npm run build
+pnpm build
 
 # Package for distribution
-npm run package
+pnpm package
 ```
 
 ## Running from Source
 
 If you want to run Auto Claude from source (for development or testing unreleased features), follow these steps:
 
-### Step 1: Clone and Set Up
+### Step 1: Clone and Set Up Python Backend
 
 ```bash
 git clone https://github.com/AndyMik90/Auto-Claude.git
-cd Auto-Claude/apps/backend
+cd Auto-Claude/auto-claude
 
 # Using uv (recommended)
 uv venv && uv pip install -r requirements.txt
@@ -218,7 +99,6 @@ source .venv/bin/activate  # On Windows: .venv\Scripts\activate
 pip install -r requirements.txt
 
 # Set up environment
-cd apps/backend
 cp .env.example .env
 # Edit .env and add your CLAUDE_CODE_OAUTH_TOKEN (get it via: claude setup-token)
 ```
@@ -226,16 +106,16 @@ cp .env.example .env
 ### Step 2: Run the Desktop UI
 
 ```bash
-cd ../frontend
+cd ../auto-claude-ui
 
 # Install dependencies
-npm install
+pnpm install
 
 # Development mode (hot reload)
-npm run dev
+pnpm dev
 
 # Or production build
-npm run build && npm run start
+pnpm run build && pnpm run start
 ```
 
 <details>
@@ -246,7 +126,7 @@ Auto Claude automatically downloads prebuilt binaries for Windows. If prebuilts
 1. Download [Visual Studio Build Tools 2022](https://visualstudio.microsoft.com/visual-cpp-build-tools/)
 2. Select "Desktop development with C++" workload
 3. In "Individual Components", add "MSVC v143 - VS 2022 C++ x64/x86 Spectre-mitigated libs"
-4. Restart terminal and run `npm install` again
+4. Restart terminal and run `pnpm install` again
 
 </details>
 
@@ -272,10 +152,10 @@ When you commit, the following checks run automatically:
 
 | Check | Scope | Description |
 |-------|-------|-------------|
-| **ruff** | `apps/backend/` | Python linter with auto-fix |
-| **ruff-format** | `apps/backend/` | Python code formatter |
-| **eslint** | `apps/frontend/` | TypeScript/React linter |
-| **typecheck** | `apps/frontend/` | TypeScript type checking |
+| **ruff** | `auto-claude/` | Python linter with auto-fix |
+| **ruff-format** | `auto-claude/` | Python code formatter |
+| **eslint** | `auto-claude-ui/` | TypeScript/React linter |
+| **typecheck** | `auto-claude-ui/` | TypeScript type checking |
 | **trailing-whitespace** | All files | Removes trailing whitespace |
 | **end-of-file-fixer** | All files | Ensures files end with newline |
 | **check-yaml** | All files | Validates YAML syntax |
@@ -332,7 +212,7 @@ def gnc(sd):
 ### TypeScript/React
 
 - Use TypeScript strict mode
-- Follow the existing component patterns in `apps/frontend/src/`
+- Follow the existing component patterns in `auto-claude-ui/src/`
 - Use functional components with hooks
 - Prefer named exports over default exports
 - Use the UI components from `src/renderer/components/ui/`
@@ -362,25 +242,20 @@ export default function(props) {
 ### Python Tests
 
 ```bash
-# Run all tests (from repository root)
-npm run test:backend
-
-# Or manually with pytest
-cd apps/backend
-.venv/Scripts/pytest.exe ../tests -v          # Windows
-.venv/bin/pytest ../tests -v                   # macOS/Linux
+# Run all tests
+pytest tests/ -v
 
 # Run a specific test file
-npm run test:backend -- tests/test_security.py -v
+pytest tests/test_security.py -v
 
 # Run a specific test
-npm run test:backend -- tests/test_security.py::test_bash_command_validation -v
+pytest tests/test_security.py::test_bash_command_validation -v
 
 # Skip slow tests
-npm run test:backend -- -m "not slow"
+pytest tests/ -m "not slow"
 
 # Run with coverage
-pytest tests/ --cov=apps/backend --cov-report=html
+pytest tests/ --cov=auto-claude --cov-report=html
 ```
 
 Test configuration is in `tests/pytest.ini`.
@@ -388,26 +263,26 @@ Test configuration is in `tests/pytest.ini`.
 ### Frontend Tests
 
 ```bash
-cd apps/frontend
+cd auto-claude-ui
 
 # Run unit tests
-npm test
+pnpm test
 
 # Run tests in watch mode
-npm run test:watch
+pnpm test:watch
 
 # Run with coverage
-npm run test:coverage
+pnpm test:coverage
 
 # Run E2E tests (requires built app)
-npm run build
-npm run test:e2e
+pnpm build
+pnpm test:e2e
 
 # Run linting
-npm run lint
+pnpm lint
 
 # Run type checking
-npm run typecheck
+pnpm typecheck
 ```
 
 ### Testing Requirements
@@ -445,50 +320,19 @@ Before a PR can be merged:
 
 ```bash
 # Python tests
-cd apps/backend
+cd auto-claude
 source .venv/bin/activate
-pytest ../../tests/ -v
+pytest ../tests/ -v
 
 # Frontend tests
-cd apps/frontend
-npm test
-npm run lint
-npm run typecheck
+cd auto-claude-ui
+pnpm test
+pnpm lint
+pnpm typecheck
 ```
 
 ## Git Workflow
 
-We use a **Git Flow** branching strategy to manage releases and parallel development.
-
-### Branch Overview
-
-```
-main (stable)          ← Only released, tested code (tagged versions)
-  │
-develop                ← Integration branch - all PRs merge here first
-  │
-├── feature/xxx        ← New features
-├── fix/xxx            ← Bug fixes
-├── release/vX.Y.Z     ← Release preparation
-└── hotfix/xxx         ← Emergency production fixes
-```
-
-### Main Branches
-
-| Branch | Purpose | Protected |
-|--------|---------|-----------|
-| `main` | Production-ready code. Only receives merges from `release/*` or `hotfix/*` branches. Every merge is tagged (v2.7.0, v2.8.0, etc.) | ✅ Yes |
-| `develop` | Integration branch where all features and fixes are combined. This is the default target for all PRs. | ✅ Yes |
-
-### Supporting Branches
-
-| Branch Type | Branch From | Merge To | Purpose |
-|-------------|-------------|----------|---------|
-| `feature/*` | `develop` | `develop` | New features and enhancements |
-| `fix/*` | `develop` | `develop` | Bug fixes (non-critical) |
-| `release/*` | `develop` | `main` + `develop` | Release preparation and final testing |
-| `hotfix/*` | `main` | `main` + `develop` | Critical production bug fixes |
-
 ### Branch Naming
 
 Use descriptive branch names with a prefix indicating the type of change:
@@ -497,146 +341,10 @@ Use descriptive branch names with a prefix indicating the type of change:
 |--------|---------|---------|
 | `feature/` | New feature | `feature/add-dark-mode` |
 | `fix/` | Bug fix | `fix/memory-leak-in-worker` |
-| `hotfix/` | Urgent production fix | `hotfix/critical-crash-fix` |
 | `docs/` | Documentation | `docs/update-readme` |
 | `refactor/` | Code refactoring | `refactor/simplify-auth-flow` |
 | `test/` | Test additions/fixes | `test/add-integration-tests` |
 | `chore/` | Maintenance tasks | `chore/update-dependencies` |
-| `release/` | Release preparation | `release/v2.8.0` |
-| `hotfix/` | Emergency fixes | `hotfix/critical-auth-bug` |
-
-### Where to Branch From
-
-```bash
-# For features and bug fixes - ALWAYS branch from develop
-git checkout develop
-git pull origin develop
-git checkout -b feature/my-new-feature
-
-# For hotfixes only - branch from main
-git checkout main
-git pull origin main
-git checkout -b hotfix/critical-fix
-```
-
-### Pull Request Targets
-
-> ⚠️ **Important:** All PRs should target `develop`, NOT `main`!
-
-| Your Branch Type | Target Branch |
-|------------------|---------------|
-| `feature/*` | `develop` |
-| `fix/*` | `develop` |
-| `docs/*` | `develop` |
-| `refactor/*` | `develop` |
-| `test/*` | `develop` |
-| `chore/*` | `develop` |
-| `hotfix/*` | `main` (maintainers only) |
-| `release/*` | `main` (maintainers only) |
-
-### Release Process (Maintainers)
-
-When ready to release a new version:
-
-```bash
-# 1. Create release branch from develop
-git checkout develop
-git pull origin develop
-git checkout -b release/v2.8.0
-
-# 2. Update version numbers, CHANGELOG, final fixes only
-# No new features allowed in release branches!
-
-# 3. Merge to main and tag
-git checkout main
-git merge release/v2.8.0
-git tag v2.8.0
-git push origin main --tags
-
-# 4. Merge back to develop (important!)
-git checkout develop
-git merge release/v2.8.0
-git push origin develop
-
-# 5. Delete release branch
-git branch -d release/v2.8.0
-git push origin --delete release/v2.8.0
-```
-
-### Beta Release Process (Maintainers)
-
-Beta releases allow users to test new features before they're included in a stable release. Beta releases are published from the `develop` branch.
-
-**Creating a Beta Release:**
-
-1. Go to **Actions** → **Beta Release** workflow in GitHub
-2. Click **Run workflow**
-3. Enter the beta version (e.g., `2.8.0-beta.1`)
-4. Optionally enable dry run to test without publishing
-5. Click **Run workflow**
-
-The workflow will:
-- Validate the version format
-- Update `package.json` on develop
-- Create and push a tag (e.g., `v2.8.0-beta.1`)
-- Build installers for all platforms
-- Create a GitHub pre-release
-
-**Version Format:**
-```
-X.Y.Z-beta.N   (e.g., 2.8.0-beta.1, 2.8.0-beta.2)
-X.Y.Z-alpha.N  (e.g., 2.8.0-alpha.1)
-X.Y.Z-rc.N     (e.g., 2.8.0-rc.1)
-```
-
-**For Users:**
-Users can opt into beta updates in Settings → Updates → "Beta Updates" toggle. When enabled, the app will check for and install beta versions. Users can switch back to stable at any time.
-
-### Hotfix Workflow
-
-For urgent production fixes that can't wait for the normal release cycle:
-
-**1. Create hotfix from main**
-
-```bash
-git checkout main
-git pull origin main
-git checkout -b hotfix/150-critical-fix
-```
-
-**2. Fix the issue**
-
-```bash
-# ... make changes ...
-git commit -m "hotfix: fix critical crash on startup"
-```
-
-**3. Open PR to main (fast-track review)**
-
-```bash
-gh pr create --base main --title "hotfix: fix critical crash on startup"
-```
-
-**4. After merge to main, sync to develop**
-
-```bash
-git checkout develop
-git pull origin develop
-git merge main
-git push origin develop
-```
-
-```
-main ─────●─────●─────●─────●───── (production)
-          ↑     ↑     ↑     ↑
-develop ──●─────●─────●─────●───── (integration)
-          ↑     ↑     ↑
-feature/123 ────●
-feature/124 ──────────●
-hotfix/125 ─────────────────●───── (from main, merge to both)
-```
-
-> **Note:** Hotfixes branch FROM `main` and merge TO `main` first, then sync back to `develop` to keep branches aligned.
 
 ### Commit Messages
 
@@ -668,60 +376,19 @@ git commit -m "WIP"
 - **body**: Detailed explanation if needed (wrap at 72 chars)
 - **footer**: Reference issues, breaking changes
 
-### PR Hygiene
-
-**Rebasing:**
-- **Rebase onto develop** before opening a PR and before merge to maintain linear history
-- Use `git fetch origin && git rebase origin/develop` to sync your branch
-- Use `--force-with-lease` when force-pushing rebased branches (safer than `--force`)
-- Notify reviewers after force-pushing during active review
-- **Exception:** Never rebase after PR is approved and others have reviewed specific commits
-
-**Commit organization:**
-- **Squash fixup commits** (typos, "oops", review feedback) into their parent commits
-- **Keep logically distinct changes** as separate commits that could be reverted independently
-- Each commit should compile and pass tests independently
-- No "WIP", "fix tests", or "lint" commits in final PR - squash these
-
-**Before requesting review:**
-```bash
-# Ensure up-to-date with develop
-git fetch origin && git rebase origin/develop
-
-# Clean up commit history (squash fixups, reword messages)
-git rebase -i origin/develop
-
-# Force push with safety check
-git push --force-with-lease
-
-# Verify everything works
-npm run test:backend
-cd apps/frontend && npm test && npm run lint && npm run typecheck
-```
-
-**PR size:**
-- Keep PRs small (<400 lines changed ideally)
-- Split large features into stacked PRs if possible
-
 ## Pull Request Process
 
-1. **Fork the repository** and create your branch from `develop` (not main!)
-
-   ```bash
-   git checkout develop
-   git pull origin develop
-   git checkout -b feature/your-feature-name
-   ```
+1. **Fork the repository** and create your branch from `main`
 
 2. **Make your changes** following the code style guidelines
 
 3. **Test thoroughly**:
    ```bash
-   # Python (from repository root)
-   npm run test:backend
+   # Python
+   pytest tests/ -v
 
    # Frontend
-   cd apps/frontend && npm test && npm run lint && npm run typecheck
+   cd auto-claude-ui && pnpm test && pnpm lint && pnpm typecheck
    ```
 
 4. **Update documentation** if your changes affect:
@@ -780,7 +447,7 @@ When requesting a feature:
 
 Auto Claude consists of two main parts:
 
-### Python Backend (`apps/backend/`)
+### Python Backend (`auto-claude/`)
 
 The core autonomous coding framework:
 
@@ -790,9 +457,9 @@ The core autonomous coding framework:
 - **Memory**: `memory.py` (file-based), `graphiti_memory.py` (graph-based)
 - **QA**: `qa_loop.py`, `prompts/qa_*.md`
 
-### Electron Frontend (`apps/frontend/`)
+### Electron Frontend (`auto-claude-ui/`)
 
-Desktop interface:
+Optional desktop interface:
 
 - **Main Process**: `src/main/` - Electron main process, IPC handlers
 - **Renderer**: `src/renderer/` - React UI components

INVESTIGATION.md

@@ -0,0 +1,641 @@
+# Investigation: v2.7.1 Release Artifacts Issue
+
+## Investigation Date
+
+2025-12-25
+
+## Summary
+
+The v2.7.1 release has **incorrect files attached**. All artifacts have v2.7.0 in their filenames, indicating the wrong build artifacts were uploaded.
+
+---
+
+## Phase 1: Reproduce and Verify Issue
+
+### Subtask 1-1: Current v2.7.1 Assets
+
+**Command:** `gh release view v2.7.1 --json assets -q '.assets[].name'`
+
+**Release Metadata:**
+- Tag Name: v2.7.1
+- Release Name: v2.7.1
+- Published At: 2025-12-22T13:35:38Z
+- Is Draft: false
+- Is Prerelease: false
+
+**Files Currently Attached to v2.7.1:**
+
+| File Name | Size (bytes) | Expected Name |
+|-----------|-------------|---------------|
+| Auto-Claude-2.7.0-darwin-arm64.dmg | 124,187,073 | Auto-Claude-2.7.1-darwin-arm64.dmg |
+| Auto-Claude-2.7.0-darwin-arm64.zip | 117,694,085 | Auto-Claude-2.7.1-darwin-arm64.zip |
+| Auto-Claude-2.7.0-darwin-x64.dmg | 130,635,398 | Auto-Claude-2.7.1-darwin-x64.dmg |
+| Auto-Claude-2.7.0-darwin-x64.zip | 124,176,354 | Auto-Claude-2.7.1-darwin-x64.zip |
+| Auto-Claude-2.7.0-linux-amd64.deb | 104,558,694 | Auto-Claude-2.7.1-linux-amd64.deb |
+| Auto-Claude-2.7.0-linux-x86_64.AppImage | 145,482,885 | Auto-Claude-2.7.1-linux-x86_64.AppImage |
+| Auto-Claude-2.7.0-win32-x64.exe | 101,941,972 | Auto-Claude-2.7.1-win32-x64.exe |
+| checksums.sha256 | 718 | checksums.sha256 (with v2.7.1 filenames) |
+
+### Issue Confirmed
+
+**Problem:** All 7 platform artifacts attached to v2.7.1 have "2.7.0" in their filename instead of "2.7.1".
+
+**Impact:**
+- Users downloading v2.7.1 are receiving v2.7.0 binaries
+- File naming does not match the release version
+- Checksums file likely references v2.7.0 filenames
+- Auto-update mechanisms may be confused by version mismatch
+
+**Evidence:**
+```
+Files attached to v2.7.1:
+- Auto-Claude-2.7.0-darwin-arm64.dmg   (WRONG - should be 2.7.1)
+- Auto-Claude-2.7.0-darwin-arm64.zip   (WRONG - should be 2.7.1)
+- Auto-Claude-2.7.0-darwin-x64.dmg     (WRONG - should be 2.7.1)
+- Auto-Claude-2.7.0-darwin-x64.zip     (WRONG - should be 2.7.1)
+- Auto-Claude-2.7.0-linux-amd64.deb    (WRONG - should be 2.7.1)
+- Auto-Claude-2.7.0-linux-x86_64.AppImage (WRONG - should be 2.7.1)
+- Auto-Claude-2.7.0-win32-x64.exe      (WRONG - should be 2.7.1)
+- checksums.sha256                      (likely references wrong filenames)
+```
+
+---
+
+### Subtask 1-2: Comparison with v2.7.0 and Expected Naming
+
+**Command:** `gh release view v2.7.0 --json assets -q '.assets[].name'`
+
+#### v2.7.0 Release Analysis
+
+**Release Metadata:**
+- Tag Name: v2.7.0
+- Release Name: v2.7.0
+- Published At: 2025-12-22T13:19:13Z
+- Target Commitish: main
+- Is Draft: false
+- Is Prerelease: false
+
+**Critical Finding:** v2.7.0 has **NO assets attached** (empty assets array).
+
+#### Release Timeline
+
+| Release | Published At | Assets Count | Status |
+|---------|-------------|--------------|--------|
+| v2.7.0  | 2025-12-22T13:19:13Z | 0 | No files attached |
+| v2.7.1  | 2025-12-22T13:35:38Z | 8 | Wrong version in filenames |
+| v2.7.2  | 2025-12-22T13:52:51Z | ? | Draft release |
+
+**Observation:** v2.7.0 was published 16 minutes before v2.7.1, but has no artifacts attached.
+
+#### Checksums File Analysis
+
+The `checksums.sha256` file attached to v2.7.1 contains:
+```
+0a0094ff3e52609665f6f0d6d54180dbfc592956f91ef2cdd94e43a61b6b24d2  ./Auto-Claude-2.7.0-darwin-arm64.dmg
+43b168f3073d60644bb111c8fa548369431dc448e67700ed526cb4cad61034e0  ./Auto-Claude-2.7.0-darwin-arm64.zip
+5150cbba934fbeb3d97309a493cc8ef3c035e9ec38b31f01382d628025f5c451  ./Auto-Claude-2.7.0-darwin-x64.dmg
+ea9139277290a8189f799d00bc3cd1aaf81a16e890ff90327eca01a4cce73e61  ./Auto-Claude-2.7.0-darwin-x64.zip
+078b2ba6a2594bf048932776dc31a45e59cd9cb23b34b2cf2f810f4101f04736  ./Auto-Claude-2.7.0-linux-amd64.deb
+1feb6b9be348a5e23238e009dbc1ce8b2788103a262cd856613332b3ab1711e9  ./Auto-Claude-2.7.0-linux-x86_64.AppImage
+25383314b3bc032ceaf8a8416d5383879ed351c906f03175b8533047647a612d  ./Auto-Claude-2.7.0-win32-x64.exe
+```
+
+**Issue:** Checksums file also references v2.7.0 filenames, confirming the build was run with v2.7.0 version.
+
+#### Expected Naming Pattern (from release.yml)
+
+Based on the release workflow analysis, artifacts follow this naming convention:
+```
+Auto-Claude-{version}-{platform}-{arch}.{ext}
+```
+
+Where version comes from `package.json` in `auto-claude-ui/`.
+
+**Expected v2.7.1 Artifacts:**
+| Expected Filename | Actual Filename (Wrong) |
+|-------------------|-------------------------|
+| Auto-Claude-2.7.1-darwin-arm64.dmg | Auto-Claude-2.7.0-darwin-arm64.dmg |
+| Auto-Claude-2.7.1-darwin-arm64.zip | Auto-Claude-2.7.0-darwin-arm64.zip |
+| Auto-Claude-2.7.1-darwin-x64.dmg | Auto-Claude-2.7.0-darwin-x64.dmg |
+| Auto-Claude-2.7.1-darwin-x64.zip | Auto-Claude-2.7.0-darwin-x64.zip |
+| Auto-Claude-2.7.1-linux-amd64.deb | Auto-Claude-2.7.0-linux-amd64.deb |
+| Auto-Claude-2.7.1-linux-x86_64.AppImage | Auto-Claude-2.7.0-linux-x86_64.AppImage |
+| Auto-Claude-2.7.1-win32-x64.exe | Auto-Claude-2.7.0-win32-x64.exe |
+| checksums.sha256 (v2.7.1 refs) | checksums.sha256 (v2.7.0 refs) |
+
+#### Hypothesis
+
+The evidence suggests one of the following scenarios:
+
+1. **Tag/Version Mismatch:** The v2.7.1 tag may point to a commit where `package.json` still had version `2.7.0`
+2. **Workflow Re-run:** The v2.7.1 release may have been created by re-running the v2.7.0 workflow artifacts
+3. **Manual Upload Error:** Artifacts from v2.7.0 were manually attached to the v2.7.1 release
+4. **Artifact Caching:** Old workflow artifacts were incorrectly reused for v2.7.1
+
+**Next step:** Check git tags and package.json versions to determine root cause.
+
+---
+
+### Subtask 1-3: Package.json Version and Git State Analysis
+
+**Commands Used:**
+- `git show v2.7.1:auto-claude-ui/package.json | jq -r '.version'`
+- `git show v2.7.0:auto-claude-ui/package.json | jq -r '.version'`
+- `git log --oneline v2.7.0..v2.7.1`
+- `git rev-parse v2.7.1^{commit}`
+
+#### Current Package.json State
+
+| Location | Current Version |
+|----------|-----------------|
+| `auto-claude-ui/package.json` (HEAD) | 2.7.1 |
+
+**Note:** The subtask referenced `apps/frontend/package.json`, but the actual path is `auto-claude-ui/package.json`.
+
+#### Version at Git Tags
+
+| Tag | Commit | package.json Version | Expected |
+|-----|--------|---------------------|----------|
+| v2.7.0 | `fe7290a8` | 2.6.5 | 2.7.0 |
+| v2.7.1 | `772a5006` | **2.7.0** ❌ | 2.7.1 |
+
+#### Commit Timeline
+
+```
+fc2075dd auto-claude: subtask-1-2 - Compare v2.7.1 artifacts...
+ff033a8e auto-claude: subtask-1-1 - List all files...
+8db71f3d Update version to 2.7.1 in package.json    <-- Version bump (AFTER tag)
+772a5006 2.7.1                                      <-- v2.7.1 TAG placed here
+d23fcd86 Enhance VirusTotal scan error handling...
+...more commits...
+fe7290a8 Release v2.7.0...                          <-- v2.7.0 TAG placed here
+```
+
+#### Root Cause Identified ✅
+
+**Problem:** The `v2.7.1` tag was placed on commit `772a5006` BEFORE the `package.json` version was updated to `2.7.1`.
+
+**Timeline of error:**
+1. Commit `772a5006` created with message "2.7.1" - tag `v2.7.1` placed here
+2. At this commit, `package.json` still contained version `2.7.0`
+3. The release workflow triggered on tag push, building with version `2.7.0` from `package.json`
+4. All artifacts named with `2.7.0` because that's what was in `package.json`
+5. Commit `8db71f3d` later updated `package.json` to `2.7.1` (but tag was already pushed)
+
+**This is a "tag before version bump" error.**
+
+The release workflow correctly read the version from `package.json`, but the tag was created before the version was bumped. The naming convention `${productName}-${version}-${platform}-${arch}.${ext}` correctly used version `2.7.0` because that's what was in `package.json` at the tagged commit.
+
+#### Verification of Build Configuration
+
+From `auto-claude-ui/package.json`:
+```json
+"build": {
+  "artifactName": "${productName}-${version}-${platform}-${arch}.${ext}",
+  ...
+}
+```
+
+This confirms the version is sourced from `package.json` during the build process.
+
+#### Git State Summary
+
+| Metric | Value |
+|--------|-------|
+| Current Branch | `auto-claude/009-latest-release-v2-7-1-has-wrong-files-attached` |
+| Working Tree | Clean |
+| Current HEAD package.json | 2.7.1 |
+| v2.7.1 tag package.json | 2.7.0 ❌ |
+| v2.7.0 tag package.json | 2.6.5 ❌ |
+
+**Note:** Both v2.7.0 and v2.7.1 tags have version mismatches in `package.json`, indicating a pattern of tagging before version bumping.
+
+---
+
+## Root Cause Summary
+
+| Factor | Finding |
+|--------|---------|
+| What happened? | v2.7.1 tag placed before package.json version bump |
+| Why? | Incorrect release process: tag first, version bump second |
+| Impact | All 7 artifacts have v2.7.0 in filename |
+| Evidence | `git show v2.7.1:auto-claude-ui/package.json` shows version 2.7.0 |
+
+---
+
+## Phase 2: Root Cause Analysis
+
+### Subtask 2-1: Inspect v2.7.1 Git Tag and Commit
+
+**Commands Used:**
+```bash
+git log -1 v2.7.1 --format='%H %s %ci'
+git show v2.7.1 --format='Commit: %H%nAuthor: %an <%ae>%nDate: %ci%nMessage: %s' --no-patch
+git tag -l v2.7.1 -n1
+git cat-file -t v2.7.1
+git show v2.7.1:auto-claude-ui/package.json | head -10 | grep version
+```
+
+#### Tag Details
+
+| Property | Value |
+|----------|-------|
+| Tag Name | v2.7.1 |
+| Tag Type | Lightweight (commit reference, not annotated) |
+| Points To | `772a5006d45487b600ce4079bae1c98f9ccf6b2e` |
+
+#### Tagged Commit Details
+
+| Property | Value |
+|----------|-------|
+| Commit Hash | `772a5006d45487b600ce4079bae1c98f9ccf6b2e` |
+| Author | AndyMik90 <andre@mikalsenutvikling.no> |
+| Commit Date | 2025-12-22 14:35:30 +0100 |
+| Commit Message | `2.7.1` |
+| package.json Version | **2.7.0** (MISMATCH) |
+
+#### Verification Output
+
+```
+$ git log -1 v2.7.1 --format='%H %s %ci'
+772a5006d45487b600ce4079bae1c98f9ccf6b2e 2.7.1 2025-12-22 14:35:30 +0100
+
+$ git show v2.7.1:auto-claude-ui/package.json | grep version
+  "version": "2.7.0",
+```
+
+#### Commit Context
+
+```
+$ git log -3 --oneline v2.7.1
+772a5006 2.7.1                                        <-- v2.7.1 TAG HERE
+d23fcd86 Enhance VirusTotal scan error handling...
+326118bd Refactor macOS build workflow...
+```
+
+#### Analysis
+
+1. **Tag Type:** The tag is a lightweight tag (just a commit reference), not an annotated tag. This means there's no separate tag object with metadata, author, or message.
+
+2. **Commit Message vs Version:** The commit message says "2.7.1" but the `package.json` at this commit still contains version `2.7.0`. This is the source of the mismatch.
+
+3. **Release Workflow Behavior:** When the GitHub release workflow triggered on tag push `v2.7.1`:
+   - It checked out commit `772a5006`
+   - It read version from `auto-claude-ui/package.json` which was `2.7.0`
+   - It built artifacts with `2.7.0` in the filename
+   - It uploaded these incorrectly-versioned artifacts to the v2.7.1 release
+
+4. **Timeline Confirmation:**
+   - Tag created: 2025-12-22 14:35:30 +0100
+   - Release published: 2025-12-22T13:35:38Z (same time, UTC)
+   - Version bump commit `8db71f3d` happened AFTER this
+
+#### Root Cause Confirmed
+
+The v2.7.1 tag points to a commit where `package.json` still had version `2.7.0`. This is a **"tag before version bump"** error in the release process.
+
+The correct sequence should have been:
+1. First: Bump package.json version to 2.7.1
+2. Second: Commit the version bump
+3. Third: Create and push the v2.7.1 tag
+
+What actually happened:
+1. Created tag v2.7.1 on commit with package.json version 2.7.0
+2. Workflow triggered and built with wrong version
+3. Version bump to 2.7.1 committed afterwards (too late)
+
+---
+
+### Subtask 2-2: GitHub Actions Workflow Run Analysis
+
+**Commands Used:**
+```bash
+gh run list --workflow=release.yml --limit=20
+gh run view 20433472030 --json conclusion,status,headSha,event,jobs
+gh run view 20433472034 --json conclusion,status,headSha,jobs  # Validate Version workflow
+```
+
+#### Release Workflow Run Details
+
+| Property | Value |
+|----------|-------|
+| Run ID | 20433472030 |
+| Status | Completed |
+| Conclusion | **success** |
+| Event | push (tag v2.7.1) |
+| Head SHA | `772a5006d45487b600ce4079bae1c98f9ccf6b2e` |
+| Created At | 2025-12-22T13:35:39Z |
+| Updated At | 2025-12-22T13:53:02Z |
+| Total Duration | ~17 minutes |
+
+#### Build Jobs Summary
+
+| Job | Status | Duration | Started | Completed |
+|-----|--------|----------|---------|-----------|
+| build-linux | ✅ success | ~2.5 min | 13:35:42Z | 13:38:15Z |
+| build-windows | ✅ success | ~4.5 min | 13:35:41Z | 13:40:11Z |
+| build-macos-intel | ✅ success | ~7 min | 13:35:42Z | 13:42:52Z |
+| build-macos-arm64 | ✅ success | ~5.5 min | 13:35:42Z | 13:41:12Z |
+| create-release | ✅ success | ~10 min | 13:42:55Z | 13:53:01Z |
+
+#### Create-Release Job Steps
+
+| Step | Conclusion |
+|------|------------|
+| Set up job | ✅ success |
+| Run actions/checkout@v4 | ✅ success |
+| Download all artifacts | ✅ success |
+| Flatten and validate artifacts | ✅ success |
+| Generate checksums | ✅ success |
+| Scan with VirusTotal | ✅ success |
+| Dry run summary | ⏭️ skipped |
+| Generate changelog | ✅ success |
+| Create Release | ✅ success |
+
+**Workflow Analysis:** The release workflow executed **successfully** - all build jobs and the release creation completed without errors. The workflow correctly:
+1. Checked out commit `772a5006d45487b600ce4079bae1c98f9ccf6b2e`
+2. Built artifacts for all platforms (Linux, Windows, macOS Intel, macOS ARM64)
+3. Generated checksums
+4. Ran VirusTotal scans
+5. Created the GitHub release with artifacts
+
+**Key Finding:** The workflow operated as designed. The problem was the **input** (source code at tagged commit), not the **workflow logic**.
+
+---
+
+#### 🚨 CRITICAL: Validate Version Workflow FAILED
+
+**Run ID:** 20433472034
+**Conclusion:** ❌ **FAILURE**
+
+| Step | Conclusion |
+|------|------------|
+| Set up job | ✅ success |
+| Checkout | ✅ success |
+| Extract version from tag | ✅ success |
+| Extract version from package.json | ✅ success |
+| **Compare versions** | ❌ **FAILURE** |
+| Version validation result | ⏭️ skipped |
+
+**What Happened:**
+1. The `validate-version.yml` workflow triggered on the v2.7.1 tag push
+2. It correctly detected that:
+   - Tag version: `2.7.1`
+   - package.json version: `2.7.0`
+3. It **FAILED** with an error because versions didn't match
+
+**Why Didn't This Stop the Release?**
+
+The `validate-version.yml` and `release.yml` workflows are **independent**:
+- Both trigger on `push: tags: - 'v*'`
+- They run in **parallel**, not sequentially
+- The release workflow has **no dependency** on the validation workflow
+- Even though validation failed, the release proceeded and succeeded
+
+**Validation Workflow (from `.github/workflows/validate-version.yml`):**
+```yaml
+on:
+  push:
+    tags:
+      - 'v*'
+```
+
+**Expected Output from Failed Validation:**
+```
+❌ ERROR: Version mismatch detected!
+
+The version in package.json (2.7.0) does not match
+the git tag version (2.7.1).
+
+To fix this:
+  1. Delete this tag: git tag -d v2.7.1
+  2. Update package.json version to 2.7.1
+  3. Commit the change
+  4. Recreate the tag: git tag -a v2.7.1 -m 'Release v2.7.1'
+```
+
+---
+
+#### Workflow Architecture Issue
+
+```
+Tag Push (v2.7.1)
+       │
+       ├──────────────────────────────────┐
+       │                                  │
+       ▼                                  ▼
+┌──────────────────┐            ┌──────────────────┐
+│  validate-version │            │     release      │
+│    ❌ FAILED      │            │   ✅ SUCCESS     │
+│ (detected error)  │  ← No    │  (built wrong     │
+│                   │   link →  │   version)        │
+└──────────────────┘            └──────────────────┘
+```
+
+**Problem:** The validation workflow runs but cannot **block** the release workflow.
+
+---
+
+#### Other v2.7.1 Workflows
+
+| Workflow | Run ID | Conclusion | Notes |
+|----------|--------|------------|-------|
+| Release | 20433472030 | ✅ success | Built and released v2.7.0 files |
+| Validate Version | 20433472034 | ❌ failure | Detected mismatch but couldn't stop release |
+| Discord Release Notification | 20433472029 | ✅ success | Notified Discord about "v2.7.1" |
+| Test on Tag | 20433472046 | ✅ success | Tests passed |
+| Build Native Module Prebuilds | 20433472017 | ❌ failure | Separate prebuilt module issue |
+
+---
+
+#### Root Cause Confirmation
+
+The GitHub Actions analysis confirms:
+
+1. **The release workflow worked correctly** - it built exactly what was in the source code at the tagged commit
+2. **The validation workflow detected the problem** - it correctly identified the version mismatch
+3. **The workflows are not connected** - validation failure could not prevent the release
+4. **The artifacts are from the right commit but wrong version** - v2.7.1 release contains v2.7.0 artifacts because that's what package.json said at commit `772a5006`
+
+---
+
+### Subtask 2-3: Root Cause Statement and Fix Options
+
+#### Root Cause Statement
+
+**Summary:** The v2.7.1 release contains v2.7.0 artifacts because the git tag was created BEFORE the `package.json` version was updated.
+
+**Root Cause:** "Tag Before Version Bump" Error
+
+| Factor | Details |
+|--------|---------|
+| **What happened** | The `v2.7.1` git tag was placed on commit `772a5006` which still had `package.json` version `2.7.0` |
+| **Why it happened** | Incorrect release procedure: tag was created before version bump was committed |
+| **How it propagated** | The release workflow correctly built from the tagged commit, reading version `2.7.0` from `package.json` |
+| **Why it wasn't caught** | The `validate-version.yml` workflow detected the mismatch but runs in parallel with `release.yml` and cannot block it |
+
+**Evidence Chain:**
+1. `git show v2.7.1:auto-claude-ui/package.json` → version `2.7.0`
+2. Release workflow run #20433472030 → built from commit `772a5006` → success
+3. Validate-version workflow run #20433472034 → detected mismatch → **FAILED** (but couldn't stop release)
+4. All 7 artifacts named `Auto-Claude-2.7.0-*` instead of `Auto-Claude-2.7.1-*`
+
+**Contributing Factors:**
+- Lightweight tag (no metadata) - easier to create on wrong commit
+- No pre-tag validation hook or script
+- Independent parallel workflows with no blocking dependency
+- Version in `package.json` is the single source of truth for artifact naming
+
+---
+
+#### Fix Options
+
+##### Option A: Recreate v2.7.1 Tag and Release (RECOMMENDED)
+
+**Description:** Delete the current v2.7.1 tag and release, then create a new tag on a commit where `package.json` has version `2.7.1`.
+
+**Steps:**
+1. Delete the v2.7.1 GitHub release: `gh release delete v2.7.1 --cleanup-tag --yes`
+2. Identify correct commit: `git log --oneline | grep -A1 "Update version to 2.7.1"`
+3. Create new tag at correct commit: `git tag v2.7.1 8db71f3d && git push origin v2.7.1`
+4. Release workflow will trigger automatically with correct version
+5. Verify new artifacts have `2.7.1` in filenames
+
+**Pros:**
+- ✅ Users get the correct version they expect (v2.7.1)
+- ✅ Maintains clean version history
+- ✅ Checksums will match the correct filenames
+- ✅ Auto-update mechanisms will work correctly
+- ✅ No need to update documentation or links
+
+**Cons:**
+- ⚠️ Users who already downloaded v2.7.1 (v2.7.0 files) may be confused
+- ⚠️ Requires deleting and recreating the release
+- ⚠️ Brief window where v2.7.1 doesn't exist
+
+**Risk Level:** Medium - temporary unavailability, but correct outcome
+
+---
+
+##### Option B: Publish v2.7.2 with Correct Files
+
+**Description:** Leave v2.7.1 as-is (deprecated) and publish v2.7.2 with the correct build.
+
+**Steps:**
+1. Mark v2.7.1 as deprecated in release notes
+2. Bump package.json to 2.7.2
+3. Create and push v2.7.2 tag
+4. Publish v2.7.2 release with correct artifacts
+5. Update download links/documentation to point to v2.7.2
+
+**Pros:**
+- ✅ No disruption to existing v2.7.1 downloads
+- ✅ Preserves release history for audit trail
+- ✅ Clear indication that v2.7.2 supersedes v2.7.1
+
+**Cons:**
+- ❌ Version number gap in release history (no "real" 2.7.1)
+- ❌ Confusing version progression for users
+- ❌ Requires updating all download links and documentation
+- ❌ Users may still download deprecated v2.7.1
+
+**Risk Level:** Low - no deletion, but messy version history
+
+---
+
+##### Option C: Manual File Upload with --clobber
+
+**Description:** Build correct v2.7.1 artifacts locally and upload to replace existing files.
+
+**Steps:**
+1. Checkout commit with package.json version 2.7.1
+2. Build all platform artifacts locally (or trigger workflow to download)
+3. Delete existing assets: `gh release delete-asset v2.7.1 Auto-Claude-2.7.0-* --yes`
+4. Upload correct files: `gh release upload v2.7.1 ./dist/* --clobber`
+5. Update checksums file
+
+**Pros:**
+- ✅ Keeps same release and tag
+- ✅ No temporary unavailability window
+
+**Cons:**
+- ❌ Complex manual process prone to errors
+- ❌ Requires local build environment for all platforms (macOS, Windows, Linux)
+- ❌ May not match workflow-built artifacts exactly
+- ❌ Code signing could be different than CI
+- ❌ Does not address underlying tag/commit mismatch
+
+**Risk Level:** High - manual process, potential signing issues
+
+---
+
+#### Recommendation
+
+**Recommended Option: A - Recreate v2.7.1 Tag and Release**
+
+**Rationale:**
+1. **Correctness**: The tag should point to a commit where the codebase reflects v2.7.1
+2. **Automation**: Letting the release workflow rebuild ensures identical CI artifacts
+3. **User Experience**: Users expect v2.7.1 to contain 2.7.1 code and files
+4. **Maintainability**: Clean version history is easier to manage long-term
+5. **Auto-updates**: Electron auto-updater relies on version matching
+
+**Implementation Priority:**
+1. First: Fix v2.7.1 release (Option A)
+2. Then: Update workflow to prevent recurrence (make validation blocking)
+
+---
+
+#### Process Improvements Required
+
+Regardless of fix option chosen, these changes should be implemented to prevent recurrence:
+
+| Improvement | Priority | Description |
+|-------------|----------|-------------|
+| Make validation blocking | HIGH | Modify `release.yml` to depend on `validate-version.yml` passing |
+| Add pre-tag script | MEDIUM | Create script that validates version before allowing tag creation |
+| Use annotated tags | LOW | Annotated tags include metadata and require explicit message |
+| Document release procedure | MEDIUM | Create runbook for correct release process |
+
+**Workflow Architecture Change:**
+```yaml
+# Before (parallel, independent):
+Tag Push → release.yml (runs)
+         → validate-version.yml (runs, but can't block)
+
+# After (sequential, dependent):
+Tag Push → validate-version.yml (runs first)
+           ↓ success required
+         → release.yml (only runs if validation passes)
+```
+
+---
+
+## Next Steps
+
+1. ~~**Subtask 1-1:** Verify v2.7.1 assets~~ ✅ Complete
+2. ~~**Subtask 1-2:** Compare with v2.7.0 release and verify expected naming pattern~~ ✅ Complete
+3. ~~**Subtask 1-3:** Check package.json version and git state~~ ✅ Complete - ROOT CAUSE IDENTIFIED
+4. ~~**Subtask 2-1:** Inspect v2.7.1 git tag and commit~~ ✅ Complete - TAG/COMMIT MISMATCH CONFIRMED
+5. ~~**Subtask 2-2:** Check release workflow runs~~ ✅ Complete - VALIDATION DETECTED BUT COULDN'T STOP RELEASE
+6. ~~**Subtask 2-3:** Document fix options~~ ✅ Complete - 3 OPTIONS DOCUMENTED, OPTION A RECOMMENDED
+7. **Phase 3:** Implement fix (re-upload correct files or publish v2.7.2)
+8. **Phase 4:** Add validation to prevent future occurrences
+
+---
+
+## Status: Phase 2 Complete ✅
+
+**Root Cause:** The v2.7.1 tag was created on commit `772a5006` which still had `package.json` version `2.7.0`. The validation workflow detected this but couldn't stop the release workflow.
+
+**Key Findings from Workflow Analysis:**
+- Release workflow (ID: 20433472030): ✅ Success - correctly built from tagged commit
+- Validate Version workflow (ID: 20433472034): ❌ Failed - correctly detected version mismatch
+- The workflows run in parallel with no dependency relationship
+
+**Recommended Fix:** Option A - Delete v2.7.1 tag and release, recreate tag at commit `8db71f3d` where `package.json` has version `2.7.1`, let workflow rebuild.
+
+**Process Improvement Needed:**
+- Version bump should ALWAYS happen BEFORE tagging
+- **Make release.yml depend on validate-version.yml** using `needs:` or combine them
+- Consider using a reusable workflow or job dependency to enforce validation

README.md

@@ -1,222 +1,269 @@
 # Auto Claude
 
-**Autonomous multi-agent coding framework that plans, builds, and validates software for you.**
+Your AI coding companion. Build features, fix bugs, and ship faster — with autonomous agents that plan, code, and validate for you.
 
 ![Auto Claude Kanban Board](.github/assets/Auto-Claude-Kanban.png)
 
-[![License](https://img.shields.io/badge/license-AGPL--3.0-green?style=flat-square)](./agpl-3.0.txt)
-[![Discord](https://img.shields.io/badge/Discord-Join%20Community-5865F2?style=flat-square&logo=discord&logoColor=white)](https://discord.gg/KCXaPBr4Dj)
-[![YouTube](https://img.shields.io/badge/YouTube-Subscribe-FF0000?style=flat-square&logo=youtube&logoColor=white)](https://www.youtube.com/@AndreMikalsen)
-[![CI](https://img.shields.io/github/actions/workflow/status/AndyMik90/Auto-Claude/ci.yml?branch=main&style=flat-square&label=CI)](https://github.com/AndyMik90/Auto-Claude/actions)
+[![Discord](https://img.shields.io/badge/Discord-Join%20Community-5865F2?style=for-the-badge&logo=discord&logoColor=white)](https://discord.gg/KCXaPBr4Dj)
 
----
+## What It Does ✨
 
-## Download
+**Auto Claude is a desktop app that supercharges your AI coding workflow.** Whether you're a vibe coder just getting started or an experienced developer, Auto Claude meets you where you are.
 
-### Stable Release
+- **Autonomous Tasks** — Describe what you want to build, and agents handle planning, coding, and validation while you focus on other work
+- **Agent Terminals** — Run Claude Code in up to 12 terminals with a clean layout, smart naming based on context, and one-click task context injection
+- **Safe by Default** — All work happens in git worktrees, keeping your main branch undisturbed until you're ready to merge
+- **Self-Validating** — Built-in QA agents check their own work before you review
 
-<!-- STABLE_VERSION_BADGE -->
-[![Stable](https://img.shields.io/badge/stable-2.7.4-blue?style=flat-square)](https://github.com/AndyMik90/Auto-Claude/releases/tag/v2.7.4)
-<!-- STABLE_VERSION_BADGE_END -->
+**The result?** 10x your output while maintaining code quality.
 
-<!-- STABLE_DOWNLOADS -->
-| Platform | Download |
-|----------|----------|
-| **Windows** | [Auto-Claude-2.7.3-win32-x64.exe](https://github.com/AndyMik90/Auto-Claude/releases/download/v2.7.3/Auto-Claude-2.7.3-win32-x64.exe) |
-| **macOS (Apple Silicon)** | [Auto-Claude-2.7.3-darwin-arm64.dmg](https://github.com/AndyMik90/Auto-Claude/releases/download/v2.7.3/Auto-Claude-2.7.3-darwin-arm64.dmg) |
-| **macOS (Intel)** | [Auto-Claude-2.7.3-darwin-x64.dmg](https://github.com/AndyMik90/Auto-Claude/releases/download/v2.7.3/Auto-Claude-2.7.3-darwin-x64.dmg) |
-| **Linux** | [Auto-Claude-2.7.3-linux-x86_64.AppImage](https://github.com/AndyMik90/Auto-Claude/releases/download/v2.7.3/Auto-Claude-2.7.3-linux-x86_64.AppImage) |
-| **Linux (Debian)** | [Auto-Claude-2.7.3-linux-amd64.deb](https://github.com/AndyMik90/Auto-Claude/releases/download/v2.7.3/Auto-Claude-2.7.3-linux-amd64.deb) |
-| **Linux (Flatpak)** | [Auto-Claude-2.7.3-linux-x86_64.flatpak](https://github.com/AndyMik90/Auto-Claude/releases/download/v2.7.3/Auto-Claude-2.7.3-linux-x86_64.flatpak) |
-<!-- STABLE_DOWNLOADS_END -->
+## Key Features
 
-### Beta Release
-
-> ⚠️ Beta releases may contain bugs and breaking changes. [View all releases](https://github.com/AndyMik90/Auto-Claude/releases)
-
-<!-- BETA_VERSION_BADGE -->
-[![Beta](https://img.shields.io/badge/beta-2.7.2--beta.10-orange?style=flat-square)](https://github.com/AndyMik90/Auto-Claude/releases/tag/v2.7.2-beta.10)
-<!-- BETA_VERSION_BADGE_END -->
-
-<!-- BETA_DOWNLOADS -->
-| Platform | Download |
-|----------|----------|
-| **Windows** | [Auto-Claude-2.7.2-beta.10-win32-x64.exe](https://github.com/AndyMik90/Auto-Claude/releases/download/v2.7.2-beta.10/Auto-Claude-2.7.2-beta.10-win32-x64.exe) |
-| **macOS (Apple Silicon)** | [Auto-Claude-2.7.2-beta.10-darwin-arm64.dmg](https://github.com/AndyMik90/Auto-Claude/releases/download/v2.7.2-beta.10/Auto-Claude-2.7.2-beta.10-darwin-arm64.dmg) |
-| **macOS (Intel)** | [Auto-Claude-2.7.2-beta.10-darwin-x64.dmg](https://github.com/AndyMik90/Auto-Claude/releases/download/v2.7.2-beta.10/Auto-Claude-2.7.2-beta.10-darwin-x64.dmg) |
-| **Linux** | [Auto-Claude-2.7.2-beta.10-linux-x86_64.AppImage](https://github.com/AndyMik90/Auto-Claude/releases/download/v2.7.2-beta.10/Auto-Claude-2.7.2-beta.10-linux-x86_64.AppImage) |
-| **Linux (Debian)** | [Auto-Claude-2.7.2-beta.10-linux-amd64.deb](https://github.com/AndyMik90/Auto-Claude/releases/download/v2.7.2-beta.10/Auto-Claude-2.7.2-beta.10-linux-amd64.deb) |
-| **Linux (Flatpak)** | [Auto-Claude-2.7.2-beta.10-linux-x86_64.flatpak](https://github.com/AndyMik90/Auto-Claude/releases/download/v2.7.2-beta.10/Auto-Claude-2.7.2-beta.10-linux-x86_64.flatpak) |
-<!-- BETA_DOWNLOADS_END -->
-
-> All releases include SHA256 checksums and VirusTotal scan results for security verification.
-
----
-
-## Requirements
-
-- **Claude Pro/Max subscription** - [Get one here](https://claude.ai/upgrade)
-- **Claude Code CLI** - `npm install -g @anthropic-ai/claude-code`
-- **Git repository** - Your project must be initialized as a git repo
-
----
+- **Parallel Agents**: Run multiple builds simultaneously while you focus on other work
+- **Context Engineering**: Agents understand your codebase structure before writing code
+- **Self-Validating**: Built-in QA loop catches issues before you review
+- **Isolated Workspaces**: All work happens in git worktrees — your code stays safe
+- **AI Merge Resolution**: Intelligent conflict resolution when merging back to main — no manual conflict fixing
+- **Cross-Platform**: Desktop app runs on Mac, Windows, and Linux
+- **Any Project Type**: Build web apps, APIs, CLIs — works with any software project
 
 ## Quick Start
 
-1. **Download and install** the app for your platform
-2. **Open your project** - Select a git repository folder
-3. **Connect Claude** - The app will guide you through OAuth setup
-4. **Create a task** - Describe what you want to build
-5. **Watch it work** - Agents plan, code, and validate autonomously
+### Download Auto Claude
+
+Download the latest release for your platform from [GitHub Releases](https://github.com/AndyMik90/Auto-Claude/releases/latest):
+
+| Platform | Download |
+|----------|----------|
+| **macOS (Apple Silicon M1-M4)** | `*-arm64.dmg` |
+| **macOS (Intel)** | `*-x64.dmg` |
+| **Windows** | `*.exe` |
+| **Linux** | `*.AppImage` or `*.deb` |
+
+> **Not sure which Mac?** Click the Apple menu () > "About This Mac". Look for "Chip" - M1/M2/M3/M4 = Apple Silicon, otherwise Intel.
+
+### Prerequisites
+
+Before using Auto Claude, you need:
+
+1. **Claude Subscription** - Requires [Claude Pro or Max](https://claude.ai/upgrade) for Claude Code access
+2. **Claude Code CLI** - Install with: `npm install -g @anthropic-ai/claude-code`
+
+### Install and Run
+
+1. **Download** the installer for your platform from the table above
+2. **Install**:
+   - **macOS**: Open the `.dmg`, drag Auto Claude to Applications
+   - **Windows**: Run the `.exe` installer (see note below about security warning)
+   - **Linux**: Make the AppImage executable (`chmod +x`) and run it, or install the `.deb`
+3. **Launch** Auto Claude
+4. **Add your project** and start building!
+
+<details>
+<summary><b>Windows users:</b> Security warning when installing</summary>
+
+The Windows installer is not yet code-signed, so you may see a "Windows protected your PC" warning from Microsoft Defender SmartScreen.
+
+**To proceed:**
+1. Click "More info"
+2. Click "Run anyway"
+
+This is safe — all releases are automatically scanned with VirusTotal before publishing. You can verify any installer by checking the **VirusTotal Scan Results** section in each [release's notes](https://github.com/AndyMik90/Auto-Claude/releases).
+
+We're working on obtaining a code signing certificate for future releases.
+
+</details>
+
+> **Want to build from source?** See [CONTRIBUTING.md](CONTRIBUTING.md#running-from-source) for development setup.
 
 ---
 
-## Features
-
-| Feature | Description |
-|---------|-------------|
-| **Autonomous Tasks** | Describe your goal; agents handle planning, implementation, and validation |
-| **Parallel Execution** | Run multiple builds simultaneously with up to 12 agent terminals |
-| **Isolated Workspaces** | All changes happen in git worktrees - your main branch stays safe |
-| **Self-Validating QA** | Built-in quality assurance loop catches issues before you review |
-| **AI-Powered Merge** | Automatic conflict resolution when integrating back to main |
-| **Memory Layer** | Agents retain insights across sessions for smarter builds |
-| **GitHub/GitLab Integration** | Import issues, investigate with AI, create merge requests |
-| **Linear Integration** | Sync tasks with Linear for team progress tracking |
-| **Cross-Platform** | Native desktop apps for Windows, macOS, and Linux |
-| **Auto-Updates** | App updates automatically when new versions are released |
-
----
-
-## Interface
+## 🎯 Features
 
 ### Kanban Board
-Visual task management from planning through completion. Create tasks and monitor agent progress in real-time.
+
+Plan tasks and let AI handle the planning, coding, and validation — all in a visual interface. Track progress from "Planning" to "Done" while agents work autonomously.
 
 ### Agent Terminals
-AI-powered terminals with one-click task context injection. Spawn multiple agents for parallel work.
 
-![Agent Terminals](.github/assets/Auto-Claude-Agents-terminals.png)
+Spawn up to 12 AI-powered terminals for hands-on coding. Inject task context with a click, reference files from your project, and work rapidly across multiple sessions.
+
+**Power users:** Connect multiple Claude Code subscriptions to run even more agents in parallel — perfect for teams or heavy workloads.
+
+![Auto Claude Agent Terminals](.github/assets/Auto-Claude-Agents-terminals.png)
+
+### Insights
+
+Have a conversation about your project in a ChatGPT-style interface. Ask questions, get explanations, and explore your codebase through natural dialogue.
 
 ### Roadmap
-AI-assisted feature planning with competitor analysis and audience targeting.
 
-![Roadmap](.github/assets/Auto-Claude-roadmap.png)
+Based on your target audience, AI anticipates and plans the most impactful features you should focus on. Prioritize what matters most to your users.
 
-### Additional Features
-- **Insights** - Chat interface for exploring your codebase
-- **Ideation** - Discover improvements, performance issues, and vulnerabilities
-- **Changelog** - Generate release notes from completed tasks
+![Auto Claude Roadmap](.github/assets/Auto-Claude-roadmap.png)
+
+### Ideation
+
+Let AI help you create a project that shines. Rapidly understand your codebase and discover:
+- Code improvements and refactoring opportunities
+- Performance bottlenecks
+- Security vulnerabilities
+- Documentation gaps
+- UI/UX enhancements
+- Overall code quality issues
+
+### Changelog
+
+Write professional changelogs effortlessly. Generate release notes from completed Auto Claude tasks or integrate with GitHub to create masterclass changelogs automatically.
+
+### Context
+
+See exactly what Auto Claude understands about your project — the tech stack, file structure, patterns, and insights it uses to write better code.
+
+### AI Merge Resolution
+
+When your main branch evolves while a build is in progress, Auto Claude automatically resolves merge conflicts using AI — no manual `<<<<<<< HEAD` fixing required.
+
+**How it works:**
+1. **Git Auto-Merge First** — Simple non-conflicting changes merge instantly without AI
+2. **Conflict-Only AI** — For actual conflicts, AI receives only the specific conflict regions (not entire files), achieving ~98% prompt reduction
+3. **Parallel Processing** — Multiple conflicting files resolve simultaneously for faster merges
+4. **Syntax Validation** — Every merge is validated before being applied
+
+**The result:** A build that was 50+ commits behind main merges in seconds instead of requiring manual conflict resolution.
 
 ---
 
+## CLI Usage (Terminal-Only)
+
+For terminal-based workflows, headless servers, or CI/CD integration, see **[guides/CLI-USAGE.md](guides/CLI-USAGE.md)**.
+
+## ⚙️ How It Works
+
+Auto Claude focuses on three core principles: **context engineering** (understanding your codebase before writing code), **good coding standards** (following best practices and patterns), and **validation logic** (ensuring code works before you see it).
+
+### The Agent Pipeline
+
+**Phase 1: Spec Creation** (3-8 phases based on complexity)
+
+Before any code is written, agents gather context and create a detailed specification:
+
+1. **Discovery** — Analyzes your project structure and tech stack
+2. **Requirements** — Gathers what you want to build through interactive conversation
+3. **Research** — Validates external integrations against real documentation
+4. **Context Discovery** — Finds relevant files in your codebase
+5. **Spec Writer** — Creates a comprehensive specification document
+6. **Spec Critic** — Self-critiques using extended thinking to find issues early
+7. **Planner** — Breaks work into subtasks with dependencies
+8. **Validation** — Ensures all outputs are valid before proceeding
+
+**Phase 2: Implementation**
+
+With a validated spec, coding agents execute the plan:
+
+1. **Planner Agent** — Creates subtask-based implementation plan
+2. **Coder Agent** — Implements subtasks one-by-one with verification
+3. **QA Reviewer** — Validates all acceptance criteria
+4. **QA Fixer** — Fixes issues in a self-healing loop (up to 50 iterations)
+
+Each session runs with a fresh context window. Progress is tracked via `implementation_plan.json` and Git commits.
+
+**Phase 3: Merge**
+
+When you're ready to merge, AI handles any conflicts that arose while you were working:
+
+1. **Conflict Detection** — Identifies files modified in both main and the build
+2. **3-Tier Resolution** — Git auto-merge → Conflict-only AI → Full-file AI (fallback)
+3. **Parallel Merge** — Multiple files resolve simultaneously
+4. **Staged for Review** — Changes are staged but not committed, so you can review before finalizing
+
+### 🔒 Security Model
+
+Three-layer defense keeps your code safe:
+- **OS Sandbox** — Bash commands run in isolation
+- **Filesystem Restrictions** — Operations limited to project directory
+- **Command Allowlist** — Only approved commands based on your project's stack
+
 ## Project Structure
 
 ```
-Auto-Claude/
-├── apps/
-│   ├── backend/     # Python agents, specs, QA pipeline
-│   └── frontend/    # Electron desktop application
-├── guides/          # Additional documentation
-├── tests/           # Test suite
-└── scripts/         # Build utilities
+your-project/
+├── .worktrees/               # Created during build (git-ignored)
+│   └── auto-claude/          # Isolated workspace for AI coding
+├── .auto-claude/             # Per-project data (specs, plans, QA reports)
+│   ├── specs/                # Task specifications
+│   ├── roadmap/              # Project roadmap
+│   └── ideation/             # Ideas and planning
+├── auto-claude/              # Python backend (framework code)
+│   ├── run.py                # Build entry point
+│   ├── spec_runner.py        # Spec creation orchestrator
+│   ├── prompts/              # Agent prompt templates
+│   └── ...
+└── auto-claude-ui/           # Electron desktop application
+    └── ...
 ```
 
----
+### Understanding the Folders
 
-## CLI Usage
+**You don't create these folders manually** - they serve different purposes:
 
-For headless operation, CI/CD integration, or terminal-only workflows:
+- **`auto-claude/`** - The framework repository itself (clone this once from GitHub)
+- **`.auto-claude/`** - Created automatically in YOUR project when you run Auto Claude (stores specs, plans, QA reports)
+- **`.worktrees/`** - Temporary isolated workspaces created during builds (git-ignored, deleted after merge)
 
+**When using Auto Claude on your project:**
 ```bash
-cd apps/backend
-
-# Create a spec interactively
-python spec_runner.py --interactive
-
-# Run autonomous build
-python run.py --spec 001
-
-# Review and merge
-python run.py --spec 001 --review
-python run.py --spec 001 --merge
+cd your-project/              # Your own project directory
+python /path/to/auto-claude/run.py --spec 001
+# Auto Claude creates .auto-claude/ automatically in your-project/
 ```
 
-See [guides/CLI-USAGE.md](guides/CLI-USAGE.md) for complete CLI documentation.
+**When developing Auto Claude itself:**
+```bash
+git clone https://github.com/yourusername/auto-claude
+cd auto-claude/               # You're working in the framework repo
+```
 
----
+The `.auto-claude/` directory is gitignored and project-specific - you'll have one per project you use Auto Claude on.
 
-## Development
+## Environment Variables (CLI Only)
 
-Want to build from source or contribute? See [CONTRIBUTING.md](CONTRIBUTING.md) for complete development setup instructions.
+> **Desktop UI users:** These are configured through the app settings — no manual setup needed.
 
-For Linux-specific builds (Flatpak, AppImage), see [guides/linux.md](guides/linux.md).
+| Variable | Required | Description |
+|----------|----------|-------------|
+| `CLAUDE_CODE_OAUTH_TOKEN` | Yes | OAuth token from `claude setup-token` |
+| `AUTO_BUILD_MODEL` | No | Model override (default: claude-opus-4-5-20251101) |
 
----
+See `auto-claude/.env.example` for complete configuration options.
 
-## Security
+## 💬 Community
 
-Auto Claude uses a three-layer security model:
+Join our Discord to get help, share what you're building, and connect with other Auto Claude users:
 
-1. **OS Sandbox** - Bash commands run in isolation
-2. **Filesystem Restrictions** - Operations limited to project directory
-3. **Dynamic Command Allowlist** - Only approved commands based on detected project stack
+[![Discord](https://img.shields.io/badge/Discord-Join%20Community-5865F2?style=for-the-badge&logo=discord&logoColor=white)](https://discord.gg/KCXaPBr4Dj)
 
-All releases are:
-- Scanned with VirusTotal before publishing
-- Include SHA256 checksums for verification
-- Code-signed where applicable (macOS)
+## 🤝 Contributing
 
----
+We welcome contributions! Whether it's bug fixes, new features, or documentation improvements.
 
-## Available Scripts
+See **[CONTRIBUTING.md](CONTRIBUTING.md)** for guidelines on how to get started.
 
-| Command | Description |
-|---------|-------------|
-| `npm run install:all` | Install backend and frontend dependencies |
-| `npm start` | Build and run the desktop app |
-| `npm run dev` | Run in development mode with hot reload |
-| `npm run package` | Package for current platform |
-| `npm run package:mac` | Package for macOS |
-| `npm run package:win` | Package for Windows |
-| `npm run package:linux` | Package for Linux |
-| `npm run package:flatpak` | Package as Flatpak (see [guides/linux.md](guides/linux.md)) |
-| `npm run lint` | Run linter |
-| `npm test` | Run frontend tests |
-| `npm run test:backend` | Run backend tests |
+## Acknowledgments
 
----
-
-## Contributing
-
-We welcome contributions! Please read [CONTRIBUTING.md](CONTRIBUTING.md) for:
-- Development setup instructions
-- Code style guidelines
-- Testing requirements
-- Pull request process
-
----
-
-## Community
-
-- **Discord** - [Join our community](https://discord.gg/KCXaPBr4Dj)
-- **Issues** - [Report bugs or request features](https://github.com/AndyMik90/Auto-Claude/issues)
-- **Discussions** - [Ask questions](https://github.com/AndyMik90/Auto-Claude/discussions)
-
----
+This framework was inspired by Anthropic's [Autonomous Coding Agent](https://github.com/anthropics/claude-quickstarts/tree/main/autonomous-coding). Thank you to the Anthropic team for their innovative work on autonomous coding systems.
 
 ## License
 
 **AGPL-3.0** - GNU Affero General Public License v3.0
 
-Auto Claude is free to use. If you modify and distribute it, or run it as a service, your code must also be open source under AGPL-3.0.
+This software is licensed under AGPL-3.0, which means:
 
-Commercial licensing available for closed-source use cases.
+- **Attribution Required**: You must give appropriate credit, provide a link to the license, and indicate if changes were made. When using Auto Claude, please credit the project.
+- **Open Source Required**: If you modify this software and distribute it or run it as a service, you must release your source code under AGPL-3.0.
+- **Network Use (Copyleft)**: If you run this software as a network service (e.g., SaaS), users interacting with it over a network must be able to receive the source code.
+- **No Closed-Source Usage**: You cannot use this software in proprietary/closed-source projects without open-sourcing your entire project under AGPL-3.0.
 
----
+**In simple terms**: You can use Auto Claude freely, but if you build on it, your code must also be open source under AGPL-3.0 and attribute this project. Closed-source commercial use requires a separate license.
 
-## Star History
-
-[![GitHub Repo stars](https://img.shields.io/github/stars/AndyMik90/Auto-Claude?style=social)](https://github.com/AndyMik90/Auto-Claude/stargazers)
-
-[![Star History Chart](https://api.star-history.com/svg?repos=AndyMik90/Auto-Claude&type=Date)](https://star-history.com/#AndyMik90/Auto-Claude&Date)
+For commercial licensing inquiries (closed-source usage), please contact the maintainers.

RELEASE.md

@@ -1,255 +1,186 @@
 # Release Process
 
-This document describes how releases are created for Auto Claude.
+This document describes how to create a new release of Auto Claude.
 
-## Overview
+## Automated Release Process (Recommended)
 
-Auto Claude uses an automated release pipeline that ensures releases are only published after all builds succeed. This prevents version mismatches between documentation and actual releases.
+We provide an automated script that handles version bumping, git commits, and tagging to ensure version consistency.
+
+### Prerequisites
+
+- Clean git working directory (no uncommitted changes)
+- You're on the branch you want to release from (usually `main`)
+
+### Steps
+
+1. **Run the version bump script:**
+
+   ```bash
+   # Bump patch version (2.5.5 -> 2.5.6)
+   node scripts/bump-version.js patch
+
+   # Bump minor version (2.5.5 -> 2.6.0)
+   node scripts/bump-version.js minor
+
+   # Bump major version (2.5.5 -> 3.0.0)
+   node scripts/bump-version.js major
+
+   # Set specific version
+   node scripts/bump-version.js 2.6.0
+   ```
+
+   This script will:
+   - ✅ Update `auto-claude-ui/package.json` with the new version
+   - ✅ Create a git commit with the version change
+   - ✅ Create a git tag (e.g., `v2.5.6`)
+   - ⚠️  **NOT** push to remote (you control when to push)
+
+2. **Review the changes:**
+
+   ```bash
+   git log -1              # View the commit
+   git show v2.5.6         # View the tag
+   ```
+
+3. **Push to GitHub:**
+
+   ```bash
+   # Push the commit
+   git push origin main
+
+   # Push the tag
+   git push origin v2.5.6
+   ```
+
+4. **Create GitHub Release:**
+
+   - Go to [GitHub Releases](https://github.com/AndyMik90/Auto-Claude/releases)
+   - Click "Draft a new release"
+   - Select the tag you just pushed (e.g., `v2.5.6`)
+   - Add release notes (describe what changed)
+   - Click "Publish release"
+
+5. **Automated builds will trigger:**
+
+   - ✅ Version validation workflow will verify version consistency
+   - ✅ Tests will run (`test-on-tag.yml`)
+   - ✅ Native module prebuilds will be created (`build-prebuilds.yml`)
+   - ✅ Discord notification will be sent (`discord-release.yml`)
+
+## Manual Release Process (Not Recommended)
+
+If you need to create a release manually, follow these steps **carefully** to avoid version mismatches:
+
+1. **Update `auto-claude-ui/package.json`:**
+
+   ```json
+   {
+     "version": "2.5.6"
+   }
+   ```
+
+2. **Commit the change:**
+
+   ```bash
+   git add auto-claude-ui/package.json
+   git commit -m "chore: bump version to 2.5.6"
+   ```
+
+3. **Create and push tag:**
+
+   ```bash
+   git tag -a v2.5.6 -m "Release v2.5.6"
+   git push origin main
+   git push origin v2.5.6
+   ```
+
+4. **Create GitHub Release** (same as step 4 above)
+
+## Version Validation
+
+A GitHub Action automatically validates that the version in `package.json` matches the git tag.
+
+If there's a mismatch, the workflow will **fail** with a clear error message:
 
 ```
-┌─────────────────────────────────────────────────────────────────────────────┐
-│                           RELEASE FLOW                                       │
-├─────────────────────────────────────────────────────────────────────────────┤
-│                                                                              │
-│   develop branch                    main branch                              │
-│   ──────────────                    ───────────                              │
-│        │                                 │                                   │
-│        │  1. bump-version.js             │                                   │
-│        │     (creates commit)            │                                   │
-│        │                                 │                                   │
-│        ▼                                 │                                   │
-│   ┌─────────┐                           │                                   │
-│   │ v2.8.0  │  2. Create PR             │                                   │
-│   │ commit  │ ────────────────────►     │                                   │
-│   └─────────┘                           │                                   │
-│                                          │                                   │
-│                           3. Merge PR    ▼                                   │
-│                                    ┌──────────┐                              │
-│                                    │ v2.8.0   │                              │
-│                                    │ on main  │                              │
-│                                    └────┬─────┘                              │
-│                                         │                                    │
-│                     ┌───────────────────┴───────────────────┐               │
-│                     │     GitHub Actions (automatic)         │               │
-│                     ├───────────────────────────────────────┤               │
-│                     │ 4. prepare-release.yml                 │               │
-│                     │    - Detects version > latest tag      │               │
-│                     │    - Creates tag v2.8.0                │               │
-│                     │                                        │               │
-│                     │ 5. release.yml (triggered by tag)      │               │
-│                     │    - Builds macOS (Intel + ARM)        │               │
-│                     │    - Builds Windows                    │               │
-│                     │    - Builds Linux                      │               │
-│                     │    - Generates changelog               │               │
-│                     │    - Creates GitHub release            │               │
-│                     │    - Updates README                    │               │
-│                     └───────────────────────────────────────┘               │
-│                                                                              │
-└─────────────────────────────────────────────────────────────────────────────┘
+❌ ERROR: Version mismatch detected!
+
+The version in package.json (2.5.0) does not match
+the git tag version (2.5.5).
+
+To fix this:
+  1. Delete this tag: git tag -d v2.5.5
+  2. Update package.json version to 2.5.5
+  3. Commit the change
+  4. Recreate the tag: git tag -a v2.5.5 -m 'Release v2.5.5'
 ```
 
-## For Maintainers: Creating a Release
-
-### Step 1: Bump the Version
-
-On your development branch (typically `develop` or a feature branch):
-
-```bash
-# Navigate to project root
-cd /path/to/auto-claude
-
-# Bump version (choose one)
-node scripts/bump-version.js patch   # 2.7.1 -> 2.7.2 (bug fixes)
-node scripts/bump-version.js minor   # 2.7.1 -> 2.8.0 (new features)
-node scripts/bump-version.js major   # 2.7.1 -> 3.0.0 (breaking changes)
-node scripts/bump-version.js 2.8.0   # Set specific version
-```
-
-This will:
-- Update `apps/frontend/package.json`
-- Update `package.json` (root)
-- Update `apps/backend/__init__.py`
-- Check if `CHANGELOG.md` has an entry for the new version (warns if missing)
-- Create a commit with message `chore: bump version to X.Y.Z`
-
-### Step 2: Update CHANGELOG.md (REQUIRED)
-
-**IMPORTANT: The release will fail if CHANGELOG.md doesn't have an entry for the new version.**
-
-Add release notes to `CHANGELOG.md` at the top of the file:
-
-```markdown
-## 2.8.0 - Your Release Title
-
-### ✨ New Features
-- Feature description
-
-### 🛠️ Improvements
-- Improvement description
-
-### 🐛 Bug Fixes
-- Fix description
-
----
-```
-
-Then amend the version bump commit:
-
-```bash
-git add CHANGELOG.md
-git commit --amend --no-edit
-```
-
-### Step 3: Push and Create PR
-
-```bash
-# Push your branch
-git push origin your-branch
-
-# Create PR to main (via GitHub UI or gh CLI)
-gh pr create --base main --title "Release v2.8.0"
-```
-
-### Step 4: Merge to Main
-
-Once the PR is approved and merged to `main`, GitHub Actions will automatically:
-
-1. **Detect the version bump** (`prepare-release.yml`)
-2. **Validate CHANGELOG.md** has an entry for the new version (FAILS if missing)
-3. **Extract release notes** from CHANGELOG.md
-4. **Create a git tag** (e.g., `v2.8.0`)
-5. **Trigger the release workflow** (`release.yml`)
-6. **Build binaries** for all platforms:
-   - macOS Intel (x64) - code signed & notarized
-   - macOS Apple Silicon (arm64) - code signed & notarized
-   - Windows (NSIS installer) - code signed
-   - Linux (AppImage + .deb)
-7. **Scan binaries** with VirusTotal
-8. **Create GitHub release** with release notes from CHANGELOG.md
-9. **Update README** with new version badge and download links
-
-### Step 5: Verify
-
-After merging, check:
-- [GitHub Actions](https://github.com/AndyMik90/Auto-Claude/actions) - ensure all workflows pass
-- [Releases](https://github.com/AndyMik90/Auto-Claude/releases) - verify release was created
-- [README](https://github.com/AndyMik90/Auto-Claude#download) - confirm version updated
-
-## Version Numbering
-
-We follow [Semantic Versioning](https://semver.org/):
-
-- **MAJOR** (X.0.0): Breaking changes, incompatible API changes
-- **MINOR** (0.X.0): New features, backwards compatible
-- **PATCH** (0.0.X): Bug fixes, backwards compatible
-
-## Changelog Management
-
-Release notes are managed in `CHANGELOG.md` and used for GitHub releases.
-
-### Changelog Format
-
-Each version entry in `CHANGELOG.md` should follow this format:
-
-```markdown
-## X.Y.Z - Release Title
-
-### ✨ New Features
-- Feature description with context
-
-### 🛠️ Improvements
-- Improvement description
-
-### 🐛 Bug Fixes
-- Fix description
-
----
-```
-
-### Changelog Validation
-
-The release workflow **validates** that `CHANGELOG.md` has an entry for the version being released:
-
-- If the entry is **missing**, the release is **blocked** with a clear error message
-- If the entry **exists**, its content is used for the GitHub release notes
-
-### Writing Good Release Notes
-
-- **Be specific**: Instead of "Fixed bug", write "Fixed crash when opening large files"
-- **Group by impact**: Features first, then improvements, then fixes
-- **Credit contributors**: Mention contributors for significant changes
-- **Link issues**: Reference GitHub issues where relevant (e.g., "Fixes #123")
-
-## Workflows
-
-| Workflow | Trigger | Purpose |
-|----------|---------|---------|
-| `prepare-release.yml` | Push to `main` | Detects version bump, **validates CHANGELOG.md**, creates tag |
-| `release.yml` | Tag `v*` pushed | Builds binaries, extracts changelog, creates release |
-| `validate-version.yml` | Tag `v*` pushed | Validates tag matches package.json |
-| `update-readme` (in release.yml) | After release | Updates README with new version |
+This validation ensures we never ship a release where the updater shows the wrong version.
 
 ## Troubleshooting
 
-### Release didn't trigger after merge
+### Version Mismatch Error
 
-1. Check if version in `package.json` is greater than latest tag:
+If you see a version mismatch error in GitHub Actions:
+
+1. **Delete the incorrect tag:**
    ```bash
-   git tag -l 'v*' --sort=-version:refname | head -1
-   cat apps/frontend/package.json | grep version
+   git tag -d v2.5.6                    # Delete locally
+   git push origin :refs/tags/v2.5.6    # Delete remotely
    ```
 
-2. Ensure the merge commit touched `package.json`:
+2. **Use the automated script:**
    ```bash
-   git diff HEAD~1 --name-only | grep package.json
+   node scripts/bump-version.js 2.5.6
+   git push origin main
+   git push origin v2.5.6
    ```
 
-### Release blocked: Missing changelog entry
+### Git Working Directory Not Clean
 
-If you see "CHANGELOG VALIDATION FAILED" in the workflow:
-
-1. The `prepare-release.yml` workflow validated that `CHANGELOG.md` doesn't have an entry for the new version
-2. **Fix**: Add an entry to `CHANGELOG.md` with the format `## X.Y.Z - Title`
-3. Commit and push the changelog update
-4. The workflow will automatically retry when the changes are pushed to `main`
+If the version bump script fails with "Git working directory is not clean":
 
 ```bash
-# Add changelog entry, then:
-git add CHANGELOG.md
-git commit -m "docs: add changelog for vX.Y.Z"
-git push origin main
+# Commit or stash your changes first
+git status
+git add .
+git commit -m "your changes"
+
+# Then run the version bump script
+node scripts/bump-version.js patch
 ```
 
-### Build failed after tag was created
+## Release Checklist
 
-- The release won't be published if builds fail
-- Fix the issue and create a new patch version
-- Don't reuse failed version numbers
+Use this checklist when creating a new release:
 
-### README shows wrong version
+- [ ] All tests passing on main branch
+- [ ] CHANGELOG updated (if applicable)
+- [ ] Run `node scripts/bump-version.js <type>`
+- [ ] Review commit and tag
+- [ ] Push commit and tag to GitHub
+- [ ] Create GitHub Release with release notes
+- [ ] Verify version validation passed
+- [ ] Verify builds completed successfully
+- [ ] Test the updater shows correct version
 
-- README is only updated after successful release
-- If release failed, README keeps the previous version (this is intentional)
-- Once you successfully release, README will update automatically
+## What Gets Released
 
-## Manual Release (Emergency Only)
+When you create a release, the following are built and published:
 
-In rare cases where you need to bypass the automated flow:
+1. **Native module prebuilds** - Windows node-pty binaries
+2. **Electron app packages** - Desktop installers (triggered manually or via electron-builder)
+3. **Discord notification** - Sent to the Auto Claude community
 
-```bash
-# Create tag manually (NOT RECOMMENDED)
-git tag -a v2.8.0 -m "Release v2.8.0"
-git push origin v2.8.0
+## Version Numbering
 
-# This will trigger release.yml directly
-```
+We follow [Semantic Versioning (SemVer)](https://semver.org/):
 
-**Warning:** Only do this if you're certain the version in package.json matches the tag.
+- **MAJOR** version (X.0.0) - Breaking changes
+- **MINOR** version (0.X.0) - New features (backward compatible)
+- **PATCH** version (0.0.X) - Bug fixes (backward compatible)
 
-## Security
-
-- All macOS binaries are code signed with Apple Developer certificate
-- All macOS binaries are notarized by Apple
-- Windows binaries are code signed
-- All binaries are scanned with VirusTotal
-- SHA256 checksums are generated for all artifacts
+Examples:
+- `2.5.5 -> 2.5.6` - Bug fix
+- `2.5.6 -> 2.6.0` - New feature
+- `2.6.0 -> 3.0.0` - Breaking change

apps/backend/README.md

@@ -1,120 +0,0 @@
-# Auto Claude Backend
-
-Autonomous coding framework powered by Claude AI. Builds software features through coordinated multi-agent sessions.
-
-## Getting Started
-
-### 1. Install
-
-```bash
-cd apps/backend
-python -m pip install -r requirements.txt
-```
-
-### 2. Configure
-
-```bash
-cp .env.example .env
-```
-
-Set your Claude API token in `.env`:
-```
-CLAUDE_CODE_OAUTH_TOKEN=your-token-here
-```
-
-Get your token by running: `claude setup-token`
-
-### 3. Run
-
-```bash
-# List available specs
-python run.py --list
-
-# Run a spec
-python run.py --spec 001
-```
-
-## Requirements
-
-- Python 3.10+
-- Claude API token
-
-## Commands
-
-| Command | Description |
-|---------|-------------|
-| `--list` | List all specs |
-| `--spec 001` | Run spec 001 |
-| `--spec 001 --isolated` | Run in isolated workspace |
-| `--spec 001 --direct` | Run directly in repo |
-| `--spec 001 --merge` | Merge completed build |
-| `--spec 001 --review` | Review build changes |
-| `--spec 001 --discard` | Discard build |
-| `--spec 001 --qa` | Run QA validation |
-| `--list-worktrees` | List all worktrees |
-| `--help` | Show all options |
-
-## Configuration
-
-Optional `.env` settings:
-
-| Variable | Description |
-|----------|-------------|
-| `AUTO_BUILD_MODEL` | Override Claude model |
-| `DEBUG=true` | Enable debug logging |
-| `LINEAR_API_KEY` | Enable Linear integration |
-| `GRAPHITI_ENABLED=true` | Enable memory system |
-
-## Troubleshooting
-
-**"tree-sitter not available"** - Safe to ignore, uses regex fallback.
-
-**Missing module errors** - Run `python -m pip install -r requirements.txt`
-
-**Debug mode** - Set `DEBUG=true DEBUG_LEVEL=2` before running.
-
----
-
-## For Developers
-
-### Project Structure
-
-```
-backend/
-├── agents/          # AI agent execution
-├── analysis/        # Code analysis
-├── cli/             # Command-line interface
-├── core/            # Core utilities
-├── integrations/    # External services (Linear, Graphiti)
-├── merge/           # Git merge handling
-├── project/         # Project detection
-├── prompts/         # Prompt templates
-├── qa/              # QA validation
-├── spec/            # Spec management
-└── ui/              # Terminal UI
-```
-
-### Design Principles
-
-- **SOLID** - Single responsibility, clean interfaces
-- **DRY** - Shared utilities in `core/`
-- **KISS** - Simple flat imports via facade modules
-
-### Import Convention
-
-```python
-# Use facade modules for clean imports
-from debug import debug, debug_error
-from progress import count_subtasks
-from workspace import setup_workspace
-```
-
-### Adding Features
-
-1. Create module in appropriate folder
-2. Export API in `__init__.py`
-3. Add facade module at root if commonly imported
-
-## License
-
-AGPL-3.0

apps/backend/__init__.py

@@ -1,23 +0,0 @@
-"""
-Auto Claude Backend - Autonomous Coding Framework
-==================================================
-
-Multi-agent autonomous coding framework that builds software through
-coordinated AI agent sessions.
-
-This package provides:
-- Autonomous agent execution for building features from specs
-- Workspace isolation via git worktrees
-- QA validation loops
-- Memory management (Graphiti + file-based)
-- Linear integration for project management
-
-Quick Start:
-    python run.py --spec 001    # Run a spec
-    python run.py --list        # List all specs
-
-See README.md for full documentation.
-"""
-
-__version__ = "2.7.4"
-__author__ = "Auto Claude Team"

apps/backend/agents/__init__.py

@@ -1,96 +0,0 @@
-"""
-Agents Module
-=============
-
-Modular agent system for autonomous coding.
-
-This module provides:
-- run_autonomous_agent: Main coder agent loop
-- run_followup_planner: Follow-up planner for completed specs
-- Memory management (Graphiti + file-based fallback)
-- Session management and post-processing
-- Utility functions for git and plan management
-
-Uses lazy imports to avoid circular dependencies.
-"""
-
-# Explicit import required by CodeQL static analysis
-# (CodeQL doesn't recognize __getattr__ dynamic exports)
-from .utils import sync_spec_to_source
-
-__all__ = [
-    # Main API
-    "run_autonomous_agent",
-    "run_followup_planner",
-    # Memory
-    "debug_memory_system_status",
-    "get_graphiti_context",
-    "save_session_memory",
-    "save_session_to_graphiti",
-    # Session
-    "run_agent_session",
-    "post_session_processing",
-    # Utils
-    "get_latest_commit",
-    "get_commit_count",
-    "load_implementation_plan",
-    "find_subtask_in_plan",
-    "find_phase_for_subtask",
-    "sync_spec_to_source",
-    # Constants
-    "AUTO_CONTINUE_DELAY_SECONDS",
-    "HUMAN_INTERVENTION_FILE",
-]
-
-
-def __getattr__(name):
-    """Lazy imports to avoid circular dependencies."""
-    if name in ("AUTO_CONTINUE_DELAY_SECONDS", "HUMAN_INTERVENTION_FILE"):
-        from .base import AUTO_CONTINUE_DELAY_SECONDS, HUMAN_INTERVENTION_FILE
-
-        return locals()[name]
-    elif name == "run_autonomous_agent":
-        from .coder import run_autonomous_agent
-
-        return run_autonomous_agent
-    elif name in (
-        "debug_memory_system_status",
-        "get_graphiti_context",
-        "save_session_memory",
-        "save_session_to_graphiti",
-    ):
-        from .memory_manager import (
-            debug_memory_system_status,
-            get_graphiti_context,
-            save_session_memory,
-            save_session_to_graphiti,
-        )
-
-        return locals()[name]
-    elif name == "run_followup_planner":
-        from .planner import run_followup_planner
-
-        return run_followup_planner
-    elif name in ("post_session_processing", "run_agent_session"):
-        from .session import post_session_processing, run_agent_session
-
-        return locals()[name]
-    elif name in (
-        "find_phase_for_subtask",
-        "find_subtask_in_plan",
-        "get_commit_count",
-        "get_latest_commit",
-        "load_implementation_plan",
-        "sync_spec_to_source",
-    ):
-        from .utils import (
-            find_phase_for_subtask,
-            find_subtask_in_plan,
-            get_commit_count,
-            get_latest_commit,
-            load_implementation_plan,
-            sync_spec_to_source,
-        )
-
-        return locals()[name]
-    raise AttributeError(f"module 'agents' has no attribute '{name}'")

apps/backend/agents/tools_pkg/models.py

@@ -1,510 +0,0 @@
-"""
-Tool Models and Constants
-==========================
-
-Defines tool name constants and configuration for auto-claude MCP tools.
-
-This module is the single source of truth for all tool definitions used by
-the Claude Agent SDK client. Tool lists are organized by category:
-
-- Base tools: Core file operations (Read, Write, Edit, etc.)
-- Web tools: Documentation and research (WebFetch, WebSearch)
-- MCP tools: External integrations (Context7, Linear, Graphiti, etc.)
-- Auto-Claude tools: Custom build management tools
-"""
-
-import os
-
-# =============================================================================
-# Base Tools (Built-in Claude Code tools)
-# =============================================================================
-
-# Core file operation tools
-BASE_READ_TOOLS = ["Read", "Glob", "Grep"]
-BASE_WRITE_TOOLS = ["Write", "Edit", "Bash"]
-
-# Web tools for documentation lookup and research
-# Always available to all agents for accessing external information
-WEB_TOOLS = ["WebFetch", "WebSearch"]
-
-# =============================================================================
-# Auto-Claude MCP Tools (Custom build management)
-# =============================================================================
-
-# Auto-Claude MCP tool names (prefixed with mcp__auto-claude__)
-TOOL_UPDATE_SUBTASK_STATUS = "mcp__auto-claude__update_subtask_status"
-TOOL_GET_BUILD_PROGRESS = "mcp__auto-claude__get_build_progress"
-TOOL_RECORD_DISCOVERY = "mcp__auto-claude__record_discovery"
-TOOL_RECORD_GOTCHA = "mcp__auto-claude__record_gotcha"
-TOOL_GET_SESSION_CONTEXT = "mcp__auto-claude__get_session_context"
-TOOL_UPDATE_QA_STATUS = "mcp__auto-claude__update_qa_status"
-
-# =============================================================================
-# External MCP Tools
-# =============================================================================
-
-# Context7 MCP tools for documentation lookup (always enabled)
-CONTEXT7_TOOLS = [
-    "mcp__context7__resolve-library-id",
-    "mcp__context7__get-library-docs",
-]
-
-# Linear MCP tools for project management (when LINEAR_API_KEY is set)
-LINEAR_TOOLS = [
-    "mcp__linear-server__list_teams",
-    "mcp__linear-server__get_team",
-    "mcp__linear-server__list_projects",
-    "mcp__linear-server__get_project",
-    "mcp__linear-server__create_project",
-    "mcp__linear-server__update_project",
-    "mcp__linear-server__list_issues",
-    "mcp__linear-server__get_issue",
-    "mcp__linear-server__create_issue",
-    "mcp__linear-server__update_issue",
-    "mcp__linear-server__list_comments",
-    "mcp__linear-server__create_comment",
-    "mcp__linear-server__list_issue_statuses",
-    "mcp__linear-server__list_issue_labels",
-    "mcp__linear-server__list_users",
-    "mcp__linear-server__get_user",
-]
-
-# Graphiti MCP tools for knowledge graph memory (when GRAPHITI_MCP_URL is set)
-# See: https://github.com/getzep/graphiti
-GRAPHITI_MCP_TOOLS = [
-    "mcp__graphiti-memory__search_nodes",  # Search entity summaries
-    "mcp__graphiti-memory__search_facts",  # Search relationships between entities
-    "mcp__graphiti-memory__add_episode",  # Add data to knowledge graph
-    "mcp__graphiti-memory__get_episodes",  # Retrieve recent episodes
-    "mcp__graphiti-memory__get_entity_edge",  # Get specific entity/relationship
-]
-
-# =============================================================================
-# Browser Automation MCP Tools (QA agents only)
-# =============================================================================
-
-# Puppeteer MCP tools for web browser automation
-# Used for web frontend validation (non-Electron web apps)
-# NOTE: Screenshots must be compressed (1280x720, quality 60, JPEG) to stay under
-# Claude SDK's 1MB JSON message buffer limit. See GitHub issue #74.
-PUPPETEER_TOOLS = [
-    "mcp__puppeteer__puppeteer_connect_active_tab",
-    "mcp__puppeteer__puppeteer_navigate",
-    "mcp__puppeteer__puppeteer_screenshot",
-    "mcp__puppeteer__puppeteer_click",
-    "mcp__puppeteer__puppeteer_fill",
-    "mcp__puppeteer__puppeteer_select",
-    "mcp__puppeteer__puppeteer_hover",
-    "mcp__puppeteer__puppeteer_evaluate",
-]
-
-# Electron MCP tools for desktop app automation (when ELECTRON_MCP_ENABLED is set)
-# Uses electron-mcp-server to connect to Electron apps via Chrome DevTools Protocol.
-# Electron app must be started with --remote-debugging-port=9222 (or ELECTRON_DEBUG_PORT).
-# These tools are only available to QA agents (qa_reviewer, qa_fixer), not Coder/Planner.
-# NOTE: Screenshots must be compressed to stay under Claude SDK's 1MB JSON message buffer limit.
-ELECTRON_TOOLS = [
-    "mcp__electron__get_electron_window_info",  # Get info about running Electron windows
-    "mcp__electron__take_screenshot",  # Capture screenshot of Electron window
-    "mcp__electron__send_command_to_electron",  # Send commands (click, fill, evaluate JS)
-    "mcp__electron__read_electron_logs",  # Read console logs from Electron app
-]
-
-# =============================================================================
-# Configuration
-# =============================================================================
-
-
-def is_electron_mcp_enabled() -> bool:
-    """
-    Check if Electron MCP server integration is enabled.
-
-    Requires ELECTRON_MCP_ENABLED to be set to 'true'.
-    When enabled, QA agents can use Electron MCP tools to connect to Electron apps
-    via Chrome DevTools Protocol on the configured debug port.
-    """
-    return os.environ.get("ELECTRON_MCP_ENABLED", "").lower() == "true"
-
-
-# =============================================================================
-# Agent Configuration Registry
-# =============================================================================
-# Single source of truth for phase → tools → MCP servers mapping.
-# This enables phase-aware tool control and context window optimization.
-
-AGENT_CONFIGS = {
-    # ═══════════════════════════════════════════════════════════════════════
-    # SPEC CREATION PHASES (Minimal tools, fast startup)
-    # ═══════════════════════════════════════════════════════════════════════
-    "spec_gatherer": {
-        "tools": BASE_READ_TOOLS + WEB_TOOLS,
-        "mcp_servers": [],  # No MCP needed - just reads project
-        "auto_claude_tools": [],
-        "thinking_default": "medium",
-    },
-    "spec_researcher": {
-        "tools": BASE_READ_TOOLS + WEB_TOOLS,
-        "mcp_servers": ["context7"],  # Needs docs lookup
-        "auto_claude_tools": [],
-        "thinking_default": "medium",
-    },
-    "spec_writer": {
-        "tools": BASE_READ_TOOLS + BASE_WRITE_TOOLS,
-        "mcp_servers": [],  # Just writes spec.md
-        "auto_claude_tools": [],
-        "thinking_default": "high",
-    },
-    "spec_critic": {
-        "tools": BASE_READ_TOOLS,
-        "mcp_servers": [],  # Self-critique, no external tools
-        "auto_claude_tools": [],
-        "thinking_default": "ultrathink",
-    },
-    "spec_discovery": {
-        "tools": BASE_READ_TOOLS + WEB_TOOLS,
-        "mcp_servers": [],
-        "auto_claude_tools": [],
-        "thinking_default": "medium",
-    },
-    "spec_context": {
-        "tools": BASE_READ_TOOLS,
-        "mcp_servers": [],
-        "auto_claude_tools": [],
-        "thinking_default": "medium",
-    },
-    "spec_validation": {
-        "tools": BASE_READ_TOOLS,
-        "mcp_servers": [],
-        "auto_claude_tools": [],
-        "thinking_default": "high",
-    },
-    "spec_compaction": {
-        "tools": BASE_READ_TOOLS + BASE_WRITE_TOOLS,
-        "mcp_servers": [],
-        "auto_claude_tools": [],
-        "thinking_default": "medium",
-    },
-    # ═══════════════════════════════════════════════════════════════════════
-    # BUILD PHASES (Full tools + Graphiti memory)
-    # Note: "linear" is conditional on project setting "update_linear_with_tasks"
-    # ═══════════════════════════════════════════════════════════════════════
-    "planner": {
-        "tools": BASE_READ_TOOLS + BASE_WRITE_TOOLS + WEB_TOOLS,
-        "mcp_servers": ["context7", "graphiti", "auto-claude"],
-        "mcp_servers_optional": ["linear"],  # Only if project setting enabled
-        "auto_claude_tools": [
-            TOOL_GET_BUILD_PROGRESS,
-            TOOL_GET_SESSION_CONTEXT,
-            TOOL_RECORD_DISCOVERY,
-        ],
-        "thinking_default": "high",
-    },
-    "coder": {
-        "tools": BASE_READ_TOOLS + BASE_WRITE_TOOLS + WEB_TOOLS,
-        "mcp_servers": ["context7", "graphiti", "auto-claude"],
-        "mcp_servers_optional": ["linear"],
-        "auto_claude_tools": [
-            TOOL_UPDATE_SUBTASK_STATUS,
-            TOOL_GET_BUILD_PROGRESS,
-            TOOL_RECORD_DISCOVERY,
-            TOOL_RECORD_GOTCHA,
-            TOOL_GET_SESSION_CONTEXT,
-        ],
-        "thinking_default": "none",  # Coding doesn't use extended thinking
-    },
-    # ═══════════════════════════════════════════════════════════════════════
-    # QA PHASES (Read + test + browser + Graphiti memory)
-    # ═══════════════════════════════════════════════════════════════════════
-    "qa_reviewer": {
-        # Read + Write/Edit (for QA reports and plan updates) + Bash (for tests)
-        # Note: Reviewer writes to spec directory only (qa_report.md, implementation_plan.json)
-        "tools": BASE_READ_TOOLS + BASE_WRITE_TOOLS + WEB_TOOLS,
-        "mcp_servers": ["context7", "graphiti", "auto-claude", "browser"],
-        "mcp_servers_optional": ["linear"],  # For updating issue status
-        "auto_claude_tools": [
-            TOOL_GET_BUILD_PROGRESS,
-            TOOL_UPDATE_QA_STATUS,
-            TOOL_GET_SESSION_CONTEXT,
-        ],
-        "thinking_default": "high",
-    },
-    "qa_fixer": {
-        "tools": BASE_READ_TOOLS + BASE_WRITE_TOOLS + WEB_TOOLS,
-        "mcp_servers": ["context7", "graphiti", "auto-claude", "browser"],
-        "mcp_servers_optional": ["linear"],
-        "auto_claude_tools": [
-            TOOL_UPDATE_SUBTASK_STATUS,
-            TOOL_GET_BUILD_PROGRESS,
-            TOOL_UPDATE_QA_STATUS,
-            TOOL_RECORD_GOTCHA,
-        ],
-        "thinking_default": "medium",
-    },
-    # ═══════════════════════════════════════════════════════════════════════
-    # UTILITY PHASES (Minimal, no MCP)
-    # ═══════════════════════════════════════════════════════════════════════
-    "insights": {
-        "tools": BASE_READ_TOOLS + WEB_TOOLS,
-        "mcp_servers": [],
-        "auto_claude_tools": [],
-        "thinking_default": "medium",
-    },
-    "merge_resolver": {
-        "tools": [],  # Text-only analysis
-        "mcp_servers": [],
-        "auto_claude_tools": [],
-        "thinking_default": "low",
-    },
-    "commit_message": {
-        "tools": [],
-        "mcp_servers": [],
-        "auto_claude_tools": [],
-        "thinking_default": "low",
-    },
-    "pr_reviewer": {
-        "tools": BASE_READ_TOOLS + WEB_TOOLS,  # Read-only
-        "mcp_servers": ["context7"],
-        "auto_claude_tools": [],
-        "thinking_default": "high",
-    },
-    "pr_orchestrator_parallel": {
-        "tools": BASE_READ_TOOLS + WEB_TOOLS,  # Read-only for parallel PR orchestrator
-        "mcp_servers": ["context7"],
-        "auto_claude_tools": [],
-        "thinking_default": "high",
-    },
-    "pr_followup_parallel": {
-        "tools": BASE_READ_TOOLS
-        + WEB_TOOLS,  # Read-only for parallel followup reviewer
-        "mcp_servers": ["context7"],
-        "auto_claude_tools": [],
-        "thinking_default": "high",
-    },
-    # ═══════════════════════════════════════════════════════════════════════
-    # ANALYSIS PHASES
-    # ═══════════════════════════════════════════════════════════════════════
-    "analysis": {
-        "tools": BASE_READ_TOOLS + WEB_TOOLS,
-        "mcp_servers": ["context7"],
-        "auto_claude_tools": [],
-        "thinking_default": "medium",
-    },
-    "batch_analysis": {
-        "tools": BASE_READ_TOOLS + WEB_TOOLS,
-        "mcp_servers": [],
-        "auto_claude_tools": [],
-        "thinking_default": "low",
-    },
-    "batch_validation": {
-        "tools": BASE_READ_TOOLS,
-        "mcp_servers": [],
-        "auto_claude_tools": [],
-        "thinking_default": "low",
-    },
-    # ═══════════════════════════════════════════════════════════════════════
-    # ROADMAP & IDEATION
-    # ═══════════════════════════════════════════════════════════════════════
-    "roadmap_discovery": {
-        "tools": BASE_READ_TOOLS + WEB_TOOLS,
-        "mcp_servers": ["context7"],
-        "auto_claude_tools": [],
-        "thinking_default": "high",
-    },
-    "competitor_analysis": {
-        "tools": BASE_READ_TOOLS + WEB_TOOLS,
-        "mcp_servers": ["context7"],  # WebSearch for competitor research
-        "auto_claude_tools": [],
-        "thinking_default": "high",
-    },
-    "ideation": {
-        "tools": BASE_READ_TOOLS + WEB_TOOLS,
-        "mcp_servers": [],
-        "auto_claude_tools": [],
-        "thinking_default": "high",
-    },
-}
-
-
-# =============================================================================
-# Agent Config Helper Functions
-# =============================================================================
-
-
-def get_agent_config(agent_type: str) -> dict:
-    """
-    Get full configuration for an agent type.
-
-    Args:
-        agent_type: The agent type identifier (e.g., 'coder', 'planner', 'qa_reviewer')
-
-    Returns:
-        Configuration dict containing tools, mcp_servers, auto_claude_tools, thinking_default
-
-    Raises:
-        ValueError: If agent_type is not found in AGENT_CONFIGS (strict mode)
-    """
-    if agent_type not in AGENT_CONFIGS:
-        raise ValueError(
-            f"Unknown agent type: '{agent_type}'. "
-            f"Valid types: {sorted(AGENT_CONFIGS.keys())}"
-        )
-    return AGENT_CONFIGS[agent_type]
-
-
-def _map_mcp_server_name(
-    name: str, custom_server_ids: list[str] | None = None
-) -> str | None:
-    """
-    Map user-friendly MCP server names to internal identifiers.
-    Also accepts custom server IDs directly.
-
-    Args:
-        name: User-provided MCP server name
-        custom_server_ids: List of custom server IDs to accept as-is
-
-    Returns:
-        Internal server identifier or None if not recognized
-    """
-    if not name:
-        return None
-    mappings = {
-        "context7": "context7",
-        "graphiti-memory": "graphiti",
-        "graphiti": "graphiti",
-        "linear": "linear",
-        "electron": "electron",
-        "puppeteer": "puppeteer",
-        "auto-claude": "auto-claude",
-    }
-    # Check if it's a known mapping
-    mapped = mappings.get(name.lower().strip())
-    if mapped:
-        return mapped
-    # Check if it's a custom server ID (accept as-is)
-    if custom_server_ids and name in custom_server_ids:
-        return name
-    return None
-
-
-def get_required_mcp_servers(
-    agent_type: str,
-    project_capabilities: dict | None = None,
-    linear_enabled: bool = False,
-    mcp_config: dict | None = None,
-) -> list[str]:
-    """
-    Get MCP servers required for this agent type.
-
-    Handles dynamic server selection:
-    - "browser" → electron (if is_electron) or puppeteer (if is_web_frontend)
-    - "linear" → only if in mcp_servers_optional AND linear_enabled is True
-    - "graphiti" → only if GRAPHITI_MCP_URL is set
-    - Respects per-project MCP config overrides from .auto-claude/.env
-    - Applies per-agent ADD/REMOVE overrides from AGENT_MCP_<agent>_ADD/REMOVE
-
-    Args:
-        agent_type: The agent type identifier
-        project_capabilities: Dict from detect_project_capabilities() or None
-        linear_enabled: Whether Linear integration is enabled for this project
-        mcp_config: Per-project MCP server toggles from .auto-claude/.env
-                   Keys: CONTEXT7_ENABLED, LINEAR_MCP_ENABLED, ELECTRON_MCP_ENABLED,
-                         PUPPETEER_MCP_ENABLED, AGENT_MCP_<agent>_ADD/REMOVE
-
-    Returns:
-        List of MCP server names to start
-    """
-    config = get_agent_config(agent_type)
-    servers = list(config.get("mcp_servers", []))
-
-    # Load per-project config (or use defaults)
-    if mcp_config is None:
-        mcp_config = {}
-
-    # Filter context7 if explicitly disabled by project config
-    if "context7" in servers:
-        context7_enabled = mcp_config.get("CONTEXT7_ENABLED", "true")
-        if str(context7_enabled).lower() == "false":
-            servers = [s for s in servers if s != "context7"]
-
-    # Handle optional servers (e.g., Linear if project setting enabled)
-    optional = config.get("mcp_servers_optional", [])
-    if "linear" in optional and linear_enabled:
-        # Also check per-project LINEAR_MCP_ENABLED override
-        linear_mcp_enabled = mcp_config.get("LINEAR_MCP_ENABLED", "true")
-        if str(linear_mcp_enabled).lower() != "false":
-            servers.append("linear")
-
-    # Handle dynamic "browser" → electron/puppeteer based on project type and config
-    if "browser" in servers:
-        servers = [s for s in servers if s != "browser"]
-        if project_capabilities:
-            is_electron = project_capabilities.get("is_electron", False)
-            is_web_frontend = project_capabilities.get("is_web_frontend", False)
-
-            # Check per-project overrides (default false for both)
-            electron_enabled = mcp_config.get("ELECTRON_MCP_ENABLED", "false")
-            puppeteer_enabled = mcp_config.get("PUPPETEER_MCP_ENABLED", "false")
-
-            # Electron: enabled by project config OR global env var
-            if is_electron and (
-                str(electron_enabled).lower() == "true" or is_electron_mcp_enabled()
-            ):
-                servers.append("electron")
-            # Puppeteer: enabled by project config (no global env var)
-            elif is_web_frontend and not is_electron:
-                if str(puppeteer_enabled).lower() == "true":
-                    servers.append("puppeteer")
-
-    # Filter graphiti if not enabled
-    if "graphiti" in servers:
-        if not os.environ.get("GRAPHITI_MCP_URL"):
-            servers = [s for s in servers if s != "graphiti"]
-
-    # ========== Apply per-agent MCP overrides ==========
-    # Format: AGENT_MCP_<agent_type>_ADD=server1,server2
-    #         AGENT_MCP_<agent_type>_REMOVE=server1,server2
-    add_key = f"AGENT_MCP_{agent_type}_ADD"
-    remove_key = f"AGENT_MCP_{agent_type}_REMOVE"
-
-    # Extract custom server IDs for mapping (allows custom servers to be recognized)
-    custom_servers = mcp_config.get("CUSTOM_MCP_SERVERS", [])
-    custom_server_ids = [s.get("id") for s in custom_servers if s.get("id")]
-
-    # Process additions
-    if add_key in mcp_config:
-        additions = [
-            s.strip() for s in str(mcp_config[add_key]).split(",") if s.strip()
-        ]
-        for server in additions:
-            mapped = _map_mcp_server_name(server, custom_server_ids)
-            if mapped and mapped not in servers:
-                servers.append(mapped)
-
-    # Process removals (but never remove auto-claude)
-    if remove_key in mcp_config:
-        removals = [
-            s.strip() for s in str(mcp_config[remove_key]).split(",") if s.strip()
-        ]
-        for server in removals:
-            mapped = _map_mcp_server_name(server, custom_server_ids)
-            if mapped and mapped != "auto-claude":  # auto-claude cannot be removed
-                servers = [s for s in servers if s != mapped]
-
-    return servers
-
-
-def get_default_thinking_level(agent_type: str) -> str:
-    """
-    Get default thinking level string for agent type.
-
-    This returns the thinking level name (e.g., 'medium', 'high'), not the token budget.
-    To convert to tokens, use phase_config.get_thinking_budget(level).
-
-    Args:
-        agent_type: The agent type identifier
-
-    Returns:
-        Thinking level string (none, low, medium, high, ultrathink)
-    """
-    config = get_agent_config(agent_type)
-    return config.get("thinking_default", "medium")

apps/backend/agents/tools_pkg/permissions.py

@@ -1,120 +0,0 @@
-"""
-Agent Tool Permissions
-======================
-
-Manages which tools are allowed for each agent type to prevent context
-pollution and accidental misuse.
-
-Supports dynamic tool filtering based on project capabilities to optimize
-context window usage. For example, Electron tools are only included for
-Electron projects, not for Next.js or CLI projects.
-
-This module now uses AGENT_CONFIGS from models.py as the single source of truth
-for tool permissions. The get_allowed_tools() function remains the primary API
-for backwards compatibility.
-"""
-
-from .models import (
-    AGENT_CONFIGS,
-    CONTEXT7_TOOLS,
-    ELECTRON_TOOLS,
-    GRAPHITI_MCP_TOOLS,
-    LINEAR_TOOLS,
-    PUPPETEER_TOOLS,
-    get_agent_config,
-    get_required_mcp_servers,
-)
-from .registry import is_tools_available
-
-
-def get_allowed_tools(
-    agent_type: str,
-    project_capabilities: dict | None = None,
-    linear_enabled: bool = False,
-    mcp_config: dict | None = None,
-) -> list[str]:
-    """
-    Get the list of allowed tools for a specific agent type.
-
-    This ensures each agent only sees tools relevant to their role,
-    preventing context pollution and accidental misuse.
-
-    Uses AGENT_CONFIGS as the single source of truth for tool permissions.
-    Dynamic MCP tools are added based on project capabilities and required servers.
-
-    Args:
-        agent_type: Agent type identifier (e.g., 'coder', 'planner', 'qa_reviewer')
-        project_capabilities: Optional dict from detect_project_capabilities()
-                            containing flags like is_electron, is_web_frontend, etc.
-        linear_enabled: Whether Linear integration is enabled for this project
-        mcp_config: Per-project MCP server toggles from .auto-claude/.env
-
-    Returns:
-        List of allowed tool names
-
-    Raises:
-        ValueError: If agent_type is not found in AGENT_CONFIGS
-    """
-    # Get agent configuration (raises ValueError if unknown type)
-    config = get_agent_config(agent_type)
-
-    # Start with base tools from config
-    tools = list(config.get("tools", []))
-
-    # Get required MCP servers for this agent
-    required_servers = get_required_mcp_servers(
-        agent_type,
-        project_capabilities,
-        linear_enabled,
-        mcp_config,
-    )
-
-    # Add auto-claude tools ONLY if the MCP server is available
-    # This prevents allowing tools that won't work because the server isn't running
-    if "auto-claude" in required_servers and is_tools_available():
-        tools.extend(config.get("auto_claude_tools", []))
-
-    # Add MCP tool names based on required servers
-    tools.extend(_get_mcp_tools_for_servers(required_servers))
-
-    return tools
-
-
-def _get_mcp_tools_for_servers(servers: list[str]) -> list[str]:
-    """
-    Get the list of MCP tools for a list of required servers.
-
-    Maps server names to their corresponding tool lists.
-
-    Args:
-        servers: List of MCP server names (e.g., ['context7', 'linear', 'electron'])
-
-    Returns:
-        List of MCP tool names for all specified servers
-    """
-    tools = []
-
-    for server in servers:
-        if server == "context7":
-            tools.extend(CONTEXT7_TOOLS)
-        elif server == "linear":
-            tools.extend(LINEAR_TOOLS)
-        elif server == "graphiti":
-            tools.extend(GRAPHITI_MCP_TOOLS)
-        elif server == "electron":
-            tools.extend(ELECTRON_TOOLS)
-        elif server == "puppeteer":
-            tools.extend(PUPPETEER_TOOLS)
-        # auto-claude tools are already added via config["auto_claude_tools"]
-
-    return tools
-
-
-def get_all_agent_types() -> list[str]:
-    """
-    Get all registered agent types.
-
-    Returns:
-        Sorted list of all agent type identifiers
-    """
-    return sorted(AGENT_CONFIGS.keys())

apps/backend/agents/utils.py

@@ -1,181 +0,0 @@
-"""
-Utility Functions for Agent System
-===================================
-
-Helper functions for git operations, plan management, and file syncing.
-"""
-
-import json
-import logging
-import shutil
-from pathlib import Path
-
-from core.git_executable import run_git
-
-logger = logging.getLogger(__name__)
-
-
-def get_latest_commit(project_dir: Path) -> str | None:
-    """Get the hash of the latest git commit."""
-    result = run_git(
-        ["rev-parse", "HEAD"],
-        cwd=project_dir,
-        timeout=10,
-    )
-    if result.returncode == 0:
-        return result.stdout.strip()
-    return None
-
-
-def get_commit_count(project_dir: Path) -> int:
-    """Get the total number of commits."""
-    result = run_git(
-        ["rev-list", "--count", "HEAD"],
-        cwd=project_dir,
-        timeout=10,
-    )
-    if result.returncode == 0:
-        try:
-            return int(result.stdout.strip())
-        except ValueError:
-            return 0
-    return 0
-
-
-def load_implementation_plan(spec_dir: Path) -> dict | None:
-    """Load the implementation plan JSON."""
-    plan_file = spec_dir / "implementation_plan.json"
-    if not plan_file.exists():
-        return None
-    try:
-        with open(plan_file) as f:
-            return json.load(f)
-    except (OSError, json.JSONDecodeError):
-        return None
-
-
-def find_subtask_in_plan(plan: dict, subtask_id: str) -> dict | None:
-    """Find a subtask by ID in the plan."""
-    for phase in plan.get("phases", []):
-        for subtask in phase.get("subtasks", []):
-            if subtask.get("id") == subtask_id:
-                return subtask
-    return None
-
-
-def find_phase_for_subtask(plan: dict, subtask_id: str) -> dict | None:
-    """Find the phase containing a subtask."""
-    for phase in plan.get("phases", []):
-        for subtask in phase.get("subtasks", []):
-            if subtask.get("id") == subtask_id:
-                return phase
-    return None
-
-
-def sync_spec_to_source(spec_dir: Path, source_spec_dir: Path | None) -> bool:
-    """
-    Sync ALL spec files from worktree back to source spec directory.
-
-    When running in isolated mode (worktrees), the agent creates and updates
-    many files inside the worktree's spec directory. This function syncs ALL
-    of them back to the main project's spec directory.
-
-    IMPORTANT: Since .auto-claude/ is gitignored, this sync happens to the
-    local filesystem regardless of what branch the user is on. The worktree
-    may be on a different branch (e.g., auto-claude/093-task), but the sync
-    target is always the main project's .auto-claude/specs/ directory.
-
-    Files synced (all files in spec directory):
-    - implementation_plan.json - Task status and subtask completion
-    - build-progress.txt - Session-by-session progress notes
-    - task_logs.json - Execution logs
-    - review_state.json - QA review state
-    - critique_report.json - Spec critique findings
-    - suggested_commit_message.txt - Commit suggestions
-    - REGRESSION_TEST_REPORT.md - Test regression report
-    - spec.md, context.json, etc. - Original spec files (for completeness)
-    - memory/ directory - Codebase map, patterns, gotchas, session insights
-
-    Args:
-        spec_dir: Current spec directory (inside worktree)
-        source_spec_dir: Original spec directory in main project (outside worktree)
-
-    Returns:
-        True if sync was performed, False if not needed or failed
-    """
-    # Skip if no source specified or same path (not in worktree mode)
-    if not source_spec_dir:
-        return False
-
-    # Resolve paths and check if they're different
-    spec_dir_resolved = spec_dir.resolve()
-    source_spec_dir_resolved = source_spec_dir.resolve()
-
-    if spec_dir_resolved == source_spec_dir_resolved:
-        return False  # Same directory, no sync needed
-
-    synced_any = False
-
-    # Ensure source directory exists
-    source_spec_dir.mkdir(parents=True, exist_ok=True)
-
-    try:
-        # Sync all files and directories from worktree spec to source spec
-        for item in spec_dir.iterdir():
-            # Skip symlinks to prevent path traversal attacks
-            if item.is_symlink():
-                logger.warning(f"Skipping symlink during sync: {item.name}")
-                continue
-
-            source_item = source_spec_dir / item.name
-
-            if item.is_file():
-                # Copy file (preserves timestamps)
-                shutil.copy2(item, source_item)
-                logger.debug(f"Synced {item.name} to source")
-                synced_any = True
-
-            elif item.is_dir():
-                # Recursively sync directory
-                _sync_directory(item, source_item)
-                synced_any = True
-
-    except Exception as e:
-        logger.warning(f"Failed to sync spec directory to source: {e}")
-
-    return synced_any
-
-
-def _sync_directory(source_dir: Path, target_dir: Path) -> None:
-    """
-    Recursively sync a directory from source to target.
-
-    Args:
-        source_dir: Source directory (in worktree)
-        target_dir: Target directory (in main project)
-    """
-    # Create target directory if needed
-    target_dir.mkdir(parents=True, exist_ok=True)
-
-    for item in source_dir.iterdir():
-        # Skip symlinks to prevent path traversal attacks
-        if item.is_symlink():
-            logger.warning(
-                f"Skipping symlink during sync: {source_dir.name}/{item.name}"
-            )
-            continue
-
-        target_item = target_dir / item.name
-
-        if item.is_file():
-            shutil.copy2(item, target_item)
-            logger.debug(f"Synced {source_dir.name}/{item.name} to source")
-        elif item.is_dir():
-            # Recurse into subdirectories
-            _sync_directory(item, target_item)
-
-
-# Keep the old name as an alias for backward compatibility
-def sync_plan_to_source(spec_dir: Path, source_spec_dir: Path | None) -> bool:
-    """Alias for sync_spec_to_source for backward compatibility."""
-    return sync_spec_to_source(spec_dir, source_spec_dir)

apps/backend/analyzer.py

@@ -1,26 +0,0 @@
-#!/usr/bin/env python3
-"""
-Analyzer facade module.
-
-Provides backward compatibility for scripts that import from analyzer.py at the root.
-Actual implementation is in analysis/analyzer.py.
-"""
-
-from analysis.analyzer import (
-    ProjectAnalyzer,
-    ServiceAnalyzer,
-    analyze_project,
-    analyze_service,
-    main,
-)
-
-__all__ = [
-    "ServiceAnalyzer",
-    "ProjectAnalyzer",
-    "analyze_project",
-    "analyze_service",
-    "main",
-]
-
-if __name__ == "__main__":
-    main()

apps/backend/auto_claude_tools.py

@@ -1,36 +0,0 @@
-"""
-Auto Claude tools module facade.
-
-Provides MCP tools for agent operations.
-Re-exports from agents.tools_pkg for clean imports.
-"""
-
-from agents.tools_pkg.models import (  # noqa: F401
-    ELECTRON_TOOLS,
-    TOOL_GET_BUILD_PROGRESS,
-    TOOL_GET_SESSION_CONTEXT,
-    TOOL_RECORD_DISCOVERY,
-    TOOL_RECORD_GOTCHA,
-    TOOL_UPDATE_QA_STATUS,
-    TOOL_UPDATE_SUBTASK_STATUS,
-    is_electron_mcp_enabled,
-)
-from agents.tools_pkg.permissions import get_allowed_tools  # noqa: F401
-from agents.tools_pkg.registry import (  # noqa: F401
-    create_auto_claude_mcp_server,
-    is_tools_available,
-)
-
-__all__ = [
-    "create_auto_claude_mcp_server",
-    "get_allowed_tools",
-    "is_tools_available",
-    "TOOL_UPDATE_SUBTASK_STATUS",
-    "TOOL_GET_BUILD_PROGRESS",
-    "TOOL_RECORD_DISCOVERY",
-    "TOOL_RECORD_GOTCHA",
-    "TOOL_GET_SESSION_CONTEXT",
-    "TOOL_UPDATE_QA_STATUS",
-    "ELECTRON_TOOLS",
-    "is_electron_mcp_enabled",
-]

apps/backend/cli/batch_commands.py

@@ -1,266 +0,0 @@
-"""
-Batch Task Management Commands
-==============================
-
-Commands for creating and managing multiple tasks from batch files.
-"""
-
-import json
-import shutil
-import subprocess
-from pathlib import Path
-
-from ui import highlight, print_status
-
-
-def handle_batch_create_command(batch_file: str, project_dir: str) -> bool:
-    """
-    Create multiple tasks from a batch JSON file.
-
-    Args:
-        batch_file: Path to JSON file with task definitions
-        project_dir: Project directory
-
-    Returns:
-        True if successful
-    """
-    batch_path = Path(batch_file)
-
-    if not batch_path.exists():
-        print_status(f"Batch file not found: {batch_file}", "error")
-        return False
-
-    try:
-        with open(batch_path) as f:
-            batch_data = json.load(f)
-    except json.JSONDecodeError as e:
-        print_status(f"Invalid JSON in batch file: {e}", "error")
-        return False
-
-    tasks = batch_data.get("tasks", [])
-    if not tasks:
-        print_status("No tasks found in batch file", "warning")
-        return False
-
-    print_status(f"Creating {len(tasks)} tasks from batch file", "info")
-    print()
-
-    specs_dir = Path(project_dir) / ".auto-claude" / "specs"
-    specs_dir.mkdir(parents=True, exist_ok=True)
-
-    # Find next spec ID
-    existing_specs = [d.name for d in specs_dir.iterdir() if d.is_dir()]
-    next_id = (
-        max([int(s.split("-")[0]) for s in existing_specs if s[0].isdigit()] or [0]) + 1
-    )
-
-    created_specs = []
-
-    for idx, task in enumerate(tasks, 1):
-        spec_id = f"{next_id:03d}"
-        task_title = task.get("title", f"Task {idx}")
-        task_slug = task_title.lower().replace(" ", "-")[:50]
-        spec_name = f"{spec_id}-{task_slug}"
-        spec_dir = specs_dir / spec_name
-        spec_dir.mkdir(exist_ok=True)
-
-        # Create requirements.json
-        requirements = {
-            "task_description": task.get("description", task_title),
-            "description": task.get("description", task_title),
-            "workflow_type": task.get("workflow_type", "feature"),
-            "services_involved": task.get("services", ["frontend"]),
-            "priority": task.get("priority", 5),
-            "complexity_inferred": task.get("complexity", "standard"),
-            "inferred_from": {},
-            "created_at": Path(spec_dir).stat().st_mtime,
-            "estimate": {
-                "estimated_hours": task.get("estimated_hours", 4.0),
-                "estimated_days": task.get("estimated_days", 0.5),
-            },
-        }
-
-        req_file = spec_dir / "requirements.json"
-        with open(req_file, "w") as f:
-            json.dump(requirements, f, indent=2, default=str)
-
-        created_specs.append(
-            {
-                "id": spec_id,
-                "name": spec_name,
-                "title": task_title,
-                "status": "pending_spec_creation",
-            }
-        )
-
-        print_status(
-            f"[{idx}/{len(tasks)}] Created {spec_id} - {task_title}", "success"
-        )
-        next_id += 1
-
-    print()
-    print_status(f"Created {len(created_specs)} spec(s) successfully", "success")
-    print()
-
-    # Show summary
-    print(highlight("Next steps:"))
-    print("  1. Generate specs: spec_runner.py --continue <spec_id>")
-    print("  2. Approve specs and build them")
-    print("  3. Run: python run.py --spec <id> to execute")
-
-    return True
-
-
-def handle_batch_status_command(project_dir: str) -> bool:
-    """
-    Show status of all specs in project.
-
-    Args:
-        project_dir: Project directory
-
-    Returns:
-        True if successful
-    """
-    specs_dir = Path(project_dir) / ".auto-claude" / "specs"
-
-    if not specs_dir.exists():
-        print_status("No specs found in project", "warning")
-        return True
-
-    specs = sorted([d for d in specs_dir.iterdir() if d.is_dir()])
-
-    if not specs:
-        print_status("No specs found", "warning")
-        return True
-
-    print_status(f"Found {len(specs)} spec(s)", "info")
-    print()
-
-    for spec_dir in specs:
-        spec_name = spec_dir.name
-        req_file = spec_dir / "requirements.json"
-
-        status = "unknown"
-        title = spec_name
-
-        if req_file.exists():
-            try:
-                with open(req_file) as f:
-                    req = json.load(f)
-                    title = req.get("task_description", title)
-            except json.JSONDecodeError:
-                pass
-
-        # Determine status
-        if (spec_dir / "spec.md").exists():
-            status = "spec_created"
-        elif (spec_dir / "implementation_plan.json").exists():
-            status = "building"
-        elif (spec_dir / "qa_report.md").exists():
-            status = "qa_approved"
-        else:
-            status = "pending_spec"
-
-        status_icon = {
-            "pending_spec": "⏳",
-            "spec_created": "📋",
-            "building": "⚙️",
-            "qa_approved": "✅",
-            "unknown": "❓",
-        }.get(status, "❓")
-
-        print(f"{status_icon} {spec_name:<40} {title}")
-
-    return True
-
-
-def handle_batch_cleanup_command(project_dir: str, dry_run: bool = True) -> bool:
-    """
-    Clean up completed specs and worktrees.
-
-    Args:
-        project_dir: Project directory
-        dry_run: If True, show what would be deleted
-
-    Returns:
-        True if successful
-    """
-    specs_dir = Path(project_dir) / ".auto-claude" / "specs"
-    worktrees_dir = Path(project_dir) / ".auto-claude" / "worktrees" / "tasks"
-
-    if not specs_dir.exists():
-        print_status("No specs directory found", "info")
-        return True
-
-    # Find completed specs
-    completed = []
-    for spec_dir in specs_dir.iterdir():
-        if spec_dir.is_dir() and (spec_dir / "qa_report.md").exists():
-            completed.append(spec_dir.name)
-
-    if not completed:
-        print_status("No completed specs to clean up", "info")
-        return True
-
-    print_status(f"Found {len(completed)} completed spec(s)", "info")
-
-    if dry_run:
-        print()
-        print("Would remove:")
-        for spec_name in completed:
-            print(f"  - {spec_name}")
-            wt_path = worktrees_dir / spec_name
-            if wt_path.exists():
-                print(f"    └─ .auto-claude/worktrees/tasks/{spec_name}/")
-        print()
-        print("Run with --no-dry-run to actually delete")
-    else:
-        # Actually delete specs and worktrees
-        deleted_count = 0
-        for spec_name in completed:
-            spec_path = specs_dir / spec_name
-            wt_path = worktrees_dir / spec_name
-
-            # Remove worktree first (if exists)
-            if wt_path.exists():
-                try:
-                    result = subprocess.run(
-                        ["git", "worktree", "remove", "--force", str(wt_path)],
-                        cwd=project_dir,
-                        capture_output=True,
-                        text=True,
-                        timeout=30,
-                    )
-                    if result.returncode == 0:
-                        print_status(f"Removed worktree: {spec_name}", "success")
-                    else:
-                        # Fallback: remove directory manually if git fails
-                        shutil.rmtree(wt_path, ignore_errors=True)
-                        print_status(
-                            f"Removed worktree directory: {spec_name}", "success"
-                        )
-                except subprocess.TimeoutExpired:
-                    # Timeout: fall back to manual removal
-                    shutil.rmtree(wt_path, ignore_errors=True)
-                    print_status(
-                        f"Worktree removal timed out, removed directory: {spec_name}",
-                        "warning",
-                    )
-                except Exception as e:
-                    print_status(
-                        f"Failed to remove worktree {spec_name}: {e}", "warning"
-                    )
-
-            # Remove spec directory
-            if spec_path.exists():
-                try:
-                    shutil.rmtree(spec_path)
-                    print_status(f"Removed spec: {spec_name}", "success")
-                    deleted_count += 1
-                except Exception as e:
-                    print_status(f"Failed to remove spec {spec_name}: {e}", "error")
-
-        print()
-        print_status(f"Cleaned up {deleted_count} spec(s)", "info")
-
-    return True

apps/backend/cli/recovery.py

@@ -1,217 +0,0 @@
-#!/usr/bin/env python3
-"""
-JSON Recovery Utility
-=====================
-
-Detects and repairs corrupted JSON files in specs directories.
-
-Usage:
-    python -m cli.recovery --project-dir /path/to/project --detect
-    python -m cli.recovery --project-dir /path/to/project --spec-id 004-feature --delete
-    python -m cli.recovery --project-dir /path/to/project --all --delete
-"""
-
-import argparse
-import json
-import sys
-import uuid
-from pathlib import Path
-
-from cli.utils import find_specs_dir
-
-
-def check_json_file(filepath: Path) -> tuple[bool, str | None]:
-    """
-    Check if a JSON file is valid.
-
-    Returns:
-        (is_valid, error_message)
-    """
-    try:
-        with open(filepath, encoding="utf-8") as f:
-            json.load(f)
-        return True, None
-    except json.JSONDecodeError as e:
-        return False, str(e)
-    except Exception as e:
-        return False, str(e)
-
-
-def detect_corrupted_files(specs_dir: Path) -> list[tuple[Path, str]]:
-    """
-    Scan specs directory recursively for corrupted JSON files.
-
-    Returns:
-        List of (filepath, error_message) tuples
-    """
-    corrupted = []
-
-    if not specs_dir.exists():
-        return corrupted
-
-    # Recursively scan for JSON files (includes nested files like memory/*.json)
-    for json_file in specs_dir.rglob("*.json"):
-        is_valid, error = check_json_file(json_file)
-        if not is_valid:
-            # Type narrowing: error is str when is_valid is False
-            assert error is not None
-            corrupted.append((json_file, error))
-
-    return corrupted
-
-
-def backup_corrupted_file(filepath: Path) -> bool:
-    """
-    Backup a corrupted file by renaming it with a .corrupted suffix.
-
-    Args:
-        filepath: Path to the corrupted file
-
-    Returns:
-        True if backed up successfully, False otherwise
-    """
-    try:
-        # Create backup before deleting
-        base_backup_path = filepath.with_suffix(f"{filepath.suffix}.corrupted")
-        backup_path = base_backup_path
-
-        # Handle existing backup files by generating unique name with UUID
-        if backup_path.exists():
-            # Use UUID for unique naming to avoid races
-            unique_suffix = uuid.uuid4().hex[:8]
-            backup_path = filepath.with_suffix(
-                f"{filepath.suffix}.corrupted.{unique_suffix}"
-            )
-
-        filepath.rename(backup_path)
-        print(f"  [BACKUP] Moved corrupted file to: {backup_path}")
-        return True
-    except Exception as e:
-        print(f"  [ERROR] Failed to backup file: {e}")
-        return False
-
-
-def main() -> None:
-    parser = argparse.ArgumentParser(
-        description="Detect and repair corrupted JSON files in specs directories"
-    )
-    parser.add_argument(
-        "--project-dir",
-        type=Path,
-        default=Path.cwd(),
-        help="Project directory (default: current directory)",
-    )
-    parser.add_argument(
-        "--specs-dir",
-        type=Path,
-        help="Specs directory path (overrides auto-detection)",
-    )
-    parser.add_argument(
-        "--detect",
-        action="store_true",
-        help="Detect corrupted JSON files",
-    )
-    parser.add_argument(
-        "--spec-id",
-        type=str,
-        help="Specific spec ID to fix (e.g., 004-feature)",
-    )
-    parser.add_argument(
-        "--delete",
-        action="store_true",
-        help="Delete corrupted files (creates .corrupted backup)",
-    )
-    parser.add_argument(
-        "--all",
-        action="store_true",
-        help="Fix all corrupted files (requires --delete)",
-    )
-
-    args = parser.parse_args()
-
-    # Validate --all requires --delete
-    if args.all and not args.delete:
-        parser.error("--all requires --delete")
-
-    # Find specs directory
-    if args.specs_dir:
-        specs_dir = args.specs_dir
-    else:
-        specs_dir = find_specs_dir(args.project_dir)
-
-    print(f"[INFO] Scanning specs directory: {specs_dir}")
-
-    # Default to detect mode if no flags provided
-    if not args.detect and not args.delete:
-        args.detect = True
-
-    # Detect corrupted files (dry-run when detect-only, otherwise for deletion)
-    corrupted = detect_corrupted_files(specs_dir)
-
-    # Detect-only mode: show results and exit
-    if args.detect and not args.delete:
-        if not corrupted:
-            print("[OK] No corrupted JSON files found")
-            sys.exit(0)
-
-        print(f"\n[FOUND] {len(corrupted)} corrupted file(s):\n")
-        for filepath, error in corrupted:
-            print(f"  - {filepath.relative_to(specs_dir.parent)}")
-            print(f"    Error: {error}")
-        print()
-        # Exit with error code when corrupted files are found
-        sys.exit(1)
-
-    # Delete corrupted files
-    if args.delete:
-        if args.spec_id:
-            # Delete specific spec
-            spec_dir = (specs_dir / args.spec_id).resolve()
-            specs_dir_resolved = specs_dir.resolve()
-            # Validate path doesn't escape specs directory
-            if not spec_dir.is_relative_to(specs_dir_resolved):
-                print("[ERROR] Invalid spec ID: path traversal detected")
-                sys.exit(1)
-
-            if not spec_dir.exists():
-                print(f"[ERROR] Spec directory not found: {spec_dir}")
-                sys.exit(1)
-
-            print(f"[INFO] Processing spec: {args.spec_id}")
-            has_failures = False
-            for json_file in spec_dir.rglob("*.json"):
-                is_valid, error = check_json_file(json_file)
-                if not is_valid:
-                    print(f"  [CORRUPTED] {json_file.name}")
-                    if not backup_corrupted_file(json_file):
-                        has_failures = True
-
-            if has_failures:
-                sys.exit(1)
-
-        elif args.all:
-            # Delete all corrupted files
-            # Use the already-detected corrupted list, or re-scan if needed
-            if not corrupted:
-                corrupted = detect_corrupted_files(specs_dir)
-            if not corrupted:
-                print("[OK] No corrupted files to delete")
-                sys.exit(0)
-
-            print(f"\n[INFO] Backing up {len(corrupted)} corrupted file(s):\n")
-            has_failures = False
-            for filepath, _ in corrupted:
-                # backup_corrupted_file prints its own [BACKUP] message
-                if not backup_corrupted_file(filepath):
-                    has_failures = True
-
-            if has_failures:
-                sys.exit(1)
-
-        else:
-            print("[ERROR] Must specify --spec-id or --all with --delete")
-            sys.exit(1)
-
-
-if __name__ == "__main__":
-    main()

apps/backend/client.py

@@ -1,25 +0,0 @@
-"""
-Claude client module facade.
-
-Provides Claude API client utilities.
-Uses lazy imports to avoid circular dependencies.
-"""
-
-
-def __getattr__(name):
-    """Lazy import to avoid circular imports with auto_claude_tools."""
-    from core import client as _client
-
-    return getattr(_client, name)
-
-
-def create_client(*args, **kwargs):
-    """Create a Claude client instance."""
-    from core.client import create_client as _create_client
-
-    return _create_client(*args, **kwargs)
-
-
-__all__ = [
-    "create_client",
-]

apps/backend/core/auth.py

@@ -1,339 +0,0 @@
-"""
-Authentication helpers for Auto Claude.
-
-Provides centralized authentication token resolution with fallback support
-for multiple environment variables, and SDK environment variable passthrough
-for custom API endpoints.
-"""
-
-import json
-import os
-import platform
-import subprocess
-
-# Priority order for auth token resolution
-# NOTE: We intentionally do NOT fall back to ANTHROPIC_API_KEY.
-# Auto Claude is designed to use Claude Code OAuth tokens only.
-# This prevents silent billing to user's API credits when OAuth fails.
-AUTH_TOKEN_ENV_VARS = [
-    "CLAUDE_CODE_OAUTH_TOKEN",  # OAuth token from Claude Code CLI
-    "ANTHROPIC_AUTH_TOKEN",  # CCR/proxy token (for enterprise setups)
-]
-
-# Environment variables to pass through to SDK subprocess
-# NOTE: ANTHROPIC_API_KEY is intentionally excluded to prevent silent API billing
-SDK_ENV_VARS = [
-    # API endpoint configuration
-    "ANTHROPIC_BASE_URL",
-    "ANTHROPIC_AUTH_TOKEN",
-    # Model overrides (from API Profile custom model mappings)
-    "ANTHROPIC_MODEL",
-    "ANTHROPIC_DEFAULT_HAIKU_MODEL",
-    "ANTHROPIC_DEFAULT_SONNET_MODEL",
-    "ANTHROPIC_DEFAULT_OPUS_MODEL",
-    # SDK behavior configuration
-    "NO_PROXY",
-    "DISABLE_TELEMETRY",
-    "DISABLE_COST_WARNINGS",
-    "API_TIMEOUT_MS",
-    # Windows-specific: Git Bash path for Claude Code CLI
-    "CLAUDE_CODE_GIT_BASH_PATH",
-]
-
-
-def get_token_from_keychain() -> str | None:
-    """
-    Get authentication token from system credential store.
-
-    Reads Claude Code credentials from:
-    - macOS: Keychain
-    - Windows: Credential Manager
-    - Linux: Not yet supported (use env var)
-
-    Returns:
-        Token string if found, None otherwise
-    """
-    system = platform.system()
-
-    if system == "Darwin":
-        return _get_token_from_macos_keychain()
-    elif system == "Windows":
-        return _get_token_from_windows_credential_files()
-    else:
-        # Linux: secret-service not yet implemented
-        return None
-
-
-def _get_token_from_macos_keychain() -> str | None:
-    """Get token from macOS Keychain."""
-    try:
-        result = subprocess.run(
-            [
-                "/usr/bin/security",
-                "find-generic-password",
-                "-s",
-                "Claude Code-credentials",
-                "-w",
-            ],
-            capture_output=True,
-            text=True,
-            timeout=5,
-        )
-
-        if result.returncode != 0:
-            return None
-
-        credentials_json = result.stdout.strip()
-        if not credentials_json:
-            return None
-
-        data = json.loads(credentials_json)
-        token = data.get("claudeAiOauth", {}).get("accessToken")
-
-        if not token:
-            return None
-
-        # Validate token format (Claude OAuth tokens start with sk-ant-oat01-)
-        if not token.startswith("sk-ant-oat01-"):
-            return None
-
-        return token
-
-    except (subprocess.TimeoutExpired, json.JSONDecodeError, KeyError, Exception):
-        return None
-
-
-def _get_token_from_windows_credential_files() -> str | None:
-    """Get token from Windows credential files.
-
-    Claude Code on Windows stores credentials in ~/.claude/.credentials.json
-    """
-    try:
-        # Claude Code stores credentials in ~/.claude/.credentials.json
-        cred_paths = [
-            os.path.expandvars(r"%USERPROFILE%\.claude\.credentials.json"),
-            os.path.expandvars(r"%USERPROFILE%\.claude\credentials.json"),
-            os.path.expandvars(r"%LOCALAPPDATA%\Claude\credentials.json"),
-            os.path.expandvars(r"%APPDATA%\Claude\credentials.json"),
-        ]
-
-        for cred_path in cred_paths:
-            if os.path.exists(cred_path):
-                with open(cred_path, encoding="utf-8") as f:
-                    data = json.load(f)
-                    token = data.get("claudeAiOauth", {}).get("accessToken")
-                    if token and token.startswith("sk-ant-oat01-"):
-                        return token
-
-        return None
-
-    except (json.JSONDecodeError, KeyError, FileNotFoundError, Exception):
-        return None
-
-
-def get_auth_token() -> str | None:
-    """
-    Get authentication token from environment variables or system credential store.
-
-    Checks multiple sources in priority order:
-    1. CLAUDE_CODE_OAUTH_TOKEN (env var)
-    2. ANTHROPIC_AUTH_TOKEN (CCR/proxy env var for enterprise setups)
-    3. System credential store (macOS Keychain, Windows Credential Manager)
-
-    NOTE: ANTHROPIC_API_KEY is intentionally NOT supported to prevent
-    silent billing to user's API credits when OAuth is misconfigured.
-
-    Returns:
-        Token string if found, None otherwise
-    """
-    # First check environment variables
-    for var in AUTH_TOKEN_ENV_VARS:
-        token = os.environ.get(var)
-        if token:
-            return token
-
-    # Fallback to system credential store
-    return get_token_from_keychain()
-
-
-def get_auth_token_source() -> str | None:
-    """Get the name of the source that provided the auth token."""
-    # Check environment variables first
-    for var in AUTH_TOKEN_ENV_VARS:
-        if os.environ.get(var):
-            return var
-
-    # Check if token came from system credential store
-    if get_token_from_keychain():
-        system = platform.system()
-        if system == "Darwin":
-            return "macOS Keychain"
-        elif system == "Windows":
-            return "Windows Credential Files"
-        else:
-            return "System Credential Store"
-
-    return None
-
-
-def require_auth_token() -> str:
-    """
-    Get authentication token or raise ValueError.
-
-    Raises:
-        ValueError: If no auth token is found in any supported source
-    """
-    token = get_auth_token()
-    if not token:
-        error_msg = (
-            "No OAuth token found.\n\n"
-            "Auto Claude requires Claude Code OAuth authentication.\n"
-            "Direct API keys (ANTHROPIC_API_KEY) are not supported.\n\n"
-        )
-        # Provide platform-specific guidance
-        system = platform.system()
-        if system == "Darwin":
-            error_msg += (
-                "To authenticate:\n"
-                "  1. Run: claude setup-token\n"
-                "  2. The token will be saved to macOS Keychain automatically\n\n"
-                "Or set CLAUDE_CODE_OAUTH_TOKEN in your .env file."
-            )
-        elif system == "Windows":
-            error_msg += (
-                "To authenticate:\n"
-                "  1. Run: claude setup-token\n"
-                "  2. The token should be saved to Windows Credential Manager\n\n"
-                "If auto-detection fails, set CLAUDE_CODE_OAUTH_TOKEN in your .env file.\n"
-                "Check: %LOCALAPPDATA%\\Claude\\credentials.json"
-            )
-        else:
-            error_msg += (
-                "To authenticate:\n"
-                "  1. Run: claude setup-token\n"
-                "  2. Set CLAUDE_CODE_OAUTH_TOKEN in your .env file"
-            )
-        raise ValueError(error_msg)
-    return token
-
-
-def _find_git_bash_path() -> str | None:
-    """
-    Find git-bash (bash.exe) path on Windows.
-
-    Uses 'where git' to find git.exe, then derives bash.exe location from it.
-    Git for Windows installs bash.exe in the 'bin' directory alongside git.exe
-    or in the parent 'bin' directory when git.exe is in 'cmd'.
-
-    Returns:
-        Full path to bash.exe if found, None otherwise
-    """
-    if platform.system() != "Windows":
-        return None
-
-    # If already set in environment, use that
-    existing = os.environ.get("CLAUDE_CODE_GIT_BASH_PATH")
-    if existing and os.path.exists(existing):
-        return existing
-
-    git_path = None
-
-    # Method 1: Use 'where' command to find git.exe
-    try:
-        # Use where.exe explicitly for reliability
-        result = subprocess.run(
-            ["where.exe", "git"],
-            capture_output=True,
-            text=True,
-            timeout=5,
-            shell=False,
-        )
-
-        if result.returncode == 0 and result.stdout.strip():
-            git_paths = result.stdout.strip().splitlines()
-            if git_paths:
-                git_path = git_paths[0].strip()
-    except (subprocess.TimeoutExpired, FileNotFoundError, subprocess.SubprocessError):
-        # Intentionally suppress errors - best-effort detection with fallback to common paths
-        pass
-
-    # Method 2: Check common installation paths if 'where' didn't work
-    if not git_path:
-        common_git_paths = [
-            os.path.expandvars(r"%PROGRAMFILES%\Git\cmd\git.exe"),
-            os.path.expandvars(r"%PROGRAMFILES%\Git\bin\git.exe"),
-            os.path.expandvars(r"%PROGRAMFILES(X86)%\Git\cmd\git.exe"),
-            os.path.expandvars(r"%LOCALAPPDATA%\Programs\Git\cmd\git.exe"),
-        ]
-        for path in common_git_paths:
-            if os.path.exists(path):
-                git_path = path
-                break
-
-    if not git_path:
-        return None
-
-    # Derive bash.exe location from git.exe location
-    # Git for Windows structure:
-    #   C:\...\Git\cmd\git.exe     -> bash.exe is at C:\...\Git\bin\bash.exe
-    #   C:\...\Git\bin\git.exe     -> bash.exe is at C:\...\Git\bin\bash.exe
-    #   C:\...\Git\mingw64\bin\git.exe -> bash.exe is at C:\...\Git\bin\bash.exe
-    git_dir = os.path.dirname(git_path)
-    git_parent = os.path.dirname(git_dir)
-    git_grandparent = os.path.dirname(git_parent)
-
-    # Check common bash.exe locations relative to git installation
-    possible_bash_paths = [
-        os.path.join(git_parent, "bin", "bash.exe"),  # cmd -> bin
-        os.path.join(git_dir, "bash.exe"),  # If git.exe is in bin
-        os.path.join(git_grandparent, "bin", "bash.exe"),  # mingw64/bin -> bin
-    ]
-
-    for bash_path in possible_bash_paths:
-        if os.path.exists(bash_path):
-            return bash_path
-
-    return None
-
-
-def get_sdk_env_vars() -> dict[str, str]:
-    """
-    Get environment variables to pass to SDK.
-
-    Collects relevant env vars (ANTHROPIC_BASE_URL, etc.) that should
-    be passed through to the claude-agent-sdk subprocess.
-
-    On Windows, auto-detects CLAUDE_CODE_GIT_BASH_PATH if not already set.
-
-    Returns:
-        Dict of env var name -> value for non-empty vars
-    """
-    env = {}
-    for var in SDK_ENV_VARS:
-        value = os.environ.get(var)
-        if value:
-            env[var] = value
-
-    # On Windows, auto-detect git-bash path if not already set
-    # Claude Code CLI requires bash.exe to run on Windows
-    if platform.system() == "Windows" and "CLAUDE_CODE_GIT_BASH_PATH" not in env:
-        bash_path = _find_git_bash_path()
-        if bash_path:
-            env["CLAUDE_CODE_GIT_BASH_PATH"] = bash_path
-
-    return env
-
-
-def ensure_claude_code_oauth_token() -> None:
-    """
-    Ensure CLAUDE_CODE_OAUTH_TOKEN is set (for SDK compatibility).
-
-    If not set but other auth tokens are available, copies the value
-    to CLAUDE_CODE_OAUTH_TOKEN so the underlying SDK can use it.
-    """
-    if os.environ.get("CLAUDE_CODE_OAUTH_TOKEN"):
-        return
-
-    token = get_auth_token()
-    if token:
-        os.environ["CLAUDE_CODE_OAUTH_TOKEN"] = token

apps/backend/core/dependency_validator.py

@@ -1,50 +0,0 @@
-"""
-Dependency Validator
-====================
-
-Validates platform-specific dependencies are installed before running agents.
-"""
-
-import sys
-from pathlib import Path
-
-
-def validate_platform_dependencies() -> None:
-    """
-    Validate that platform-specific dependencies are installed.
-
-    Raises:
-        SystemExit: If required platform-specific dependencies are missing,
-                   with helpful installation instructions.
-    """
-    # Check Windows-specific dependencies
-    if sys.platform == "win32" and sys.version_info >= (3, 12):
-        try:
-            import pywintypes  # noqa: F401
-        except ImportError:
-            _exit_with_pywin32_error()
-
-
-def _exit_with_pywin32_error() -> None:
-    """Exit with helpful error message for missing pywin32."""
-    # Use sys.prefix to detect the virtual environment path
-    # This works for venv and poetry environments
-    venv_activate = Path(sys.prefix) / "Scripts" / "activate"
-
-    sys.exit(
-        "Error: Required Windows dependency 'pywin32' is not installed.\n"
-        "\n"
-        "Auto Claude requires pywin32 on Windows for LadybugDB/Graphiti memory integration.\n"
-        "\n"
-        "To fix this:\n"
-        "1. Activate your virtual environment:\n"
-        f"   {venv_activate}\n"
-        "\n"
-        "2. Install pywin32:\n"
-        "   pip install pywin32>=306\n"
-        "\n"
-        "   Or reinstall all dependencies:\n"
-        "   pip install -r requirements.txt\n"
-        "\n"
-        f"Current Python: {sys.executable}\n"
-    )

apps/backend/core/file_utils.py

@@ -1,121 +0,0 @@
-#!/usr/bin/env python3
-"""
-Atomic File Write Utilities
-============================
-
-Synchronous utilities for atomic file writes to prevent corruption.
-
-Uses temp file + os.replace() pattern which is atomic on POSIX systems
-and atomic on Windows when source and destination are on the same volume.
-
-Usage:
-    from core.file_utils import write_json_atomic
-
-    write_json_atomic("/path/to/file.json", {"key": "value"})
-"""
-
-import json
-import logging
-import os
-import tempfile
-from collections.abc import Iterator
-from contextlib import contextmanager
-from pathlib import Path
-from typing import IO, Any, Literal
-
-
-@contextmanager
-def atomic_write(
-    filepath: str | Path,
-    mode: Literal["w", "wb", "wt"] = "w",
-    encoding: str | None = "utf-8",
-) -> Iterator[IO]:
-    """
-    Atomic file write using temp file and rename.
-
-    Writes to .tmp file first, then atomically replaces target file
-    using os.replace() which is atomic on POSIX systems and same-volume Windows.
-
-    Note: This function supports both text and binary modes. For binary modes
-    (mode containing 'b'), encoding must be None.
-
-    Args:
-        filepath: Target file path
-        mode: File open mode (default: "w", text mode only)
-        encoding: File encoding for text modes, None for binary (default: "utf-8")
-
-    Example:
-        with atomic_write("/path/to/file.json") as f:
-            json.dump(data, f)
-
-    Yields:
-        File handle to temp file
-    """
-    filepath = Path(filepath)
-    filepath.parent.mkdir(parents=True, exist_ok=True)
-
-    # Binary modes require encoding=None
-    actual_encoding = None if "b" in mode else encoding
-
-    # Create temp file in same directory for atomic rename
-    fd, tmp_path = tempfile.mkstemp(
-        dir=filepath.parent, prefix=f".{filepath.name}.tmp.", suffix=""
-    )
-
-    # Open temp file with requested mode
-    # If fdopen fails, close fd and clean up temp file
-    try:
-        f = os.fdopen(fd, mode, encoding=actual_encoding)
-    except Exception:
-        os.close(fd)
-        os.unlink(tmp_path)
-        raise
-
-    try:
-        with f:
-            yield f
-    except Exception:
-        # Clean up temp file on error (replace didn't happen yet)
-        try:
-            os.unlink(tmp_path)
-        except Exception as cleanup_err:
-            # Best-effort cleanup, ignore errors to not mask original exception
-            # Log cleanup failure for debugging (orphaned temp files may accumulate)
-            logging.warning(
-                f"Failed to cleanup temp file {tmp_path}: {cleanup_err}",
-                exc_info=True,
-            )
-        raise
-    else:
-        # Atomic replace - only runs if no exception was raised
-        # If os.replace itself fails, do NOT clean up (may be partially renamed)
-        os.replace(tmp_path, filepath)
-
-
-def write_json_atomic(
-    filepath: str | Path,
-    data: Any,
-    indent: int = 2,
-    ensure_ascii: bool = False,
-    encoding: str = "utf-8",
-) -> None:
-    """
-    Write JSON data to file atomically.
-
-    This function prevents file corruption by:
-    1. Writing to a temporary file first
-    2. Only replacing the target file if the write succeeds
-    3. Using os.replace() for atomicity
-
-    Args:
-        filepath: Target file path
-        data: Data to serialize as JSON
-        indent: JSON indentation (default: 2)
-        ensure_ascii: Whether to escape non-ASCII characters (default: False)
-        encoding: File encoding (default: "utf-8")
-
-    Example:
-        write_json_atomic("/path/to/file.json", {"key": "value"})
-    """
-    with atomic_write(filepath, "w", encoding=encoding) as f:
-        json.dump(data, f, indent=indent, ensure_ascii=ensure_ascii)

apps/backend/core/git_executable.py

@@ -1,142 +0,0 @@
-#!/usr/bin/env python3
-"""
-Git Executable Finder
-======================
-
-Utility to find the git executable, with Windows-specific fallbacks.
-Separated into its own module to avoid circular imports.
-"""
-
-import os
-import shutil
-import subprocess
-from pathlib import Path
-
-_cached_git_path: str | None = None
-
-
-def get_git_executable() -> str:
-    """Find the git executable, with Windows-specific fallbacks.
-
-    Returns the path to git executable. On Windows, checks multiple sources:
-    1. CLAUDE_CODE_GIT_BASH_PATH env var (set by Electron frontend)
-    2. shutil.which (if git is in PATH)
-    3. Common installation locations
-    4. Windows 'where' command
-
-    Caches the result after first successful find.
-    """
-    global _cached_git_path
-
-    # Return cached result if available
-    if _cached_git_path is not None:
-        return _cached_git_path
-
-    git_path = _find_git_executable()
-    _cached_git_path = git_path
-    return git_path
-
-
-def _find_git_executable() -> str:
-    """Internal function to find git executable."""
-    # 1. Check CLAUDE_CODE_GIT_BASH_PATH (set by Electron frontend)
-    # This env var points to bash.exe, we can derive git.exe from it
-    bash_path = os.environ.get("CLAUDE_CODE_GIT_BASH_PATH")
-    if bash_path:
-        try:
-            bash_path_obj = Path(bash_path)
-            if bash_path_obj.exists():
-                git_dir = bash_path_obj.parent.parent
-                # Try cmd/git.exe first (preferred), then bin/git.exe
-                for git_subpath in ["cmd/git.exe", "bin/git.exe"]:
-                    git_path = git_dir / git_subpath
-                    if git_path.is_file():
-                        return str(git_path)
-        except (OSError, ValueError):
-            pass  # Invalid path or permission error - try next method
-
-    # 2. Try shutil.which (works if git is in PATH)
-    git_path = shutil.which("git")
-    if git_path:
-        return git_path
-
-    # 3. Windows-specific: check common installation locations
-    if os.name == "nt":
-        common_paths = [
-            os.path.expandvars(r"%PROGRAMFILES%\Git\cmd\git.exe"),
-            os.path.expandvars(r"%PROGRAMFILES%\Git\bin\git.exe"),
-            os.path.expandvars(r"%PROGRAMFILES(X86)%\Git\cmd\git.exe"),
-            os.path.expandvars(r"%LOCALAPPDATA%\Programs\Git\cmd\git.exe"),
-            r"C:\Program Files\Git\cmd\git.exe",
-            r"C:\Program Files (x86)\Git\cmd\git.exe",
-        ]
-        for path in common_paths:
-            try:
-                if os.path.isfile(path):
-                    return path
-            except OSError:
-                continue
-
-        # 4. Try 'where' command with shell=True (more reliable on Windows)
-        try:
-            result = subprocess.run(
-                "where git",
-                capture_output=True,
-                text=True,
-                timeout=5,
-                shell=True,
-            )
-            if result.returncode == 0 and result.stdout.strip():
-                found_path = result.stdout.strip().split("\n")[0].strip()
-                if found_path and os.path.isfile(found_path):
-                    return found_path
-        except (subprocess.TimeoutExpired, OSError):
-            pass  # 'where' command failed - fall through to default
-
-    # Default fallback - let subprocess handle it (may fail)
-    return "git"
-
-
-def run_git(
-    args: list[str],
-    cwd: Path | str | None = None,
-    timeout: int = 60,
-    input_data: str | None = None,
-) -> subprocess.CompletedProcess:
-    """Run a git command with proper executable finding.
-
-    Args:
-        args: Git command arguments (without 'git' prefix)
-        cwd: Working directory for the command
-        timeout: Command timeout in seconds (default: 60)
-        input_data: Optional string data to pass to stdin
-
-    Returns:
-        CompletedProcess with command results.
-    """
-    git = get_git_executable()
-    try:
-        return subprocess.run(
-            [git] + args,
-            cwd=cwd,
-            input=input_data,
-            capture_output=True,
-            text=True,
-            encoding="utf-8",
-            errors="replace",
-            timeout=timeout,
-        )
-    except subprocess.TimeoutExpired:
-        return subprocess.CompletedProcess(
-            args=[git] + args,
-            returncode=-1,
-            stdout="",
-            stderr=f"Command timed out after {timeout} seconds",
-        )
-    except FileNotFoundError:
-        return subprocess.CompletedProcess(
-            args=[git] + args,
-            returncode=-1,
-            stdout="",
-            stderr="Git executable not found. Please ensure git is installed and in PATH.",
-        )

apps/backend/core/io_utils.py

@@ -1,94 +0,0 @@
-"""
-I/O Utilities for Safe Console Output
-=====================================
-
-Safe I/O operations for processes running as subprocesses.
-
-When the backend runs as a subprocess of the Electron app, the parent
-process may close the pipe at any time (e.g., user closes the app,
-process killed, etc.). This module provides utilities to handle these
-cases gracefully.
-"""
-
-from __future__ import annotations
-
-import logging
-import sys
-
-logger = logging.getLogger(__name__)
-
-# Track if pipe is broken to avoid repeated failed writes
-_pipe_broken = False
-
-
-def safe_print(message: str, flush: bool = True) -> None:
-    """
-    Print to stdout with BrokenPipeError handling.
-
-    When running as a subprocess (e.g., from Electron), the parent process
-    may close the pipe at any time. This function gracefully handles that
-    case instead of raising an exception.
-
-    Args:
-        message: The message to print
-        flush: Whether to flush stdout after printing (default True)
-    """
-    global _pipe_broken
-
-    # Skip if we already know the pipe is broken
-    if _pipe_broken:
-        return
-
-    try:
-        print(message, flush=flush)
-    except BrokenPipeError:
-        # Pipe closed by parent process - this is expected during shutdown
-        _pipe_broken = True
-        # Quietly close stdout to prevent further errors
-        try:
-            sys.stdout.close()
-        except Exception:
-            pass
-        logger.debug("Output pipe closed by parent process")
-    except ValueError as e:
-        # Handle writes to closed file (can happen after stdout.close())
-        if "closed file" in str(e).lower():
-            _pipe_broken = True
-            logger.debug("Output stream closed")
-        else:
-            # Re-raise unexpected ValueErrors
-            raise
-    except OSError as e:
-        # Handle other pipe-related errors (EPIPE, etc.)
-        if e.errno == 32:  # EPIPE - Broken pipe
-            _pipe_broken = True
-            try:
-                sys.stdout.close()
-            except Exception:
-                pass
-            logger.debug("Output pipe closed (EPIPE)")
-        else:
-            # Re-raise unexpected OS errors
-            raise
-
-
-def is_pipe_broken() -> bool:
-    """Check if the output pipe has been closed."""
-    return _pipe_broken
-
-
-def reset_pipe_state() -> None:
-    """
-    Reset pipe broken state.
-
-    Useful for testing or when starting a new subprocess context where
-    stdout has been reopened. Should only be called when stdout is known
-    to be functional (e.g., in a fresh subprocess with a new stdout).
-
-    Warning:
-        Calling this after stdout has been closed will result in safe_print()
-        attempting to write to the closed stream. The ValueError will be
-        caught and the pipe will be marked as broken again.
-    """
-    global _pipe_broken
-    _pipe_broken = False

apps/backend/core/model_config.py

@@ -1,68 +0,0 @@
-"""
-Model Configuration Utilities
-==============================
-
-Shared utilities for reading and parsing model configuration from environment variables.
-Used by both commit_message.py and merge resolver.
-"""
-
-import logging
-import os
-
-logger = logging.getLogger(__name__)
-
-# Default model for utility operations (commit messages, merge resolution)
-DEFAULT_UTILITY_MODEL = "claude-haiku-4-5-20251001"
-
-
-def get_utility_model_config(
-    default_model: str = DEFAULT_UTILITY_MODEL,
-) -> tuple[str, int | None]:
-    """
-    Get utility model configuration from environment variables.
-
-    Reads UTILITY_MODEL_ID and UTILITY_THINKING_BUDGET from environment,
-    with sensible defaults and validation.
-
-    Args:
-        default_model: Default model ID to use if UTILITY_MODEL_ID not set
-
-    Returns:
-        Tuple of (model_id, thinking_budget) where thinking_budget is None
-        if extended thinking is disabled, or an int representing token budget
-    """
-    model = os.environ.get("UTILITY_MODEL_ID", default_model)
-    thinking_budget_str = os.environ.get("UTILITY_THINKING_BUDGET", "")
-
-    # Parse thinking budget: empty string = disabled (None), number = budget tokens
-    # Note: 0 is treated as "disable thinking" (same as None) since 0 tokens is meaningless
-    thinking_budget: int | None
-    if not thinking_budget_str:
-        # Empty string means "none" level - disable extended thinking
-        thinking_budget = None
-    else:
-        try:
-            parsed_budget = int(thinking_budget_str)
-            # Validate positive values - 0 or negative are invalid
-            # 0 would mean "thinking enabled but 0 tokens" which is meaningless
-            if parsed_budget <= 0:
-                if parsed_budget == 0:
-                    # Zero means disable thinking (same as empty string)
-                    logger.debug(
-                        "UTILITY_THINKING_BUDGET=0 interpreted as 'disable thinking'"
-                    )
-                    thinking_budget = None
-                else:
-                    logger.warning(
-                        f"Negative UTILITY_THINKING_BUDGET value '{thinking_budget_str}' not allowed, using default 1024"
-                    )
-                    thinking_budget = 1024
-            else:
-                thinking_budget = parsed_budget
-        except ValueError:
-            logger.warning(
-                f"Invalid UTILITY_THINKING_BUDGET value '{thinking_budget_str}', using default 1024"
-            )
-            thinking_budget = 1024
-
-    return model, thinking_budget

apps/backend/core/phase_event.py

@@ -1,59 +0,0 @@
-"""
-Execution phase event protocol for frontend synchronization.
-
-Protocol: __EXEC_PHASE__:{"phase":"coding","message":"Starting"}
-"""
-
-import json
-import os
-import sys
-from enum import Enum
-from typing import Any
-
-PHASE_MARKER_PREFIX = "__EXEC_PHASE__:"
-_DEBUG = os.environ.get("DEBUG", "").lower() in ("1", "true", "yes")
-
-
-class ExecutionPhase(str, Enum):
-    """Maps to frontend's ExecutionPhase type for task card badges."""
-
-    PLANNING = "planning"
-    CODING = "coding"
-    QA_REVIEW = "qa_review"
-    QA_FIXING = "qa_fixing"
-    COMPLETE = "complete"
-    FAILED = "failed"
-
-
-def emit_phase(
-    phase: ExecutionPhase | str,
-    message: str = "",
-    *,
-    progress: int | None = None,
-    subtask: str | None = None,
-) -> None:
-    """Emit structured phase event to stdout for frontend parsing."""
-    phase_value = phase.value if isinstance(phase, ExecutionPhase) else phase
-
-    payload: dict[str, Any] = {
-        "phase": phase_value,
-        "message": message,
-    }
-
-    if progress is not None:
-        if not (0 <= progress <= 100):
-            progress = max(0, min(100, progress))
-        payload["progress"] = progress
-
-    if subtask is not None:
-        payload["subtask"] = subtask
-
-    try:
-        print(f"{PHASE_MARKER_PREFIX}{json.dumps(payload, default=str)}", flush=True)
-    except (OSError, UnicodeEncodeError) as e:
-        if _DEBUG:
-            try:
-                sys.stderr.write(f"[phase_event] emit failed: {e}\n")
-                sys.stderr.flush()
-            except (OSError, UnicodeEncodeError):
-                pass  # Truly silent on complete I/O failure

apps/backend/core/plan_normalization.py

@@ -1,50 +0,0 @@
-"""
-Implementation Plan Normalization Utilities
-===========================================
-
-Small helpers for normalizing common LLM/legacy field variants in
-implementation_plan.json without changing status semantics.
-"""
-
-from typing import Any
-
-
-def normalize_subtask_aliases(subtask: dict[str, Any]) -> tuple[dict[str, Any], bool]:
-    """Normalize common subtask field aliases.
-
-    - If `id` is missing and `subtask_id` exists, copy it into `id` as a string.
-    - If `description` is missing/empty and `title` is a non-empty string, copy it
-      into `description`.
-    """
-
-    normalized = dict(subtask)
-    changed = False
-
-    id_value = normalized.get("id")
-    id_missing = (
-        "id" not in normalized
-        or id_value is None
-        or (isinstance(id_value, str) and not id_value.strip())
-    )
-    if id_missing and "subtask_id" in normalized:
-        subtask_id = normalized.get("subtask_id")
-        if subtask_id is not None:
-            subtask_id_str = str(subtask_id).strip()
-            if subtask_id_str:
-                normalized["id"] = subtask_id_str
-                changed = True
-
-    description_value = normalized.get("description")
-    description_missing = (
-        "description" not in normalized
-        or description_value is None
-        or (isinstance(description_value, str) and not description_value.strip())
-    )
-    title = normalized.get("title")
-    if description_missing and isinstance(title, str):
-        title_str = title.strip()
-        if title_str:
-            normalized["description"] = title_str
-            changed = True
-
-    return normalized, changed

apps/backend/core/sentry.py

@@ -1,406 +0,0 @@
-"""
-Sentry Error Tracking for Python Backend
-=========================================
-
-Initializes Sentry for the Python backend with:
-- Privacy-preserving path masking (usernames removed)
-- Release tracking matching the Electron frontend
-- Environment variable configuration (same as frontend)
-
-Configuration:
-- SENTRY_DSN: Required to enable Sentry (same as frontend)
-- SENTRY_TRACES_SAMPLE_RATE: Performance monitoring sample rate (0-1, default: 0.1)
-- SENTRY_ENVIRONMENT: Override environment (default: auto-detected)
-
-Privacy Note:
-- Usernames are masked from all file paths
-- Project paths remain visible for debugging (this is expected)
-- No user identifiers are collected
-"""
-
-from __future__ import annotations
-
-import logging
-import os
-import re
-import sys
-from pathlib import Path
-from typing import Any
-
-logger = logging.getLogger(__name__)
-
-# Track initialization state
-_sentry_initialized = False
-_sentry_enabled = False
-
-# Production trace sample rate (10%)
-PRODUCTION_TRACE_SAMPLE_RATE = 0.1
-
-
-def _get_version() -> str:
-    """
-    Get the application version.
-
-    Tries to read from package.json in the frontend directory,
-    falling back to a default version.
-    """
-    try:
-        # Try to find package.json relative to this file
-        backend_dir = Path(__file__).parent.parent
-        frontend_dir = backend_dir.parent / "frontend"
-        package_json = frontend_dir / "package.json"
-
-        if package_json.exists():
-            import json
-
-            with open(package_json) as f:
-                data = json.load(f)
-                return data.get("version", "0.0.0")
-    except Exception as e:
-        logger.debug(f"Version detection failed: {e}")
-
-    return "0.0.0"
-
-
-def _mask_user_paths(text: str) -> str:
-    """
-    Mask user-specific paths for privacy.
-
-    Replaces usernames in common OS path patterns:
-    - macOS: /Users/username/... becomes /Users/***/...
-    - Windows: C:\\Users\\username\\... becomes C:\\Users\\***\\...
-    - Linux: /home/username/... becomes /home/***/...
-    - WSL: /mnt/c/Users/username/... becomes /mnt/c/Users/***/...
-
-    Note: Project paths remain visible for debugging purposes.
-    """
-    if not text:
-        return text
-
-    # macOS: /Users/username/...
-    text = re.sub(r"/Users/[^/]+(?=/|$)", "/Users/***", text)
-
-    # Windows: C:\Users\username\...
-    text = re.sub(
-        r"[A-Za-z]:\\Users\\[^\\]+(?=\\|$)",
-        lambda m: f"{m.group(0)[0]}:\\Users\\***",
-        text,
-    )
-
-    # Linux: /home/username/...
-    text = re.sub(r"/home/[^/]+(?=/|$)", "/home/***", text)
-
-    # WSL: /mnt/c/Users/username/... (accessing Windows filesystem from WSL)
-    text = re.sub(
-        r"/mnt/[a-z]/Users/[^/]+(?=/|$)",
-        lambda m: f"{m.group(0)[:6]}/Users/***",
-        text,
-    )
-
-    return text
-
-
-def _mask_object_paths(obj: Any, _depth: int = 0) -> Any:
-    """
-    Recursively mask paths in an object.
-
-    Args:
-        obj: The object to mask paths in
-        _depth: Current recursion depth (internal use)
-
-    Returns:
-        Object with paths masked
-    """
-    # Prevent stack overflow on deeply nested or circular structures
-    if _depth > 50:
-        return obj
-
-    if obj is None:
-        return obj
-
-    if isinstance(obj, str):
-        return _mask_user_paths(obj)
-
-    if isinstance(obj, list):
-        return [_mask_object_paths(item, _depth + 1) for item in obj]
-
-    if isinstance(obj, dict):
-        return {
-            key: _mask_object_paths(value, _depth + 1) for key, value in obj.items()
-        }
-
-    return obj
-
-
-def _before_send(event: dict, hint: dict) -> dict | None:
-    """
-    Process event before sending to Sentry.
-
-    Applies privacy masking to all paths in the event.
-    """
-    if not _sentry_enabled:
-        return None
-
-    # Mask paths in exception stack traces
-    if "exception" in event and "values" in event["exception"]:
-        for exception in event["exception"]["values"]:
-            if "stacktrace" in exception and "frames" in exception["stacktrace"]:
-                for frame in exception["stacktrace"]["frames"]:
-                    if "filename" in frame:
-                        frame["filename"] = _mask_user_paths(frame["filename"])
-                    if "abs_path" in frame:
-                        frame["abs_path"] = _mask_user_paths(frame["abs_path"])
-            if "value" in exception:
-                exception["value"] = _mask_user_paths(exception["value"])
-
-    # Mask paths in breadcrumbs
-    if "breadcrumbs" in event:
-        for breadcrumb in event.get("breadcrumbs", {}).get("values", []):
-            if "message" in breadcrumb:
-                breadcrumb["message"] = _mask_user_paths(breadcrumb["message"])
-            if "data" in breadcrumb:
-                breadcrumb["data"] = _mask_object_paths(breadcrumb["data"])
-
-    # Mask paths in message
-    if "message" in event:
-        event["message"] = _mask_user_paths(event["message"])
-
-    # Mask paths in tags
-    if "tags" in event:
-        event["tags"] = _mask_object_paths(event["tags"])
-
-    # Mask paths in contexts
-    if "contexts" in event:
-        event["contexts"] = _mask_object_paths(event["contexts"])
-
-    # Mask paths in extra data
-    if "extra" in event:
-        event["extra"] = _mask_object_paths(event["extra"])
-
-    # Clear user info for privacy
-    if "user" in event:
-        event["user"] = {}
-
-    return event
-
-
-def init_sentry(
-    component: str = "backend",
-    force_enable: bool = False,
-) -> bool:
-    """
-    Initialize Sentry for the Python backend.
-
-    Args:
-        component: Component name for tagging (e.g., "backend", "github-runner")
-        force_enable: Force enable even without packaged app detection
-
-    Returns:
-        True if Sentry was initialized, False otherwise
-    """
-    global _sentry_initialized, _sentry_enabled
-
-    if _sentry_initialized:
-        return _sentry_enabled
-
-    _sentry_initialized = True
-
-    # Get DSN from environment variable
-    dsn = os.environ.get("SENTRY_DSN", "")
-
-    if not dsn:
-        logger.debug("[Sentry] No SENTRY_DSN configured - error reporting disabled")
-        return False
-
-    # Check if we should enable Sentry
-    # Enable if:
-    # - Running from packaged app (detected by __compiled__ or frozen)
-    # - SENTRY_DEV=true is set
-    # - force_enable is True
-    is_packaged = getattr(sys, "frozen", False) or hasattr(sys, "__compiled__")
-    sentry_dev = os.environ.get("SENTRY_DEV", "").lower() in ("true", "1", "yes")
-    should_enable = is_packaged or sentry_dev or force_enable
-
-    if not should_enable:
-        logger.debug(
-            "[Sentry] Development mode - error reporting disabled (set SENTRY_DEV=true to enable)"
-        )
-        return False
-
-    try:
-        import sentry_sdk
-        from sentry_sdk.integrations.logging import LoggingIntegration
-    except ImportError:
-        logger.warning("[Sentry] sentry-sdk not installed - error reporting disabled")
-        return False
-
-    # Get configuration from environment variables
-    version = _get_version()
-    environment = os.environ.get(
-        "SENTRY_ENVIRONMENT", "production" if is_packaged else "development"
-    )
-
-    # Get sample rates
-    traces_sample_rate = PRODUCTION_TRACE_SAMPLE_RATE
-    try:
-        env_rate = os.environ.get("SENTRY_TRACES_SAMPLE_RATE")
-        if env_rate:
-            parsed = float(env_rate)
-            if 0 <= parsed <= 1:
-                traces_sample_rate = parsed
-    except (ValueError, TypeError):
-        pass
-
-    # Configure logging integration to capture errors and warnings
-    logging_integration = LoggingIntegration(
-        level=logging.INFO,  # Capture INFO and above as breadcrumbs
-        event_level=logging.ERROR,  # Send ERROR and above as events
-    )
-
-    # Initialize Sentry
-    sentry_sdk.init(
-        dsn=dsn,
-        environment=environment,
-        release=f"auto-claude@{version}",
-        traces_sample_rate=traces_sample_rate,
-        before_send=_before_send,
-        integrations=[logging_integration],
-        # Don't send PII
-        send_default_pii=False,
-    )
-
-    # Set component tag
-    sentry_sdk.set_tag("component", component)
-
-    _sentry_enabled = True
-    logger.info(
-        f"[Sentry] Backend initialized (component: {component}, release: auto-claude@{version}, traces: {traces_sample_rate})"
-    )
-
-    return True
-
-
-def capture_exception(error: Exception, **kwargs) -> None:
-    """
-    Capture an exception and send to Sentry.
-
-    Safe to call even if Sentry is not initialized.
-
-    Args:
-        error: The exception to capture
-        **kwargs: Additional context to attach to the event
-    """
-    if not _sentry_enabled:
-        logger.error(f"[Sentry] Not enabled, exception not captured: {error}")
-        return
-
-    try:
-        import sentry_sdk
-
-        with sentry_sdk.push_scope() as scope:
-            for key, value in kwargs.items():
-                # Apply defensive path masking for extra data
-                masked_value = (
-                    _mask_object_paths(value)
-                    if isinstance(value, (str, dict, list))
-                    else value
-                )
-                scope.set_extra(key, masked_value)
-            sentry_sdk.capture_exception(error)
-    except ImportError:
-        logger.error(f"[Sentry] SDK not installed, exception not captured: {error}")
-    except Exception as e:
-        logger.error(f"[Sentry] Failed to capture exception: {e}")
-
-
-def capture_message(message: str, level: str = "info", **kwargs) -> None:
-    """
-    Capture a message and send to Sentry.
-
-    Safe to call even if Sentry is not initialized.
-
-    Args:
-        message: The message to capture
-        level: Log level (debug, info, warning, error, fatal)
-        **kwargs: Additional context to attach to the event
-    """
-    if not _sentry_enabled:
-        return
-
-    try:
-        import sentry_sdk
-
-        with sentry_sdk.push_scope() as scope:
-            for key, value in kwargs.items():
-                # Apply defensive path masking for extra data (same as capture_exception)
-                masked_value = (
-                    _mask_object_paths(value)
-                    if isinstance(value, (str, dict, list))
-                    else value
-                )
-                scope.set_extra(key, masked_value)
-            sentry_sdk.capture_message(message, level=level)
-    except ImportError:
-        logger.debug("[Sentry] SDK not installed")
-    except Exception as e:
-        logger.error(f"[Sentry] Failed to capture message: {e}")
-
-
-def set_context(name: str, data: dict) -> None:
-    """
-    Set context data for subsequent events.
-
-    Safe to call even if Sentry is not initialized.
-
-    Args:
-        name: Context name (e.g., "pr_review", "spec")
-        data: Context data dictionary
-    """
-    if not _sentry_enabled:
-        return
-
-    try:
-        import sentry_sdk
-
-        # Apply path masking to context data before sending to Sentry
-        masked_data = _mask_object_paths(data)
-        sentry_sdk.set_context(name, masked_data)
-    except ImportError:
-        logger.debug("[Sentry] SDK not installed")
-    except Exception as e:
-        logger.debug(f"Failed to set context '{name}': {e}")
-
-
-def set_tag(key: str, value: str) -> None:
-    """
-    Set a tag for subsequent events.
-
-    Safe to call even if Sentry is not initialized.
-
-    Args:
-        key: Tag key
-        value: Tag value
-    """
-    if not _sentry_enabled:
-        return
-
-    try:
-        import sentry_sdk
-
-        # Apply path masking to tag value
-        masked_value = _mask_user_paths(value) if isinstance(value, str) else value
-        sentry_sdk.set_tag(key, masked_value)
-    except ImportError:
-        logger.debug("[Sentry] SDK not installed")
-    except Exception as e:
-        logger.debug(f"Failed to set tag '{key}': {e}")
-
-
-def is_enabled() -> bool:
-    """Check if Sentry is enabled."""
-    return _sentry_enabled
-
-
-def is_initialized() -> bool:
-    """Check if Sentry initialization has been attempted."""
-    return _sentry_initialized

apps/backend/core/simple_client.py

@@ -1,106 +0,0 @@
-"""
-Simple Claude SDK Client Factory
-================================
-
-Factory for creating minimal Claude SDK clients for single-turn utility operations
-like commit message generation, merge conflict resolution, and batch analysis.
-
-These clients don't need full security configurations, MCP servers, or hooks.
-Use `create_client()` from `core.client` for full agent sessions with security.
-
-Example usage:
-    from core.simple_client import create_simple_client
-
-    # For commit message generation (text-only, no tools)
-    client = create_simple_client(agent_type="commit_message")
-
-    # For merge conflict resolution (text-only, no tools)
-    client = create_simple_client(agent_type="merge_resolver")
-
-    # For insights extraction (read tools only)
-    client = create_simple_client(agent_type="insights", cwd=project_dir)
-"""
-
-from pathlib import Path
-
-from agents.tools_pkg import get_agent_config, get_default_thinking_level
-from claude_agent_sdk import ClaudeAgentOptions, ClaudeSDKClient
-from core.auth import get_sdk_env_vars, require_auth_token
-from core.client import find_claude_cli
-from phase_config import get_thinking_budget
-
-
-def create_simple_client(
-    agent_type: str = "merge_resolver",
-    model: str = "claude-haiku-4-5-20251001",
-    system_prompt: str | None = None,
-    cwd: Path | None = None,
-    max_turns: int = 1,
-    max_thinking_tokens: int | None = None,
-) -> ClaudeSDKClient:
-    """
-    Create a minimal Claude SDK client for single-turn utility operations.
-
-    This factory creates lightweight clients without MCP servers, security hooks,
-    or full permission configurations. Use for text-only analysis tasks.
-
-    Args:
-        agent_type: Agent type from AGENT_CONFIGS. Determines available tools.
-                   Common utility types:
-                   - "merge_resolver" - Text-only merge conflict analysis
-                   - "commit_message" - Text-only commit message generation
-                   - "insights" - Read-only code insight extraction
-                   - "batch_analysis" - Read-only batch issue analysis
-                   - "batch_validation" - Read-only validation
-        model: Claude model to use (defaults to Haiku for fast/cheap operations)
-        system_prompt: Optional custom system prompt (for specialized tasks)
-        cwd: Working directory for file operations (optional)
-        max_turns: Maximum conversation turns (default: 1 for single-turn)
-        max_thinking_tokens: Override thinking budget (None = use agent default from
-                            AGENT_CONFIGS, converted using phase_config.THINKING_BUDGET_MAP)
-
-    Returns:
-        Configured ClaudeSDKClient for single-turn operations
-
-    Raises:
-        ValueError: If agent_type is not found in AGENT_CONFIGS
-    """
-    # Get authentication
-    oauth_token = require_auth_token()
-    import os
-
-    os.environ["CLAUDE_CODE_OAUTH_TOKEN"] = oauth_token
-
-    # Get environment variables for SDK
-    sdk_env = get_sdk_env_vars()
-
-    # Get agent configuration (raises ValueError if unknown type)
-    config = get_agent_config(agent_type)
-
-    # Get tools from config (no MCP tools for simple clients)
-    allowed_tools = list(config.get("tools", []))
-
-    # Determine thinking budget using the single source of truth (phase_config.py)
-    if max_thinking_tokens is None:
-        thinking_level = get_default_thinking_level(agent_type)
-        max_thinking_tokens = get_thinking_budget(thinking_level)
-
-    # Find Claude CLI path (handles non-standard installations)
-    cli_path = find_claude_cli()
-
-    # Build options dict
-    options_kwargs = {
-        "model": model,
-        "system_prompt": system_prompt,
-        "allowed_tools": allowed_tools,
-        "max_turns": max_turns,
-        "cwd": str(cwd.resolve()) if cwd else None,
-        "env": sdk_env,
-        "max_thinking_tokens": max_thinking_tokens,
-    }
-
-    # Add CLI path if found
-    if cli_path:
-        options_kwargs["cli_path"] = cli_path
-
-    return ClaudeSDKClient(options=ClaudeAgentOptions(**options_kwargs))

apps/backend/core/workspace/models.py

@@ -1,275 +0,0 @@
-#!/usr/bin/env python3
-"""
-Workspace Models
-================
-
-Data classes and enums for workspace management.
-"""
-
-from dataclasses import dataclass
-from enum import Enum
-from pathlib import Path
-
-
-class WorkspaceMode(Enum):
-    """How auto-claude should work."""
-
-    ISOLATED = "isolated"  # Work in a separate worktree (safe)
-    DIRECT = "direct"  # Work directly in user's project
-
-
-class WorkspaceChoice(Enum):
-    """User's choice after build completes."""
-
-    MERGE = "merge"  # Add changes to project
-    REVIEW = "review"  # Show what changed
-    TEST = "test"  # Test the feature in the staging worktree
-    LATER = "later"  # Decide later
-
-
-@dataclass
-class ParallelMergeTask:
-    """A file merge task to be executed in parallel."""
-
-    file_path: str
-    main_content: str
-    worktree_content: str
-    base_content: str | None
-    spec_name: str
-    project_dir: Path
-
-
-@dataclass
-class ParallelMergeResult:
-    """Result of a parallel merge task."""
-
-    file_path: str
-    merged_content: str | None
-    success: bool
-    error: str | None = None
-    was_auto_merged: bool = False  # True if git auto-merged without AI
-
-
-class MergeLockError(Exception):
-    """Raised when a merge lock cannot be acquired."""
-
-    pass
-
-
-class MergeLock:
-    """
-    Context manager for merge locking to prevent concurrent merges.
-
-    Uses a lock file in .auto-claude/ to ensure only one merge operation
-    runs at a time for a given project.
-    """
-
-    def __init__(self, project_dir: Path, spec_name: str):
-        self.project_dir = project_dir
-        self.spec_name = spec_name
-        self.lock_dir = project_dir / ".auto-claude" / ".locks"
-        self.lock_file = self.lock_dir / f"merge-{spec_name}.lock"
-        self.acquired = False
-
-    def __enter__(self):
-        """Acquire the merge lock."""
-        import os
-        import time
-
-        self.lock_dir.mkdir(parents=True, exist_ok=True)
-
-        # Try to acquire lock with timeout
-        max_wait = 30  # seconds
-        start_time = time.time()
-
-        while True:
-            try:
-                # Try to create lock file exclusively
-                fd = os.open(
-                    str(self.lock_file),
-                    os.O_CREAT | os.O_EXCL | os.O_WRONLY,
-                    0o644,
-                )
-                os.close(fd)
-
-                # Write our PID to the lock file
-                self.lock_file.write_text(str(os.getpid()))
-                self.acquired = True
-                return self
-
-            except FileExistsError:
-                # Lock file exists - check if process is still running
-                if self.lock_file.exists():
-                    try:
-                        pid = int(self.lock_file.read_text().strip())
-                        # Import locally to avoid circular dependency
-                        import os as _os
-
-                        try:
-                            _os.kill(pid, 0)
-                            is_running = True
-                        except (OSError, ProcessLookupError):
-                            is_running = False
-
-                        if not is_running:
-                            # Stale lock - remove it
-                            self.lock_file.unlink()
-                            continue
-                    except (ValueError, ProcessLookupError):
-                        # Invalid PID or can't check - remove stale lock
-                        self.lock_file.unlink()
-                        continue
-
-                # Active lock - wait or timeout
-                if time.time() - start_time >= max_wait:
-                    raise MergeLockError(
-                        f"Could not acquire merge lock for {self.spec_name} after {max_wait}s"
-                    )
-
-                time.sleep(0.5)
-
-    def __exit__(self, exc_type, exc_val, exc_tb):
-        """Release the merge lock."""
-        if self.acquired and self.lock_file.exists():
-            try:
-                self.lock_file.unlink()
-            except Exception:
-                pass  # Best effort cleanup
-
-
-class SpecNumberLockError(Exception):
-    """Raised when a spec number lock cannot be acquired."""
-
-    pass
-
-
-class SpecNumberLock:
-    """
-    Context manager for spec number coordination across main project and worktrees.
-
-    Prevents race conditions when creating specs by:
-    1. Acquiring an exclusive file lock
-    2. Scanning ALL spec locations (main + worktrees)
-    3. Finding global maximum spec number
-    4. Allowing atomic spec directory creation
-    5. Releasing lock
-    """
-
-    def __init__(self, project_dir: Path):
-        self.project_dir = project_dir
-        self.lock_dir = project_dir / ".auto-claude" / ".locks"
-        self.lock_file = self.lock_dir / "spec-numbering.lock"
-        self.acquired = False
-        self._global_max: int | None = None
-
-    def __enter__(self) -> "SpecNumberLock":
-        """Acquire the spec numbering lock."""
-        import os
-        import time
-
-        self.lock_dir.mkdir(parents=True, exist_ok=True)
-
-        max_wait = 30  # seconds
-        start_time = time.time()
-
-        while True:
-            try:
-                # Try to create lock file exclusively (atomic operation)
-                fd = os.open(
-                    str(self.lock_file),
-                    os.O_CREAT | os.O_EXCL | os.O_WRONLY,
-                    0o644,
-                )
-                os.close(fd)
-
-                # Write our PID to the lock file
-                self.lock_file.write_text(str(os.getpid()))
-                self.acquired = True
-                return self
-
-            except FileExistsError:
-                # Lock file exists - check if process is still running
-                if self.lock_file.exists():
-                    try:
-                        pid = int(self.lock_file.read_text().strip())
-                        import os as _os
-
-                        try:
-                            _os.kill(pid, 0)
-                            is_running = True
-                        except (OSError, ProcessLookupError):
-                            is_running = False
-
-                        if not is_running:
-                            # Stale lock - remove it
-                            self.lock_file.unlink()
-                            continue
-                    except (ValueError, ProcessLookupError):
-                        # Invalid PID or can't check - remove stale lock
-                        self.lock_file.unlink()
-                        continue
-
-                # Active lock - wait or timeout
-                if time.time() - start_time >= max_wait:
-                    raise SpecNumberLockError(
-                        f"Could not acquire spec numbering lock after {max_wait}s"
-                    )
-
-                time.sleep(0.1)  # Shorter sleep for spec creation
-
-    def __exit__(self, exc_type, exc_val, exc_tb):
-        """Release the spec numbering lock."""
-        if self.acquired and self.lock_file.exists():
-            try:
-                self.lock_file.unlink()
-            except Exception:
-                pass  # Best effort cleanup
-
-    def get_next_spec_number(self) -> int:
-        """
-        Scan all spec locations and return the next available spec number.
-
-        Must be called while lock is held.
-
-        Returns:
-            Next available spec number (global max + 1)
-        """
-        if not self.acquired:
-            raise SpecNumberLockError(
-                "Lock must be acquired before getting next spec number"
-            )
-
-        if self._global_max is not None:
-            return self._global_max + 1
-
-        max_number = 0
-
-        # 1. Scan main project specs
-        main_specs_dir = self.project_dir / ".auto-claude" / "specs"
-        max_number = max(max_number, self._scan_specs_dir(main_specs_dir))
-
-        # 2. Scan all worktree specs
-        worktrees_dir = self.project_dir / ".auto-claude" / "worktrees" / "tasks"
-        if worktrees_dir.exists():
-            for worktree in worktrees_dir.iterdir():
-                if worktree.is_dir():
-                    worktree_specs = worktree / ".auto-claude" / "specs"
-                    max_number = max(max_number, self._scan_specs_dir(worktree_specs))
-
-        self._global_max = max_number
-        return max_number + 1
-
-    def _scan_specs_dir(self, specs_dir: Path) -> int:
-        """Scan a specs directory and return the highest spec number found."""
-        if not specs_dir.exists():
-            return 0
-
-        max_num = 0
-        for folder in specs_dir.glob("[0-9][0-9][0-9]-*"):
-            try:
-                num = int(folder.name[:3])
-                max_num = max(max_num, num)
-            except ValueError:
-                pass
-
-        return max_num

apps/backend/debug.py

@@ -1,40 +0,0 @@
-"""
-Debug module facade.
-
-Provides debug logging utilities for the Auto-Claude framework.
-Re-exports from core.debug for clean imports.
-"""
-
-from core.debug import (
-    Colors,
-    debug,
-    debug_async_timer,
-    debug_detailed,
-    debug_env_status,
-    debug_error,
-    debug_info,
-    debug_section,
-    debug_success,
-    debug_timer,
-    debug_verbose,
-    debug_warning,
-    get_debug_level,
-    is_debug_enabled,
-)
-
-__all__ = [
-    "Colors",
-    "debug",
-    "debug_async_timer",
-    "debug_detailed",
-    "debug_env_status",
-    "debug_error",
-    "debug_info",
-    "debug_section",
-    "debug_success",
-    "debug_timer",
-    "debug_verbose",
-    "debug_warning",
-    "get_debug_level",
-    "is_debug_enabled",
-]

apps/backend/init.py

@@ -1,210 +0,0 @@
-"""
-Auto Claude project initialization utilities.
-
-Handles first-time setup of .auto-claude directory and ensures proper gitignore configuration.
-"""
-
-from pathlib import Path
-
-# All entries that should be added to .gitignore for auto-claude projects
-AUTO_CLAUDE_GITIGNORE_ENTRIES = [
-    ".auto-claude/",
-    ".auto-claude-security.json",
-    ".auto-claude-status",
-    ".claude_settings.json",
-    ".worktrees/",
-    ".security-key",
-    "logs/security/",
-]
-
-
-def _entry_exists_in_gitignore(lines: list[str], entry: str) -> bool:
-    """Check if an entry already exists in gitignore (handles trailing slash variations)."""
-    entry_normalized = entry.rstrip("/")
-    for line in lines:
-        line_stripped = line.strip()
-        # Match both "entry" and "entry/"
-        if (
-            line_stripped == entry
-            or line_stripped == entry_normalized
-            or line_stripped == entry_normalized + "/"
-        ):
-            return True
-    return False
-
-
-def ensure_gitignore_entry(project_dir: Path, entry: str = ".auto-claude/") -> bool:
-    """
-    Ensure an entry exists in the project's .gitignore file.
-
-    Creates .gitignore if it doesn't exist.
-
-    Args:
-        project_dir: The project root directory
-        entry: The gitignore entry to add (default: ".auto-claude/")
-
-    Returns:
-        True if entry was added, False if it already existed
-    """
-    gitignore_path = project_dir / ".gitignore"
-
-    # Check if .gitignore exists and if entry is already present
-    if gitignore_path.exists():
-        content = gitignore_path.read_text()
-        lines = content.splitlines()
-
-        if _entry_exists_in_gitignore(lines, entry):
-            return False  # Already exists
-
-        # Entry doesn't exist, append it
-        # Ensure file ends with newline before adding our entry
-        if content and not content.endswith("\n"):
-            content += "\n"
-
-        # Add a comment and the entry
-        content += "\n# Auto Claude data directory\n"
-        content += entry + "\n"
-
-        gitignore_path.write_text(content)
-        return True
-    else:
-        # Create new .gitignore with the entry
-        content = "# Auto Claude data directory\n"
-        content += entry + "\n"
-
-        gitignore_path.write_text(content)
-        return True
-
-
-def ensure_all_gitignore_entries(project_dir: Path) -> list[str]:
-    """
-    Ensure all auto-claude related entries exist in the project's .gitignore file.
-
-    Creates .gitignore if it doesn't exist.
-
-    Args:
-        project_dir: The project root directory
-
-    Returns:
-        List of entries that were added (empty if all already existed)
-    """
-    gitignore_path = project_dir / ".gitignore"
-    added_entries: list[str] = []
-
-    # Read existing content or start fresh
-    if gitignore_path.exists():
-        content = gitignore_path.read_text()
-        lines = content.splitlines()
-    else:
-        content = ""
-        lines = []
-
-    # Find entries that need to be added
-    entries_to_add = [
-        entry
-        for entry in AUTO_CLAUDE_GITIGNORE_ENTRIES
-        if not _entry_exists_in_gitignore(lines, entry)
-    ]
-
-    if not entries_to_add:
-        return []
-
-    # Build the new content to append
-    # Ensure file ends with newline before adding our entries
-    if content and not content.endswith("\n"):
-        content += "\n"
-
-    content += "\n# Auto Claude generated files\n"
-    for entry in entries_to_add:
-        content += entry + "\n"
-        added_entries.append(entry)
-
-    gitignore_path.write_text(content)
-    return added_entries
-
-
-def init_auto_claude_dir(project_dir: Path) -> tuple[Path, bool]:
-    """
-    Initialize the .auto-claude directory for a project.
-
-    Creates the directory if needed and ensures all auto-claude files are in .gitignore.
-
-    Args:
-        project_dir: The project root directory
-
-    Returns:
-        Tuple of (auto_claude_dir path, gitignore_was_updated)
-    """
-    project_dir = Path(project_dir)
-    auto_claude_dir = project_dir / ".auto-claude"
-
-    # Create the directory if it doesn't exist
-    dir_created = not auto_claude_dir.exists()
-    auto_claude_dir.mkdir(parents=True, exist_ok=True)
-
-    # Ensure all auto-claude entries are in .gitignore (only on first creation)
-    gitignore_updated = False
-    if dir_created:
-        added = ensure_all_gitignore_entries(project_dir)
-        gitignore_updated = len(added) > 0
-    else:
-        # Even if dir exists, check gitignore on first run
-        # Use a marker file to track if we've already checked
-        marker = auto_claude_dir / ".gitignore_checked"
-        if not marker.exists():
-            added = ensure_all_gitignore_entries(project_dir)
-            gitignore_updated = len(added) > 0
-            marker.touch()
-
-    return auto_claude_dir, gitignore_updated
-
-
-def get_auto_claude_dir(project_dir: Path, ensure_exists: bool = True) -> Path:
-    """
-    Get the .auto-claude directory path, optionally ensuring it exists.
-
-    Args:
-        project_dir: The project root directory
-        ensure_exists: If True, create directory and update gitignore if needed
-
-    Returns:
-        Path to the .auto-claude directory
-    """
-    if ensure_exists:
-        auto_claude_dir, _ = init_auto_claude_dir(project_dir)
-        return auto_claude_dir
-
-    return Path(project_dir) / ".auto-claude"
-
-
-def repair_gitignore(project_dir: Path) -> list[str]:
-    """
-    Repair an existing project's .gitignore to include all auto-claude entries.
-
-    This is useful for projects created before all entries were being added,
-    or when gitignore entries were manually removed.
-
-    Also resets the .gitignore_checked marker to allow future updates.
-
-    Args:
-        project_dir: The project root directory
-
-    Returns:
-        List of entries that were added (empty if all already existed)
-    """
-    project_dir = Path(project_dir)
-    auto_claude_dir = project_dir / ".auto-claude"
-
-    # Remove the marker file so future checks will also run
-    marker = auto_claude_dir / ".gitignore_checked"
-    if marker.exists():
-        marker.unlink()
-
-    # Add all missing entries
-    added = ensure_all_gitignore_entries(project_dir)
-
-    # Re-create the marker
-    if auto_claude_dir.exists():
-        marker.touch()
-
-    return added

apps/backend/integrations/graphiti/providers_pkg/embedder_providers/openrouter_embedder.py

@@ -1,60 +0,0 @@
-"""
-OpenRouter Embedder Provider
-=============================
-
-OpenRouter embedder implementation for Graphiti.
-Uses OpenAI-compatible embedding API.
-"""
-
-from typing import TYPE_CHECKING, Any
-
-if TYPE_CHECKING:
-    from ...config import GraphitiConfig
-
-from ..exceptions import ProviderError, ProviderNotInstalled
-
-
-def create_openrouter_embedder(config: "GraphitiConfig") -> Any:
-    """
-    Create OpenRouter embedder client.
-
-    OpenRouter uses OpenAI-compatible API, so we use the OpenAI embedder
-    with custom base URL.
-
-    Args:
-        config: GraphitiConfig with OpenRouter settings
-
-    Returns:
-        OpenAI-compatible embedder instance
-
-    Raises:
-        ProviderNotInstalled: If graphiti-core is not installed
-        ProviderError: If API key is missing
-
-    Example:
-        >>> from auto_claude.integrations.graphiti.config import GraphitiConfig
-        >>> config = GraphitiConfig(
-        ...     openrouter_api_key="sk-or-...",
-        ...     openrouter_embedding_model="openai/text-embedding-3-small"
-        ... )
-        >>> embedder = create_openrouter_embedder(config)
-    """
-    try:
-        from graphiti_core.embedder import EmbedderConfig, OpenAIEmbedder
-    except ImportError as e:
-        raise ProviderNotInstalled(
-            f"OpenRouter provider requires graphiti-core. "
-            f"Install with: pip install graphiti-core\n"
-            f"Error: {e}"
-        )
-
-    if not config.openrouter_api_key:
-        raise ProviderError("OpenRouter provider requires OPENROUTER_API_KEY")
-
-    embedder_config = EmbedderConfig(
-        api_key=config.openrouter_api_key,
-        model=config.openrouter_embedding_model,
-        base_url=config.openrouter_base_url,
-    )
-
-    return OpenAIEmbedder(config=embedder_config)

apps/backend/integrations/graphiti/providers_pkg/llm_providers/openrouter_llm.py

@@ -1,63 +0,0 @@
-"""
-OpenRouter LLM Provider
-=======================
-
-OpenRouter LLM client implementation for Graphiti.
-Uses OpenAI-compatible API.
-"""
-
-from typing import TYPE_CHECKING, Any
-
-if TYPE_CHECKING:
-    from ...config import GraphitiConfig
-
-from ..exceptions import ProviderError, ProviderNotInstalled
-
-
-def create_openrouter_llm_client(config: "GraphitiConfig") -> Any:
-    """
-    Create OpenRouter LLM client.
-
-    OpenRouter uses OpenAI-compatible API, so we use the OpenAI client
-    with custom base URL.
-
-    Args:
-        config: GraphitiConfig with OpenRouter settings
-
-    Returns:
-        OpenAI-compatible LLM client instance
-
-    Raises:
-        ProviderNotInstalled: If graphiti-core is not installed
-        ProviderError: If API key is missing
-
-    Example:
-        >>> from auto_claude.integrations.graphiti.config import GraphitiConfig
-        >>> config = GraphitiConfig(
-        ...     openrouter_api_key="sk-or-...",
-        ...     openrouter_llm_model="anthropic/claude-3.5-sonnet"
-        ... )
-        >>> client = create_openrouter_llm_client(config)
-    """
-    try:
-        from graphiti_core.llm_client.config import LLMConfig
-        from graphiti_core.llm_client.openai_client import OpenAIClient
-    except ImportError as e:
-        raise ProviderNotInstalled(
-            f"OpenRouter provider requires graphiti-core. "
-            f"Install with: pip install graphiti-core\n"
-            f"Error: {e}"
-        )
-
-    if not config.openrouter_api_key:
-        raise ProviderError("OpenRouter provider requires OPENROUTER_API_KEY")
-
-    llm_config = LLMConfig(
-        api_key=config.openrouter_api_key,
-        model=config.openrouter_llm_model,
-        base_url=config.openrouter_base_url,
-    )
-
-    # OpenRouter uses OpenAI-compatible API
-    # Disable reasoning/verbosity for compatibility
-    return OpenAIClient(config=llm_config, reasoning=None, verbosity=None)

apps/backend/integrations/graphiti/queries_pkg/kuzu_driver_patched.py

@@ -1,176 +0,0 @@
-"""
-Patched KuzuDriver that properly creates FTS indexes and fixes parameter handling.
-
-The original graphiti-core KuzuDriver has two bugs:
-1. build_indices_and_constraints() is a no-op, so FTS indexes are never created
-2. execute_query() filters out None parameters, but queries still reference them
-
-This patched driver fixes both issues for LadybugDB compatibility.
-"""
-
-import logging
-import re
-from typing import Any
-
-# Import kuzu (might be real_ladybug via monkeypatch)
-try:
-    import kuzu
-except ImportError:
-    import real_ladybug as kuzu  # type: ignore
-
-logger = logging.getLogger(__name__)
-
-
-def create_patched_kuzu_driver(db: str = ":memory:", max_concurrent_queries: int = 1):
-    from graphiti_core.driver.driver import GraphProvider
-    from graphiti_core.driver.kuzu_driver import KuzuDriver as OriginalKuzuDriver
-    from graphiti_core.graph_queries import get_fulltext_indices
-
-    class PatchedKuzuDriver(OriginalKuzuDriver):
-        """
-        KuzuDriver with proper FTS index creation and parameter handling.
-
-        Fixes two bugs in graphiti-core:
-        1. FTS indexes are never created (build_indices_and_constraints is a no-op)
-        2. None parameters are filtered out, causing "Parameter not found" errors
-        """
-
-        def __init__(
-            self,
-            db: str = ":memory:",
-            max_concurrent_queries: int = 1,
-        ):
-            # Store database path before calling parent (which creates the Database)
-            self._database = db  # Required by Graphiti for group_id checks
-            super().__init__(db, max_concurrent_queries)
-
-        async def execute_query(
-            self, cypher_query_: str, **kwargs: Any
-        ) -> tuple[list[dict[str, Any]] | list[list[dict[str, Any]]], None, None]:
-            """
-            Execute a Cypher query with proper None parameter handling.
-
-            The original driver filters out None values, but LadybugDB requires
-            all referenced parameters to exist. This override keeps None values
-            in the parameters dict.
-            """
-            # Don't filter out None values - LadybugDB needs them
-            params = {k: v for k, v in kwargs.items()}
-            # Still remove these unsupported parameters
-            params.pop("database_", None)
-            params.pop("routing_", None)
-
-            try:
-                results = await self.client.execute(cypher_query_, parameters=params)
-            except Exception as e:
-                # Truncate long values for logging
-                log_params = {
-                    k: (v[:5] if isinstance(v, list) else v) for k, v in params.items()
-                }
-                logger.error(
-                    f"Error executing Kuzu query: {e}\n{cypher_query_}\n{log_params}"
-                )
-                raise
-
-            if not results:
-                return [], None, None
-
-            if isinstance(results, list):
-                dict_results = [list(result.rows_as_dict()) for result in results]
-            else:
-                dict_results = list(results.rows_as_dict())
-            return dict_results, None, None  # type: ignore
-
-        async def build_indices_and_constraints(self, delete_existing: bool = False):
-            """
-            Build FTS indexes required for Graphiti's hybrid search.
-
-            The original KuzuDriver has this as a no-op, but we need to actually
-            create the FTS indexes for search to work.
-
-            Args:
-                delete_existing: If True, drop and recreate indexes (default: False)
-            """
-            logger.info("Building FTS indexes for Kuzu/LadybugDB...")
-
-            # Get the FTS index creation queries from Graphiti
-            fts_queries = get_fulltext_indices(GraphProvider.KUZU)
-
-            # Create a sync connection for index creation
-            conn = kuzu.Connection(self.db)
-
-            try:
-                for query in fts_queries:
-                    try:
-                        # Check if we need to drop existing index first
-                        if delete_existing:
-                            # Extract index name from query
-                            # Format: CALL CREATE_FTS_INDEX('TableName', 'index_name', [...])
-                            match = re.search(
-                                r"CREATE_FTS_INDEX\('([^']+)',\s*'([^']+)'", query
-                            )
-                            if match:
-                                table_name, index_name = match.groups()
-                                drop_query = f"CALL DROP_FTS_INDEX('{table_name}', '{index_name}')"
-                                try:
-                                    conn.execute(drop_query)
-                                    logger.debug(
-                                        f"Dropped existing FTS index: {index_name}"
-                                    )
-                                except Exception:
-                                    # Index might not exist, that's fine
-                                    pass
-
-                        # Create the FTS index
-                        conn.execute(query)
-                        logger.debug(f"Created FTS index: {query[:80]}...")
-
-                    except Exception as e:
-                        error_msg = str(e).lower()
-                        # Handle "index already exists" gracefully
-                        if "already exists" in error_msg or "duplicate" in error_msg:
-                            logger.debug(
-                                f"FTS index already exists (skipping): {query[:60]}..."
-                            )
-                        else:
-                            # Log but don't fail - some indexes might fail in certain Kuzu versions
-                            logger.warning(f"Failed to create FTS index: {e}")
-                            logger.debug(f"Query was: {query}")
-
-                logger.info("FTS indexes created successfully")
-            finally:
-                conn.close()
-
-        def setup_schema(self):
-            """
-            Set up the database schema and install/load the FTS extension.
-
-            Extends the parent setup_schema() to properly set up FTS support.
-            """
-            conn = kuzu.Connection(self.db)
-
-            try:
-                # First, install the FTS extension (required before loading)
-                try:
-                    conn.execute("INSTALL fts")
-                    logger.debug("Installed FTS extension")
-                except Exception as e:
-                    error_msg = str(e).lower()
-                    if "already" not in error_msg:
-                        logger.debug(f"FTS extension install note: {e}")
-
-                # Then load the FTS extension
-                try:
-                    conn.execute("LOAD EXTENSION fts")
-                    logger.debug("Loaded FTS extension")
-                except Exception as e:
-                    error_msg = str(e).lower()
-                    if "already loaded" not in error_msg:
-                        logger.debug(f"FTS extension load note: {e}")
-            finally:
-                conn.close()
-
-            # Run the parent schema setup (creates tables)
-            super().setup_schema()
-
-    return PatchedKuzuDriver(db=db, max_concurrent_queries=max_concurrent_queries)

apps/backend/integrations/graphiti/test_ollama_embedding_memory.py

@@ -1,862 +0,0 @@
-#!/usr/bin/env python3
-"""
-Test Script for Ollama Embedding Memory Integration
-====================================================
-
-This test validates that the memory system works correctly with local Ollama
-embedding models (like embeddinggemma, nomic-embed-text) for creating and
-retrieving memories in the hybrid RAG system.
-
-The test covers:
-1. Ollama embedding generation (direct API test)
-2. Creating memories with Ollama embeddings via GraphitiMemory
-3. Retrieving memories via semantic search
-4. Verifying the full create → store → retrieve cycle
-
-Prerequisites:
-    1. Install Ollama: https://ollama.ai/
-    2. Pull an embedding model:
-       ollama pull embeddinggemma    # 768 dimensions (lightweight)
-       ollama pull nomic-embed-text  # 768 dimensions (good quality)
-    3. Pull an LLM model (for knowledge graph construction):
-       ollama pull deepseek-r1:7b    # or llama3.2:3b, mistral:7b
-    4. Start Ollama server: ollama serve
-    5. Configure environment:
-       export GRAPHITI_ENABLED=true
-       export GRAPHITI_LLM_PROVIDER=ollama
-       export GRAPHITI_EMBEDDER_PROVIDER=ollama
-       export OLLAMA_LLM_MODEL=deepseek-r1:7b
-       export OLLAMA_EMBEDDING_MODEL=embeddinggemma
-       export OLLAMA_EMBEDDING_DIM=768
-
-NOTE: graphiti-core internally uses an OpenAI reranker for search ranking.
-      For full offline operation, set a dummy key: export OPENAI_API_KEY=dummy
-      The reranker will fail at search time, but embedding creation works.
-      For production, use OpenAI API key for best search quality.
-
-Usage:
-    cd apps/backend
-    python integrations/graphiti/test_ollama_embedding_memory.py
-
-    # Run specific tests:
-    python integrations/graphiti/test_ollama_embedding_memory.py --test embeddings
-    python integrations/graphiti/test_ollama_embedding_memory.py --test create
-    python integrations/graphiti/test_ollama_embedding_memory.py --test retrieve
-    python integrations/graphiti/test_ollama_embedding_memory.py --test full-cycle
-"""
-
-import argparse
-import asyncio
-import os
-import shutil
-import sys
-import tempfile
-from datetime import datetime
-from pathlib import Path
-
-# Add auto-claude to path
-auto_claude_dir = Path(__file__).parent.parent.parent
-sys.path.insert(0, str(auto_claude_dir))
-
-# Load .env file
-try:
-    from dotenv import load_dotenv
-
-    env_file = auto_claude_dir / ".env"
-    if env_file.exists():
-        load_dotenv(env_file)
-        print(f"Loaded .env from {env_file}")
-except ImportError:
-    print("Note: python-dotenv not installed, using environment variables only")
-
-
-# ============================================================================
-# Helper Functions
-# ============================================================================
-
-
-def print_header(title: str):
-    """Print a section header."""
-    print("\n" + "=" * 70)
-    print(f"  {title}")
-    print("=" * 70 + "\n")
-
-
-def print_result(label: str, value: str, success: bool = True):
-    """Print a result line."""
-    status = "PASS" if success else "FAIL"
-    print(f"  [{status}] {label}: {value}")
-
-
-def print_info(message: str):
-    """Print an info line."""
-    print(f"  INFO: {message}")
-
-
-def print_step(step: int, message: str):
-    """Print a step indicator."""
-    print(f"\n  Step {step}: {message}")
-
-
-def apply_ladybug_monkeypatch():
-    """Apply LadybugDB monkeypatch for embedded database support."""
-    try:
-        import real_ladybug
-
-        sys.modules["kuzu"] = real_ladybug
-        return True
-    except ImportError:
-        pass
-
-    # Try native kuzu as fallback
-    try:
-        import kuzu  # noqa: F401
-
-        return True
-    except ImportError:
-        return False
-
-
-# ============================================================================
-# Test 1: Ollama Embedding Generation
-# ============================================================================
-
-
-async def test_ollama_embeddings() -> bool:
-    """
-    Test Ollama embedding generation directly via API.
-
-    This validates that Ollama is running and can generate embeddings
-    with the configured model.
-    """
-    print_header("Test 1: Ollama Embedding Generation")
-
-    ollama_model = os.environ.get("OLLAMA_EMBEDDING_MODEL", "embeddinggemma")
-    ollama_base_url = os.environ.get("OLLAMA_BASE_URL", "http://localhost:11434")
-    expected_dim = int(os.environ.get("OLLAMA_EMBEDDING_DIM", "768"))
-
-    print(f"  Ollama Model: {ollama_model}")
-    print(f"  Base URL: {ollama_base_url}")
-    print(f"  Expected Dimension: {expected_dim}")
-    print()
-
-    try:
-        import requests
-    except ImportError:
-        print_result("requests library", "Not installed - pip install requests", False)
-        return False
-
-    # Step 1: Check Ollama is running
-    print_step(1, "Checking Ollama server status")
-    try:
-        resp = requests.get(f"{ollama_base_url}/api/tags", timeout=10)
-        if resp.status_code != 200:
-            print_result(
-                "Ollama server",
-                f"Not responding (status {resp.status_code})",
-                False,
-            )
-            return False
-
-        models = resp.json().get("models", [])
-        model_names = [m.get("name", "") for m in models]
-        print_result("Ollama server", f"Running with {len(models)} models", True)
-
-        # Check if embedding model is available
-        embedding_model_found = any(
-            ollama_model in name or ollama_model.split(":")[0] in name
-            for name in model_names
-        )
-        if not embedding_model_found:
-            print_info(f"Model '{ollama_model}' not found. Available: {model_names}")
-            print_info(f"Pull it with: ollama pull {ollama_model}")
-
-    except requests.exceptions.ConnectionError:
-        print_result(
-            "Ollama server",
-            "Not running - start with 'ollama serve'",
-            False,
-        )
-        return False
-
-    # Step 2: Generate test embedding
-    print_step(2, "Generating test embeddings")
-
-    test_texts = [
-        "This is a test memory about implementing OAuth authentication.",
-        "The user prefers using TypeScript for frontend development.",
-        "A gotcha discovered: always validate JWT tokens on the server side.",
-    ]
-
-    embeddings = []
-    for i, text in enumerate(test_texts):
-        resp = requests.post(
-            f"{ollama_base_url}/api/embeddings",
-            json={"model": ollama_model, "prompt": text},
-            timeout=60,
-        )
-
-        if resp.status_code != 200:
-            print_result(
-                f"Embedding {i + 1}",
-                f"Failed: {resp.status_code} - {resp.text[:100]}",
-                False,
-            )
-            return False
-
-        data = resp.json()
-        embedding = data.get("embedding", [])
-        embeddings.append(embedding)
-
-        print_result(
-            f"Embedding {i + 1}",
-            f"Generated {len(embedding)} dimensions",
-            True,
-        )
-
-    # Step 3: Validate embedding dimensions
-    print_step(3, "Validating embedding dimensions")
-
-    for i, embedding in enumerate(embeddings):
-        if len(embedding) != expected_dim:
-            print_result(
-                f"Embedding {i + 1} dimension",
-                f"Mismatch! Got {len(embedding)}, expected {expected_dim}",
-                False,
-            )
-            print_info(f"Update OLLAMA_EMBEDDING_DIM={len(embedding)} in your config")
-            return False
-        print_result(
-            f"Embedding {i + 1} dimension", f"{len(embedding)} matches expected", True
-        )
-
-    # Step 4: Test embedding similarity (basic sanity check)
-    print_step(4, "Testing embedding similarity")
-
-    def cosine_similarity(a, b):
-        """Calculate cosine similarity between two vectors."""
-        dot_product = sum(x * y for x, y in zip(a, b))
-        norm_a = sum(x * x for x in a) ** 0.5
-        norm_b = sum(x * x for x in b) ** 0.5
-        return dot_product / (norm_a * norm_b) if norm_a and norm_b else 0
-
-    # Generate embedding for a similar query
-    query = "OAuth authentication implementation"
-    resp = requests.post(
-        f"{ollama_base_url}/api/embeddings",
-        json={"model": ollama_model, "prompt": query},
-        timeout=60,
-    )
-    query_embedding = resp.json().get("embedding", [])
-
-    similarities = [cosine_similarity(query_embedding, emb) for emb in embeddings]
-
-    print(f"  Query: '{query}'")
-    print("  Similarities to test texts:")
-    for i, (text, sim) in enumerate(zip(test_texts, similarities)):
-        print(f"    {i + 1}. {sim:.4f} - '{text[:50]}...'")
-
-    # First text (about OAuth) should have highest similarity to OAuth query
-    if similarities[0] > similarities[1] and similarities[0] > similarities[2]:
-        print_result("Semantic similarity", "OAuth query matches OAuth text best", True)
-    else:
-        print_info("Similarity ordering may vary - embeddings are still working")
-
-    print()
-    print_result("Ollama Embeddings", "All tests passed", True)
-    return True
-
-
-# ============================================================================
-# Test 2: Memory Creation with Ollama
-# ============================================================================
-
-
-async def test_memory_creation(test_db_path: Path) -> tuple[Path, Path, bool]:
-    """
-    Test creating memories using GraphitiMemory with Ollama embeddings.
-
-    Returns:
-        Tuple of (spec_dir, project_dir, success)
-    """
-    print_header("Test 2: Memory Creation with Ollama Embeddings")
-
-    # Create test directories
-    spec_dir = test_db_path / "test_spec"
-    project_dir = test_db_path / "test_project"
-    spec_dir.mkdir(parents=True, exist_ok=True)
-    project_dir.mkdir(parents=True, exist_ok=True)
-
-    print(f"  Spec dir: {spec_dir}")
-    print(f"  Project dir: {project_dir}")
-    print(f"  Database path: {test_db_path}")
-    print()
-
-    # Override database path for testing
-    os.environ["GRAPHITI_DB_PATH"] = str(test_db_path / "graphiti_db")
-    os.environ["GRAPHITI_DATABASE"] = "test_ollama_memory"
-
-    try:
-        from integrations.graphiti.memory import GraphitiMemory
-    except ImportError as e:
-        print_result("Import GraphitiMemory", f"Failed: {e}", False)
-        return spec_dir, project_dir, False
-
-    # Step 1: Initialize GraphitiMemory
-    print_step(1, "Initializing GraphitiMemory")
-
-    memory = GraphitiMemory(spec_dir, project_dir)
-    print(f"  Is enabled: {memory.is_enabled}")
-    print(f"  Group ID: {memory.group_id}")
-
-    if not memory.is_enabled:
-        print_result(
-            "GraphitiMemory",
-            "Not enabled - check GRAPHITI_ENABLED=true",
-            False,
-        )
-        return spec_dir, project_dir, False
-
-    init_result = await memory.initialize()
-    if not init_result:
-        print_result("Initialize", "Failed to initialize", False)
-        return spec_dir, project_dir, False
-
-    print_result("Initialize", "SUCCESS", True)
-
-    # Step 2: Save session insights
-    print_step(2, "Saving session insights")
-
-    session_insights = {
-        "subtasks_completed": ["implement-oauth-login", "add-jwt-validation"],
-        "discoveries": {
-            "files_understood": {
-                "auth/oauth.py": "OAuth 2.0 flow implementation with Google/GitHub",
-                "auth/jwt.py": "JWT token generation and validation utilities",
-            },
-            "patterns_found": [
-                "Pattern: Use refresh tokens for long-lived sessions",
-                "Pattern: Store tokens in httpOnly cookies for security",
-            ],
-            "gotchas_encountered": [
-                "Gotcha: Always validate JWT signature on server side",
-                "Gotcha: OAuth state parameter prevents CSRF attacks",
-            ],
-        },
-        "what_worked": [
-            "Using PyJWT for token handling",
-            "Separating OAuth providers into individual modules",
-        ],
-        "what_failed": [],
-        "recommendations_for_next_session": [
-            "Consider adding refresh token rotation",
-            "Add rate limiting to auth endpoints",
-        ],
-    }
-
-    save_result = await memory.save_session_insights(
-        session_num=1, insights=session_insights
-    )
-    print_result(
-        "save_session_insights", "SUCCESS" if save_result else "FAILED", save_result
-    )
-
-    # Step 3: Save patterns
-    print_step(3, "Saving code patterns")
-
-    patterns = [
-        "OAuth implementation uses authorization code flow for web apps",
-        "JWT tokens include user ID, roles, and expiration in payload",
-        "Token refresh happens automatically when access token expires",
-    ]
-
-    for i, pattern in enumerate(patterns):
-        result = await memory.save_pattern(pattern)
-        print_result(f"save_pattern {i + 1}", "SUCCESS" if result else "FAILED", result)
-
-    # Step 4: Save gotchas
-    print_step(4, "Saving gotchas (pitfalls)")
-
-    gotchas = [
-        "Never store config values in frontend code or files checked into git",
-        "API redirect URIs must exactly match the registered URIs",
-        "Cache expiration times should be short for performance (15 min default)",
-    ]
-
-    for i, gotcha in enumerate(gotchas):
-        result = await memory.save_gotcha(gotcha)
-        print_result(f"save_gotcha {i + 1}", "SUCCESS" if result else "FAILED", result)
-
-    # Step 5: Save codebase discoveries
-    print_step(5, "Saving codebase discoveries")
-
-    discoveries = {
-        "api/routes/users.py": "User management API endpoints (list, create, update)",
-        "middleware/logging.py": "Request logging middleware for all routes",
-        "models/user.py": "User model with profile data and role management",
-        "services/notifications.py": "Notification service integrations (email, SMS, push)",
-    }
-
-    discovery_result = await memory.save_codebase_discoveries(discoveries)
-    print_result(
-        "save_codebase_discoveries",
-        "SUCCESS" if discovery_result else "FAILED",
-        discovery_result,
-    )
-
-    # Brief wait for embedding processing
-    print()
-    print_info("Waiting 3 seconds for embedding processing...")
-    await asyncio.sleep(3)
-
-    await memory.close()
-
-    print()
-    print_result("Memory Creation", "All memories saved successfully", True)
-    return spec_dir, project_dir, True
-
-
-# ============================================================================
-# Test 3: Memory Retrieval with Semantic Search
-# ============================================================================
-
-
-async def test_memory_retrieval(spec_dir: Path, project_dir: Path) -> bool:
-    """
-    Test retrieving memories using semantic search with Ollama embeddings.
-
-    This validates that saved memories can be found via semantic similarity.
-    """
-    print_header("Test 3: Memory Retrieval with Semantic Search")
-
-    try:
-        from integrations.graphiti.memory import GraphitiMemory
-    except ImportError as e:
-        print_result("Import GraphitiMemory", f"Failed: {e}", False)
-        return False
-
-    # Step 1: Initialize memory (reconnect)
-    print_step(1, "Reconnecting to GraphitiMemory")
-
-    memory = GraphitiMemory(spec_dir, project_dir)
-    init_result = await memory.initialize()
-
-    if not init_result:
-        print_result("Initialize", "Failed to reconnect", False)
-        return False
-
-    print_result("Initialize", "Reconnected successfully", True)
-
-    # Step 2: Semantic search for API-related content
-    print_step(2, "Searching for API-related memories")
-
-    api_query = "How do the API endpoints work in this project?"
-    results = await memory.get_relevant_context(api_query, num_results=5)
-
-    print(f"  Query: '{api_query}'")
-    print(f"  Found {len(results)} results:")
-
-    api_found = False
-    for i, result in enumerate(results):
-        content = result.get("content", "")[:100]
-        result_type = result.get("type", "unknown")
-        score = result.get("score", 0)
-        print(f"    {i + 1}. [{result_type}] (score: {score:.4f}) {content}...")
-        if "api" in content.lower() or "routes" in content.lower():
-            api_found = True
-
-    if api_found:
-        print_result("API search", "Found API-related content", True)
-    else:
-        print_info("API content may not be in top results - checking other queries")
-
-    # Step 3: Search for middleware-related content
-    print_step(3, "Searching for middleware patterns")
-
-    middleware_query = "middleware and request handling best practices"
-    results = await memory.get_relevant_context(middleware_query, num_results=5)
-
-    print(f"  Query: '{middleware_query}'")
-    print(f"  Found {len(results)} results:")
-
-    middleware_found = False
-    for i, result in enumerate(results):
-        content = result.get("content", "")[:100]
-        result_type = result.get("type", "unknown")
-        score = result.get("score", 0)
-        print(f"    {i + 1}. [{result_type}] (score: {score:.4f}) {content}...")
-        if "middleware" in content.lower() or "routes" in content.lower():
-            middleware_found = True
-
-    print_result(
-        "Middleware search",
-        "Found middleware-related content" if middleware_found else "No direct matches",
-        middleware_found or len(results) > 0,
-    )
-
-    # Step 4: Get session history
-    print_step(4, "Retrieving session history")
-
-    history = await memory.get_session_history(limit=3)
-    print(f"  Found {len(history)} session records:")
-
-    for i, session in enumerate(history):
-        session_num = session.get("session_number", "?")
-        subtasks = session.get("subtasks_completed", [])
-        print(f"    Session {session_num}: {len(subtasks)} subtasks completed")
-        for subtask in subtasks[:3]:
-            print(f"      - {subtask}")
-
-    print_result(
-        "Session history", f"Retrieved {len(history)} sessions", len(history) > 0
-    )
-
-    # Step 5: Get status summary
-    print_step(5, "Memory status summary")
-
-    status = memory.get_status_summary()
-    for key, value in status.items():
-        print(f"    {key}: {value}")
-
-    await memory.close()
-
-    print()
-    all_passed = len(results) > 0 and len(history) > 0
-    print_result(
-        "Memory Retrieval",
-        "All retrieval tests passed" if all_passed else "Some tests had issues",
-        all_passed,
-    )
-    return all_passed
-
-
-# ============================================================================
-# Test 4: Full Create → Store → Retrieve Cycle
-# ============================================================================
-
-
-async def test_full_cycle(test_db_path: Path) -> bool:
-    """
-    Test the complete memory lifecycle:
-    1. Create unique test data
-    2. Store in graph database with Ollama embeddings
-    3. Search and retrieve via semantic similarity
-    4. Verify retrieved data matches what was stored
-    """
-    print_header("Test 4: Full Create-Store-Retrieve Cycle")
-
-    # Create fresh test directories
-    spec_dir = test_db_path / "cycle_test_spec"
-    project_dir = test_db_path / "cycle_test_project"
-    spec_dir.mkdir(parents=True, exist_ok=True)
-    project_dir.mkdir(parents=True, exist_ok=True)
-
-    # Override database path for testing
-    os.environ["GRAPHITI_DB_PATH"] = str(test_db_path / "graphiti_db")
-    os.environ["GRAPHITI_DATABASE"] = "test_full_cycle"
-
-    try:
-        from integrations.graphiti.memory import GraphitiMemory
-    except ImportError as e:
-        print_result("Import", f"Failed: {e}", False)
-        return False
-
-    # Step 1: Create unique test content
-    print_step(1, "Creating unique test content")
-
-    unique_id = datetime.now().strftime("%Y%m%d_%H%M%S")
-    unique_pattern = (
-        f"Unique pattern {unique_id}: Use dependency injection for database connections"
-    )
-    unique_gotcha = f"Unique gotcha {unique_id}: Always close database connections in finally blocks"
-
-    print(f"  Unique ID: {unique_id}")
-    print(f"  Pattern: {unique_pattern[:60]}...")
-    print(f"  Gotcha: {unique_gotcha[:60]}...")
-
-    # Step 2: Store the content
-    print_step(2, "Storing content in memory system")
-
-    memory = GraphitiMemory(spec_dir, project_dir)
-    init_result = await memory.initialize()
-
-    if not init_result:
-        print_result("Initialize", "Failed", False)
-        return False
-
-    print_result("Initialize", "SUCCESS", True)
-
-    pattern_result = await memory.save_pattern(unique_pattern)
-    print_result(
-        "save_pattern", "SUCCESS" if pattern_result else "FAILED", pattern_result
-    )
-
-    gotcha_result = await memory.save_gotcha(unique_gotcha)
-    print_result("save_gotcha", "SUCCESS" if gotcha_result else "FAILED", gotcha_result)
-
-    # Wait for embedding processing
-    print()
-    print_info("Waiting 4 seconds for embedding processing and indexing...")
-    await asyncio.sleep(4)
-
-    # Step 3: Search for the unique content
-    print_step(3, "Searching for unique content")
-
-    # Search for the pattern
-    pattern_query = "dependency injection database connections"
-    pattern_results = await memory.get_relevant_context(pattern_query, num_results=5)
-
-    print(f"  Query: '{pattern_query}'")
-    print(f"  Found {len(pattern_results)} results")
-
-    pattern_found = False
-    for result in pattern_results:
-        content = result.get("content", "")
-        if unique_id in content:
-            pattern_found = True
-            print(f"    MATCH: {content[:80]}...")
-
-    print_result(
-        "Pattern retrieval",
-        f"Found unique pattern (ID: {unique_id})"
-        if pattern_found
-        else "Unique pattern not in top results",
-        pattern_found,
-    )
-
-    # Search for the gotcha
-    gotcha_query = "database connection cleanup finally block"
-    gotcha_results = await memory.get_relevant_context(gotcha_query, num_results=5)
-
-    print(f"  Query: '{gotcha_query}'")
-    print(f"  Found {len(gotcha_results)} results")
-
-    gotcha_found = False
-    for result in gotcha_results:
-        content = result.get("content", "")
-        if unique_id in content:
-            gotcha_found = True
-            print(f"    MATCH: {content[:80]}...")
-
-    print_result(
-        "Gotcha retrieval",
-        f"Found unique gotcha (ID: {unique_id})"
-        if gotcha_found
-        else "Unique gotcha not in top results",
-        gotcha_found,
-    )
-
-    # Step 4: Verify semantic similarity works
-    print_step(4, "Verifying semantic similarity")
-
-    # Search with semantically similar but different wording
-    alt_query = "closing connections properly in error handling"
-    alt_results = await memory.get_relevant_context(alt_query, num_results=3)
-
-    print(f"  Alternative query: '{alt_query}'")
-    print(f"  Found {len(alt_results)} semantically similar results:")
-
-    for i, result in enumerate(alt_results):
-        content = result.get("content", "")[:80]
-        score = result.get("score", 0)
-        print(f"    {i + 1}. (score: {score:.4f}) {content}...")
-
-    semantic_works = len(alt_results) > 0
-    print_result(
-        "Semantic similarity",
-        "Working - found related content" if semantic_works else "No results",
-        semantic_works,
-    )
-
-    await memory.close()
-
-    # Summary
-    print()
-    cycle_passed = (
-        pattern_result
-        and gotcha_result
-        and (pattern_found or gotcha_found or len(alt_results) > 0)
-    )
-    print_result(
-        "Full Cycle Test",
-        "Create-Store-Retrieve cycle verified"
-        if cycle_passed
-        else "Some steps had issues",
-        cycle_passed,
-    )
-
-    return cycle_passed
-
-
-# ============================================================================
-# Main Entry Point
-# ============================================================================
-
-
-async def main():
-    """Run Ollama embedding memory tests."""
-    parser = argparse.ArgumentParser(
-        description="Test Ollama Embedding Memory Integration"
-    )
-    parser.add_argument(
-        "--test",
-        choices=["all", "embeddings", "create", "retrieve", "full-cycle"],
-        default="all",
-        help="Which test to run",
-    )
-    parser.add_argument(
-        "--keep-db",
-        action="store_true",
-        help="Keep test database after completion (default: cleanup)",
-    )
-
-    args = parser.parse_args()
-
-    print("\n" + "=" * 70)
-    print("  OLLAMA EMBEDDING MEMORY TEST SUITE")
-    print("=" * 70)
-
-    # Configuration check
-    print_header("Configuration Check")
-
-    config_items = {
-        "GRAPHITI_ENABLED": os.environ.get("GRAPHITI_ENABLED", ""),
-        "GRAPHITI_LLM_PROVIDER": os.environ.get("GRAPHITI_LLM_PROVIDER", ""),
-        "GRAPHITI_EMBEDDER_PROVIDER": os.environ.get("GRAPHITI_EMBEDDER_PROVIDER", ""),
-        "OLLAMA_LLM_MODEL": os.environ.get("OLLAMA_LLM_MODEL", ""),
-        "OLLAMA_EMBEDDING_MODEL": os.environ.get("OLLAMA_EMBEDDING_MODEL", ""),
-        "OLLAMA_EMBEDDING_DIM": os.environ.get("OLLAMA_EMBEDDING_DIM", ""),
-        "OLLAMA_BASE_URL": os.environ.get("OLLAMA_BASE_URL", "http://localhost:11434"),
-        "OPENAI_API_KEY": "(set)"
-        if os.environ.get("OPENAI_API_KEY")
-        else "(not set - needed for reranker)",
-    }
-
-    all_configured = True
-    required_keys = [
-        "GRAPHITI_ENABLED",
-        "GRAPHITI_LLM_PROVIDER",
-        "GRAPHITI_EMBEDDER_PROVIDER",
-        "OLLAMA_LLM_MODEL",
-        "OLLAMA_EMBEDDING_MODEL",
-    ]
-
-    for key, value in config_items.items():
-        is_optional = key in [
-            "OLLAMA_BASE_URL",
-            "OPENAI_API_KEY",
-            "OLLAMA_EMBEDDING_DIM",
-        ]
-        is_set = bool(value) if not is_optional else True
-        display_value = value or "(not set)"
-        if key == "OPENAI_API_KEY":
-            display_value = value  # Already formatted above
-            is_set = True  # Optional for testing
-        print_result(key, display_value, is_set)
-        if key in required_keys and not bool(os.environ.get(key)):
-            all_configured = False
-
-    if not all_configured:
-        print()
-        print("  Missing required configuration. Please set:")
-        print("    export GRAPHITI_ENABLED=true")
-        print("    export GRAPHITI_LLM_PROVIDER=ollama")
-        print("    export GRAPHITI_EMBEDDER_PROVIDER=ollama")
-        print("    export OLLAMA_LLM_MODEL=deepseek-r1:7b")
-        print("    export OLLAMA_EMBEDDING_MODEL=embeddinggemma")
-        print("    export OLLAMA_EMBEDDING_DIM=768")
-        print("    export OPENAI_API_KEY=dummy  # For graphiti-core reranker")
-        print()
-        return
-
-    # Check LadybugDB
-    if not apply_ladybug_monkeypatch():
-        print()
-        print_result("LadybugDB", "Not installed - pip install real-ladybug", False)
-        return
-
-    print_result("LadybugDB", "Installed", True)
-
-    # Create temp directory for test database
-    test_db_path = Path(tempfile.mkdtemp(prefix="ollama_memory_test_"))
-    print()
-    print_info(f"Test database: {test_db_path}")
-
-    # Run tests
-    test = args.test
-    results = {}
-
-    try:
-        if test in ["all", "embeddings"]:
-            results["embeddings"] = await test_ollama_embeddings()
-
-        spec_dir = None
-        project_dir = None
-
-        if test in ["all", "create"]:
-            spec_dir, project_dir, results["create"] = await test_memory_creation(
-                test_db_path
-            )
-
-        if test in ["all", "retrieve"]:
-            if spec_dir and project_dir:
-                results["retrieve"] = await test_memory_retrieval(spec_dir, project_dir)
-            else:
-                print_info(
-                    "Skipping retrieve test - no spec/project dir from create test"
-                )
-
-        if test in ["all", "full-cycle"]:
-            results["full-cycle"] = await test_full_cycle(test_db_path)
-
-    finally:
-        # Cleanup unless --keep-db specified
-        if not args.keep_db and test_db_path.exists():
-            print()
-            print_info(f"Cleaning up test database: {test_db_path}")
-            shutil.rmtree(test_db_path, ignore_errors=True)
-
-    # Summary
-    print_header("TEST SUMMARY")
-
-    all_passed = True
-    for test_name, passed in results.items():
-        status = "PASSED" if passed else "FAILED"
-        print(f"  {test_name}: {status}")
-        if not passed:
-            all_passed = False
-
-    print()
-    if all_passed:
-        print("  All tests PASSED!")
-        print()
-        print("  The memory system is working correctly with Ollama embeddings.")
-        print("  Memories can be created and retrieved using semantic search.")
-    else:
-        print("  Some tests FAILED. Check the output above for details.")
-        print()
-        print("  Common issues:")
-        print("    - Ollama not running: ollama serve")
-        print("    - Model not pulled: ollama pull embeddinggemma")
-        print("    - Wrong dimension: Update OLLAMA_EMBEDDING_DIM to match model")
-
-    print()
-    print("  Commands:")
-    print("    # Run all tests:")
-    print("    python integrations/graphiti/test_ollama_embedding_memory.py")
-    print()
-    print("    # Run specific test:")
-    print(
-        "    python integrations/graphiti/test_ollama_embedding_memory.py --test embeddings"
-    )
-    print(
-        "    python integrations/graphiti/test_ollama_embedding_memory.py --test full-cycle"
-    )
-    print()
-    print("    # Keep database for inspection:")
-    print("    python integrations/graphiti/test_ollama_embedding_memory.py --keep-db")
-    print()
-
-
-if __name__ == "__main__":
-    asyncio.run(main())

apps/backend/linear_integration.py

@@ -1,22 +0,0 @@
-"""
-Linear integration module facade.
-
-Provides Linear project management integration.
-Re-exports from integrations.linear.integration for clean imports.
-"""
-
-from integrations.linear.integration import (
-    LinearManager,
-    get_linear_manager,
-    is_linear_enabled,
-    prepare_coder_linear_instructions,
-    prepare_planner_linear_instructions,
-)
-
-__all__ = [
-    "LinearManager",
-    "get_linear_manager",
-    "is_linear_enabled",
-    "prepare_coder_linear_instructions",
-    "prepare_planner_linear_instructions",
-]

apps/backend/linear_updater.py

@@ -1,42 +0,0 @@
-"""
-Linear updater module facade.
-
-Provides Linear integration functionality.
-Re-exports from integrations.linear.updater for clean imports.
-"""
-
-from integrations.linear.updater import (
-    LinearTaskState,
-    add_linear_comment,
-    create_linear_task,
-    get_linear_api_key,
-    is_linear_enabled,
-    linear_build_complete,
-    linear_qa_approved,
-    linear_qa_max_iterations,
-    linear_qa_rejected,
-    linear_qa_started,
-    linear_subtask_completed,
-    linear_subtask_failed,
-    linear_task_started,
-    linear_task_stuck,
-    update_linear_status,
-)
-
-__all__ = [
-    "LinearTaskState",
-    "add_linear_comment",
-    "create_linear_task",
-    "get_linear_api_key",
-    "is_linear_enabled",
-    "linear_build_complete",
-    "linear_qa_approved",
-    "linear_qa_max_iterations",
-    "linear_qa_rejected",
-    "linear_qa_started",
-    "linear_subtask_completed",
-    "linear_subtask_failed",
-    "linear_task_started",
-    "linear_task_stuck",
-    "update_linear_status",
-]

apps/backend/merge/file_evolution/modification_tracker.py

@@ -1,395 +0,0 @@
-"""
-Modification Tracking Module
-=============================
-
-Handles recording and analyzing file modifications:
-- Recording task modifications with semantic analysis
-- Refreshing modifications from git worktrees
-- Managing task completion status
-"""
-
-from __future__ import annotations
-
-import logging
-import subprocess
-from datetime import datetime
-from pathlib import Path
-
-from ..semantic_analyzer import SemanticAnalyzer
-from ..types import FileEvolution, TaskSnapshot, compute_content_hash
-from .storage import EvolutionStorage
-
-# Import debug utilities
-try:
-    from debug import debug, debug_warning
-except ImportError:
-
-    def debug(*args, **kwargs):
-        pass
-
-    def debug_warning(*args, **kwargs):
-        pass
-
-
-logger = logging.getLogger(__name__)
-MODULE = "merge.file_evolution.modification_tracker"
-
-
-class ModificationTracker:
-    """
-    Manages tracking of file modifications by tasks.
-
-    Responsibilities:
-    - Record modifications with semantic analysis
-    - Refresh modifications from git worktrees
-    - Mark tasks as completed
-    """
-
-    def __init__(
-        self,
-        storage: EvolutionStorage,
-        semantic_analyzer: SemanticAnalyzer | None = None,
-    ):
-        """
-        Initialize modification tracker.
-
-        Args:
-            storage: Storage manager for file operations
-            semantic_analyzer: Optional pre-configured semantic analyzer
-        """
-        self.storage = storage
-        self.analyzer = semantic_analyzer or SemanticAnalyzer()
-
-    def record_modification(
-        self,
-        task_id: str,
-        file_path: Path | str,
-        old_content: str,
-        new_content: str,
-        evolutions: dict[str, FileEvolution],
-        raw_diff: str | None = None,
-        skip_semantic_analysis: bool = False,
-    ) -> TaskSnapshot | None:
-        """
-        Record a file modification by a task.
-
-        Args:
-            task_id: The task that made the modification
-            file_path: Path to the modified file
-            old_content: File content before modification
-            new_content: File content after modification
-            evolutions: Current evolution data (will be updated)
-            raw_diff: Optional unified diff for reference
-            skip_semantic_analysis: If True, skip expensive semantic analysis.
-                Use this for lightweight file tracking when only conflict
-                detection is needed (not conflict resolution).
-
-        Returns:
-            Updated TaskSnapshot, or None if file not being tracked
-        """
-        rel_path = self.storage.get_relative_path(file_path)
-
-        # Get or create evolution
-        if rel_path not in evolutions:
-            # Debug level: this is expected for files not in baseline (e.g., from main's changes)
-            logger.debug(f"File {rel_path} not in evolution tracking - skipping")
-            return None
-
-        evolution = evolutions.get(rel_path)
-        if not evolution:
-            return None
-
-        # Get existing snapshot or create new one
-        snapshot = evolution.get_task_snapshot(task_id)
-        if not snapshot:
-            snapshot = TaskSnapshot(
-                task_id=task_id,
-                task_intent="",
-                started_at=datetime.now(),
-                content_hash_before=compute_content_hash(old_content),
-            )
-
-        # Analyze semantic changes (or skip for lightweight tracking)
-        if skip_semantic_analysis:
-            # Fast path: just track the file change without analysis
-            # This is used for files that don't have conflicts
-            semantic_changes = []
-            debug(
-                MODULE,
-                f"Skipping semantic analysis for {rel_path} (lightweight tracking)",
-            )
-        else:
-            # Full analysis (only for conflict files)
-            analysis = self.analyzer.analyze_diff(rel_path, old_content, new_content)
-            semantic_changes = analysis.changes
-
-        # Update snapshot
-        snapshot.completed_at = datetime.now()
-        snapshot.content_hash_after = compute_content_hash(new_content)
-        snapshot.semantic_changes = semantic_changes
-        snapshot.raw_diff = raw_diff
-
-        # Update evolution
-        evolution.add_task_snapshot(snapshot)
-
-        logger.info(
-            f"Recorded modification to {rel_path} by {task_id}: "
-            f"{len(semantic_changes)} semantic changes"
-            + (" (lightweight)" if skip_semantic_analysis else "")
-        )
-        return snapshot
-
-    def refresh_from_git(
-        self,
-        task_id: str,
-        worktree_path: Path,
-        evolutions: dict[str, FileEvolution],
-        target_branch: str | None = None,
-        analyze_only_files: set[str] | None = None,
-    ) -> None:
-        """
-        Refresh task snapshots by analyzing git diff from worktree.
-
-        This is useful when we didn't capture real-time modifications
-        and need to retroactively analyze what a task changed.
-
-        Args:
-            task_id: The task identifier
-            worktree_path: Path to the task's worktree
-            evolutions: Current evolution data (will be updated)
-            target_branch: Branch to compare against (default: detect from worktree)
-            analyze_only_files: If provided, only run full semantic analysis on
-                these files. Other files will be tracked with lightweight mode
-                (no semantic analysis). This optimizes performance by only
-                analyzing files that have actual conflicts.
-        """
-        # Determine the target branch to compare against
-        if not target_branch:
-            # Try to detect the base branch from the worktree's upstream
-            target_branch = self._detect_target_branch(worktree_path)
-
-        debug(
-            MODULE,
-            f"refresh_from_git() for task {task_id}",
-            task_id=task_id,
-            worktree_path=str(worktree_path),
-            target_branch=target_branch,
-            analyze_only_files=list(analyze_only_files)[:10]
-            if analyze_only_files
-            else "all",
-        )
-
-        try:
-            # Get the merge-base to accurately identify task-only changes
-            # Using two-dot diff (merge-base..HEAD) returns only files changed by the task,
-            # not files changed on the target branch since divergence
-            merge_base_result = subprocess.run(
-                ["git", "merge-base", target_branch, "HEAD"],
-                cwd=worktree_path,
-                capture_output=True,
-                text=True,
-                check=True,
-            )
-            merge_base = merge_base_result.stdout.strip()
-
-            # Get list of files changed in the worktree since the merge-base
-            result = subprocess.run(
-                ["git", "diff", "--name-only", f"{merge_base}..HEAD"],
-                cwd=worktree_path,
-                capture_output=True,
-                text=True,
-                check=True,
-            )
-            changed_files = [f for f in result.stdout.strip().split("\n") if f]
-
-            debug(
-                MODULE,
-                f"Found {len(changed_files)} changed files",
-                changed_files=changed_files[:10]
-                if len(changed_files) > 10
-                else changed_files,
-            )
-
-            processed_count = 0
-            for file_path in changed_files:
-                try:
-                    # Get the diff for this file (using merge-base for accurate task-only diff)
-                    diff_result = subprocess.run(
-                        ["git", "diff", f"{merge_base}..HEAD", "--", file_path],
-                        cwd=worktree_path,
-                        capture_output=True,
-                        text=True,
-                        check=True,
-                    )
-
-                    # Get content before (from merge-base - the point where task branched)
-                    try:
-                        show_result = subprocess.run(
-                            ["git", "show", f"{merge_base}:{file_path}"],
-                            cwd=worktree_path,
-                            capture_output=True,
-                            text=True,
-                            check=True,
-                        )
-                        old_content = show_result.stdout
-                    except subprocess.CalledProcessError:
-                        # File is new
-                        old_content = ""
-
-                    current_file = worktree_path / file_path
-                    if current_file.exists():
-                        try:
-                            new_content = current_file.read_text(encoding="utf-8")
-                        except UnicodeDecodeError:
-                            new_content = current_file.read_text(
-                                encoding="utf-8", errors="replace"
-                            )
-                    else:
-                        # File was deleted
-                        new_content = ""
-
-                    # Auto-create FileEvolution entry if not already tracked
-                    # This handles retroactive tracking when capture_baselines wasn't called
-                    rel_path = self.storage.get_relative_path(file_path)
-                    if rel_path not in evolutions:
-                        evolutions[rel_path] = FileEvolution(
-                            file_path=rel_path,
-                            baseline_commit=merge_base,
-                            baseline_captured_at=datetime.now(),
-                            baseline_content_hash=compute_content_hash(old_content),
-                            baseline_snapshot_path="",  # Not storing baseline file
-                            task_snapshots=[],
-                        )
-                        debug(
-                            MODULE,
-                            f"Auto-created evolution entry for {rel_path}",
-                            baseline_commit=merge_base[:8],
-                        )
-
-                    # Determine if this file needs full semantic analysis
-                    # If analyze_only_files is provided, only analyze files in that set
-                    # Otherwise, analyze all files (backward compatible)
-                    skip_analysis = False
-                    if analyze_only_files is not None:
-                        skip_analysis = rel_path not in analyze_only_files
-
-                    # Record the modification
-                    self.record_modification(
-                        task_id=task_id,
-                        file_path=file_path,
-                        old_content=old_content,
-                        new_content=new_content,
-                        evolutions=evolutions,
-                        raw_diff=diff_result.stdout,
-                        skip_semantic_analysis=skip_analysis,
-                    )
-                    processed_count += 1
-
-                except subprocess.CalledProcessError as e:
-                    # Log error but continue with remaining files
-                    logger.warning(
-                        f"Failed to process {file_path} in refresh_from_git: {e}"
-                    )
-                    continue
-
-            # Calculate how many files were fully analyzed vs just tracked
-            if analyze_only_files is not None:
-                analyzed_count = len(
-                    [f for f in changed_files if f in analyze_only_files]
-                )
-                tracked_only_count = processed_count - analyzed_count
-                logger.info(
-                    f"Refreshed {processed_count}/{len(changed_files)} files from worktree for task {task_id} "
-                    f"(analyzed: {analyzed_count}, tracked only: {tracked_only_count})"
-                )
-            else:
-                logger.info(
-                    f"Refreshed {processed_count}/{len(changed_files)} files from worktree for task {task_id} "
-                    "(full analysis on all files)"
-                )
-
-        except subprocess.CalledProcessError as e:
-            logger.error(f"Failed to refresh from git: {e}")
-
-    def mark_task_completed(
-        self,
-        task_id: str,
-        evolutions: dict[str, FileEvolution],
-    ) -> None:
-        """
-        Mark a task as completed (set completed_at on all snapshots).
-
-        Args:
-            task_id: The task identifier
-            evolutions: Current evolution data (will be updated)
-        """
-        now = datetime.now()
-        for evolution in evolutions.values():
-            snapshot = evolution.get_task_snapshot(task_id)
-            if snapshot and snapshot.completed_at is None:
-                snapshot.completed_at = now
-
-    def _detect_target_branch(self, worktree_path: Path) -> str:
-        """
-        Detect the base branch to compare against for a worktree.
-
-        This finds the branch that the worktree was created FROM by looking
-        for common branch names (main, master, develop) that have a valid
-        merge-base with the worktree.
-
-        Note: We don't use upstream tracking because that returns the worktree's
-        own branch (e.g., origin/auto-claude/...) rather than the base branch.
-
-        Args:
-            worktree_path: Path to the worktree
-
-        Returns:
-            The detected base branch name, defaults to 'main' if detection fails
-        """
-        # Try common branch names and find which one has a valid merge-base
-        # This is the reliable way to find what branch the worktree diverged from
-        for branch in ["main", "master", "develop"]:
-            try:
-                result = subprocess.run(
-                    ["git", "merge-base", branch, "HEAD"],
-                    cwd=worktree_path,
-                    capture_output=True,
-                    text=True,
-                )
-                if result.returncode == 0:
-                    debug(
-                        MODULE,
-                        f"Detected base branch: {branch}",
-                        worktree_path=str(worktree_path),
-                    )
-                    return branch
-            except subprocess.CalledProcessError:
-                continue
-
-        # Before defaulting to 'main', verify it exists
-        # This handles non-standard projects that use trunk, production, etc.
-        try:
-            result = subprocess.run(
-                ["git", "rev-parse", "--verify", "main"],
-                cwd=worktree_path,
-                capture_output=True,
-                text=True,
-            )
-            if result.returncode == 0:
-                debug_warning(
-                    MODULE,
-                    "Could not find merge-base with standard branches, defaulting to 'main'",
-                    worktree_path=str(worktree_path),
-                )
-                return "main"
-        except subprocess.CalledProcessError:
-            pass  # 'main' branch doesn't exist - fall through to last resort
-
-        # Last resort: use HEAD~10 as a fallback comparison point
-        # This allows modification tracking even on non-standard branch setups
-        debug_warning(
-            MODULE,
-            "No standard base branch found, modification tracking may be limited",
-            worktree_path=str(worktree_path),
-        )
-        return "HEAD~10"

apps/backend/merge/semantic_analyzer.py

@@ -1,149 +0,0 @@
-"""
-Semantic Analyzer
-=================
-
-Analyzes code changes at a semantic level using regex-based heuristics.
-
-This module provides analysis of code changes, extracting meaningful
-semantic changes like "added import", "modified function", "wrapped JSX element"
-rather than line-level diffs.
-"""
-
-from __future__ import annotations
-
-import logging
-from pathlib import Path
-
-from .types import FileAnalysis
-
-# Import debug utilities
-try:
-    from debug import (
-        debug,
-        debug_detailed,
-        debug_success,
-        debug_verbose,
-    )
-except ImportError:
-    # Fallback if debug module not available
-    def debug(*args, **kwargs):
-        pass
-
-    def debug_detailed(*args, **kwargs):
-        pass
-
-    def debug_verbose(*args, **kwargs):
-        pass
-
-    def debug_success(*args, **kwargs):
-        pass
-
-
-logger = logging.getLogger(__name__)
-MODULE = "merge.semantic_analyzer"
-
-# Import regex-based analyzer
-from .semantic_analysis.models import ExtractedElement
-from .semantic_analysis.regex_analyzer import analyze_with_regex
-
-
-class SemanticAnalyzer:
-    """
-    Analyzes code changes at a semantic level using regex-based heuristics.
-
-    Example:
-        analyzer = SemanticAnalyzer()
-        analysis = analyzer.analyze_diff("src/App.tsx", before_code, after_code)
-        for change in analysis.changes:
-            print(f"{change.change_type.value}: {change.target}")
-    """
-
-    def __init__(self):
-        """Initialize the analyzer."""
-        debug(MODULE, "Initializing SemanticAnalyzer (regex-based)")
-
-    def analyze_diff(
-        self,
-        file_path: str,
-        before: str,
-        after: str,
-        task_id: str | None = None,
-    ) -> FileAnalysis:
-        """
-        Analyze the semantic differences between two versions of a file.
-
-        Args:
-            file_path: Path to the file being analyzed
-            before: Content before changes
-            after: Content after changes
-            task_id: Optional task ID for context
-
-        Returns:
-            FileAnalysis containing semantic changes
-        """
-        ext = Path(file_path).suffix.lower()
-
-        debug(
-            MODULE,
-            f"Analyzing diff for {file_path}",
-            file_path=file_path,
-            extension=ext,
-            before_length=len(before),
-            after_length=len(after),
-            task_id=task_id,
-        )
-
-        # Use regex-based analysis
-        analysis = analyze_with_regex(file_path, before, after, ext)
-
-        debug_success(
-            MODULE,
-            f"Analysis complete for {file_path}",
-            changes_found=len(analysis.changes),
-            functions_modified=len(analysis.functions_modified),
-            functions_added=len(analysis.functions_added),
-            imports_added=len(analysis.imports_added),
-            total_lines_changed=analysis.total_lines_changed,
-        )
-
-        # Log each change at verbose level
-        for change in analysis.changes:
-            debug_verbose(
-                MODULE,
-                f"  Change: {change.change_type.value}",
-                target=change.target,
-                location=change.location,
-                lines=f"{change.line_start}-{change.line_end}",
-            )
-
-        return analysis
-
-    def analyze_file(self, file_path: str, content: str) -> FileAnalysis:
-        """
-        Analyze a single file's structure (not a diff).
-
-        Useful for capturing baseline state.
-
-        Args:
-            file_path: Path to the file
-            content: File content
-
-        Returns:
-            FileAnalysis with structural elements (no changes, just structure)
-        """
-        # Analyze against empty string to get all elements as "additions"
-        return self.analyze_diff(file_path, "", content)
-
-    @property
-    def supported_extensions(self) -> set[str]:
-        """Get the set of supported file extensions."""
-        return {".py", ".js", ".jsx", ".ts", ".tsx"}
-
-    def is_supported(self, file_path: str) -> bool:
-        """Check if a file type is supported for semantic analysis."""
-        ext = Path(file_path).suffix.lower()
-        return ext in self.supported_extensions
-
-
-# Re-export ExtractedElement for backwards compatibility
-__all__ = ["SemanticAnalyzer", "ExtractedElement"]

apps/backend/phase_event.py

@@ -1,16 +0,0 @@
-"""
-Phase event facade for frontend synchronization.
-Re-exports from core.phase_event for clean imports.
-"""
-
-from core.phase_event import (
-    PHASE_MARKER_PREFIX,
-    ExecutionPhase,
-    emit_phase,
-)
-
-__all__ = [
-    "PHASE_MARKER_PREFIX",
-    "ExecutionPhase",
-    "emit_phase",
-]

apps/backend/progress.py

@@ -1,36 +0,0 @@
-"""
-Progress tracking module facade.
-
-Provides progress tracking utilities for build execution.
-Re-exports from core.progress for clean imports.
-"""
-
-from core.progress import (
-    count_subtasks,
-    count_subtasks_detailed,
-    format_duration,
-    get_current_phase,
-    get_next_subtask,
-    get_plan_summary,
-    get_progress_percentage,
-    is_build_complete,
-    print_build_complete_banner,
-    print_paused_banner,
-    print_progress_summary,
-    print_session_header,
-)
-
-__all__ = [
-    "count_subtasks",
-    "count_subtasks_detailed",
-    "format_duration",
-    "get_current_phase",
-    "get_next_subtask",
-    "get_plan_summary",
-    "get_progress_percentage",
-    "is_build_complete",
-    "print_build_complete_banner",
-    "print_paused_banner",
-    "print_progress_summary",
-    "print_session_header",
-]

apps/backend/prompts/github/duplicate_detector.md

@@ -1,90 +0,0 @@
-# Duplicate Issue Detector
-
-You are a duplicate issue detection specialist. Your task is to compare a target issue against a list of existing issues and determine if it's a duplicate.
-
-## Detection Strategy
-
-### Semantic Similarity Checks
-1. **Core problem matching**: Same underlying issue, different wording
-2. **Error signature matching**: Same stack traces, error messages
-3. **Feature request overlap**: Same functionality requested
-4. **Symptom matching**: Same symptoms, possibly different root cause
-
-### Similarity Indicators
-
-**Strong indicators (weight: high)**
-- Identical error messages
-- Same stack trace patterns
-- Same steps to reproduce
-- Same affected component
-
-**Moderate indicators (weight: medium)**
-- Similar description of the problem
-- Same area of functionality
-- Same user-facing symptoms
-- Related keywords in title
-
-**Weak indicators (weight: low)**
-- Same labels/tags
-- Same author (not reliable)
-- Similar time of submission
-
-## Comparison Process
-
-1. **Title Analysis**: Compare titles for semantic similarity
-2. **Description Analysis**: Compare problem descriptions
-3. **Technical Details**: Match error messages, stack traces
-4. **Context Analysis**: Same component/feature area
-5. **Comments Review**: Check if someone already mentioned similarity
-
-## Output Format
-
-For each potential duplicate, provide:
-
-```json
-{
-  "is_duplicate": true,
-  "duplicate_of": 123,
-  "confidence": 0.87,
-  "similarity_type": "same_error",
-  "explanation": "Both issues describe the same authentication timeout error occurring after 30 seconds of inactivity. The stack traces in both issues point to the same SessionManager.validateToken() method.",
-  "key_similarities": [
-    "Identical error: 'Session expired unexpectedly'",
-    "Same component: authentication module",
-    "Same trigger: 30-second timeout"
-  ],
-  "key_differences": [
-    "Different browser (Chrome vs Firefox)",
-    "Different user account types"
-  ]
-}
-```
-
-## Confidence Thresholds
-
-- **90%+**: Almost certainly duplicate, strong evidence
-- **80-89%**: Likely duplicate, needs quick verification
-- **70-79%**: Possibly duplicate, needs review
-- **60-69%**: Related but may be distinct issues
-- **<60%**: Not a duplicate
-
-## Important Guidelines
-
-1. **Err on the side of caution**: Only flag high-confidence duplicates
-2. **Consider nuance**: Same symptom doesn't always mean same issue
-3. **Check closed issues**: A "duplicate" might reference a closed issue
-4. **Version matters**: Same issue in different versions might not be duplicate
-5. **Platform specifics**: Platform-specific issues are usually distinct
-
-## Edge Cases
-
-### Not Duplicates Despite Similarity
-- Same feature, different implementation suggestions
-- Same error, different root cause
-- Same area, but distinct bugs
-- General vs specific version of request
-
-### Duplicates Despite Differences
-- Same bug, different reproduction steps
-- Same error message, different contexts
-- Same feature request, different justifications

apps/backend/prompts/github/issue_analyzer.md

@@ -1,112 +0,0 @@
-# Issue Analyzer for Auto-Fix
-
-You are an issue analysis specialist preparing a GitHub issue for automatic fixing. Your task is to extract structured requirements from the issue that can be used to create a development spec.
-
-## Analysis Goals
-
-1. **Understand the request**: What is the user actually asking for?
-2. **Identify scope**: What files/components are affected?
-3. **Define acceptance criteria**: How do we know it's fixed?
-4. **Assess complexity**: How much work is this?
-5. **Identify risks**: What could go wrong?
-
-## Issue Types
-
-### Bug Report Analysis
-Extract:
-- Current behavior (what's broken)
-- Expected behavior (what should happen)
-- Reproduction steps
-- Affected components
-- Environment details
-- Error messages/logs
-
-### Feature Request Analysis
-Extract:
-- Requested functionality
-- Use case/motivation
-- Acceptance criteria
-- UI/UX requirements
-- API changes needed
-- Breaking changes
-
-### Documentation Issue Analysis
-Extract:
-- What's missing/wrong
-- Affected docs
-- Target audience
-- Examples needed
-
-## Output Format
-
-```json
-{
-  "issue_type": "bug",
-  "title": "Concise task title",
-  "summary": "One paragraph summary of what needs to be done",
-  "requirements": [
-    "Fix the authentication timeout after 30 seconds",
-    "Ensure sessions persist correctly",
-    "Add retry logic for failed auth attempts"
-  ],
-  "acceptance_criteria": [
-    "User sessions remain valid for configured duration",
-    "Auth timeout errors no longer occur",
-    "Existing tests pass"
-  ],
-  "affected_areas": [
-    "src/auth/session.ts",
-    "src/middleware/auth.ts"
-  ],
-  "complexity": "standard",
-  "estimated_subtasks": 3,
-  "risks": [
-    "May affect existing session handling",
-    "Need to verify backwards compatibility"
-  ],
-  "needs_clarification": [],
-  "ready_for_spec": true
-}
-```
-
-## Complexity Levels
-
-- **simple**: Single file change, clear fix, < 1 hour
-- **standard**: Multiple files, moderate changes, 1-4 hours
-- **complex**: Architectural changes, many files, > 4 hours
-
-## Readiness Check
-
-Mark `ready_for_spec: true` only if:
-1. Clear understanding of what's needed
-2. Acceptance criteria can be defined
-3. Scope is reasonably bounded
-4. No blocking questions
-
-Mark `ready_for_spec: false` if:
-1. Requirements are ambiguous
-2. Multiple interpretations possible
-3. Missing critical information
-4. Scope is unbounded
-
-## Clarification Questions
-
-When not ready, populate `needs_clarification` with specific questions:
-```json
-{
-  "needs_clarification": [
-    "Should the timeout be configurable or hardcoded?",
-    "Does this need to work for both web and API clients?",
-    "Are there any backwards compatibility concerns?"
-  ],
-  "ready_for_spec": false
-}
-```
-
-## Guidelines
-
-1. **Be specific**: Generic requirements are unhelpful
-2. **Be realistic**: Don't promise more than the issue asks
-3. **Consider edge cases**: Think about what could go wrong
-4. **Identify dependencies**: Note if other work is needed first
-5. **Keep scope focused**: Flag feature creep for separate issues

apps/backend/prompts/github/issue_triager.md

@@ -1,199 +0,0 @@
-# Issue Triage Agent
-
-You are an expert issue triage assistant. Your goal is to classify GitHub issues, detect problems (duplicates, spam, feature creep), and suggest appropriate labels.
-
-## Classification Categories
-
-### Primary Categories
-- **bug**: Something is broken or not working as expected
-- **feature**: New functionality request
-- **documentation**: Docs improvements, corrections, or additions
-- **question**: User needs help or clarification
-- **duplicate**: Issue duplicates an existing issue
-- **spam**: Promotional content, gibberish, or abuse
-- **feature_creep**: Multiple unrelated requests bundled together
-
-## Detection Criteria
-
-### Duplicate Detection
-Consider an issue a duplicate if:
-- Same core problem described differently
-- Same feature request with different wording
-- Same question asked multiple ways
-- Similar stack traces or error messages
-- **Confidence threshold: 80%+**
-
-When detecting duplicates:
-1. Identify the original issue number
-2. Explain the similarity clearly
-3. Suggest closing with a link to the original
-
-### Spam Detection
-Flag as spam if:
-- Promotional content or advertising
-- Random characters or gibberish
-- Content unrelated to the project
-- Abusive or offensive language
-- Mass-submitted template content
-- **Confidence threshold: 75%+**
-
-When detecting spam:
-1. Don't engage with the content
-2. Recommend the `triage:needs-review` label
-3. Do not recommend auto-close (human decision)
-
-### Feature Creep Detection
-Flag as feature creep if:
-- Multiple unrelated features in one issue
-- Scope too large for a single issue
-- Mixing bugs with feature requests
-- Requesting entire systems/overhauls
-- **Confidence threshold: 70%+**
-
-When detecting feature creep:
-1. Identify the separate concerns
-2. Suggest how to break down the issue
-3. Add `triage:needs-breakdown` label
-
-## Priority Assessment
-
-### High Priority
-- Security vulnerabilities
-- Data loss potential
-- Breaks core functionality
-- Affects many users
-- Regression from previous version
-
-### Medium Priority
-- Feature requests with clear use case
-- Non-critical bugs
-- Performance issues
-- UX improvements
-
-### Low Priority
-- Minor enhancements
-- Edge cases
-- Cosmetic issues
-- "Nice to have" features
-
-## Label Taxonomy
-
-### Type Labels
-- `type:bug` - Bug report
-- `type:feature` - Feature request
-- `type:docs` - Documentation
-- `type:question` - Question or support
-
-### Priority Labels
-- `priority:high` - Urgent/important
-- `priority:medium` - Normal priority
-- `priority:low` - Nice to have
-
-### Triage Labels
-- `triage:potential-duplicate` - May be duplicate (needs human review)
-- `triage:needs-review` - Needs human review (spam/quality)
-- `triage:needs-breakdown` - Feature creep, needs splitting
-- `triage:needs-info` - Missing information
-
-### Component Labels (if applicable)
-- `component:frontend` - Frontend/UI related
-- `component:backend` - Backend/API related
-- `component:cli` - CLI related
-- `component:docs` - Documentation related
-
-### Platform Labels (if applicable)
-- `platform:windows`
-- `platform:macos`
-- `platform:linux`
-
-## Output Format
-
-Output a single JSON object:
-
-```json
-{
-  "category": "bug",
-  "confidence": 0.92,
-  "priority": "high",
-  "labels_to_add": ["type:bug", "priority:high", "component:backend"],
-  "labels_to_remove": [],
-  "is_duplicate": false,
-  "duplicate_of": null,
-  "is_spam": false,
-  "is_feature_creep": false,
-  "suggested_breakdown": [],
-  "comment": null
-}
-```
-
-### When Duplicate
-```json
-{
-  "category": "duplicate",
-  "confidence": 0.85,
-  "priority": "low",
-  "labels_to_add": ["triage:potential-duplicate"],
-  "labels_to_remove": [],
-  "is_duplicate": true,
-  "duplicate_of": 123,
-  "is_spam": false,
-  "is_feature_creep": false,
-  "suggested_breakdown": [],
-  "comment": "This appears to be a duplicate of #123 which addresses the same authentication timeout issue."
-}
-```
-
-### When Feature Creep
-```json
-{
-  "category": "feature_creep",
-  "confidence": 0.78,
-  "priority": "medium",
-  "labels_to_add": ["triage:needs-breakdown", "type:feature"],
-  "labels_to_remove": [],
-  "is_duplicate": false,
-  "duplicate_of": null,
-  "is_spam": false,
-  "is_feature_creep": true,
-  "suggested_breakdown": [
-    "Issue 1: Add dark mode support",
-    "Issue 2: Implement custom themes",
-    "Issue 3: Add color picker for accent colors"
-  ],
-  "comment": "This issue contains multiple distinct feature requests. Consider splitting into separate issues for better tracking."
-}
-```
-
-### When Spam
-```json
-{
-  "category": "spam",
-  "confidence": 0.95,
-  "priority": "low",
-  "labels_to_add": ["triage:needs-review"],
-  "labels_to_remove": [],
-  "is_duplicate": false,
-  "duplicate_of": null,
-  "is_spam": true,
-  "is_feature_creep": false,
-  "suggested_breakdown": [],
-  "comment": null
-}
-```
-
-## Guidelines
-
-1. **Be conservative**: When in doubt, don't flag as duplicate/spam
-2. **Provide reasoning**: Explain why you made classification decisions
-3. **Consider context**: New contributors may write unclear issues
-4. **Human in the loop**: Flag for review, don't auto-close
-5. **Be helpful**: If missing info, suggest what's needed
-6. **Cross-reference**: Check potential duplicates list carefully
-
-## Important Notes
-
-- Never suggest closing issues automatically
-- Labels are suggestions, not automatic applications
-- Comment field is optional - only add if truly helpful
-- Confidence should reflect genuine certainty (0.0-1.0)
-- When uncertain, use `triage:needs-review` label

apps/backend/prompts/github/pr_ai_triage.md

@@ -1,183 +0,0 @@
-# AI Comment Triage Agent
-
-## Your Role
-
-You are a senior engineer triaging comments left by **other AI code review tools** on this PR. Your job is to:
-
-1. **Verify each AI comment** - Is this a genuine issue or a false positive?
-2. **Assign a verdict** - Should the developer address this or ignore it?
-3. **Provide reasoning** - Explain why you agree or disagree with the AI's assessment
-4. **Draft a response** - Craft a helpful reply to post on the PR
-
-## Why This Matters
-
-AI code review tools (CodeRabbit, Cursor, Greptile, Copilot, etc.) are helpful but have high false positive rates (60-80% industry average). Developers waste time addressing non-issues. Your job is to:
-
-- **Amplify genuine issues** that the AI correctly identified
-- **Dismiss false positives** so developers can focus on real problems
-- **Add context** the AI may have missed (codebase conventions, intent, etc.)
-
-## Verdict Categories
-
-### CRITICAL
-The AI found a genuine, important issue that **must be addressed before merge**.
-
-Use when:
-- AI correctly identified a security vulnerability
-- AI found a real bug that will cause production issues
-- AI spotted a breaking change the author missed
-- The issue is verified and has real impact
-
-### IMPORTANT
-The AI found a valid issue that **should be addressed**.
-
-Use when:
-- AI found a legitimate code quality concern
-- The suggestion would meaningfully improve the code
-- It's a valid point but not blocking merge
-- Test coverage or documentation gaps are real
-
-### NICE_TO_HAVE
-The AI's suggestion is valid but **optional**.
-
-Use when:
-- AI suggests a refactor that would improve code but isn't necessary
-- Performance optimization that's not critical
-- Style improvements beyond project conventions
-- Valid suggestion but low priority
-
-### TRIVIAL
-The AI's comment is **not worth addressing**.
-
-Use when:
-- Style/formatting preferences that don't match project conventions
-- Overly pedantic suggestions (variable naming micro-preferences)
-- Suggestions that would add complexity without clear benefit
-- Comment is technically correct but practically irrelevant
-
-### FALSE_POSITIVE
-The AI is **wrong** about this.
-
-Use when:
-- AI misunderstood the code's intent
-- AI flagged a pattern that is intentional and correct
-- AI suggested a fix that would introduce bugs
-- AI missed context that makes the "issue" not an issue
-- AI duplicated another tool's comment
-
-## Evaluation Framework
-
-For each AI comment, analyze:
-
-### 1. Is the issue real?
-- Does the AI correctly understand what the code does?
-- Is there actually a problem, or is this working as intended?
-- Did the AI miss important context (comments, related code, conventions)?
-
-### 2. What's the actual severity?
-- AI tools often over-classify severity (e.g., "critical" for style issues)
-- Consider: What happens if this isn't fixed?
-- Is this a production risk or a minor annoyance?
-
-### 3. Is the fix correct?
-- Would the AI's suggested fix actually work?
-- Does it follow the project's patterns and conventions?
-- Would the fix introduce new problems?
-
-### 4. Is this actionable?
-- Can the developer actually do something about this?
-- Is the suggestion specific enough to implement?
-- Is the effort worth the benefit?
-
-## Output Format
-
-Return a JSON array with your triage verdict for each AI comment:
-
-```json
-[
-  {
-    "comment_id": 12345678,
-    "tool_name": "CodeRabbit",
-    "original_summary": "Potential SQL injection in user search query",
-    "verdict": "critical",
-    "reasoning": "CodeRabbit correctly identified a SQL injection vulnerability. The searchTerm parameter is directly concatenated into the SQL string without sanitization. This is exploitable and must be fixed.",
-    "response_comment": "Verified: Critical security issue. The SQL injection vulnerability is real and exploitable. Use parameterized queries to fix this before merging."
-  },
-  {
-    "comment_id": 12345679,
-    "tool_name": "Greptile",
-    "original_summary": "Function should be named getUserById instead of getUser",
-    "verdict": "trivial",
-    "reasoning": "This is a naming preference that doesn't match our codebase conventions. Our project uses shorter names like getUser() consistently. The AI's suggestion would actually make this inconsistent with the rest of the codebase.",
-    "response_comment": "Style preference - our codebase consistently uses shorter function names like getUser(). No change needed."
-  },
-  {
-    "comment_id": 12345680,
-    "tool_name": "Cursor",
-    "original_summary": "Missing error handling in API call",
-    "verdict": "important",
-    "reasoning": "Valid concern. The API call lacks try/catch and the error could bubble up unhandled. However, there's a global error boundary, so it's not critical but should be addressed for better error messages.",
-    "response_comment": "Valid point. Adding explicit error handling would improve the error message UX, though the global boundary catches it. Recommend addressing but not blocking."
-  },
-  {
-    "comment_id": 12345681,
-    "tool_name": "CodeRabbit",
-    "original_summary": "Unused import detected",
-    "verdict": "false_positive",
-    "reasoning": "The import IS used - it's a type import used in the function signature on line 45. The AI's static analysis missed the type-only usage.",
-    "response_comment": "False positive - this import is used for TypeScript type annotations (line 45). The import is correctly present."
-  }
-]
-```
-
-## Field Definitions
-
-- **comment_id**: The GitHub comment ID (for posting replies)
-- **tool_name**: Which AI tool made the comment (CodeRabbit, Cursor, Greptile, etc.)
-- **original_summary**: Brief summary of what the AI flagged (max 100 chars)
-- **verdict**: `critical` | `important` | `nice_to_have` | `trivial` | `false_positive`
-- **reasoning**: Your analysis of why you agree/disagree (2-3 sentences)
-- **response_comment**: The reply to post on GitHub (concise, helpful, professional)
-
-## Response Comment Guidelines
-
-**Keep responses concise and professional:**
-
-- **CRITICAL**: "Verified: Critical issue. [Why it matters]. Must fix before merge."
-- **IMPORTANT**: "Valid point. [Brief reasoning]. Recommend addressing but not blocking."
-- **NICE_TO_HAVE**: "Valid suggestion. [Context]. Optional improvement."
-- **TRIVIAL**: "Style preference. [Why it doesn't apply]. No change needed."
-- **FALSE_POSITIVE**: "False positive - [brief explanation of why the AI is wrong]."
-
-**Avoid:**
-- Lengthy explanations (developers are busy)
-- Condescending tone toward either the AI or the developer
-- Vague verdicts without reasoning
-- Simply agreeing/disagreeing without explanation
-
-## Important Notes
-
-1. **Be decisive** - Don't hedge with "maybe" or "possibly". Make a clear call.
-2. **Consider context** - The AI may have missed project conventions or intent
-3. **Validate claims** - If AI says "this will crash", verify it actually would
-4. **Don't pile on** - If multiple AIs flagged the same thing, triage once
-5. **Respect the developer** - They may have reasons the AI doesn't understand
-6. **Focus on impact** - What actually matters for shipping quality software?
-
-## Example Triage Scenarios
-
-### AI: "This function is too long (50+ lines)"
-**Your analysis**: Check the function. Is it actually complex, or is it a single linear flow? Does the project have other similar functions? If it's a data transformation with clear steps, length alone isn't an issue.
-**Possible verdicts**: `nice_to_have` (if genuinely complex), `trivial` (if simple linear flow)
-
-### AI: "Missing null check could cause crash"
-**Your analysis**: Trace the data flow. Is this value ever actually null? Is there validation upstream? Is this in a try/catch? TypeScript non-null assertion might be intentional.
-**Possible verdicts**: `important` (if genuinely nullable), `false_positive` (if upstream guarantees non-null)
-
-### AI: "This pattern is inefficient, use X instead"
-**Your analysis**: Is the inefficiency measurable? Is this a hot path? Does the "efficient" pattern sacrifice readability? Is the AI's suggested pattern even correct for this use case?
-**Possible verdicts**: `nice_to_have` (if valid optimization), `trivial` (if premature optimization), `false_positive` (if AI's suggestion is wrong)
-
-### AI: "Security: User input not sanitized"
-**Your analysis**: Is this actually user input or internal data? Is there sanitization elsewhere (middleware, framework)? What's the actual attack vector?
-**Possible verdicts**: `critical` (if genuine vulnerability), `false_positive` (if input is trusted/sanitized elsewhere)

apps/backend/prompts/github/pr_codebase_fit_agent.md

@@ -1,220 +0,0 @@
-# Codebase Fit Review Agent
-
-You are a focused codebase fit review agent. You have been spawned by the orchestrating agent to verify that new code fits well within the existing codebase, follows established patterns, and doesn't reinvent existing functionality.
-
-## Your Mission
-
-Ensure new code integrates well with the existing codebase. Check for consistency with project conventions, reuse of existing utilities, and architectural alignment. Focus ONLY on codebase fit - not security, logic correctness, or general quality.
-
-## CRITICAL: PR Scope and Context
-
-### What IS in scope (report these issues):
-1. **Codebase fit issues in changed code** - New code not following project patterns
-2. **Missed reuse opportunities** - "Existing `utils.ts` has a helper for this"
-3. **Inconsistent with PR's own changes** - "You used `camelCase` here but `snake_case` elsewhere in the PR"
-4. **Breaking conventions in touched areas** - "Your change deviates from the pattern in this file"
-
-### What is NOT in scope (do NOT report):
-1. **Pre-existing inconsistencies** - Old code that doesn't follow patterns
-2. **Unrelated suggestions** - Don't suggest patterns for code the PR didn't touch
-
-**Key distinction:**
-- ✅ "Your new component doesn't follow the existing pattern in `components/`" - GOOD
-- ✅ "Consider using existing `formatDate()` helper instead of new implementation" - GOOD
-- ❌ "The old `legacy/` folder uses different naming conventions" - BAD (pre-existing)
-
-## Codebase Fit Focus Areas
-
-### 1. Naming Conventions
-- **Inconsistent Naming**: Using `camelCase` when project uses `snake_case`
-- **Different Terminology**: Using `user` when codebase uses `account`
-- **Abbreviation Mismatch**: Using `usr` when codebase spells out `user`
-- **File Naming**: `MyComponent.tsx` vs `my-component.tsx` vs `myComponent.tsx`
-- **Directory Structure**: Placing files in wrong directories
-
-### 2. Pattern Adherence
-- **Framework Patterns**: Not following React hooks pattern, Django views pattern, etc.
-- **Project Patterns**: Not following established error handling, logging, or API patterns
-- **Architectural Patterns**: Violating layer separation (e.g., business logic in controllers)
-- **State Management**: Using different state management approach than established
-- **Configuration Patterns**: Different config file format or location
-
-### 3. Ecosystem Fit
-- **Reinventing Utilities**: Writing new helper when similar one exists
-- **Duplicate Functionality**: Adding code that duplicates existing implementation
-- **Ignoring Shared Code**: Not using established shared components/utilities
-- **Wrong Abstraction Level**: Creating too specific or too generic solutions
-- **Missing Integration**: Not integrating with existing systems (logging, metrics, etc.)
-
-### 4. Architectural Consistency
-- **Layer Violations**: Calling database directly from UI components
-- **Dependency Direction**: Wrong dependency direction between modules
-- **Module Boundaries**: Crossing module boundaries inappropriately
-- **API Contracts**: Breaking established API patterns
-- **Data Flow**: Different data flow pattern than established
-
-### 5. Monolithic File Detection
-- **Large Files**: Files exceeding 500 lines (should be split)
-- **God Objects**: Classes/modules doing too many unrelated things
-- **Mixed Concerns**: UI, business logic, and data access in same file
-- **Excessive Exports**: Files exporting too many unrelated items
-
-### 6. Import/Dependency Patterns
-- **Import Style**: Relative vs absolute imports, import grouping
-- **Circular Dependencies**: Creating import cycles
-- **Unused Imports**: Adding imports that aren't used
-- **Dependency Injection**: Not following DI patterns when established
-
-## Review Guidelines
-
-### High Confidence Only
-- Only report findings with **>80% confidence**
-- Verify pattern exists in codebase before flagging deviation
-- Consider if "inconsistency" might be intentional improvement
-
-### Severity Classification (All block merge except LOW)
-- **CRITICAL** (Blocker): Architectural violation that will cause maintenance problems
-  - Example: Tight coupling that makes testing impossible
-  - **Blocks merge: YES**
-- **HIGH** (Required): Significant deviation from established patterns
-  - Example: Reimplementing existing utility, wrong directory structure
-  - **Blocks merge: YES**
-- **MEDIUM** (Recommended): Inconsistency that affects maintainability
-  - Example: Different naming convention, unused existing helper
-  - **Blocks merge: YES** (AI fixes quickly, so be strict about quality)
-- **LOW** (Suggestion): Minor convention deviation
-  - Example: Different import ordering, minor naming variation
-  - **Blocks merge: NO** (optional polish)
-
-### Check Before Reporting
-Before flagging a "should use existing utility" issue:
-1. Verify the existing utility actually does what the new code needs
-2. Check if existing utility has the right signature/behavior
-3. Consider if the new implementation is intentionally different
-
-## Code Patterns to Flag
-
-### Reinventing Existing Utilities
-```javascript
-// If codebase has: src/utils/format.ts with formatDate()
-// Flag this:
-function formatDateString(date) {
-  return `${date.getMonth()}/${date.getDate()}/${date.getFullYear()}`;
-}
-// Should use: import { formatDate } from '@/utils/format';
-```
-
-### Naming Convention Violations
-```python
-# If codebase uses snake_case:
-def getUserById(user_id):  # Should be: get_user_by_id
-    ...
-
-# If codebase uses specific terminology:
-class Customer:  # Should be: User (if that's the codebase term)
-    ...
-```
-
-### Architectural Violations
-```typescript
-// If codebase separates concerns:
-// In UI component:
-const users = await db.query('SELECT * FROM users');  // BAD
-// Should use: const users = await userService.getAll();
-
-// If codebase has established API patterns:
-app.get('/user', ...)      // BAD: singular
-app.get('/users', ...)     // GOOD: matches codebase plural pattern
-```
-
-### Monolithic Files
-```typescript
-// File with 800 lines doing:
-// - API handlers
-// - Business logic
-// - Database queries
-// - Utility functions
-// Should be split into separate files per concern
-```
-
-### Import Pattern Violations
-```javascript
-// If codebase uses absolute imports:
-import { User } from '../../../models/user';  // BAD
-import { User } from '@/models/user';          // GOOD
-
-// If codebase groups imports:
-// 1. External packages
-// 2. Internal modules
-// 3. Relative imports
-```
-
-## Output Format
-
-Provide findings in JSON format:
-
-```json
-[
-  {
-    "file": "src/components/UserCard.tsx",
-    "line": 15,
-    "title": "Reinventing existing date formatting utility",
-    "description": "This file implements custom date formatting, but the codebase already has `formatDate()` in `src/utils/date.ts` that does the same thing.",
-    "category": "codebase_fit",
-    "severity": "high",
-    "existing_code": "src/utils/date.ts:formatDate()",
-    "suggested_fix": "Replace custom implementation with: import { formatDate } from '@/utils/date';",
-    "confidence": 92
-  },
-  {
-    "file": "src/api/customers.ts",
-    "line": 1,
-    "title": "File uses 'customer' but codebase uses 'user'",
-    "description": "This file uses 'customer' terminology but the rest of the codebase consistently uses 'user'. This creates confusion and makes search/navigation harder.",
-    "category": "codebase_fit",
-    "severity": "medium",
-    "codebase_pattern": "src/models/user.ts, src/api/users.ts, src/services/userService.ts",
-    "suggested_fix": "Rename to use 'user' terminology to match codebase conventions",
-    "confidence": 88
-  },
-  {
-    "file": "src/services/orderProcessor.ts",
-    "line": 1,
-    "title": "Monolithic file exceeds 500 lines",
-    "description": "This file is 847 lines and contains order validation, payment processing, inventory management, and notification sending. Each should be separate.",
-    "category": "codebase_fit",
-    "severity": "high",
-    "current_lines": 847,
-    "suggested_fix": "Split into: orderValidator.ts, paymentProcessor.ts, inventoryManager.ts, notificationService.ts",
-    "confidence": 95
-  }
-]
-```
-
-## Important Notes
-
-1. **Verify Existing Code**: Before flagging "use existing", verify the existing code actually fits
-2. **Check Codebase Patterns**: Look at multiple files to confirm a pattern exists
-3. **Consider Evolution**: Sometimes new code is intentionally better than existing patterns
-4. **Respect Domain Boundaries**: Different domains might have different conventions
-5. **Focus on Changed Files**: Don't audit the entire codebase, focus on new/modified code
-
-## What NOT to Report
-
-- Security issues (handled by security agent)
-- Logic correctness (handled by logic agent)
-- Code quality metrics (handled by quality agent)
-- Personal preferences about patterns
-- Style issues covered by linters
-- Test files that intentionally have different structure
-
-## Codebase Analysis Tips
-
-When analyzing codebase fit, look at:
-1. **Similar Files**: How are other similar files structured?
-2. **Shared Utilities**: What's in `utils/`, `helpers/`, `shared/`?
-3. **Naming Patterns**: What naming style do existing files use?
-4. **Directory Structure**: Where do similar files live?
-5. **Import Patterns**: How do other files import dependencies?
-
-Focus on **codebase consistency** - new code fitting seamlessly with existing code.

apps/backend/prompts/github/pr_finding_validator.md

@@ -1,214 +0,0 @@
-# Finding Validator Agent
-
-You are a finding re-investigator using EVIDENCE-BASED VALIDATION. For each unresolved finding from a previous PR review, you must actively investigate whether it is a REAL issue or a FALSE POSITIVE.
-
-**Core Principle: Evidence, not confidence scores.** Either you can prove the issue exists with actual code, or you can't. There is no middle ground.
-
-Your job is to prevent false positives from persisting indefinitely by actually reading the code and verifying the issue exists.
-
-## CRITICAL: Check PR Scope First
-
-**Before investigating any finding, verify it's within THIS PR's scope:**
-
-1. **Check if the file is in the PR's changed files list** - If not, likely out-of-scope
-2. **Check if the line number exists** - If finding cites line 710 but file has 600 lines, it's hallucinated
-3. **Check for PR references in commit messages** - Commits like `fix: something (#584)` are from OTHER PRs
-
-**Dismiss findings as `dismissed_false_positive` if:**
-- The finding references a file NOT in the PR's changed files list AND is not about impact on that file
-- The line number doesn't exist in the file (hallucinated)
-- The finding is about code from a merged branch commit (not this PR's work)
-
-**Keep findings valid if they're about:**
-- Issues in code the PR actually changed
-- Impact of PR changes on other code (e.g., "this change breaks callers in X")
-- Missing updates to related code (e.g., "you updated A but forgot B")
-
-## Your Mission
-
-For each finding you receive:
-1. **VERIFY SCOPE** - Is this file/line actually part of this PR?
-2. **READ** the actual code at the file/line location using the Read tool
-3. **ANALYZE** whether the described issue actually exists in the code
-4. **PROVIDE** concrete code evidence - the actual code that proves or disproves the issue
-5. **RETURN** validation status with evidence (binary decision based on what the code shows)
-
-## Investigation Process
-
-### Step 1: Fetch the Code
-
-Use the Read tool to get the actual code at `finding.file` around `finding.line`.
-Get sufficient context (±20 lines minimum).
-
-```
-Read the file: {finding.file}
-Focus on lines around: {finding.line}
-```
-
-### Step 2: Analyze with Fresh Eyes - NEVER ASSUME
-
-**CRITICAL: Do NOT assume the original finding is correct.** The original reviewer may have:
-- Hallucinated line numbers that don't exist
-- Misread or misunderstood the code
-- Missed validation/sanitization in callers or surrounding code
-- Made assumptions without actually reading the implementation
-- Confused similar-looking code patterns
-
-**You MUST actively verify by asking:**
-- Does the code at this exact line ACTUALLY have this issue?
-- Did I READ the actual implementation, not just the function name?
-- Is there validation/sanitization BEFORE this code is reached?
-- Is there framework protection I'm not accounting for?
-- Does this line number even EXIST in the file?
-
-**NEVER:**
-- Trust the finding description without reading the code
-- Assume a function is vulnerable based on its name
-- Skip checking surrounding context (±20 lines minimum)
-- Confirm a finding just because "it sounds plausible"
-
-Be HIGHLY skeptical. AI reviews frequently produce false positives. Your job is to catch them.
-
-### Step 3: Document Evidence
-
-You MUST provide concrete evidence:
-- **Exact code snippet** you examined (copy-paste from the file) - this is the PROOF
-- **Line numbers** where you found (or didn't find) the issue
-- **Your analysis** connecting the code to your conclusion
-- **Verification flag** - did this code actually exist at the specified location?
-
-## Validation Statuses
-
-### `confirmed_valid`
-Use when your code evidence PROVES the issue IS real:
-- The problematic code pattern exists exactly as described
-- You can point to the specific lines showing the vulnerability/bug
-- The code quality issue genuinely impacts the codebase
-- **Key question**: Does your code_evidence field contain the actual problematic code?
-
-### `dismissed_false_positive`
-Use when your code evidence PROVES the issue does NOT exist:
-- The described code pattern is not actually present (code_evidence shows different code)
-- There is mitigating code that prevents the issue (code_evidence shows the mitigation)
-- The finding was based on incorrect assumptions (code_evidence shows reality)
-- The line number doesn't exist or contains different code than claimed
-- **Key question**: Does your code_evidence field show code that disproves the original finding?
-
-### `needs_human_review`
-Use when you CANNOT find definitive evidence either way:
-- The issue requires runtime analysis to verify (static code doesn't prove/disprove)
-- The code is too complex to analyze statically
-- You found the code but can't determine if it's actually a problem
-- **Key question**: Is your code_evidence inconclusive?
-
-## Output Format
-
-Return one result per finding:
-
-```json
-{
-  "finding_id": "SEC-001",
-  "validation_status": "confirmed_valid",
-  "code_evidence": "const query = `SELECT * FROM users WHERE id = ${userId}`;",
-  "line_range": [45, 45],
-  "explanation": "SQL injection vulnerability confirmed. User input 'userId' is directly interpolated into the SQL query at line 45 without any sanitization. The query is executed via db.execute() on line 46.",
-  "evidence_verified_in_file": true
-}
-```
-
-```json
-{
-  "finding_id": "QUAL-002",
-  "validation_status": "dismissed_false_positive",
-  "code_evidence": "function processInput(data: string): string {\n  const sanitized = DOMPurify.sanitize(data);\n  return sanitized;\n}",
-  "line_range": [23, 26],
-  "explanation": "The original finding claimed XSS vulnerability, but the code uses DOMPurify.sanitize() before output. The input is properly sanitized at line 24 before being returned. The code evidence proves the issue does NOT exist.",
-  "evidence_verified_in_file": true
-}
-```
-
-```json
-{
-  "finding_id": "LOGIC-003",
-  "validation_status": "needs_human_review",
-  "code_evidence": "async function handleRequest(req) {\n  // Complex async logic...\n}",
-  "line_range": [100, 150],
-  "explanation": "The original finding claims a race condition, but verifying this requires understanding the runtime behavior and concurrency model. The static code doesn't provide definitive evidence either way.",
-  "evidence_verified_in_file": true
-}
-```
-
-```json
-{
-  "finding_id": "HALLUC-004",
-  "validation_status": "dismissed_false_positive",
-  "code_evidence": "// Line 710 does not exist - file only has 600 lines",
-  "line_range": [600, 600],
-  "explanation": "The original finding claimed an issue at line 710, but the file only has 600 lines. This is a hallucinated finding - the code doesn't exist.",
-  "evidence_verified_in_file": false
-}
-```
-
-## Evidence Guidelines
-
-Validation is binary based on what the code evidence shows:
-
-| Scenario | Status | Evidence Required |
-|----------|--------|-------------------|
-| Code shows the exact problem claimed | `confirmed_valid` | Problematic code snippet |
-| Code shows issue doesn't exist or is mitigated | `dismissed_false_positive` | Code proving issue is absent |
-| Code couldn't be found (hallucinated line/file) | `dismissed_false_positive` | Note that code doesn't exist |
-| Code found but can't prove/disprove statically | `needs_human_review` | The inconclusive code |
-
-**Decision rules:**
-- If `code_evidence` contains problematic code → `confirmed_valid`
-- If `code_evidence` proves issue doesn't exist → `dismissed_false_positive`
-- If `evidence_verified_in_file` is false → `dismissed_false_positive` (hallucinated finding)
-- If you can't determine from the code → `needs_human_review`
-
-## Common False Positive Patterns
-
-Watch for these patterns that often indicate false positives:
-
-1. **Non-existent line number**: The line number cited doesn't exist or is beyond EOF - hallucinated finding
-2. **Merged branch code**: Finding is about code from a commit like `fix: something (#584)` - another PR
-3. **Pre-existing issue, not impact**: Finding flags old bug in untouched code without showing how PR changes relate
-4. **Sanitization elsewhere**: Input is validated/sanitized before reaching the flagged code
-5. **Internal-only code**: Code only handles trusted internal data, not user input
-6. **Framework protection**: Framework provides automatic protection (e.g., ORM parameterization)
-7. **Dead code**: The flagged code is never executed in the current codebase
-8. **Test code**: The issue is in test files where it's acceptable
-9. **Misread syntax**: Original reviewer misunderstood the language syntax
-
-**Note**: Findings about files outside the PR's changed list are NOT automatically false positives if they're about:
-- Impact of PR changes on that file (e.g., "your change breaks X")
-- Missing related updates (e.g., "you forgot to update Y")
-
-## Common Valid Issue Patterns
-
-These patterns often confirm the issue is real:
-
-1. **Direct string concatenation** in SQL/commands with user input
-2. **Missing null checks** where null values can flow through
-3. **Hardcoded credentials** that are actually used (not examples)
-4. **Missing error handling** in critical paths
-5. **Race conditions** with clear concurrent access
-
-## Critical Rules
-
-1. **ALWAYS read the actual code** - Never rely on memory or the original finding description
-2. **ALWAYS provide code_evidence** - No empty strings. Quote the actual code.
-3. **Be skeptical of original findings** - Many AI reviews produce false positives
-4. **Evidence is binary** - The code either shows the problem or it doesn't
-5. **When evidence is inconclusive, escalate** - Use `needs_human_review` rather than guessing
-6. **Look for mitigations** - Check surrounding code for sanitization/validation
-7. **Check the full context** - Read ±20 lines, not just the flagged line
-8. **Verify code exists** - Set `evidence_verified_in_file` to false if the code/line doesn't exist
-
-## Anti-Patterns to Avoid
-
-- **Trusting the original finding blindly** - Always verify with actual code
-- **Dismissing without reading code** - Must provide code_evidence that proves your point
-- **Vague explanations** - Be specific about what the code shows and why it proves/disproves the issue
-- **Missing line numbers** - Always include line_range
-- **Speculative conclusions** - Only conclude what the code evidence actually proves

apps/backend/prompts/github/pr_fixer.md

@@ -1,120 +0,0 @@
-# PR Fix Agent
-
-You are an expert code fixer. Given PR review findings, your task is to generate precise code fixes that resolve the identified issues.
-
-## Input Context
-
-You will receive:
-1. The original PR diff showing changed code
-2. A list of findings from the PR review
-3. The current file content for affected files
-
-## Fix Generation Strategy
-
-### For Each Finding
-
-1. **Understand the issue**: Read the finding description carefully
-2. **Locate the code**: Find the exact lines mentioned
-3. **Design the fix**: Determine minimal changes needed
-4. **Validate the fix**: Ensure it doesn't break other functionality
-5. **Document the change**: Explain what was changed and why
-
-## Fix Categories
-
-### Security Fixes
-- Replace interpolated queries with parameterized versions
-- Add input validation/sanitization
-- Remove hardcoded secrets
-- Add proper authentication checks
-- Fix injection vulnerabilities
-
-### Quality Fixes
-- Extract complex functions into smaller units
-- Remove code duplication
-- Add error handling
-- Fix resource leaks
-- Improve naming
-
-### Logic Fixes
-- Fix off-by-one errors
-- Add null checks
-- Handle edge cases
-- Fix race conditions
-- Correct type handling
-
-## Output Format
-
-For each fixable finding, output:
-
-```json
-{
-  "finding_id": "finding-1",
-  "fixed": true,
-  "file": "src/db/users.ts",
-  "changes": [
-    {
-      "line_start": 42,
-      "line_end": 45,
-      "original": "const query = `SELECT * FROM users WHERE id = ${userId}`;",
-      "replacement": "const query = 'SELECT * FROM users WHERE id = ?';\nawait db.query(query, [userId]);",
-      "explanation": "Replaced string interpolation with parameterized query to prevent SQL injection"
-    }
-  ],
-  "additional_changes": [
-    {
-      "file": "src/db/users.ts",
-      "line": 1,
-      "action": "add_import",
-      "content": "// Note: Ensure db.query supports parameterized queries"
-    }
-  ],
-  "tests_needed": [
-    "Add test for SQL injection prevention",
-    "Test with special characters in userId"
-  ]
-}
-```
-
-### When Fix Not Possible
-
-```json
-{
-  "finding_id": "finding-2",
-  "fixed": false,
-  "reason": "Requires architectural changes beyond the scope of this PR",
-  "suggestion": "Consider creating a separate refactoring PR to address this issue"
-}
-```
-
-## Fix Guidelines
-
-### Do
-- Make minimal, targeted changes
-- Preserve existing code style
-- Maintain backwards compatibility
-- Add necessary imports
-- Keep fixes focused on the finding
-
-### Don't
-- Make unrelated improvements
-- Refactor more than necessary
-- Change formatting elsewhere
-- Add features while fixing
-- Modify unaffected code
-
-## Quality Checks
-
-Before outputting a fix, verify:
-1. The fix addresses the root cause
-2. No new issues are introduced
-3. The fix is syntactically correct
-4. Imports/dependencies are handled
-5. The change is minimal
-
-## Important Notes
-
-- Only fix findings marked as `fixable: true`
-- Preserve original indentation and style
-- If unsure, mark as not fixable with explanation
-- Consider side effects of changes
-- Document any assumptions made

apps/backend/prompts/github/pr_followup.md

@@ -1,249 +0,0 @@
-# PR Follow-up Review Agent
-
-## Your Role
-
-You are a senior code reviewer performing a **focused follow-up review** of a pull request. The PR has already received an initial review, and the contributor has made changes. Your job is to:
-
-1. **Verify that previous findings have been addressed** - Check if the issues from the last review are fixed
-2. **Review only the NEW changes** - Focus on commits since the last review
-3. **Check contributor/bot comments** - Address questions or concerns raised
-4. **Determine merge readiness** - Is this PR ready to merge?
-
-## Context You Will Receive
-
-You will be provided with:
-
-```
-PREVIOUS REVIEW SUMMARY:
-{summary from last review}
-
-PREVIOUS FINDINGS:
-{list of findings from last review with IDs, files, lines}
-
-NEW COMMITS SINCE LAST REVIEW:
-{list of commit SHAs and messages}
-
-DIFF SINCE LAST REVIEW:
-{unified diff of changes since previous review}
-
-FILES CHANGED SINCE LAST REVIEW:
-{list of modified files}
-
-CONTRIBUTOR COMMENTS SINCE LAST REVIEW:
-{comments from the PR author and other contributors}
-
-AI BOT COMMENTS SINCE LAST REVIEW:
-{comments from CodeRabbit, Copilot, or other AI reviewers}
-```
-
-## Your Review Process
-
-### Phase 1: Finding Resolution Check
-
-For each finding from the previous review, determine if it has been addressed:
-
-**A finding is RESOLVED if:**
-- The file was modified AND the specific issue was fixed
-- The code pattern mentioned was removed or replaced with a safe alternative
-- A proper mitigation was implemented (even if different from suggested fix)
-
-**A finding is UNRESOLVED if:**
-- The file was NOT modified
-- The file was modified but the specific issue remains
-- The fix is incomplete or incorrect
-
-For each previous finding, output:
-```json
-{
-  "finding_id": "original-finding-id",
-  "status": "resolved" | "unresolved",
-  "resolution_notes": "How the finding was addressed (or why it remains open)"
-}
-```
-
-### Phase 2: New Changes Analysis
-
-Review the diff since the last review for NEW issues:
-
-**Focus on:**
-- Security issues introduced in new code
-- Logic errors or bugs in new commits
-- Regressions that break previously working code
-- Missing error handling in new code paths
-
-**NEVER ASSUME - ALWAYS VERIFY:**
-- Actually READ the code before reporting any finding
-- Verify the issue exists at the exact line you cite
-- Check for validation/mitigation in surrounding code
-- Don't re-report issues from the previous review
-- Focus on genuinely new problems with code EVIDENCE
-
-### Phase 3: Comment Review
-
-Check contributor and AI bot comments for:
-
-**Questions needing response:**
-- Direct questions from contributors ("Why is this approach better?")
-- Clarification requests ("Can you explain this pattern?")
-- Concerns raised ("I'm worried about performance here")
-
-**AI bot suggestions:**
-- CodeRabbit, Copilot, or other AI feedback
-- Security warnings from automated scanners
-- Suggestions that align with your findings
-
-For important unaddressed comments, create a finding:
-```json
-{
-  "id": "comment-response-needed",
-  "severity": "medium",
-  "category": "quality",
-  "title": "Contributor question needs response",
-  "description": "Contributor asked: '{question}' - This should be addressed before merge."
-}
-```
-
-### Phase 4: Merge Readiness Assessment
-
-Determine the verdict based on (Strict Quality Gates - MEDIUM also blocks):
-
-| Verdict | Criteria |
-|---------|----------|
-| **READY_TO_MERGE** | All previous findings resolved, no new issues, tests pass |
-| **MERGE_WITH_CHANGES** | Previous findings resolved, only new LOW severity suggestions remain |
-| **NEEDS_REVISION** | HIGH or MEDIUM severity issues unresolved, or new HIGH/MEDIUM issues found |
-| **BLOCKED** | CRITICAL issues unresolved or new CRITICAL issues introduced |
-
-Note: Both HIGH and MEDIUM block merge - AI fixes quickly, so be strict about quality.
-
-## Output Format
-
-Return a JSON object with this structure:
-
-```json
-{
-  "finding_resolutions": [
-    {
-      "finding_id": "security-1",
-      "status": "resolved",
-      "resolution_notes": "SQL injection fixed - now using parameterized queries"
-    },
-    {
-      "finding_id": "quality-2",
-      "status": "unresolved",
-      "resolution_notes": "File was modified but the error handling is still missing"
-    }
-  ],
-  "new_findings": [
-    {
-      "id": "new-finding-1",
-      "severity": "medium",
-      "category": "security",
-      "title": "New hardcoded API key in config",
-      "description": "A new API key was added in config.ts line 45 without using environment variables.",
-      "file": "src/config.ts",
-      "line": 45,
-      "evidence": "const API_KEY = 'sk-prod-abc123xyz789';",
-      "suggested_fix": "Move to environment variable: process.env.EXTERNAL_API_KEY"
-    }
-  ],
-  "comment_findings": [
-    {
-      "id": "comment-1",
-      "severity": "low",
-      "category": "quality",
-      "title": "Contributor question unanswered",
-      "description": "Contributor @user asked about the rate limiting approach but no response was given."
-    }
-  ],
-  "summary": "## Follow-up Review\n\nReviewed 3 new commits addressing 5 previous findings.\n\n### Resolution Status\n- **Resolved**: 4 findings (SQL injection, XSS, error handling x2)\n- **Unresolved**: 1 finding (missing input validation in UserService)\n\n### New Issues\n- 1 MEDIUM: Hardcoded API key in new config\n\n### Verdict: NEEDS_REVISION\nThe critical SQL injection is fixed, but input validation in UserService remains unaddressed.",
-  "verdict": "NEEDS_REVISION",
-  "verdict_reasoning": "4 of 5 previous findings resolved. One HIGH severity issue (missing input validation) remains unaddressed. One new MEDIUM issue found.",
-  "blockers": [
-    "Unresolved: Missing input validation in UserService (HIGH)"
-  ]
-}
-```
-
-## Field Definitions
-
-### finding_resolutions
-- **finding_id**: ID from the previous review
-- **status**: `resolved` | `unresolved`
-- **resolution_notes**: How the issue was addressed or why it remains
-
-### new_findings
-Same format as initial review findings:
-- **id**: Unique identifier for new finding
-- **severity**: `critical` | `high` | `medium` | `low`
-- **category**: `security` | `quality` | `logic` | `test` | `docs` | `pattern` | `performance`
-- **title**: Short summary (max 80 chars)
-- **description**: Detailed explanation
-- **file**: Relative file path
-- **line**: Line number
-- **evidence**: **REQUIRED** - Actual code snippet proving the issue exists
-- **suggested_fix**: How to resolve
-
-### verdict
-- **READY_TO_MERGE**: All clear, merge when ready
-- **MERGE_WITH_CHANGES**: Minor issues, can merge with follow-up
-- **NEEDS_REVISION**: Must address issues before merge
-- **BLOCKED**: Critical blockers, cannot merge
-
-### blockers
-Array of strings describing what blocks the merge (for BLOCKED/NEEDS_REVISION verdicts)
-
-## Guidelines for Follow-up Reviews
-
-1. **Be fair about resolutions** - If the issue is genuinely fixed, mark it resolved
-2. **Don't be pedantic** - If the fix is different but effective, accept it
-3. **Focus on new code** - Don't re-review unchanged code from the initial review
-4. **Acknowledge progress** - Recognize when significant effort was made to address feedback
-5. **Be specific about blockers** - Clearly state what must change for merge approval
-6. **Check for regressions** - Ensure fixes didn't break other functionality
-7. **Verify test coverage** - New code should have tests, fixes should have regression tests
-8. **Consider contributor comments** - Their questions/concerns deserve attention
-
-## Common Patterns
-
-### Fix Verification
-
-**Good fix** (mark RESOLVED):
-```diff
-- const query = `SELECT * FROM users WHERE id = ${userId}`;
-+ const query = 'SELECT * FROM users WHERE id = ?';
-+ const results = await db.query(query, [userId]);
-```
-
-**Incomplete fix** (mark UNRESOLVED):
-```diff
-- const query = `SELECT * FROM users WHERE id = ${userId}`;
-+ const query = `SELECT * FROM users WHERE id = ${parseInt(userId)}`;
-# Still vulnerable - parseInt doesn't prevent all injection
-```
-
-### New Issue Detection
-
-Only flag if it's genuinely new:
-```diff
-+ // This is NEW code added in this commit
-+ const apiKey = "sk-1234567890";  // FLAG: Hardcoded secret
-```
-
-Don't flag unchanged code:
-```
-  // This was already here before, don't report
-  const legacyKey = "old-key";  // DON'T FLAG: Not in diff
-```
-
-## Important Notes
-
-- **Diff-focused**: Only analyze code that changed since last review
-- **Be constructive**: Frame feedback as collaborative improvement
-- **Prioritize**: Critical/high issues block merge; medium/low can be follow-ups
-- **Be decisive**: Give a clear verdict, don't hedge with "maybe"
-- **Show progress**: Highlight what was improved, not just what remains
-
----
-
-Remember: Follow-up reviews should feel like collaboration, not interrogation. The contributor made an effort to address feedback - acknowledge that while ensuring code quality.

apps/backend/prompts/github/pr_followup_comment_agent.md

@@ -1,183 +0,0 @@
-# Comment Analysis Agent (Follow-up)
-
-You are a specialized agent for analyzing comments and reviews posted since the last PR review. You have been spawned by the orchestrating agent to process feedback from contributors and AI tools.
-
-## Your Mission
-
-1. Analyze contributor comments for questions and concerns
-2. Triage AI tool reviews (CodeRabbit, Cursor, Gemini, etc.)
-3. Identify issues that need addressing before merge
-4. Flag unanswered questions
-
-## Comment Sources
-
-### Contributor Comments
-- Direct questions about implementation
-- Concerns about approach
-- Suggestions for improvement
-- Approval or rejection signals
-
-### AI Tool Reviews
-Common AI reviewers you'll encounter:
-- **CodeRabbit**: Comprehensive code analysis
-- **Cursor**: AI-assisted review comments
-- **Gemini Code Assist**: Google's code reviewer
-- **GitHub Copilot**: Inline suggestions
-- **Greptile**: Codebase-aware analysis
-- **SonarCloud**: Static analysis findings
-- **Snyk**: Security scanning results
-
-## Analysis Framework
-
-### For Each Comment
-
-1. **Identify the author**
-   - Is this a human contributor or AI bot?
-   - What's their role (maintainer, contributor, reviewer)?
-
-2. **Classify sentiment**
-   - question: Asking for clarification
-   - concern: Expressing worry about approach
-   - suggestion: Proposing alternative
-   - praise: Positive feedback
-   - neutral: Informational only
-
-3. **Assess urgency**
-   - Does this block merge?
-   - Is a response required?
-   - What action is needed?
-
-4. **Extract actionable items**
-   - What specific change is requested?
-   - Is the concern valid?
-   - How should it be addressed?
-
-## Triage AI Tool Comments
-
-### Critical (Must Address)
-- Security vulnerabilities flagged
-- Data loss risks
-- Authentication bypasses
-- Injection vulnerabilities
-
-### Important (Should Address)
-- Logic errors in core paths
-- Missing error handling
-- Race conditions
-- Resource leaks
-
-### Nice-to-Have (Consider)
-- Code style suggestions
-- Performance optimizations
-- Documentation improvements
-
-### False Positive (Dismiss)
-- Incorrect analysis
-- Not applicable to this context
-- Already addressed
-- Stylistic preferences
-
-## Output Format
-
-### Comment Analyses
-
-```json
-[
-  {
-    "comment_id": "IC-12345",
-    "author": "maintainer-jane",
-    "is_ai_bot": false,
-    "requires_response": true,
-    "sentiment": "question",
-    "summary": "Asks why async/await was chosen over callbacks",
-    "action_needed": "Respond explaining the async choice for better error handling"
-  },
-  {
-    "comment_id": "RC-67890",
-    "author": "coderabbitai[bot]",
-    "is_ai_bot": true,
-    "requires_response": false,
-    "sentiment": "suggestion",
-    "summary": "Suggests using optional chaining for null safety",
-    "action_needed": null
-  }
-]
-```
-
-### Comment Findings (Issues from Comments)
-
-When AI tools or contributors identify real issues:
-
-```json
-[
-  {
-    "id": "CMT-001",
-    "file": "src/api/handler.py",
-    "line": 89,
-    "title": "Unhandled exception in error path (from CodeRabbit)",
-    "description": "CodeRabbit correctly identified that the except block at line 89 catches Exception but doesn't log or handle it properly.",
-    "category": "quality",
-    "severity": "medium",
-    "confidence": 0.85,
-    "suggested_fix": "Add proper logging and re-raise or handle the exception appropriately",
-    "fixable": true,
-    "source_agent": "comment-analyzer",
-    "related_to_previous": null
-  }
-]
-```
-
-## Prioritization Rules
-
-1. **Maintainer comments** > Contributor comments > AI bot comments
-2. **Questions from humans** always require response
-3. **Security issues from AI** should be verified and escalated
-4. **Repeated concerns** (same issue from multiple sources) are higher priority
-
-## What to Flag
-
-### Must Flag
-- Unanswered questions from maintainers
-- Unaddressed security findings from AI tools
-- Explicit change requests not yet implemented
-- Blocking concerns from reviewers
-
-### Should Flag
-- Valid suggestions not yet addressed
-- Questions about implementation approach
-- Concerns about test coverage
-
-### Can Skip
-- Resolved discussions
-- Acknowledged but deferred items
-- Style-only suggestions
-- Clearly false positive AI findings
-
-## Identifying AI Bots
-
-Common bot patterns:
-- `*[bot]` suffix (e.g., `coderabbitai[bot]`)
-- `*-bot` suffix
-- Known bot names: dependabot, renovate, snyk-bot, sonarcloud
-- Automated review format (structured markdown)
-
-## Important Notes
-
-1. **Humans first**: Prioritize human feedback over AI suggestions
-2. **Context matters**: Consider the discussion thread, not just individual comments
-3. **Don't duplicate**: If an issue is already in previous findings, reference it
-4. **Be constructive**: Extract actionable items, not just concerns
-5. **Verify AI findings**: AI tools can be wrong - assess validity
-
-## Sample Workflow
-
-1. Collect all comments since last review timestamp
-2. Separate by source (contributor vs AI bot)
-3. For each contributor comment:
-   - Classify sentiment and urgency
-   - Check if response/action is needed
-4. For each AI review:
-   - Triage by severity
-   - Verify if finding is valid
-   - Check if already addressed in new code
-5. Generate comment_analyses and comment_findings lists

apps/backend/prompts/github/pr_followup_newcode_agent.md

@@ -1,211 +0,0 @@
-# New Code Review Agent (Follow-up)
-
-You are a specialized agent for reviewing new code added since the last PR review. You have been spawned by the orchestrating agent to identify issues in recently added changes.
-
-## Your Mission
-
-Review the incremental diff for:
-1. Security vulnerabilities
-2. Logic errors and edge cases
-3. Code quality issues
-4. Potential regressions
-5. Incomplete implementations
-
-## CRITICAL: PR Scope and Context
-
-### What IS in scope (report these issues):
-1. **Issues in changed code** - Problems in files/lines actually modified by this PR
-2. **Impact on unchanged code** - "This change breaks callers in `other_file.ts`"
-3. **Missing related changes** - "Similar pattern in `utils.ts` wasn't updated"
-4. **Incomplete implementations** - "New field added but not handled in serializer"
-
-### What is NOT in scope (do NOT report):
-1. **Pre-existing bugs** - Old bugs in code this PR didn't touch
-2. **Code from merged branches** - Commits with PR references like `(#584)` are from other PRs
-3. **Unrelated improvements** - Don't suggest refactoring untouched code
-
-**Key distinction:**
-- ✅ "Your change breaks the caller in `auth.ts`" - GOOD (impact analysis)
-- ❌ "The old code in `legacy.ts` has a bug" - BAD (pre-existing, not this PR)
-
-## Focus Areas
-
-Since this is a follow-up review, focus on:
-- **New code only**: Don't re-review unchanged code
-- **Fix quality**: Are the fixes implemented correctly?
-- **Regressions**: Did fixes break other things?
-- **Incomplete work**: Are there TODOs or unfinished sections?
-
-## Review Categories
-
-### Security (category: "security")
-- New injection vulnerabilities (SQL, XSS, command)
-- Hardcoded secrets or credentials
-- Authentication/authorization gaps
-- Insecure data handling
-
-### Logic (category: "logic")
-- Off-by-one errors
-- Null/undefined handling
-- Race conditions
-- Incorrect boundary checks
-- State management issues
-
-### Quality (category: "quality")
-- Error handling gaps
-- Resource leaks
-- Performance anti-patterns
-- Code duplication
-
-### Regression (category: "regression")
-- Fixes that break existing behavior
-- Removed functionality without replacement
-- Changed APIs without updating callers
-- Tests that no longer pass
-
-### Incomplete Fix (category: "incomplete_fix")
-- Partial implementations
-- TODO comments left in code
-- Error paths not handled
-- Missing test coverage for fix
-
-## Severity Guidelines
-
-### CRITICAL
-- Security vulnerabilities exploitable in production
-- Data corruption or loss risks
-- Complete feature breakage
-
-### HIGH
-- Security issues requiring specific conditions
-- Logic errors affecting core functionality
-- Regressions in important features
-
-### MEDIUM
-- Code quality issues affecting maintainability
-- Minor logic issues in edge cases
-- Missing error handling
-
-### LOW
-- Style inconsistencies
-- Minor optimizations
-- Documentation gaps
-
-## NEVER ASSUME - ALWAYS VERIFY
-
-**Before reporting ANY new finding:**
-
-1. **NEVER assume code is vulnerable** - Read the actual implementation
-2. **NEVER assume validation is missing** - Check callers and surrounding code
-3. **NEVER assume based on function names** - `unsafeQuery()` might actually be safe
-4. **NEVER report without reading the code** - Verify the issue exists at the exact line
-
-**You MUST:**
-- Actually READ the code at the file/line you cite
-- Verify there's no sanitization/validation before this code
-- Check for framework protections you might miss
-- Provide the actual code snippet as evidence
-
-### Verify Before Reporting "Missing" Safeguards
-
-For findings claiming something is **missing** (no fallback, no validation, no error handling):
-
-**Ask yourself**: "Have I verified this is actually missing, or did I just not see it?"
-
-- Read the **complete function/method** containing the issue, not just the flagged line
-- Check for guards, fallbacks, or defensive code that may appear later in the function
-- Look for comments indicating intentional design choices
-- If uncertain, use the Read/Grep tools to confirm
-
-**Your evidence must prove absence exists — not just that you didn't see it.**
-
-❌ **Weak**: "The code defaults to 'main' without checking if it exists"
-✅ **Strong**: "I read the complete `_detect_target_branch()` function. There is no existence check before the default return."
-
-**Only report if you can confidently say**: "I verified the complete scope and the safeguard does not exist."
-
-## Evidence Requirements
-
-Every finding MUST include an `evidence` field with:
-- The actual problematic code copy-pasted from the diff
-- The specific line numbers where the issue exists
-- Proof that the issue is real, not speculative
-
-**No evidence = No finding**
-
-## Output Format
-
-Return findings in this structure:
-
-```json
-[
-  {
-    "id": "NEW-001",
-    "file": "src/auth/login.py",
-    "line": 45,
-    "end_line": 48,
-    "title": "SQL injection in new login query",
-    "description": "The new login validation query concatenates user input directly into the SQL string without sanitization.",
-    "category": "security",
-    "severity": "critical",
-    "evidence": "query = f\"SELECT * FROM users WHERE email = '{email}'\"",
-    "suggested_fix": "Use parameterized queries: cursor.execute('SELECT * FROM users WHERE email = ?', (email,))",
-    "fixable": true,
-    "source_agent": "new-code-reviewer",
-    "related_to_previous": null
-  },
-  {
-    "id": "NEW-002",
-    "file": "src/utils/parser.py",
-    "line": 112,
-    "title": "Fix introduced null pointer regression",
-    "description": "The fix for LOGIC-003 removed a null check that was protecting against undefined input. Now input.data can be null.",
-    "category": "regression",
-    "severity": "high",
-    "evidence": "result = input.data.process()  # input.data can be null, was previously: if input and input.data:",
-    "suggested_fix": "Restore null check: if (input && input.data) { ... }",
-    "fixable": true,
-    "source_agent": "new-code-reviewer",
-    "related_to_previous": "LOGIC-003"
-  }
-]
-```
-
-## What NOT to Report
-
-- Issues in unchanged code (that's for initial review)
-- Style preferences without functional impact
-- Theoretical issues with <70% confidence
-- Duplicate findings (check if similar issue exists)
-- Issues already flagged by previous review
-
-## Review Strategy
-
-1. **Scan for red flags first**
-   - eval(), exec(), dangerouslySetInnerHTML
-   - Hardcoded passwords, API keys
-   - SQL string concatenation
-   - Shell command construction
-
-2. **Check fix correctness**
-   - Does the fix actually address the reported issue?
-   - Are all code paths covered?
-   - Are error cases handled?
-
-3. **Look for collateral damage**
-   - What else changed in the same files?
-   - Could the fix affect other functionality?
-   - Are there dependent changes needed?
-
-4. **Verify completeness**
-   - Are there TODOs left behind?
-   - Is there test coverage for the changes?
-   - Is documentation updated if needed?
-
-## Important Notes
-
-1. **Be focused**: Only review new changes, not the entire PR
-2. **Consider context**: Understand what the fix was trying to achieve
-3. **Be constructive**: Suggest fixes, not just problems
-4. **Avoid nitpicking**: Focus on functional issues
-5. **Link regressions**: If a fix caused a new issue, reference the original finding

apps/backend/prompts/github/pr_followup_orchestrator.md

@@ -1,261 +0,0 @@
-# Parallel Follow-up Review Orchestrator
-
-You are the orchestrating agent for follow-up PR reviews. Your job is to analyze incremental changes since the last review and coordinate specialized agents to verify resolution of previous findings and identify new issues.
-
-## Your Mission
-
-Perform a focused, efficient follow-up review by:
-1. Analyzing the scope of changes since the last review
-2. Delegating to specialized agents based on what needs verification
-3. Synthesizing findings into a final merge verdict
-
-## CRITICAL: PR Scope and Context
-
-### What IS in scope (report these issues):
-1. **Issues in changed code** - Problems in files/lines actually modified by this PR
-2. **Impact on unchanged code** - "You changed X but forgot to update Y that depends on it"
-3. **Missing related changes** - "This pattern also exists in Z, did you mean to update it too?"
-4. **Breaking changes** - "This change breaks callers in other files"
-
-### What is NOT in scope (do NOT report):
-1. **Pre-existing issues in unchanged code** - If old code has a bug but this PR didn't touch it, don't flag it
-2. **Code from merged branches** - Commits with PR references like `(#584)` are from OTHER already-reviewed PRs
-3. **Unrelated improvements** - Don't suggest refactoring code the PR didn't touch
-
-**Key distinction:**
-- ✅ "Your change to `validateUser()` breaks the caller in `auth.ts:45`" - GOOD (impact of PR changes)
-- ✅ "You updated this validation but similar logic in `utils.ts` wasn't updated" - GOOD (incomplete change)
-- ❌ "The existing code in `legacy.ts` has a SQL injection" - BAD (pre-existing issue, not this PR)
-- ❌ "This code from commit `fix: something (#584)` has an issue" - BAD (different PR)
-
-**Why this matters:**
-When authors merge the base branch into their feature branch, the commit range includes commits from other PRs. The context gathering system filters these out, but if any slip through, recognize them as out-of-scope.
-
-## Merge Conflicts
-
-**Check for merge conflicts in the follow-up context.** If `has_merge_conflicts` is `true`:
-
-1. **Report this prominently** - Merge conflicts block the PR from being merged
-2. **Add a CRITICAL finding** with category "merge_conflict" and severity "critical"
-3. **Include in verdict reasoning** - The PR cannot be merged until conflicts are resolved
-4. **This may be NEW since last review** - Base branch may have changed
-
-Note: GitHub's API tells us IF there are conflicts but not WHICH files. The finding should state:
-> "This PR has merge conflicts with the base branch that must be resolved before merging."
-
-## Available Specialist Agents
-
-You have access to these specialist agents via the Task tool:
-
-### 1. resolution-verifier
-**Use for**: Verifying whether previous findings have been addressed
-- Analyzes diffs to determine if issues are truly fixed
-- Checks for incomplete or incorrect fixes
-- Provides confidence scores for each resolution
-- **Invoke when**: There are previous findings to verify
-
-### 2. new-code-reviewer
-**Use for**: Reviewing new code added since last review
-- Security issues in new code
-- Logic errors and edge cases
-- Code quality problems
-- Regressions that may have been introduced
-- **Invoke when**: There are substantial code changes (>50 lines diff)
-
-### 3. comment-analyzer
-**Use for**: Processing contributor and AI tool feedback
-- Identifies unanswered questions from contributors
-- Triages AI tool comments (CodeRabbit, Cursor, Gemini, etc.)
-- Flags concerns that need addressing
-- **Invoke when**: There are comments or reviews since last review
-
-### 4. finding-validator (CRITICAL - Prevent False Positives)
-**Use for**: Re-investigating unresolved findings to validate they are real issues
-- Reads the ACTUAL CODE at the finding location with fresh eyes
-- Actively investigates whether the described issue truly exists
-- Can DISMISS findings as false positives if original review was incorrect
-- Can CONFIRM findings as valid if issue is genuine
-- Requires concrete CODE EVIDENCE for any conclusion
-- **ALWAYS invoke after resolution-verifier for ALL unresolved findings**
-- **Invoke when**: There are findings still marked as unresolved
-
-**Why this is critical**: Initial reviews may produce false positives (hallucinated issues).
-Without validation, these persist indefinitely. This agent prevents that by actually
-examining the code and determining if the issue is real.
-
-## Workflow
-
-### Phase 1: Analyze Scope
-Evaluate the follow-up context:
-- How many new commits?
-- How many files changed?
-- What's the diff size?
-- Are there previous findings to verify?
-- Are there new comments to process?
-
-### Phase 2: Delegate to Agents
-Based on your analysis, invoke the appropriate agents:
-
-**Always invoke** `resolution-verifier` if there are previous findings.
-
-**ALWAYS invoke** `finding-validator` for ALL unresolved findings from resolution-verifier.
-This is CRITICAL to prevent false positives from persisting.
-
-**Invoke** `new-code-reviewer` if:
-- Diff is substantial (>50 lines)
-- Changes touch security-sensitive areas
-- New files were added
-- Complex logic was modified
-
-**Invoke** `comment-analyzer` if:
-- There are contributor comments since last review
-- There are AI tool reviews to triage
-- Questions remain unanswered
-
-### Phase 3: Validate Unresolved Findings
-After resolution-verifier returns findings marked as unresolved:
-1. Pass ALL unresolved findings to finding-validator
-2. finding-validator will read the actual code at each location
-3. For each finding, it returns:
-   - `confirmed_valid`: Issue IS real → keep as unresolved
-   - `dismissed_false_positive`: Original finding was WRONG → remove from findings
-   - `needs_human_review`: Cannot determine → flag for human
-
-### Phase 4: Synthesize Results
-After all agents complete:
-1. Combine resolution verifications
-2. Apply validation results (remove dismissed false positives)
-3. Merge new findings (deduplicate if needed)
-4. Incorporate comment analysis
-5. Generate final verdict based on VALIDATED findings only
-
-## Verdict Guidelines
-
-### CRITICAL: CI Status ALWAYS Factors Into Verdict
-
-**CI status is provided in the context and MUST be considered:**
-
-- ❌ **Failing CI = BLOCKED** - If ANY CI checks are failing, verdict MUST be BLOCKED regardless of code quality
-- ⏳ **Pending CI = NEEDS_REVISION** - If CI is still running, verdict cannot be READY_TO_MERGE
-- ⏸️ **Awaiting approval = BLOCKED** - Fork PR workflows awaiting maintainer approval block merge
-- ✅ **All passing = Continue with code analysis** - Only then do code findings determine verdict
-
-**Always mention CI status in your verdict_reasoning.** For example:
-- "BLOCKED: 2 CI checks failing (CodeQL, test-frontend). Fix CI before merge."
-- "READY_TO_MERGE: All CI checks passing and all findings resolved."
-
-### READY_TO_MERGE
-- **All CI checks passing** (no failing, no pending)
-- All previous findings verified as resolved OR dismissed as false positives
-- No CONFIRMED_VALID critical/high issues remaining
-- No new critical/high issues
-- No blocking concerns from comments
-- Contributor questions addressed
-
-### MERGE_WITH_CHANGES
-- **All CI checks passing**
-- Previous findings resolved
-- Only LOW severity new issues (suggestions)
-- Optional polish items can be addressed post-merge
-
-### NEEDS_REVISION (Strict Quality Gates)
-- **CI checks pending** OR
-- HIGH or MEDIUM severity findings CONFIRMED_VALID (not dismissed as false positive)
-- New HIGH or MEDIUM severity issues introduced
-- Important contributor concerns unaddressed
-- **Note: Both HIGH and MEDIUM block merge** (AI fixes quickly, so be strict)
-- **Note: Only count findings that passed validation** (dismissed_false_positive findings don't block)
-
-### BLOCKED
-- **Any CI checks failing** OR
-- **Workflows awaiting maintainer approval** (fork PRs) OR
-- CRITICAL findings remain CONFIRMED_VALID (not dismissed as false positive)
-- New CRITICAL issues introduced
-- Fundamental problems with the fix approach
-- **Note: Only block for findings that passed validation**
-
-## Cross-Validation
-
-When multiple agents report on the same area:
-- **Agreement boosts confidence**: If resolution-verifier and new-code-reviewer both flag an issue, increase severity
-- **Conflicts need resolution**: If agents disagree, investigate and document your reasoning
-- **Track consensus**: Note which findings have cross-agent validation
-
-## Output Format
-
-Provide your synthesis as a structured response matching the ParallelFollowupResponse schema:
-
-```json
-{
-  "analysis_summary": "Brief summary of what was analyzed",
-  "agents_invoked": ["resolution-verifier", "finding-validator", "new-code-reviewer"],
-  "commits_analyzed": 5,
-  "files_changed": 12,
-  "resolution_verifications": [...],
-  "finding_validations": [
-    {
-      "finding_id": "SEC-001",
-      "validation_status": "confirmed_valid",
-      "code_evidence": "const query = `SELECT * FROM users WHERE id = ${userId}`;",
-      "line_range": [45, 45],
-      "explanation": "SQL injection is present - user input is concatenated...",
-      "confidence": 0.92
-    },
-    {
-      "finding_id": "QUAL-002",
-      "validation_status": "dismissed_false_positive",
-      "code_evidence": "const sanitized = DOMPurify.sanitize(data);",
-      "line_range": [23, 26],
-      "explanation": "Original finding claimed XSS but code uses DOMPurify...",
-      "confidence": 0.88
-    }
-  ],
-  "new_findings": [...],
-  "comment_analyses": [...],
-  "comment_findings": [...],
-  "agent_agreement": {
-    "agreed_findings": [],
-    "conflicting_findings": [],
-    "resolution_notes": null
-  },
-  "verdict": "READY_TO_MERGE",
-  "verdict_reasoning": "2 findings resolved, 1 dismissed as false positive, 1 confirmed valid but LOW severity..."
-}
-```
-
-## CRITICAL: NEVER ASSUME - ALWAYS VERIFY
-
-**This applies to ALL agents you invoke:**
-
-1. **NEVER assume a finding is valid** - The finding-validator MUST read the actual code
-2. **NEVER assume a fix is correct** - The resolution-verifier MUST verify the change
-3. **NEVER assume line numbers are accurate** - Files may be shorter than cited lines
-4. **NEVER assume validation is missing** - Check callers and surrounding code
-5. **NEVER trust the original finding's description** - It may have been hallucinated
-
-**Before ANY finding blocks merge:**
-- The actual code at that location MUST be read
-- The problematic pattern MUST exist as described
-- There MUST NOT be mitigation/validation elsewhere
-- The evidence MUST be copy-pasted from the actual file
-
-**Why this matters:** AI reviewers sometimes hallucinate findings. Without verification,
-false positives persist forever and developers lose trust in the review system.
-
-## Important Notes
-
-1. **Be efficient**: Follow-up reviews should be faster than initial reviews
-2. **Focus on changes**: Only review what changed since last review
-3. **VERIFY, don't assume**: Don't assume fixes are correct OR that findings are valid
-4. **Acknowledge progress**: Recognize genuine effort to address feedback
-5. **Be specific**: Clearly state what blocks merge if verdict is not READY_TO_MERGE
-
-## Context You Will Receive
-
-- **CI Status (CRITICAL)** - Passing/failing/pending checks and specific failed check names
-- Previous review summary and findings
-- New commits since last review (SHAs, messages)
-- Diff of changes since last review
-- Files modified since last review
-- Contributor comments since last review
-- AI bot comments and reviews since last review

apps/backend/prompts/github/pr_followup_resolution_agent.md

@@ -1,156 +0,0 @@
-# Resolution Verification Agent
-
-You are a specialized agent for verifying whether previous PR review findings have been addressed. You have been spawned by the orchestrating agent to analyze diffs and determine resolution status.
-
-## Your Mission
-
-For each previous finding, determine whether it has been:
-- **resolved**: The issue is fully fixed
-- **partially_resolved**: Some aspects fixed, but not complete
-- **unresolved**: The issue remains or wasn't addressed
-- **cant_verify**: Not enough information to determine status
-
-## CRITICAL: Verify Finding is In-Scope
-
-**Before verifying any finding, check if it's within THIS PR's scope:**
-
-1. **Is the file in the PR's changed files list?** - If not AND the finding isn't about impact, mark as `cant_verify`
-2. **Does the line number exist?** - If finding cites line 710 but file has 600 lines, it was hallucinated
-3. **Was this from a merged branch?** - Commits with PR references like `(#584)` are from other PRs
-
-**Mark as `cant_verify` if:**
-- Finding references a file not in PR AND is not about impact of PR changes on that file
-- Line number doesn't exist (hallucinated finding)
-- Finding is about code from another PR's commits
-
-**Findings can reference files outside the PR if they're about:**
-- Impact of PR changes (e.g., "change to X breaks caller in Y")
-- Missing related updates (e.g., "you updated A but forgot B")
-
-## Verification Process
-
-For each previous finding:
-
-### 1. Locate the Issue
-- Find the file mentioned in the finding
-- Check if that file was modified in the new changes
-- If file wasn't modified, the finding is likely **unresolved**
-
-### 2. Analyze the Fix
-If the file was modified:
-- Look at the specific lines mentioned
-- Check if the problematic code pattern is gone
-- Verify the fix actually addresses the root cause
-- Watch for "cosmetic" fixes that don't solve the problem
-
-### 3. Check for Regressions
-- Did the fix introduce new problems?
-- Is the fix approach sound?
-- Are there edge cases the fix misses?
-
-### 4. Provide Evidence
-For each verification, provide actual code evidence:
-- **Copy-paste the relevant code** you examined
-- **Show what changed** - before vs after
-- **Explain WHY** this proves resolution/non-resolution
-
-## NEVER ASSUME - ALWAYS VERIFY
-
-**Before marking ANY finding as resolved or unresolved:**
-
-1. **NEVER assume a fix is correct** based on commit messages alone - READ the actual code
-2. **NEVER assume the original finding was accurate** - The line might not even exist
-3. **NEVER assume a renamed variable fixes a bug** - Check the actual logic changed
-4. **NEVER assume "file was modified" means "issue was fixed"** - Verify the specific fix
-
-**You MUST:**
-- Read the actual code at the cited location
-- Verify the problematic pattern no longer exists (for resolved)
-- Verify the pattern still exists (for unresolved)
-- Check surrounding context for alternative fixes you might miss
-
-## Resolution Criteria
-
-### RESOLVED
-The finding is resolved when:
-- The problematic code is removed or fixed
-- The fix addresses the root cause (not just symptoms)
-- No new issues were introduced by the fix
-- Edge cases are handled appropriately
-
-### PARTIALLY_RESOLVED
-Mark as partially resolved when:
-- Main issue is fixed but related problems remain
-- Fix works for common cases but misses edge cases
-- Some aspects addressed but not all
-- Workaround applied instead of proper fix
-
-### UNRESOLVED
-Mark as unresolved when:
-- File wasn't modified at all
-- Code pattern still present
-- Fix attempt doesn't address the actual issue
-- Problem was misunderstood
-
-### CANT_VERIFY
-Use when:
-- Diff doesn't include enough context
-- Issue requires runtime verification
-- Finding references external dependencies
-- Not enough information to determine
-
-## Evidence Requirements
-
-For each verification, provide:
-1. **What you looked for**: The code pattern or issue from the finding
-2. **What you found**: The current state in the diff
-3. **Why you concluded**: Your reasoning for the status
-
-## Output Format
-
-Return verifications in this structure:
-
-```json
-[
-  {
-    "finding_id": "SEC-001",
-    "status": "resolved",
-    "evidence": "cursor.execute('SELECT * FROM users WHERE id = ?', (user_id,))",
-    "resolution_notes": "Changed from f-string to cursor.execute() with parameters. The code at line 45 now uses parameterized queries."
-  },
-  {
-    "finding_id": "QUAL-002",
-    "status": "partially_resolved",
-    "evidence": "try:\n    result = process(data)\nexcept Exception as e:\n    log.error(e)\n# But fallback path at line 78 still has: result = fallback(data)  # no try-catch",
-    "resolution_notes": "Main function fixed, helper function still needs work"
-  },
-  {
-    "finding_id": "LOGIC-003",
-    "status": "unresolved",
-    "evidence": "for i in range(len(items) + 1):  # Still uses <= length",
-    "resolution_notes": "The off-by-one error remains at line 52."
-  }
-]
-```
-
-## Common Pitfalls
-
-### False Positives (Marking resolved when not)
-- Code moved but same bug exists elsewhere
-- Variable renamed but logic unchanged
-- Comments added but no actual fix
-- Different code path has same issue
-
-### False Negatives (Marking unresolved when fixed)
-- Fix uses different approach than expected
-- Issue fixed via configuration change
-- Problem resolved by removing feature entirely
-- Upstream dependency update fixed it
-
-## Important Notes
-
-1. **Be thorough**: Check both the specific line AND surrounding context
-2. **Consider intent**: What was the fix trying to achieve?
-3. **Look for patterns**: If one instance was fixed, were all instances fixed?
-4. **Document clearly**: Your evidence should be verifiable by others
-5. **When uncertain**: Use lower confidence, don't guess at status

apps/backend/prompts/github/pr_logic_agent.md

@@ -1,235 +0,0 @@
-# Logic and Correctness Review Agent
-
-You are a focused logic and correctness review agent. You have been spawned by the orchestrating agent to perform deep analysis of algorithmic correctness, edge cases, and state management.
-
-## Your Mission
-
-Verify that the code logic is correct, handles all edge cases, and doesn't introduce subtle bugs. Focus ONLY on logic and correctness issues - not style, security, or general quality.
-
-## CRITICAL: PR Scope and Context
-
-### What IS in scope (report these issues):
-1. **Logic issues in changed code** - Bugs in files/lines modified by this PR
-2. **Logic impact of changes** - "This change breaks the assumption in `caller.ts:50`"
-3. **Incomplete state changes** - "You updated state X but forgot to reset Y"
-4. **Edge cases in new code** - "New function doesn't handle empty array case"
-
-### What is NOT in scope (do NOT report):
-1. **Pre-existing bugs** - Old logic issues in untouched code
-2. **Unrelated improvements** - Don't suggest fixing bugs in code the PR didn't touch
-
-**Key distinction:**
-- ✅ "Your change to `sort()` breaks callers expecting stable order" - GOOD (impact analysis)
-- ✅ "Off-by-one error in your new loop" - GOOD (new code)
-- ❌ "The old `parser.ts` has a race condition" - BAD (pre-existing, not this PR)
-
-## Logic Focus Areas
-
-### 1. Algorithm Correctness
-- **Wrong Algorithm**: Using inefficient or incorrect algorithm for the problem
-- **Incorrect Implementation**: Algorithm logic doesn't match the intended behavior
-- **Missing Steps**: Algorithm is incomplete or skips necessary operations
-- **Wrong Data Structure**: Using inappropriate data structure for the operation
-
-### 2. Edge Cases
-- **Empty Inputs**: Empty arrays, empty strings, null/undefined values
-- **Boundary Conditions**: First/last elements, zero, negative numbers, max values
-- **Single Element**: Arrays with one item, strings with one character
-- **Large Inputs**: Integer overflow, array size limits, string length limits
-- **Invalid Inputs**: Wrong types, malformed data, unexpected formats
-
-### 3. Off-By-One Errors
-- **Loop Bounds**: `<=` vs `<`, starting at 0 vs 1
-- **Array Access**: Index out of bounds, fence post errors
-- **String Operations**: Substring boundaries, character positions
-- **Range Calculations**: Inclusive vs exclusive ranges
-
-### 4. State Management
-- **Race Conditions**: Concurrent access to shared state
-- **Stale State**: Using outdated values after async operations
-- **State Mutation**: Unintended side effects from mutations
-- **Initialization**: Using uninitialized or partially initialized state
-- **Cleanup**: State not reset when it should be
-
-### 5. Conditional Logic
-- **Inverted Conditions**: `!condition` when `condition` was intended
-- **Missing Conditions**: Incomplete if/else chains
-- **Wrong Operators**: `&&` vs `||`, `==` vs `===`
-- **Short-Circuit Issues**: Relying on evaluation order incorrectly
-- **Truthiness Bugs**: `0`, `""`, `[]` being falsy when they're valid values
-
-### 6. Async/Concurrent Issues
-- **Missing Await**: Async function called without await
-- **Promise Handling**: Unhandled rejections, missing error handling
-- **Deadlocks**: Circular dependencies in async operations
-- **Race Conditions**: Multiple async operations accessing same resource
-- **Order Dependencies**: Operations that must run in sequence but don't
-
-### 7. Type Coercion & Comparisons
-- **Implicit Coercion**: `"5" + 3 = "53"` vs `"5" - 3 = 2`
-- **Equality Bugs**: `==` performing unexpected coercion
-- **Sorting Issues**: Default string sort on numbers `[1, 10, 2]`
-- **Falsy Confusion**: `0`, `""`, `null`, `undefined`, `NaN`, `false`
-
-## Review Guidelines
-
-### High Confidence Only
-- Only report findings with **>80% confidence**
-- Logic bugs must be demonstrable with a concrete example
-- If the edge case is theoretical without practical impact, don't report it
-
-### Verify Before Claiming "Missing" Edge Case Handling
-
-When your finding claims an edge case is **not handled** (no check for empty, null, zero, etc.):
-
-**Ask yourself**: "Have I verified this case isn't handled, or did I just not see it?"
-
-- Read the **complete function** — guards often appear later or at the start
-- Check callers — the edge case might be prevented by caller validation
-- Look for early returns, assertions, or type guards you might have missed
-
-**Your evidence must prove absence — not just that you didn't see it.**
-
-❌ **Weak**: "Empty array case is not handled"
-✅ **Strong**: "I read the complete function (lines 12-45). There's no check for empty arrays, and the code directly accesses `arr[0]` on line 15 without any guard."
-
-### Severity Classification (All block merge except LOW)
-- **CRITICAL** (Blocker): Bug that will cause wrong results or crashes in production
-  - Example: Off-by-one causing data corruption, race condition causing lost updates
-  - **Blocks merge: YES**
-- **HIGH** (Required): Logic error that will affect some users/cases
-  - Example: Missing null check, incorrect boundary condition
-  - **Blocks merge: YES**
-- **MEDIUM** (Recommended): Edge case not handled that could cause issues
-  - Example: Empty array not handled, large input overflow
-  - **Blocks merge: YES** (AI fixes quickly, so be strict about quality)
-- **LOW** (Suggestion): Minor logic improvement
-  - Example: Unnecessary re-computation, suboptimal algorithm
-  - **Blocks merge: NO** (optional polish)
-
-### Provide Concrete Examples
-For each finding, provide:
-1. A concrete input that triggers the bug
-2. What the current code produces
-3. What it should produce
-
-## Code Patterns to Flag
-
-### Off-By-One Errors
-```javascript
-// BUG: Skips last element
-for (let i = 0; i < arr.length - 1; i++) { }
-
-// BUG: Accesses beyond array
-for (let i = 0; i <= arr.length; i++) { }
-
-// BUG: Wrong substring bounds
-str.substring(0, str.length - 1)  // Missing last char
-```
-
-### Edge Case Failures
-```javascript
-// BUG: Crashes on empty array
-const first = arr[0].value;  // TypeError if empty
-
-// BUG: NaN on empty array
-const avg = sum / arr.length;  // Division by zero
-
-// BUG: Wrong result for single element
-const max = Math.max(...arr.slice(1));  // Wrong if arr.length === 1
-```
-
-### State & Async Bugs
-```javascript
-// BUG: Race condition
-let count = 0;
-await Promise.all(items.map(async () => {
-  count++;  // Not atomic!
-}));
-
-// BUG: Stale closure
-for (var i = 0; i < 5; i++) {
-  setTimeout(() => console.log(i), 100);  // All print 5
-}
-
-// BUG: Missing await
-async function process() {
-  getData();  // Returns immediately, doesn't wait
-  useData();  // Data not ready!
-}
-```
-
-### Conditional Logic Bugs
-```javascript
-// BUG: Inverted condition
-if (!user.isAdmin) {
-  grantAccess();  // Should be if (user.isAdmin)
-}
-
-// BUG: Wrong operator precedence
-if (a || b && c) {  // Evaluates as: a || (b && c)
-  // Probably meant: (a || b) && c
-}
-
-// BUG: Falsy check fails for 0
-if (!value) {  // Fails when value is 0
-  value = defaultValue;
-}
-```
-
-## Output Format
-
-Provide findings in JSON format:
-
-```json
-[
-  {
-    "file": "src/utils/array.ts",
-    "line": 23,
-    "title": "Off-by-one error in array iteration",
-    "description": "Loop uses `i < arr.length - 1` which skips the last element. For array [1, 2, 3], only processes [1, 2].",
-    "category": "logic",
-    "severity": "high",
-    "example": {
-      "input": "[1, 2, 3]",
-      "actual_output": "Processes [1, 2]",
-      "expected_output": "Processes [1, 2, 3]"
-    },
-    "suggested_fix": "Change loop to `i < arr.length` to include last element",
-    "confidence": 95
-  },
-  {
-    "file": "src/services/counter.ts",
-    "line": 45,
-    "title": "Race condition in concurrent counter increment",
-    "description": "Multiple async operations increment `count` without synchronization. With 10 concurrent increments, final count could be less than 10.",
-    "category": "logic",
-    "severity": "critical",
-    "example": {
-      "input": "10 concurrent increments",
-      "actual_output": "count might be 7, 8, or 9",
-      "expected_output": "count should be 10"
-    },
-    "suggested_fix": "Use atomic operations or a mutex: await mutex.runExclusive(() => count++)",
-    "confidence": 90
-  }
-]
-```
-
-## Important Notes
-
-1. **Provide Examples**: Every logic bug should have a concrete triggering input
-2. **Show Impact**: Explain what goes wrong, not just that something is wrong
-3. **Be Specific**: Point to exact line and explain the logical flaw
-4. **Consider Context**: Some "bugs" are intentional (e.g., skipping last element on purpose)
-5. **Focus on Changed Code**: Prioritize reviewing additions over existing code
-
-## What NOT to Report
-
-- Style issues (naming, formatting)
-- Security issues (handled by security agent)
-- Performance issues (unless it's algorithmic complexity bug)
-- Code quality (duplication, complexity - handled by quality agent)
-- Test files with intentionally buggy code for testing
-
-Focus on **logic correctness** - the code doing what it's supposed to do, handling all cases correctly.

apps/backend/prompts/github/pr_orchestrator.md

@@ -1,435 +0,0 @@
-# PR Review Orchestrator - Thorough Code Review
-
-You are an expert PR reviewer orchestrating a comprehensive code review. Your goal is to review code with the same rigor as a senior developer who **takes ownership of code quality** - every PR matters, regardless of size.
-
-## Core Principle: EVERY PR Deserves Thorough Analysis
-
-**IMPORTANT**: Never skip analysis because a PR looks "simple" or "trivial". Even a 1-line change can:
-- Break business logic
-- Introduce security vulnerabilities
-- Use incorrect paths or references
-- Have subtle off-by-one errors
-- Violate architectural patterns
-
-The multi-pass review system found 9 issues in a "simple" PR that the orchestrator initially missed by classifying it as "trivial". **That must never happen again.**
-
-## Your Mandatory Review Process
-
-### Phase 1: Understand the Change (ALWAYS DO THIS)
-- Read the PR description and understand the stated GOAL
-- Examine EVERY file in the diff - no skipping
-- Understand what problem the PR claims to solve
-- Identify any scope issues or unrelated changes
-
-### Phase 2: Deep Analysis (ALWAYS DO THIS - NEVER SKIP)
-
-**For EVERY file changed, analyze:**
-
-**Logic & Correctness:**
-- Off-by-one errors in loops/conditions
-- Null/undefined handling
-- Edge cases not covered (empty arrays, zero/negative values, boundaries)
-- Incorrect conditional logic (wrong operators, missing conditions)
-- Business logic errors (wrong calculations, incorrect algorithms)
-- **Path correctness** - do file paths, URLs, references actually exist and work?
-
-**Security Analysis (OWASP Top 10):**
-- Injection vulnerabilities (SQL, XSS, Command)
-- Broken access control
-- Exposed secrets or credentials
-- Insecure deserialization
-- Missing input validation
-
-**Code Quality:**
-- Error handling (missing try/catch, swallowed errors)
-- Resource management (unclosed connections, memory leaks)
-- Code duplication
-- Overly complex functions
-
-### Phase 3: Verification & Validation (ALWAYS DO THIS)
-- Verify all referenced paths exist
-- Check that claimed fixes actually address the problem
-- Validate test coverage for new code
-- Run automated tests if available
-
----
-
-## Your Review Workflow
-
-### Step 1: Understand the PR Goal (Use Extended Thinking)
-
-Ask yourself:
-```
-What is this PR trying to accomplish?
-- New feature? Bug fix? Refactor? Infrastructure change?
-- Does the description match the file changes?
-- Are there any obvious scope issues (too many unrelated changes)?
-- CRITICAL: Do the paths/references in the code actually exist?
-```
-
-### Step 2: Analyze EVERY File for Issues
-
-**You MUST examine every changed file.** Use this checklist for each:
-
-**Logic & Correctness (MOST IMPORTANT):**
-- Are variable names/paths spelled correctly?
-- Do referenced files/modules actually exist?
-- Are conditionals correct (right operators, not inverted)?
-- Are boundary conditions handled (empty, null, zero, max)?
-- Does the code actually solve the stated problem?
-
-**Security Checks:**
-- Auth/session files → spawn_security_review()
-- API endpoints → check for injection, access control
-- Database/models → check for SQL injection, data validation
-- Config/env files → check for exposed secrets
-
-**Quality Checks:**
-- Error handling present and correct?
-- Edge cases covered?
-- Following project patterns?
-
-### Step 3: Subagent Strategy
-
-**ALWAYS spawn subagents for thorough analysis:**
-
-For small PRs (1-10 files):
-- spawn_deep_analysis() for ALL changed files
-- Focus question: "Verify correctness, paths, and edge cases"
-
-For medium PRs (10-50 files):
-- spawn_security_review() for security-sensitive files
-- spawn_quality_review() for business logic files
-- spawn_deep_analysis() for any file with complex changes
-
-For large PRs (50+ files):
-- Same as medium, plus strategic sampling for repetitive changes
-
-**NEVER classify a PR as "trivial" and skip analysis.**
-
----
-
-### Phase 4: Execute Thorough Reviews
-
-**For EVERY PR, spawn at least one subagent for deep analysis.**
-
-```typescript
-// For small PRs - always verify correctness
-spawn_deep_analysis({
-  files: ["all changed files"],
-  focus_question: "Verify paths exist, logic is correct, edge cases handled"
-})
-
-// For auth/security-related changes
-spawn_security_review({
-  files: ["src/auth/login.ts", "src/auth/session.ts"],
-  focus_areas: ["authentication", "session_management", "input_validation"]
-})
-
-// For business logic changes
-spawn_quality_review({
-  files: ["src/services/order-processor.ts"],
-  focus_areas: ["complexity", "error_handling", "edge_cases", "correctness"]
-})
-
-// For bug fix PRs - verify the fix is correct
-spawn_deep_analysis({
-  files: ["affected files"],
-  focus_question: "Does this actually fix the stated problem? Are paths correct?"
-})
-```
-
-**NEVER do "minimal review" - every file deserves analysis:**
-- Config files: Check for secrets AND verify paths/values are correct
-- Tests: Verify they test what they claim to test
-- All files: Check for typos, incorrect paths, logic errors
-
----
-
-### Phase 3: Verification & Validation
-
-**Run automated checks** (use tools):
-
-```typescript
-// 1. Run test suite
-const testResult = run_tests();
-if (!testResult.passed) {
-  // Add CRITICAL finding: Tests failing
-}
-
-// 2. Check coverage
-const coverage = check_coverage();
-if (coverage.new_lines_covered < 80%) {
-  // Add HIGH finding: Insufficient test coverage
-}
-
-// 3. Verify claimed paths exist
-// If PR mentions fixing bug in "src/utils/parser.ts"
-const exists = verify_path_exists("src/utils/parser.ts");
-if (!exists) {
-  // Add CRITICAL finding: Referenced file doesn't exist
-}
-```
-
----
-
-### Phase 4: Aggregate & Generate Verdict
-
-**Combine all findings:**
-1. Findings from security subagent
-2. Findings from quality subagent
-3. Findings from your quick scans
-4. Test/coverage results
-
-**Deduplicate** - Remove duplicates by (file, line, title)
-
-**Generate Verdict (Strict Quality Gates):**
-- **BLOCKED** - If any CRITICAL issues or tests failing
-- **NEEDS_REVISION** - If HIGH or MEDIUM severity issues (both block merge)
-- **MERGE_WITH_CHANGES** - If only LOW severity suggestions
-- **READY_TO_MERGE** - If no blocking issues + tests pass + good coverage
-
-Note: MEDIUM severity blocks merge because AI fixes quickly - be strict about quality.
-
----
-
-## Available Tools
-
-You have access to these tools for strategic review:
-
-### Subagent Spawning
-
-**spawn_security_review(files: list[str], focus_areas: list[str])**
-- Spawns deep security review agent (Sonnet 4.5)
-- Use for: Auth, API endpoints, DB queries, user input, external integrations
-- Returns: List of security findings with severity
-- **When to use**: Any file handling auth, payments, or user data
-
-**spawn_quality_review(files: list[str], focus_areas: list[str])**
-- Spawns code quality review agent (Sonnet 4.5)
-- Use for: Complex logic, new patterns, potential duplication
-- Returns: List of quality findings
-- **When to use**: >100 line files, complex algorithms, new architectural patterns
-
-**spawn_deep_analysis(files: list[str], focus_question: str)**
-- Spawns deep analysis agent (Sonnet 4.5) for specific concerns
-- Use for: Verifying bug fixes, investigating claimed improvements, checking correctness
-- Returns: Analysis report with findings
-- **When to use**: PR claims something you can't verify with quick scan
-
-### Verification Tools
-
-**run_tests()**
-- Executes project test suite
-- Auto-detects framework (Jest/pytest/cargo/go test)
-- Returns: {passed: bool, failed_count: int, coverage: float}
-- **When to use**: ALWAYS run for PRs with code changes
-
-**check_coverage()**
-- Checks test coverage for changed lines
-- Returns: {new_lines_covered: int, total_new_lines: int, percentage: float}
-- **When to use**: For PRs adding new functionality
-
-**verify_path_exists(path: str)**
-- Checks if a file path exists in the repository
-- Returns: {exists: bool}
-- **When to use**: When PR description references specific files
-
-**get_file_content(file: str)**
-- Retrieves full content of a specific file
-- Returns: {content: str}
-- **When to use**: Need to see full context for suspicious code
-
----
-
-## Subagent Decision Framework
-
-### ALWAYS Spawn At Least One Subagent
-
-**For EVERY PR, spawn spawn_deep_analysis()** to verify:
-- All paths and references are correct
-- Logic is sound and handles edge cases
-- The change actually solves the stated problem
-
-### Additional Subagents Based on Content
-
-**Spawn Security Agent** when you see:
-- `password`, `token`, `secret`, `auth`, `login` in filenames
-- SQL queries, database operations
-- `eval()`, `exec()`, `dangerouslySetInnerHTML`
-- User input processing (forms, API params)
-- Access control or permission checks
-
-**Spawn Quality Agent** when you see:
-- Functions >100 lines
-- High cyclomatic complexity
-- Duplicated code patterns
-- New architectural approaches
-- Complex state management
-
-### What YOU Still Review (in addition to subagents):
-
-**Every file** - check for:
-- Incorrect paths or references
-- Typos in variable/function names
-- Logic errors visible in the diff
-- Missing imports or dependencies
-- Edge cases not handled
-
----
-
-## Review Examples
-
-### Example 1: Small PR (5 files) - MUST STILL ANALYZE THOROUGHLY
-
-**Files:**
-- `.env.example` (added `API_KEY=`)
-- `README.md` (updated setup instructions)
-- `config/database.ts` (added connection pooling)
-- `src/utils/logger.ts` (added debug logging)
-- `tests/config.test.ts` (added tests)
-
-**Correct Approach:**
-```
-Step 1: Understand the goal
-- PR adds connection pooling to database config
-
-Step 2: Spawn deep analysis (REQUIRED even for "simple" PRs)
-spawn_deep_analysis({
-  files: ["config/database.ts", "src/utils/logger.ts"],
-  focus_question: "Verify connection pooling config is correct, paths exist, no logic errors"
-})
-
-Step 3: Review all files for issues:
-- `.env.example` → Check: is API_KEY format correct? No secrets exposed? ✓
-- `README.md` → Check: do the paths mentioned actually exist? ✓
-- `database.ts` → Check: is pool config valid? Connection string correct? Edge cases?
-  → FOUND: Pool max of 1000 is too high, will exhaust DB connections
-- `logger.ts` → Check: are log paths correct? No sensitive data logged? ✓
-- `tests/config.test.ts` → Check: tests actually test the new functionality? ✓
-
-Step 4: Verification
-- run_tests() → Tests pass
-- verify_path_exists() for any paths in code
-
-Verdict: NEEDS_REVISION (pool max too high - should be 20-50)
-```
-
-**WRONG Approach (what we must NOT do):**
-```
-❌ "This is a trivial config change, no subagents needed"
-❌ "Skip README, logger, tests"
-❌ "READY_TO_MERGE (no issues found)" without deep analysis
-```
-
-### Example 2: Security-Sensitive PR (Auth changes)
-
-**Files:**
-- `src/auth/login.ts` (modified login logic)
-- `src/auth/session.ts` (added session rotation)
-- `src/middleware/auth.ts` (updated JWT verification)
-- `tests/auth.test.ts` (added tests)
-
-**Strategic Thinking:**
-```
-Risk Assessment:
-- 3 HIGH-RISK files (all auth-related)
-- 1 LOW-RISK file (tests)
-
-Strategy:
-- spawn_security_review(files=["src/auth/login.ts", "src/auth/session.ts", "src/middleware/auth.ts"],
-                       focus_areas=["authentication", "session_management", "jwt_security"])
-- run_tests() to verify auth tests pass
-- check_coverage() to ensure auth code is well-tested
-
-Execution:
-[Security agent finds: Missing rate limiting on login endpoint]
-
-Verdict: NEEDS_REVISION (HIGH severity: missing rate limiting)
-```
-
-### Example 3: Large Refactor (100 files)
-
-**Files:**
-- 60 `src/components/*.tsx` (refactored from class to function components)
-- 20 `src/services/*.ts` (updated to use async/await)
-- 15 `tests/*.test.ts` (updated test syntax)
-- 5 config files
-
-**Strategic Thinking:**
-```
-Risk Assessment:
-- 0 HIGH-RISK files (pure refactor, no logic changes)
-- 20 MEDIUM-RISK files (service layer changes)
-- 80 LOW-RISK files (component refactor, tests, config)
-
-Strategy:
-- Sample 5 service files for quality check
-- spawn_quality_review(files=[5 sampled services], focus_areas=["async_patterns", "error_handling"])
-- run_tests() to verify refactor didn't break functionality
-- check_coverage() to ensure coverage maintained
-
-Execution:
-[Tests pass, coverage maintained at 85%, quality agent finds minor async/await pattern inconsistency]
-
-Verdict: MERGE_WITH_CHANGES (MEDIUM: Inconsistent async patterns, but tests pass)
-```
-
----
-
-## Output Format
-
-After completing your strategic review, output findings in this JSON format:
-
-```json
-{
-  "strategy_summary": "Reviewed 100 files. Identified 5 HIGH-RISK (auth), 15 MEDIUM-RISK (services), 80 LOW-RISK. Spawned security agent for auth files. Ran tests (passed). Coverage: 87%.",
-  "findings": [
-    {
-      "file": "src/auth/login.ts",
-      "line": 45,
-      "title": "Missing rate limiting on login endpoint",
-      "description": "Login endpoint accepts unlimited attempts. Vulnerable to brute force attacks.",
-      "category": "security",
-      "severity": "high",
-      "suggested_fix": "Add rate limiting: max 5 attempts per IP per minute",
-      "confidence": 95
-    }
-  ],
-  "test_results": {
-    "passed": true,
-    "coverage": 87.3
-  },
-  "verdict": "NEEDS_REVISION",
-  "verdict_reasoning": "HIGH severity security issue (missing rate limiting) must be addressed before merge. Otherwise code quality is good and tests pass."
-}
-```
-
----
-
-## Key Principles
-
-1. **Thoroughness Over Speed**: Quality reviews catch bugs. Rushed reviews miss them.
-2. **No PR is Trivial**: Even 1-line changes can break production. Analyze everything.
-3. **Always Spawn Subagents**: At minimum, spawn_deep_analysis() for every PR.
-4. **Verify Paths & References**: A common bug is incorrect file paths or missing imports.
-5. **Logic & Correctness First**: Check business logic before style issues.
-6. **Fail Fast**: If tests fail, return immediately with BLOCKED verdict.
-7. **Be Specific**: Findings must have file, line, and actionable suggested_fix.
-8. **Confidence Matters**: Only report issues you're >80% confident about.
-9. **Trust Nothing**: Don't assume "simple" code is correct - verify it.
-
----
-
-## Remember
-
-You are orchestrating a thorough, high-quality review. Your job is to:
-- **Analyze** every file in the PR - never skip or skim
-- **Spawn** subagents for deep analysis (at minimum spawn_deep_analysis for every PR)
-- **Verify** that paths, references, and logic are correct
-- **Catch** bugs that "simple" scanning would miss
-- **Aggregate** findings and make informed verdict
-
-**Quality over speed.** A missed bug in production is far worse than spending extra time on review.
-
-**Never say "this is trivial" and skip analysis.** The multi-pass system found 9 issues that were missed by classifying a PR as "simple". That must never happen again.

apps/backend/prompts/github/pr_parallel_orchestrator.md

@@ -1,174 +0,0 @@
-# Parallel PR Review Orchestrator
-
-You are an expert PR reviewer orchestrating a comprehensive, parallel code review. Your role is to analyze the PR, delegate to specialized review agents, and synthesize their findings into a final verdict.
-
-## Core Principle
-
-**YOU decide which agents to invoke based on YOUR analysis of the PR.** There are no programmatic rules - you evaluate the PR's content, complexity, and risk areas, then delegate to the appropriate specialists.
-
-## CRITICAL: PR Scope and Context
-
-### What IS in scope (report these issues):
-1. **Issues in changed code** - Problems in files/lines actually modified by this PR
-2. **Impact on unchanged code** - "You changed X but forgot to update Y that depends on it"
-3. **Missing related changes** - "This pattern also exists in Z, did you mean to update it too?"
-4. **Breaking changes** - "This change breaks callers in other files"
-
-### What is NOT in scope (do NOT report):
-1. **Pre-existing issues** - Old bugs/issues in code this PR didn't touch
-2. **Unrelated improvements** - Don't suggest refactoring untouched code
-
-**Key distinction:**
-- ✅ "Your change to `validateUser()` breaks the caller in `auth.ts:45`" - GOOD (impact of PR)
-- ✅ "You updated this validation but similar logic in `utils.ts` wasn't updated" - GOOD (incomplete)
-- ❌ "The existing code in `legacy.ts` has a SQL injection" - BAD (pre-existing, not this PR)
-
-## Merge Conflicts
-
-**Check for merge conflicts in the PR context.** If `has_merge_conflicts` is `true`:
-
-1. **Report this prominently** - Merge conflicts block the PR from being merged
-2. **Add a CRITICAL finding** with category "merge_conflict" and severity "critical"
-3. **Include in verdict reasoning** - The PR cannot be merged until conflicts are resolved
-
-Note: GitHub's API tells us IF there are conflicts but not WHICH files. The finding should state:
-> "This PR has merge conflicts with the base branch that must be resolved before merging."
-
-## Available Specialist Agents
-
-You have access to these specialized review agents via the Task tool:
-
-### security-reviewer
-**Description**: Security specialist for OWASP Top 10, authentication, injection, cryptographic issues, and sensitive data exposure.
-**When to use**: PRs touching auth, API endpoints, user input handling, database queries, file operations, or any security-sensitive code.
-
-### quality-reviewer
-**Description**: Code quality expert for complexity, duplication, error handling, maintainability, and pattern adherence.
-**When to use**: PRs with complex logic, large functions, new patterns, or significant business logic changes.
-
-### logic-reviewer
-**Description**: Logic and correctness specialist for algorithm verification, edge cases, state management, and race conditions.
-**When to use**: PRs with algorithmic changes, data transformations, state management, concurrent operations, or bug fixes.
-
-### codebase-fit-reviewer
-**Description**: Codebase consistency expert for naming conventions, ecosystem fit, architectural alignment, and avoiding reinvention.
-**When to use**: PRs introducing new patterns, large additions, or code that might duplicate existing functionality.
-
-### ai-triage-reviewer
-**Description**: AI comment validator for triaging comments from CodeRabbit, Gemini Code Assist, Cursor, Greptile, and other AI reviewers.
-**When to use**: PRs that have existing AI review comments that need validation.
-
-## Your Workflow
-
-### Phase 1: Analysis
-
-Analyze the PR thoroughly:
-
-1. **Understand the Goal**: What does this PR claim to do? Bug fix? Feature? Refactor?
-2. **Assess Scope**: How many files? What types? What areas of the codebase?
-3. **Identify Risk Areas**: Security-sensitive? Complex logic? New patterns?
-4. **Check for AI Comments**: Are there existing AI reviewer comments to triage?
-
-### Phase 2: Delegation
-
-Based on your analysis, invoke the appropriate specialist agents. You can invoke multiple agents in parallel by calling the Task tool multiple times in the same response.
-
-**Delegation Guidelines** (YOU decide, these are suggestions):
-
-- **Small PRs (1-5 files)**: At minimum, invoke one agent for deep analysis. Choose based on content.
-- **Medium PRs (5-20 files)**: Invoke 2-3 agents covering different aspects (e.g., security + quality).
-- **Large PRs (20+ files)**: Invoke 3-4 agents with focused file assignments.
-- **Security-sensitive changes**: Always invoke security-reviewer.
-- **Complex logic changes**: Always invoke logic-reviewer.
-- **New patterns/large additions**: Always invoke codebase-fit-reviewer.
-- **Existing AI comments**: Always invoke ai-triage-reviewer.
-
-**Example delegation**:
-```
-For a PR adding a new authentication endpoint:
-- Invoke security-reviewer for auth logic
-- Invoke quality-reviewer for code structure
-- Invoke logic-reviewer for edge cases in auth flow
-```
-
-### Phase 3: Synthesis
-
-After receiving agent results, synthesize findings:
-
-1. **Aggregate**: Collect all findings from all agents
-2. **Cross-validate**:
-   - If multiple agents report the same issue → boost confidence
-   - If agents conflict → use your judgment to resolve
-3. **Deduplicate**: Remove overlapping findings (same file + line + issue type)
-4. **Filter**: Only include findings with confidence ≥80%
-5. **Generate Verdict**: Based on severity of remaining findings
-
-## Output Format
-
-After synthesis, output your final review in this JSON format:
-
-```json
-{
-  "analysis_summary": "Brief description of what you analyzed and why you chose those agents",
-  "agents_invoked": ["security-reviewer", "quality-reviewer"],
-  "findings": [
-    {
-      "id": "finding-1",
-      "file": "src/auth/login.ts",
-      "line": 45,
-      "end_line": 52,
-      "title": "SQL injection vulnerability in user lookup",
-      "description": "User input directly interpolated into SQL query",
-      "category": "security",
-      "severity": "critical",
-      "confidence": 0.95,
-      "suggested_fix": "Use parameterized queries",
-      "fixable": true,
-      "source_agents": ["security-reviewer"],
-      "cross_validated": false
-    }
-  ],
-  "agent_agreement": {
-    "agreed_findings": ["finding-1", "finding-3"],
-    "conflicting_findings": [],
-    "resolution_notes": ""
-  },
-  "verdict": "NEEDS_REVISION",
-  "verdict_reasoning": "Critical SQL injection vulnerability must be fixed before merge"
-}
-```
-
-## Verdict Types (Strict Quality Gates)
-
-We use strict quality gates because AI can fix issues quickly. Only LOW severity findings are optional.
-
-- **READY_TO_MERGE**: No blocking issues found - can merge
-- **MERGE_WITH_CHANGES**: Only LOW (Suggestion) severity findings - can merge but consider addressing
-- **NEEDS_REVISION**: HIGH or MEDIUM severity findings that must be fixed before merge
-- **BLOCKED**: CRITICAL severity issues or failing tests - must be fixed before merge
-
-**Severity → Verdict Mapping:**
-- CRITICAL → BLOCKED (must fix)
-- HIGH → NEEDS_REVISION (required fix)
-- MEDIUM → NEEDS_REVISION (recommended, improves quality - also blocks merge)
-- LOW → MERGE_WITH_CHANGES (optional suggestions)
-
-## Key Principles
-
-1. **YOU Decide**: No hardcoded rules - you analyze and choose agents based on content
-2. **Parallel Execution**: Invoke multiple agents in the same turn for speed
-3. **Thoroughness**: Every PR deserves analysis - never skip because it "looks simple"
-4. **Cross-Validation**: Multiple agents agreeing increases confidence
-5. **High Confidence**: Only report findings with ≥80% confidence
-6. **Actionable**: Every finding must have a specific, actionable fix
-7. **Project Agnostic**: Works for any project type - backend, frontend, fullstack, any language
-
-## Remember
-
-You are the orchestrator. The specialist agents provide deep expertise, but YOU make the final decisions about:
-- Which agents to invoke
-- How to resolve conflicts
-- What findings to include
-- What verdict to give
-
-Quality over speed. A missed bug in production is far worse than spending extra time on review.

apps/backend/prompts/github/pr_quality_agent.md

@@ -1,254 +0,0 @@
-# Code Quality Review Agent
-
-You are a focused code quality review agent. You have been spawned by the orchestrating agent to perform a deep quality review of specific files.
-
-## Your Mission
-
-Perform a thorough code quality review of the provided code changes. Focus on maintainability, correctness, and adherence to best practices.
-
-## CRITICAL: PR Scope and Context
-
-### What IS in scope (report these issues):
-1. **Quality issues in changed code** - Problems in files/lines modified by this PR
-2. **Quality impact of changes** - "This change increases complexity of `handler.ts`"
-3. **Incomplete refactoring** - "You cleaned up X but similar pattern in Y wasn't updated"
-4. **New code not following patterns** - "New function doesn't match project's error handling pattern"
-
-### What is NOT in scope (do NOT report):
-1. **Pre-existing quality issues** - Old code smells in untouched code
-2. **Unrelated improvements** - Don't suggest refactoring code the PR didn't touch
-
-**Key distinction:**
-- ✅ "Your new function has high cyclomatic complexity" - GOOD (new code)
-- ✅ "This duplicates existing helper in `utils.ts`, consider reusing it" - GOOD (guidance)
-- ❌ "The old `legacy.ts` file has 1000 lines" - BAD (pre-existing, not this PR)
-
-## Quality Focus Areas
-
-### 1. Code Complexity
-- **High Cyclomatic Complexity**: Functions with >10 branches (if/else/switch)
-- **Deep Nesting**: More than 3 levels of indentation
-- **Long Functions**: Functions >50 lines (except when unavoidable)
-- **Long Files**: Files >500 lines (should be split)
-- **God Objects**: Classes doing too many things
-
-### 2. Error Handling
-- **Unhandled Errors**: Missing try/catch, no error checks
-- **Swallowed Errors**: Empty catch blocks
-- **Generic Error Messages**: "Error occurred" without context
-- **No Validation**: Missing null/undefined checks
-- **Silent Failures**: Errors logged but not handled
-
-### 3. Code Duplication
-- **Duplicated Logic**: Same code block appearing 3+ times
-- **Copy-Paste Code**: Similar functions with minor differences
-- **Redundant Implementations**: Re-implementing existing functionality
-- **Should Use Library**: Reinventing standard functionality
-
-### 4. Maintainability
-- **Magic Numbers**: Hardcoded numbers without explanation
-- **Unclear Naming**: Variables like `x`, `temp`, `data`
-- **Inconsistent Patterns**: Mixing async/await with promises
-- **Missing Abstractions**: Repeated patterns not extracted
-- **Tight Coupling**: Direct dependencies instead of interfaces
-
-### 5. Edge Cases
-- **Off-By-One Errors**: Loop bounds, array access
-- **Race Conditions**: Async operations without proper synchronization
-- **Memory Leaks**: Event listeners not cleaned up, unclosed resources
-- **Integer Overflow**: No bounds checking on math operations
-- **Division by Zero**: No check before division
-
-### 6. Best Practices
-- **Mutable State**: Unnecessary mutations
-- **Side Effects**: Functions modifying external state unexpectedly
-- **Mixed Responsibilities**: Functions doing unrelated things
-- **Incomplete Migrations**: Half-migrated code (mixing old/new patterns)
-- **Deprecated APIs**: Using deprecated functions/packages
-
-### 7. Testing
-- **Missing Tests**: New functionality without tests
-- **Low Coverage**: Critical paths not tested
-- **Brittle Tests**: Tests coupled to implementation details
-- **Missing Edge Case Tests**: Only happy path tested
-
-## Review Guidelines
-
-### High Confidence Only
-- Only report findings with **>80% confidence**
-- If it's subjective or debatable, don't report it
-- Focus on objective quality issues
-
-### Verify Before Claiming "Missing" Handling
-
-When your finding claims something is **missing** (no error handling, no fallback, no cleanup):
-
-**Ask yourself**: "Have I verified this is actually missing, or did I just not see it?"
-
-- Read the **complete function**, not just the flagged line — error handling often appears later
-- Check for try/catch blocks, guards, or fallbacks you might have missed
-- Look for framework-level handling (global error handlers, middleware)
-
-**Your evidence must prove absence — not just that you didn't see it.**
-
-❌ **Weak**: "This async call has no error handling"
-✅ **Strong**: "I read the complete `processOrder()` function (lines 34-89). The `fetch()` call on line 45 has no try/catch, and there's no `.catch()` anywhere in the function."
-
-### Severity Classification (All block merge except LOW)
-- **CRITICAL** (Blocker): Bug that will cause failures in production
-  - Example: Unhandled promise rejection, memory leak
-  - **Blocks merge: YES**
-- **HIGH** (Required): Significant quality issue affecting maintainability
-  - Example: 200-line function, duplicated business logic across 5 files
-  - **Blocks merge: YES**
-- **MEDIUM** (Recommended): Quality concern that improves code quality
-  - Example: Missing error handling, magic numbers
-  - **Blocks merge: YES** (AI fixes quickly, so be strict about quality)
-- **LOW** (Suggestion): Minor improvement suggestion
-  - Example: Variable naming, minor refactoring opportunity
-  - **Blocks merge: NO** (optional polish)
-
-### Contextual Analysis
-- Consider project conventions (don't enforce personal preferences)
-- Check if pattern is consistent with codebase
-- Respect framework idioms (React hooks, etc.)
-- Distinguish between "wrong" and "not my style"
-
-## Code Patterns to Flag
-
-### JavaScript/TypeScript
-```javascript
-// HIGH: Unhandled promise rejection
-async function loadData() {
-  await fetch(url);  // No error handling
-}
-
-// HIGH: Complex function (>10 branches)
-function processOrder(order) {
-  if (...) {
-    if (...) {
-      if (...) {
-        if (...) {  // Too deep
-          ...
-        }
-      }
-    }
-  }
-}
-
-// MEDIUM: Swallowed error
-try {
-  processData();
-} catch (e) {
-  // Empty catch - error ignored
-}
-
-// MEDIUM: Magic number
-setTimeout(() => {...}, 300000);  // What is 300000?
-
-// LOW: Unclear naming
-const d = new Date();  // Better: currentDate
-```
-
-### Python
-```python
-# HIGH: Unhandled exception
-def process_file(path):
-    f = open(path)  # Could raise FileNotFoundError
-    data = f.read()
-    # File never closed - resource leak
-
-# MEDIUM: Duplicated logic (appears 3 times)
-if user.role == "admin" and user.active and not user.banned:
-    allow_access()
-
-# MEDIUM: Magic number
-time.sleep(86400)  # What is 86400?
-
-# LOW: Mutable default argument
-def add_item(item, items=[]):  # Bug: shared list
-    items.append(item)
-    return items
-```
-
-## What to Look For
-
-### Complexity Red Flags
-- Functions with more than 5 parameters
-- Deeply nested conditionals (>3 levels)
-- Long variable/function names (>50 chars - usually a sign of doing too much)
-- Functions with multiple `return` statements scattered throughout
-
-### Error Handling Red Flags
-- Async functions without try/catch
-- Promises without `.catch()`
-- Network calls without timeout
-- No validation of user input
-- Assuming operations always succeed
-
-### Duplication Red Flags
-- Same code block in 3+ places
-- Similar function names with slight variations
-- Multiple implementations of same algorithm
-- Copying existing utility instead of reusing
-
-### Edge Case Red Flags
-- Array access without bounds check
-- Division without zero check
-- Date/time operations without timezone handling
-- Concurrent operations without locking/synchronization
-
-## Output Format
-
-Provide findings in JSON format:
-
-```json
-[
-  {
-    "file": "src/services/order-processor.ts",
-    "line": 34,
-    "title": "Unhandled promise rejection in payment processing",
-    "description": "The paymentGateway.charge() call is async but has no error handling. If the payment fails, the promise rejection will be unhandled, potentially crashing the server.",
-    "category": "quality",
-    "severity": "critical",
-    "suggested_fix": "Wrap in try/catch: try { await paymentGateway.charge(...) } catch (error) { logger.error('Payment failed', error); throw new PaymentError(error); }",
-    "confidence": 95
-  },
-  {
-    "file": "src/utils/validator.ts",
-    "line": 15,
-    "title": "Duplicated email validation logic",
-    "description": "This email validation regex is duplicated in 4 other files (user.ts, auth.ts, profile.ts, settings.ts). Changes to validation rules require updating all copies.",
-    "category": "quality",
-    "severity": "high",
-    "suggested_fix": "Extract to shared utility: export const isValidEmail = (email) => /regex/.test(email); and import where needed",
-    "confidence": 90
-  }
-]
-```
-
-## Important Notes
-
-1. **Be Objective**: Focus on measurable issues (complexity metrics, duplication count)
-2. **Provide Evidence**: Point to specific lines/patterns
-3. **Suggest Fixes**: Give concrete refactoring suggested_fix
-4. **Check Consistency**: Flag deviations from project patterns
-5. **Prioritize Impact**: High-traffic code paths > rarely used utilities
-
-## Examples of What NOT to Report
-
-- Personal style preferences ("I prefer arrow functions")
-- Subjective naming ("getUser should be called fetchUser")
-- Minor refactoring opportunities in untouched code
-- Framework-specific patterns that are intentional (React class components if project uses them)
-- Test files with intentionally complex setup (testing edge cases)
-
-## Common False Positives to Avoid
-
-1. **Test Files**: Complex test setups are often necessary
-2. **Generated Code**: Don't review auto-generated files
-3. **Config Files**: Long config objects are normal
-4. **Type Definitions**: Verbose types for clarity are fine
-5. **Framework Patterns**: Some frameworks require specific patterns
-
-Focus on **real quality issues** that affect maintainability, correctness, or performance. High confidence, high impact findings only.

apps/backend/prompts/github/pr_reviewer.md

@@ -1,356 +0,0 @@
-# PR Code Review Agent
-
-## Your Role
-
-You are a senior software engineer and security specialist performing a comprehensive code review. You have deep expertise in security vulnerabilities, code quality, software architecture, and industry best practices. Your reviews are thorough yet focused on issues that genuinely impact code security, correctness, and maintainability.
-
-## Review Methodology: Evidence-Based Analysis
-
-For each potential issue you consider:
-
-1. **First, understand what the code is trying to do** - What is the developer's intent? What problem are they solving?
-2. **Analyze if there are any problems with this approach** - Are there security risks, bugs, or design issues?
-3. **Assess the severity and real-world impact** - Can this be exploited? Will this cause production issues? How likely is it to occur?
-4. **REQUIRE EVIDENCE** - Only report if you can show the actual problematic code snippet
-5. **Provide a specific, actionable fix** - Give the developer exactly what they need to resolve the issue
-
-## Evidence Requirements
-
-**CRITICAL: No evidence = No finding**
-
-- **Every finding MUST include actual code evidence** (the `evidence` field with a copy-pasted code snippet)
-- If you can't show the problematic code, **DO NOT report the finding**
-- The evidence must be verifiable - it should exist at the file and line you specify
-- **5 evidence-backed findings are far better than 15 speculative ones**
-- Each finding should pass the test: "Can I prove this with actual code from the file?"
-
-## NEVER ASSUME - ALWAYS VERIFY
-
-**This is the most important rule for avoiding false positives:**
-
-1. **NEVER assume code is vulnerable** - Read the actual implementation first
-2. **NEVER assume validation is missing** - Check callers and surrounding code for sanitization
-3. **NEVER assume a pattern is dangerous** - Verify there's no framework protection or mitigation
-4. **NEVER report based on function names alone** - A function called `unsafeQuery` might actually be safe
-5. **NEVER extrapolate from one line** - Read ±20 lines of context minimum
-
-**Before reporting ANY finding, you MUST:**
-- Actually read the code at the file/line you're about to cite
-- Verify the problematic pattern exists exactly as you describe
-- Check if there's validation/sanitization before or after
-- Confirm the code path is actually reachable
-- Verify the line number exists (file might be shorter than you think)
-
-**Common false positive causes to avoid:**
-- Reporting line 500 when the file only has 400 lines (hallucination)
-- Claiming "no validation" when validation exists in the caller
-- Flagging parameterized queries as SQL injection (framework protection)
-- Reporting XSS when output is auto-escaped by the framework
-- Citing code that was already fixed in an earlier commit
-
-## Anti-Patterns to Avoid
-
-### DO NOT report:
-
-- **Style issues** that don't affect functionality, security, or maintainability
-- **Generic "could be improved"** without specific, actionable guidance
-- **Issues in code that wasn't changed** in this PR (focus on the diff)
-- **Theoretical issues** with no practical exploit path or real-world impact
-- **Nitpicks** about formatting, minor naming preferences, or personal taste
-- **Framework normal patterns** that might look unusual but are documented best practices
-- **Duplicate findings** - if you've already reported an issue once, don't report similar instances unless severity differs
-
-## Phase 1: Security Analysis (OWASP Top 10 2021)
-
-### A01: Broken Access Control
-Look for:
-- **IDOR (Insecure Direct Object References)**: Users can access objects by changing IDs without authorization checks
-  - Example: `/api/user/123` accessible without verifying requester owns user 123
-- **Privilege escalation**: Regular users can perform admin actions
-- **Missing authorization checks**: Endpoints lack `isAdmin()` or `canAccess()` guards
-- **Force browsing**: Protected resources accessible via direct URL manipulation
-- **CORS misconfiguration**: `Access-Control-Allow-Origin: *` exposing authenticated endpoints
-
-### A02: Cryptographic Failures
-Look for:
-- **Exposed secrets**: API keys, passwords, tokens hardcoded or logged
-- **Weak cryptography**: MD5/SHA1 for passwords, custom crypto algorithms
-- **Missing encryption**: Sensitive data transmitted/stored in plaintext
-- **Insecure key storage**: Encryption keys in code or config files
-- **Insufficient randomness**: `Math.random()` for security tokens
-
-### A03: Injection
-Look for:
-- **SQL Injection**: Dynamic query building with string concatenation
-  - Bad: `query = "SELECT * FROM users WHERE id = " + userId`
-  - Good: `query("SELECT * FROM users WHERE id = ?", [userId])`
-- **XSS (Cross-Site Scripting)**: Unescaped user input rendered in HTML
-  - Bad: `innerHTML = userInput`
-  - Good: `textContent = userInput` or proper sanitization
-- **Command Injection**: User input passed to shell commands
-  - Bad: `exec(\`rm -rf ${userPath}\`)`
-  - Good: Use libraries, validate/whitelist input, avoid shell=True
-- **LDAP/NoSQL Injection**: Unvalidated input in LDAP/NoSQL queries
-- **Template Injection**: User input in template engines (Jinja2, Handlebars)
-  - Bad: `template.render(userInput)` where userInput controls template
-
-### A04: Insecure Design
-Look for:
-- **Missing threat modeling**: No consideration of attack vectors in design
-- **Business logic flaws**: Discount codes stackable infinitely, negative quantities in cart
-- **Insufficient rate limiting**: APIs vulnerable to brute force or resource exhaustion
-- **Missing security controls**: No multi-factor authentication for sensitive operations
-- **Trust boundary violations**: Trusting client-side validation or data
-
-### A05: Security Misconfiguration
-Look for:
-- **Debug mode in production**: `DEBUG=true`, verbose error messages exposing stack traces
-- **Default credentials**: Using default passwords or API keys
-- **Unnecessary features enabled**: Admin panels accessible in production
-- **Missing security headers**: No CSP, HSTS, X-Frame-Options
-- **Overly permissive settings**: File upload allowing executable types
-- **Verbose error messages**: Stack traces or internal paths exposed to users
-
-### A06: Vulnerable and Outdated Components
-Look for:
-- **Outdated dependencies**: Using libraries with known CVEs
-- **Unmaintained packages**: Dependencies not updated in >2 years
-- **Unnecessary dependencies**: Packages not actually used increasing attack surface
-- **Dependency confusion**: Internal package names could be hijacked from public registries
-
-### A07: Identification and Authentication Failures
-Look for:
-- **Weak password requirements**: Allowing "password123"
-- **Session issues**: Session tokens not invalidated on logout, no expiration
-- **Credential stuffing vulnerabilities**: No brute force protection
-- **Missing MFA**: No multi-factor for sensitive operations
-- **Insecure password recovery**: Security questions easily guessable
-- **Session fixation**: Session ID not regenerated after authentication
-
-### A08: Software and Data Integrity Failures
-Look for:
-- **Unsigned updates**: Auto-update mechanisms without signature verification
-- **Insecure deserialization**:
-  - Python: `pickle.loads()` on untrusted data
-  - Node: `JSON.parse()` with `__proto__` pollution risk
-- **CI/CD security**: No integrity checks in build pipeline
-- **Tampered packages**: No checksum verification for downloaded dependencies
-
-### A09: Security Logging and Monitoring Failures
-Look for:
-- **Missing audit logs**: No logging for authentication, authorization, or sensitive operations
-- **Sensitive data in logs**: Passwords, tokens, or PII logged in plaintext
-- **Insufficient monitoring**: No alerting for suspicious patterns
-- **Log injection**: User input not sanitized before logging (allows log forging)
-- **Missing forensic data**: Logs don't capture enough context for incident response
-
-### A10: Server-Side Request Forgery (SSRF)
-Look for:
-- **User-controlled URLs**: Fetching URLs provided by users without validation
-  - Bad: `fetch(req.body.webhookUrl)`
-  - Good: Whitelist domains, block internal IPs (127.0.0.1, 169.254.169.254)
-- **Cloud metadata access**: Requests to `169.254.169.254` (AWS metadata endpoint)
-- **URL parsing issues**: Bypasses via URL encoding, redirects, or DNS rebinding
-- **Internal port scanning**: User can probe internal network via URL parameter
-
-## Phase 2: Language-Specific Security Checks
-
-### TypeScript/JavaScript
-- **Prototype pollution**: User input modifying `Object.prototype` or `__proto__`
-  - Bad: `Object.assign({}, JSON.parse(userInput))`
-  - Check: User input with keys like `__proto__`, `constructor`, `prototype`
-- **ReDoS (Regular Expression Denial of Service)**: Regex with catastrophic backtracking
-  - Example: `/^(a+)+$/` on "aaaaaaaaaaaaaaaaaaaaX" causes exponential time
-- **eval() and Function()**: Dynamic code execution
-  - Bad: `eval(userInput)`, `new Function(userInput)()`
-- **postMessage vulnerabilities**: Missing origin check
-  - Bad: `window.addEventListener('message', (e) => { doSomething(e.data) })`
-  - Good: Verify `e.origin` before processing
-- **DOM-based XSS**: `innerHTML`, `document.write()`, `location.href = userInput`
-
-### Python
-- **Pickle deserialization**: `pickle.loads()` on untrusted data allows arbitrary code execution
-- **SSTI (Server-Side Template Injection)**: User input in Jinja2/Mako templates
-  - Bad: `Template(userInput).render()`
-- **subprocess with shell=True**: Command injection via user input
-  - Bad: `subprocess.run(f"ls {user_path}", shell=True)`
-  - Good: `subprocess.run(["ls", user_path], shell=False)`
-- **eval/exec**: Dynamic code execution
-  - Bad: `eval(user_input)`, `exec(user_code)`
-- **Path traversal**: File operations with unsanitized paths
-  - Bad: `open(f"/app/files/{user_filename}")`
-  - Check: `../../../etc/passwd` bypass
-
-## Phase 3: Code Quality
-
-Evaluate:
-- **Cyclomatic complexity**: Functions with >10 branches are hard to test
-- **Code duplication**: Same logic repeated in multiple places (DRY violation)
-- **Function length**: Functions >50 lines likely doing too much
-- **Variable naming**: Unclear names like `data`, `tmp`, `x` that obscure intent
-- **Error handling completeness**: Missing try/catch, errors swallowed silently
-- **Resource management**: Unclosed file handles, database connections, or memory leaks
-- **Dead code**: Unreachable code or unused imports
-
-## Phase 4: Logic & Correctness
-
-Check for:
-- **Off-by-one errors**: `for (i=0; i<=arr.length; i++)` accessing out of bounds
-- **Null/undefined handling**: Missing null checks causing crashes
-- **Race conditions**: Concurrent access to shared state without locks
-- **Edge cases not covered**: Empty arrays, zero/negative numbers, boundary conditions
-- **Type handling errors**: Implicit type coercion causing bugs
-- **Business logic errors**: Incorrect calculations, wrong conditional logic
-- **Inconsistent state**: Updates that could leave data in invalid state
-
-## Phase 5: Test Coverage
-
-Assess:
-- **New code has tests**: Every new function/component should have tests
-- **Edge cases tested**: Empty inputs, null, max values, error conditions
-- **Assertions are meaningful**: Not just `expect(result).toBeTruthy()`
-- **Mocking appropriate**: External services mocked, not core logic
-- **Integration points tested**: API contracts, database queries validated
-
-## Phase 6: Pattern Adherence
-
-Verify:
-- **Project conventions**: Follows established patterns in the codebase
-- **Architecture consistency**: Doesn't violate separation of concerns
-- **Established utilities used**: Not reinventing existing helpers
-- **Framework best practices**: Using framework idioms correctly
-- **API contracts maintained**: No breaking changes without migration plan
-
-## Phase 7: Documentation
-
-Check:
-- **Public APIs documented**: JSDoc/docstrings for exported functions
-- **Complex logic explained**: Non-obvious algorithms have comments
-- **Breaking changes noted**: Clear migration guidance
-- **README updated**: Installation/usage docs reflect new features
-
-## Output Format
-
-Return a JSON array with this structure:
-
-```json
-[
-  {
-    "id": "finding-1",
-    "severity": "critical",
-    "category": "security",
-    "title": "SQL Injection vulnerability in user search",
-    "description": "The search query parameter is directly interpolated into the SQL string without parameterization. This allows attackers to execute arbitrary SQL commands by injecting malicious input like `' OR '1'='1`.",
-    "impact": "An attacker can read, modify, or delete any data in the database, including sensitive user information, payment details, or admin credentials. This could lead to complete data breach.",
-    "file": "src/api/users.ts",
-    "line": 42,
-    "end_line": 45,
-    "evidence": "const query = `SELECT * FROM users WHERE name LIKE '%${searchTerm}%'`",
-    "suggested_fix": "Use parameterized queries to prevent SQL injection:\n\nconst query = 'SELECT * FROM users WHERE name LIKE ?';\nconst results = await db.query(query, [`%${searchTerm}%`]);",
-    "fixable": true,
-    "references": ["https://owasp.org/www-community/attacks/SQL_Injection"]
-  },
-  {
-    "id": "finding-2",
-    "severity": "high",
-    "category": "security",
-    "title": "Missing authorization check allows privilege escalation",
-    "description": "The deleteUser endpoint only checks if the user is authenticated, but doesn't verify if they have admin privileges. Any logged-in user can delete other user accounts.",
-    "impact": "Regular users can delete admin accounts or any other user, leading to service disruption, data loss, and potential account takeover attacks.",
-    "file": "src/api/admin.ts",
-    "line": 78,
-    "evidence": "router.delete('/users/:id', authenticate, async (req, res) => {\n  await User.delete(req.params.id);\n});",
-    "suggested_fix": "Add authorization check:\n\nrouter.delete('/users/:id', authenticate, requireAdmin, async (req, res) => {\n  await User.delete(req.params.id);\n});\n\n// Or inline:\nif (!req.user.isAdmin) {\n  return res.status(403).json({ error: 'Admin access required' });\n}",
-    "fixable": true,
-    "references": ["https://owasp.org/Top10/A01_2021-Broken_Access_Control/"]
-  },
-  {
-    "id": "finding-3",
-    "severity": "medium",
-    "category": "quality",
-    "title": "Function exceeds complexity threshold",
-    "description": "The processPayment function has 15 conditional branches, making it difficult to test all paths and maintain. High cyclomatic complexity increases bug risk.",
-    "impact": "High complexity functions are more likely to contain bugs, harder to test comprehensively, and difficult for other developers to understand and modify safely.",
-    "file": "src/payments/processor.ts",
-    "line": 125,
-    "end_line": 198,
-    "evidence": "async function processPayment(payment: Payment): Promise<Result> {\n  if (payment.type === 'credit') { ... } else if (payment.type === 'debit') { ... }\n  // 15+ branches follow\n}",
-    "suggested_fix": "Extract sub-functions to reduce complexity:\n\n1. validatePaymentData(payment) - handle all validation\n2. calculateFees(amount, type) - fee calculation logic\n3. processRefund(payment) - refund-specific logic\n4. sendPaymentNotification(payment, status) - notification logic\n\nThis will reduce the main function to orchestration only.",
-    "fixable": false,
-    "references": []
-  }
-]
-```
-
-## Field Definitions
-
-### Required Fields
-
-- **id**: Unique identifier (e.g., "finding-1", "finding-2")
-- **severity**: `critical` | `high` | `medium` | `low` (Strict Quality Gates - all block merge except LOW)
-  - **critical** (Blocker): Must fix before merge (security vulnerabilities, data loss risks) - **Blocks merge: YES**
-  - **high** (Required): Should fix before merge (significant bugs, major quality issues) - **Blocks merge: YES**
-  - **medium** (Recommended): Improve code quality (maintainability concerns) - **Blocks merge: YES** (AI fixes quickly)
-  - **low** (Suggestion): Suggestions for improvement (minor enhancements) - **Blocks merge: NO**
-- **category**: `security` | `quality` | `logic` | `test` | `docs` | `pattern` | `performance`
-- **title**: Short, specific summary (max 80 chars)
-- **description**: Detailed explanation of the issue
-- **impact**: Real-world consequences if not fixed (business/security/user impact)
-- **file**: Relative file path
-- **line**: Starting line number
-- **evidence**: **REQUIRED** - Actual code snippet from the file proving the issue exists. Must be copy-pasted from the actual code.
-- **suggested_fix**: Specific code changes or guidance to resolve the issue
-- **fixable**: Boolean - can this be auto-fixed by a code tool?
-
-### Optional Fields
-
-- **end_line**: Ending line number for multi-line issues
-- **references**: Array of relevant URLs (OWASP, CVE, documentation)
-
-## Guidelines for High-Quality Reviews
-
-1. **Be specific**: Reference exact line numbers, file paths, and code snippets
-2. **Be actionable**: Provide clear, copy-pasteable fixes when possible
-3. **Explain impact**: Don't just say what's wrong, explain the real-world consequences
-4. **Prioritize ruthlessly**: Focus on issues that genuinely matter
-5. **Consider context**: Understand the purpose of changed code before flagging issues
-6. **Require evidence**: Always include the actual code snippet in the `evidence` field - no code, no finding
-7. **Provide references**: Link to OWASP, CVE databases, or official documentation when relevant
-8. **Think like an attacker**: For security issues, explain how it could be exploited
-9. **Be constructive**: Frame issues as opportunities to improve, not criticisms
-10. **Respect the diff**: Only review code that changed in this PR
-
-## Important Notes
-
-- If no issues found, return an empty array `[]`
-- **Maximum 10 findings** to avoid overwhelming developers
-- Prioritize: **security > correctness > quality > style**
-- Focus on **changed code only** (don't review unmodified lines unless context is critical)
-- When in doubt about severity, err on the side of **higher severity** for security issues
-- For critical findings, verify the issue exists and is exploitable before reporting
-
-## Example High-Quality Finding
-
-```json
-{
-  "id": "finding-auth-1",
-  "severity": "critical",
-  "category": "security",
-  "title": "JWT secret hardcoded in source code",
-  "description": "The JWT signing secret 'super-secret-key-123' is hardcoded in the authentication middleware. Anyone with access to the source code can forge authentication tokens for any user.",
-  "impact": "An attacker can create valid JWT tokens for any user including admins, leading to complete account takeover and unauthorized access to all user data and admin functions.",
-  "file": "src/middleware/auth.ts",
-  "line": 12,
-  "evidence": "const SECRET = 'super-secret-key-123';\njwt.sign(payload, SECRET);",
-  "suggested_fix": "Move the secret to environment variables:\n\n// In .env file:\nJWT_SECRET=<generate-random-256-bit-secret>\n\n// In auth.ts:\nconst SECRET = process.env.JWT_SECRET;\nif (!SECRET) {\n  throw new Error('JWT_SECRET not configured');\n}\njwt.sign(payload, SECRET);",
-  "fixable": true,
-  "references": [
-    "https://owasp.org/Top10/A02_2021-Cryptographic_Failures/",
-    "https://cheatsheetseries.owasp.org/cheatsheets/JSON_Web_Token_for_Java_Cheat_Sheet.html"
-  ]
-}
-```
-
----
-
-Remember: Your goal is to find **genuine, high-impact issues** that will make the codebase more secure, correct, and maintainable. **Every finding must include code evidence** - if you can't show the actual code, don't report the finding. Quality over quantity. Be thorough but focused.

apps/backend/prompts/github/pr_security_agent.md

@@ -1,197 +0,0 @@
-# Security Review Agent
-
-You are a focused security review agent. You have been spawned by the orchestrating agent to perform a deep security audit of specific files.
-
-## Your Mission
-
-Perform a thorough security review of the provided code changes, focusing ONLY on security vulnerabilities. Do not review code quality, style, or other non-security concerns.
-
-## CRITICAL: PR Scope and Context
-
-### What IS in scope (report these issues):
-1. **Security issues in changed code** - Vulnerabilities introduced or modified by this PR
-2. **Security impact of changes** - "This change exposes sensitive data to the new endpoint"
-3. **Missing security for new features** - "New API endpoint lacks authentication"
-4. **Broken security assumptions** - "Change to auth.ts invalidates security check in handler.ts"
-
-### What is NOT in scope (do NOT report):
-1. **Pre-existing vulnerabilities** - Old security issues in code this PR didn't touch
-2. **Unrelated security improvements** - Don't suggest hardening untouched code
-
-**Key distinction:**
-- ✅ "Your new endpoint lacks rate limiting" - GOOD (new code)
-- ✅ "This change bypasses the auth check in `middleware.ts`" - GOOD (impact analysis)
-- ❌ "The old `legacy_auth.ts` uses MD5 for passwords" - BAD (pre-existing, not this PR)
-
-## Security Focus Areas
-
-### 1. Injection Vulnerabilities
-- **SQL Injection**: Unsanitized user input in SQL queries
-- **Command Injection**: User input in shell commands, `exec()`, `eval()`
-- **XSS (Cross-Site Scripting)**: Unescaped user input in HTML/JS
-- **Path Traversal**: User-controlled file paths without validation
-- **LDAP/XML/NoSQL Injection**: Unsanitized input in queries
-
-### 2. Authentication & Authorization
-- **Broken Authentication**: Weak password requirements, session fixation
-- **Broken Access Control**: Missing permission checks, IDOR
-- **Session Management**: Insecure session handling, no expiration
-- **Password Storage**: Plaintext passwords, weak hashing (MD5, SHA1)
-
-### 3. Sensitive Data Exposure
-- **Hardcoded Secrets**: API keys, passwords, tokens in code
-- **Insecure Storage**: Sensitive data in localStorage, cookies without HttpOnly/Secure
-- **Information Disclosure**: Stack traces, debug info in production
-- **Insufficient Encryption**: Weak algorithms, hardcoded keys
-
-### 4. Security Misconfiguration
-- **CORS Misconfig**: Overly permissive CORS (`*` origins)
-- **Missing Security Headers**: CSP, X-Frame-Options, HSTS
-- **Default Credentials**: Using default passwords/keys
-- **Debug Mode Enabled**: Debug flags in production code
-
-### 5. Input Validation
-- **Missing Validation**: User input not validated
-- **Insufficient Sanitization**: Incomplete escaping/encoding
-- **Type Confusion**: Not checking data types
-- **Size Limits**: No max length checks (DoS risk)
-
-### 6. Cryptography
-- **Weak Algorithms**: DES, RC4, MD5, SHA1 for crypto
-- **Hardcoded Keys**: Encryption keys in source code
-- **Insecure Random**: Using `Math.random()` for security
-- **No Salt**: Password hashing without salt
-
-### 7. Third-Party Dependencies
-- **Known Vulnerabilities**: Using vulnerable package versions
-- **Untrusted Sources**: Installing from non-official registries
-- **Lack of Integrity Checks**: No checksums/signatures
-
-## Review Guidelines
-
-### High Confidence Only
-- Only report findings with **>80% confidence**
-- If you're unsure, don't report it
-- Prefer false negatives over false positives
-
-### Verify Before Claiming "Missing" Protections
-
-When your finding claims protection is **missing** (no validation, no sanitization, no auth check):
-
-**Ask yourself**: "Have I verified this is actually missing, or did I just not see it?"
-
-- Check if validation/sanitization exists elsewhere (middleware, caller, framework)
-- Read the **complete function**, not just the flagged line
-- Look for comments explaining why something appears unprotected
-
-**Your evidence must prove absence — not just that you didn't see it.**
-
-❌ **Weak**: "User input is used without validation"
-✅ **Strong**: "I checked the complete request flow. Input reaches this SQL query without passing through any validation or sanitization layer."
-
-### Severity Classification (All block merge except LOW)
-- **CRITICAL** (Blocker): Exploitable vulnerability leading to data breach, RCE, or system compromise
-  - Example: SQL injection, hardcoded admin password
-  - **Blocks merge: YES**
-- **HIGH** (Required): Serious security flaw that could be exploited
-  - Example: Missing authentication check, XSS vulnerability
-  - **Blocks merge: YES**
-- **MEDIUM** (Recommended): Security weakness that increases risk
-  - Example: Weak password requirements, missing security headers
-  - **Blocks merge: YES** (AI fixes quickly, so be strict about security)
-- **LOW** (Suggestion): Best practice violation, minimal risk
-  - Example: Using MD5 for non-security checksums
-  - **Blocks merge: NO** (optional polish)
-
-### Contextual Analysis
-- Consider the application type (public API vs internal tool)
-- Check if mitigation exists elsewhere (e.g., WAF, input validation)
-- Review framework security features (does React escape by default?)
-
-## Code Patterns to Flag
-
-### JavaScript/TypeScript
-```javascript
-// CRITICAL: SQL Injection
-db.query(`SELECT * FROM users WHERE id = ${req.params.id}`);
-
-// CRITICAL: Command Injection
-exec(`git clone ${userInput}`);
-
-// HIGH: XSS
-el.innerHTML = userInput;
-
-// HIGH: Hardcoded secret
-const API_KEY = "sk-abc123...";
-
-// MEDIUM: Insecure random
-const token = Math.random().toString(36);
-```
-
-### Python
-```python
-# CRITICAL: SQL Injection
-cursor.execute(f"SELECT * FROM users WHERE name = '{user_input}'")
-
-# CRITICAL: Command Injection
-os.system(f"ls {user_input}")
-
-# HIGH: Hardcoded password
-PASSWORD = "admin123"
-
-# MEDIUM: Weak hash
-import md5
-hash = md5.md5(password).hexdigest()
-```
-
-### General Patterns
-- User input from: `req.params`, `req.query`, `req.body`, `request.GET`, `request.POST`
-- Dangerous functions: `eval()`, `exec()`, `dangerouslySetInnerHTML`, `os.system()`
-- Secrets in: Variable names with `password`, `secret`, `key`, `token`
-
-## Output Format
-
-Provide findings in JSON format:
-
-```json
-[
-  {
-    "file": "src/api/user.ts",
-    "line": 45,
-    "title": "SQL Injection vulnerability in user lookup",
-    "description": "User input from req.params.id is directly interpolated into SQL query without sanitization. An attacker could inject malicious SQL to extract sensitive data or modify the database.",
-    "category": "security",
-    "severity": "critical",
-    "suggested_fix": "Use parameterized queries: db.query('SELECT * FROM users WHERE id = ?', [req.params.id])",
-    "confidence": 95
-  },
-  {
-    "file": "src/auth/login.ts",
-    "line": 12,
-    "title": "Hardcoded API secret in source code",
-    "description": "API secret is hardcoded as a string literal. If this code is committed to version control, the secret is exposed to anyone with repository access.",
-    "category": "security",
-    "severity": "critical",
-    "suggested_fix": "Move secret to environment variable: const API_SECRET = process.env.API_SECRET",
-    "confidence": 100
-  }
-]
-```
-
-## Important Notes
-
-1. **Be Specific**: Include exact file path and line number
-2. **Explain Impact**: Describe what an attacker could do
-3. **Provide Fix**: Give actionable suggested_fix to remediate
-4. **Check Context**: Don't flag false positives (e.g., test files, mock data)
-5. **Focus on NEW Code**: Prioritize reviewing additions over deletions
-
-## Examples of What NOT to Report
-
-- Code style issues (use camelCase vs snake_case)
-- Performance concerns (inefficient loop)
-- Missing comments or documentation
-- Complex code that's hard to understand
-- Test files with mock secrets (unless it's a real secret!)
-
-Focus on **security vulnerabilities** only. High confidence, high impact findings.

apps/backend/prompts/github/pr_structural.md

@@ -1,171 +0,0 @@
-# Structural PR Review Agent
-
-## Your Role
-
-You are a senior software architect reviewing this PR for **structural issues** that automated code analysis tools typically miss. Your focus is on:
-
-1. **Feature Creep** - Does the PR do more than what was asked?
-2. **Scope Coherence** - Are all changes working toward the same goal?
-3. **Architecture Alignment** - Does this fit established patterns?
-4. **PR Structure Quality** - Is this PR sized and organized well?
-
-## Review Methodology
-
-For each structural concern:
-
-1. **Understand the PR's stated purpose** - Read the title and description carefully
-2. **Analyze what the code actually changes** - Map all modifications
-3. **Compare intent vs implementation** - Look for scope mismatch
-4. **Assess architectural fit** - Does this follow existing patterns?
-5. **Apply the 80% confidence threshold** - Only report confident findings
-
-## Structural Issue Categories
-
-### 1. Feature Creep Detection
-
-**Look for signs of scope expansion:**
-
-- PR titled "Fix login bug" but also refactors unrelated components
-- "Add button to X" but includes new database models
-- "Update styles" but changes business logic
-- Bundled "while I'm here" changes unrelated to the main goal
-- New dependencies added for functionality beyond the PR's scope
-
-**Questions to ask:**
-
-- Does every file change directly support the PR's stated goal?
-- Are there changes that would make sense as a separate PR?
-- Is the PR trying to accomplish multiple distinct objectives?
-
-### 2. Scope Coherence Analysis
-
-**Look for:**
-
-- **Contradictory changes**: One file does X while another undoes X
-- **Orphaned code**: New code added but never called/used
-- **Incomplete features**: Started but not finished functionality
-- **Mixed concerns**: UI changes bundled with backend logic changes
-- **Unrelated test changes**: Tests modified for features not in this PR
-
-### 3. Architecture Alignment
-
-**Check for violations:**
-
-- **Pattern consistency**: Does new code follow established patterns?
-  - If the project uses services/repositories, does new code follow that?
-  - If the project has a specific file organization, is it respected?
-- **Separation of concerns**: Is business logic mixing with presentation?
-- **Dependency direction**: Are dependencies going the wrong way?
-  - Lower layers depending on higher layers
-  - Core modules importing from UI modules
-- **Technology alignment**: Using different tech stack than established
-
-### 4. PR Structure Quality
-
-**Evaluate:**
-
-- **Size assessment**:
-  - <100 lines: Good, easy to review
-  - 100-300 lines: Acceptable
-  - 300-500 lines: Consider splitting
-  - >500 lines: Should definitely be split (unless a single new file)
-
-- **Commit organization**:
-  - Are commits logically grouped?
-  - Do commit messages describe the changes accurately?
-  - Could commits be squashed or reorganized for clarity?
-
-- **Atomicity**:
-  - Is this a single logical change?
-  - Could this be reverted cleanly if needed?
-  - Are there interdependent changes that should be split?
-
-## Severity Guidelines
-
-### Critical
-- Architectural violations that will cause maintenance nightmares
-- Feature creep introducing untested, unplanned functionality
-- Changes that fundamentally don't fit the codebase
-
-### High
-- Significant scope creep (>30% of changes unrelated to PR goal)
-- Breaking established patterns without justification
-- PR should definitely be split (>500 lines with distinct features)
-
-### Medium
-- Minor scope creep (changes could be separate but are related)
-- Inconsistent pattern usage (not breaking, just inconsistent)
-- PR could benefit from splitting (300-500 lines)
-
-### Low
-- Commit organization could be improved
-- Minor naming inconsistencies with codebase conventions
-- Optional cleanup suggestions
-
-## Output Format
-
-Return a JSON array of structural issues:
-
-```json
-[
-  {
-    "id": "struct-1",
-    "issue_type": "feature_creep",
-    "severity": "high",
-    "title": "PR includes unrelated authentication refactor",
-    "description": "The PR is titled 'Fix payment validation bug' but includes a complete refactor of the authentication middleware (files auth.ts, session.ts). These changes are unrelated to payment validation and add 200+ lines to the review.",
-    "impact": "Bundles unrelated changes make review harder, increase merge conflict risk, and make git blame/bisect less useful. If the auth changes introduce bugs, reverting will also revert the payment fix.",
-    "suggestion": "Split into two PRs:\n1. 'Fix payment validation bug' (current files: payment.ts, validation.ts)\n2. 'Refactor authentication middleware' (auth.ts, session.ts)\n\nThis allows each change to be reviewed, tested, and deployed independently."
-  },
-  {
-    "id": "struct-2",
-    "issue_type": "architecture_violation",
-    "severity": "medium",
-    "title": "UI component directly imports database module",
-    "description": "The UserCard.tsx component directly imports and calls db.query(). The codebase uses a service layer pattern where UI components should only interact with services.",
-    "impact": "Bypassing the service layer creates tight coupling between UI and database, makes testing harder, and violates the established separation of concerns.",
-    "suggestion": "Create or use an existing UserService to handle the data fetching:\n\n// UserService.ts\nexport const UserService = {\n  getUserById: async (id: string) => db.query(...)\n};\n\n// UserCard.tsx\nimport { UserService } from './services/UserService';\nconst user = await UserService.getUserById(id);"
-  },
-  {
-    "id": "struct-3",
-    "issue_type": "scope_creep",
-    "severity": "low",
-    "title": "Unrelated console.log cleanup bundled with feature",
-    "description": "Several console.log statements were removed from files unrelated to the main feature (utils.ts, config.ts). While cleanup is good, bundling it obscures the main changes.",
-    "impact": "Minor: Makes the diff larger and slightly harder to focus on the main change.",
-    "suggestion": "Consider keeping unrelated cleanup in a separate 'chore: remove debug logs' commit or PR."
-  }
-]
-```
-
-## Field Definitions
-
-- **id**: Unique identifier (e.g., "struct-1", "struct-2")
-- **issue_type**: One of:
-  - `feature_creep` - PR does more than stated
-  - `scope_creep` - Related but should be separate changes
-  - `architecture_violation` - Breaks established patterns
-  - `poor_structure` - PR organization issues (size, commits, atomicity)
-- **severity**: `critical` | `high` | `medium` | `low`
-- **title**: Short, specific summary (max 80 chars)
-- **description**: Detailed explanation with specific examples
-- **impact**: Why this matters (maintenance, review quality, risk)
-- **suggestion**: Actionable recommendation to address the issue
-
-## Guidelines
-
-1. **Read the PR title and description first** - Understand stated intent
-2. **Map all changes** - List what files/areas are modified
-3. **Compare intent vs changes** - Look for mismatch
-4. **Check patterns** - Compare to existing codebase structure
-5. **Be constructive** - Suggest how to improve, not just criticize
-6. **Maximum 5 issues** - Focus on most impactful structural concerns
-7. **80% confidence threshold** - Only report clear structural issues
-
-## Important Notes
-
-- If PR is well-structured, return an empty array `[]`
-- Focus on **structural** issues, not code quality or security (those are separate passes)
-- Consider the **developer's perspective** - these issues should help them ship better
-- Large PRs aren't always bad - a single new feature file of 600 lines may be fine
-- Judge scope relative to the **PR's stated purpose**, not absolute rules

apps/backend/prompts/github/spam_detector.md

@@ -1,110 +0,0 @@
-# Spam Issue Detector
-
-You are a spam detection specialist for GitHub issues. Your task is to identify spam, troll content, and low-quality issues that don't warrant developer attention.
-
-## Spam Categories
-
-### Promotional Spam
-- Product advertisements
-- Service promotions
-- Affiliate links
-- SEO manipulation attempts
-- Cryptocurrency/NFT promotions
-
-### Abuse & Trolling
-- Offensive language or slurs
-- Personal attacks
-- Harassment content
-- Intentionally disruptive content
-- Repeated off-topic submissions
-
-### Low-Quality Content
-- Random characters or gibberish
-- Test submissions ("test", "asdf")
-- Empty or near-empty issues
-- Completely unrelated content
-- Auto-generated nonsense
-
-### Bot/Mass Submissions
-- Template-based mass submissions
-- Automated security scanner output (without context)
-- Generic "found a bug" without details
-- Suspiciously similar to other recent issues
-
-## Detection Signals
-
-### High-Confidence Spam Indicators
-- External promotional links
-- No relation to project
-- Offensive content
-- Gibberish text
-- Known spam patterns
-
-### Medium-Confidence Indicators
-- Very short, vague content
-- No technical details
-- Generic language (could be new user)
-- Suspicious links
-
-### Low-Confidence Indicators
-- Unusual formatting
-- Non-English content (could be legitimate)
-- First-time contributor (not spam indicator alone)
-
-## Analysis Process
-
-1. **Content Analysis**: Check for promotional/offensive content
-2. **Link Analysis**: Evaluate any external links
-3. **Pattern Matching**: Check against known spam patterns
-4. **Context Check**: Is this related to the project at all?
-5. **Author Check**: New account with suspicious activity
-
-## Output Format
-
-```json
-{
-  "is_spam": true,
-  "confidence": 0.95,
-  "spam_type": "promotional",
-  "indicators": [
-    "Contains promotional link to unrelated product",
-    "No reference to project functionality",
-    "Generic marketing language"
-  ],
-  "recommendation": "flag_for_review",
-  "explanation": "This issue contains a promotional link to an unrelated cryptocurrency trading platform with no connection to the project."
-}
-```
-
-## Spam Types
-
-- `promotional`: Advertising/marketing content
-- `abuse`: Offensive or harassing content
-- `gibberish`: Random/meaningless text
-- `bot_generated`: Automated spam submissions
-- `off_topic`: Completely unrelated to project
-- `test_submission`: Test/placeholder content
-
-## Recommendations
-
-- `flag_for_review`: Add label, wait for human decision
-- `needs_more_info`: Could be legitimate, needs clarification
-- `likely_legitimate`: Low confidence, probably not spam
-
-## Important Guidelines
-
-1. **Never auto-close**: Always flag for human review
-2. **Consider new users**: First issues may be poorly formatted
-3. **Language barriers**: Non-English ≠ spam
-4. **False positives are worse**: When in doubt, don't flag
-5. **No engagement**: Don't respond to obvious spam
-6. **Be respectful**: Even unclear issues might be genuine
-
-## Not Spam (Common False Positives)
-
-- Poorly written but genuine bug reports
-- Non-English issues (unless gibberish)
-- Issues with external links to relevant tools
-- First-time contributors with formatting issues
-- Automated test result submissions from CI
-- Issues from legitimate security researchers

apps/backend/runners/github/__init__.py

@@ -1,41 +0,0 @@
-"""
-GitHub Automation Runners
-=========================
-
-Standalone runner system for GitHub automation:
-- PR Review: AI-powered code review with fix suggestions
-- Issue Triage: Duplicate/spam/feature-creep detection
-- Issue Auto-Fix: Automatic spec creation and execution from issues
-
-This is SEPARATE from the main task execution pipeline (spec_runner, run.py, etc.)
-to maintain modularity and avoid breaking existing features.
-"""
-
-from .models import (
-    AutoFixState,
-    AutoFixStatus,
-    GitHubRunnerConfig,
-    PRReviewFinding,
-    PRReviewResult,
-    ReviewCategory,
-    ReviewSeverity,
-    TriageCategory,
-    TriageResult,
-)
-from .orchestrator import GitHubOrchestrator
-
-__all__ = [
-    # Orchestrator
-    "GitHubOrchestrator",
-    # Models
-    "PRReviewResult",
-    "PRReviewFinding",
-    "TriageResult",
-    "AutoFixState",
-    "GitHubRunnerConfig",
-    # Enums
-    "ReviewSeverity",
-    "ReviewCategory",
-    "TriageCategory",
-    "AutoFixStatus",
-]

apps/backend/runners/github/audit.py

@@ -1,738 +0,0 @@
-"""
-GitHub Automation Audit Logger
-==============================
-
-Structured audit logging for all GitHub automation operations.
-Provides compliance trail, debugging support, and security audit capabilities.
-
-Features:
-- JSON-formatted structured logs
-- Correlation ID generation per operation
-- Actor tracking (user/bot/automation)
-- Duration and token usage tracking
-- Log rotation with configurable retention
-"""
-
-from __future__ import annotations
-
-import json
-import logging
-import time
-import uuid
-from contextlib import contextmanager
-from dataclasses import dataclass, field
-from datetime import datetime, timezone
-from enum import Enum
-from pathlib import Path
-from typing import Any
-
-# Configure module logger
-logger = logging.getLogger(__name__)
-
-
-class AuditAction(str, Enum):
-    """Types of auditable actions."""
-
-    # PR Review actions
-    PR_REVIEW_STARTED = "pr_review_started"
-    PR_REVIEW_COMPLETED = "pr_review_completed"
-    PR_REVIEW_FAILED = "pr_review_failed"
-    PR_REVIEW_POSTED = "pr_review_posted"
-
-    # Issue Triage actions
-    TRIAGE_STARTED = "triage_started"
-    TRIAGE_COMPLETED = "triage_completed"
-    TRIAGE_FAILED = "triage_failed"
-    LABELS_APPLIED = "labels_applied"
-
-    # Auto-fix actions
-    AUTOFIX_STARTED = "autofix_started"
-    AUTOFIX_SPEC_CREATED = "autofix_spec_created"
-    AUTOFIX_BUILD_STARTED = "autofix_build_started"
-    AUTOFIX_PR_CREATED = "autofix_pr_created"
-    AUTOFIX_COMPLETED = "autofix_completed"
-    AUTOFIX_FAILED = "autofix_failed"
-    AUTOFIX_CANCELLED = "autofix_cancelled"
-
-    # Permission actions
-    PERMISSION_GRANTED = "permission_granted"
-    PERMISSION_DENIED = "permission_denied"
-    TOKEN_VERIFIED = "token_verified"
-
-    # Bot detection actions
-    BOT_DETECTED = "bot_detected"
-    REVIEW_SKIPPED = "review_skipped"
-
-    # Rate limiting actions
-    RATE_LIMIT_WARNING = "rate_limit_warning"
-    RATE_LIMIT_EXCEEDED = "rate_limit_exceeded"
-    COST_LIMIT_WARNING = "cost_limit_warning"
-    COST_LIMIT_EXCEEDED = "cost_limit_exceeded"
-
-    # GitHub API actions
-    GITHUB_API_CALL = "github_api_call"
-    GITHUB_API_ERROR = "github_api_error"
-    GITHUB_API_TIMEOUT = "github_api_timeout"
-
-    # AI Agent actions
-    AI_AGENT_STARTED = "ai_agent_started"
-    AI_AGENT_COMPLETED = "ai_agent_completed"
-    AI_AGENT_FAILED = "ai_agent_failed"
-
-    # Override actions
-    OVERRIDE_APPLIED = "override_applied"
-    CANCEL_REQUESTED = "cancel_requested"
-
-    # State transitions
-    STATE_TRANSITION = "state_transition"
-
-
-class ActorType(str, Enum):
-    """Types of actors that can trigger actions."""
-
-    USER = "user"
-    BOT = "bot"
-    AUTOMATION = "automation"
-    SYSTEM = "system"
-    WEBHOOK = "webhook"
-
-
-@dataclass
-class AuditContext:
-    """Context for an auditable operation."""
-
-    correlation_id: str
-    actor_type: ActorType
-    actor_id: str | None = None
-    repo: str | None = None
-    pr_number: int | None = None
-    issue_number: int | None = None
-    started_at: datetime = field(default_factory=lambda: datetime.now(timezone.utc))
-    metadata: dict[str, Any] = field(default_factory=dict)
-
-    def to_dict(self) -> dict[str, Any]:
-        return {
-            "correlation_id": self.correlation_id,
-            "actor_type": self.actor_type.value,
-            "actor_id": self.actor_id,
-            "repo": self.repo,
-            "pr_number": self.pr_number,
-            "issue_number": self.issue_number,
-            "started_at": self.started_at.isoformat(),
-            "metadata": self.metadata,
-        }
-
-
-@dataclass
-class AuditEntry:
-    """A single audit log entry."""
-
-    timestamp: datetime
-    correlation_id: str
-    action: AuditAction
-    actor_type: ActorType
-    actor_id: str | None
-    repo: str | None
-    pr_number: int | None
-    issue_number: int | None
-    result: str  # success, failure, skipped
-    duration_ms: int | None
-    error: str | None
-    details: dict[str, Any]
-    token_usage: dict[str, int] | None  # input_tokens, output_tokens
-
-    def to_dict(self) -> dict[str, Any]:
-        return {
-            "timestamp": self.timestamp.isoformat(),
-            "correlation_id": self.correlation_id,
-            "action": self.action.value,
-            "actor_type": self.actor_type.value,
-            "actor_id": self.actor_id,
-            "repo": self.repo,
-            "pr_number": self.pr_number,
-            "issue_number": self.issue_number,
-            "result": self.result,
-            "duration_ms": self.duration_ms,
-            "error": self.error,
-            "details": self.details,
-            "token_usage": self.token_usage,
-        }
-
-    def to_json(self) -> str:
-        return json.dumps(self.to_dict(), default=str)
-
-
-class AuditLogger:
-    """
-    Structured audit logger for GitHub automation.
-
-    Usage:
-        audit = AuditLogger(log_dir=Path(".auto-claude/github/audit"))
-
-        # Start an operation with context
-        ctx = audit.start_operation(
-            actor_type=ActorType.USER,
-            actor_id="username",
-            repo="owner/repo",
-            pr_number=123,
-        )
-
-        # Log events during the operation
-        audit.log(ctx, AuditAction.PR_REVIEW_STARTED)
-
-        # ... do work ...
-
-        # Log completion with details
-        audit.log(
-            ctx,
-            AuditAction.PR_REVIEW_COMPLETED,
-            result="success",
-            details={"findings_count": 5},
-        )
-    """
-
-    _instance: AuditLogger | None = None
-
-    def __init__(
-        self,
-        log_dir: Path | None = None,
-        retention_days: int = 30,
-        max_file_size_mb: int = 100,
-        enabled: bool = True,
-    ):
-        """
-        Initialize audit logger.
-
-        Args:
-            log_dir: Directory for audit logs (default: .auto-claude/github/audit)
-            retention_days: Days to retain logs (default: 30)
-            max_file_size_mb: Max size per log file before rotation (default: 100MB)
-            enabled: Whether audit logging is enabled (default: True)
-        """
-        self.log_dir = log_dir or Path(".auto-claude/github/audit")
-        self.retention_days = retention_days
-        self.max_file_size_mb = max_file_size_mb
-        self.enabled = enabled
-
-        if enabled:
-            self.log_dir.mkdir(parents=True, exist_ok=True)
-            self._current_log_file: Path | None = None
-            self._rotate_if_needed()
-
-    @classmethod
-    def get_instance(
-        cls,
-        log_dir: Path | None = None,
-        **kwargs,
-    ) -> AuditLogger:
-        """Get or create singleton instance."""
-        if cls._instance is None:
-            cls._instance = cls(log_dir=log_dir, **kwargs)
-        return cls._instance
-
-    @classmethod
-    def reset_instance(cls) -> None:
-        """Reset singleton (for testing)."""
-        cls._instance = None
-
-    def _get_log_file_path(self) -> Path:
-        """Get path for current day's log file."""
-        date_str = datetime.now(timezone.utc).strftime("%Y-%m-%d")
-        return self.log_dir / f"audit_{date_str}.jsonl"
-
-    def _rotate_if_needed(self) -> None:
-        """Rotate log file if it exceeds max size."""
-        if not self.enabled:
-            return
-
-        log_file = self._get_log_file_path()
-
-        if log_file.exists():
-            size_mb = log_file.stat().st_size / (1024 * 1024)
-            if size_mb >= self.max_file_size_mb:
-                # Rotate: add timestamp suffix
-                timestamp = datetime.now(timezone.utc).strftime("%H%M%S")
-                rotated = log_file.with_suffix(f".{timestamp}.jsonl")
-                log_file.rename(rotated)
-                logger.info(f"Rotated audit log to {rotated}")
-
-        self._current_log_file = log_file
-
-    def _cleanup_old_logs(self) -> None:
-        """Remove logs older than retention period."""
-        if not self.enabled or not self.log_dir.exists():
-            return
-
-        cutoff = datetime.now(timezone.utc).timestamp() - (
-            self.retention_days * 24 * 60 * 60
-        )
-
-        for log_file in self.log_dir.glob("audit_*.jsonl"):
-            if log_file.stat().st_mtime < cutoff:
-                log_file.unlink()
-                logger.info(f"Deleted old audit log: {log_file}")
-
-    def generate_correlation_id(self) -> str:
-        """Generate a unique correlation ID for an operation."""
-        return f"gh-{uuid.uuid4().hex[:12]}"
-
-    def start_operation(
-        self,
-        actor_type: ActorType,
-        actor_id: str | None = None,
-        repo: str | None = None,
-        pr_number: int | None = None,
-        issue_number: int | None = None,
-        correlation_id: str | None = None,
-        metadata: dict[str, Any] | None = None,
-    ) -> AuditContext:
-        """
-        Start a new auditable operation.
-
-        Args:
-            actor_type: Type of actor (USER, BOT, AUTOMATION, SYSTEM)
-            actor_id: Identifier for the actor (username, bot name, etc.)
-            repo: Repository in owner/repo format
-            pr_number: PR number if applicable
-            issue_number: Issue number if applicable
-            correlation_id: Optional existing correlation ID
-            metadata: Additional context metadata
-
-        Returns:
-            AuditContext for use with log() calls
-        """
-        return AuditContext(
-            correlation_id=correlation_id or self.generate_correlation_id(),
-            actor_type=actor_type,
-            actor_id=actor_id,
-            repo=repo,
-            pr_number=pr_number,
-            issue_number=issue_number,
-            metadata=metadata or {},
-        )
-
-    def log(
-        self,
-        context: AuditContext,
-        action: AuditAction,
-        result: str = "success",
-        error: str | None = None,
-        details: dict[str, Any] | None = None,
-        token_usage: dict[str, int] | None = None,
-        duration_ms: int | None = None,
-    ) -> AuditEntry:
-        """
-        Log an audit event.
-
-        Args:
-            context: Audit context from start_operation()
-            action: The action being logged
-            result: Result status (success, failure, skipped)
-            error: Error message if failed
-            details: Additional details about the action
-            token_usage: Token usage if AI-related (input_tokens, output_tokens)
-            duration_ms: Duration in milliseconds if timed
-
-        Returns:
-            The created AuditEntry
-        """
-        # Calculate duration from context start if not provided
-        if duration_ms is None and context.started_at:
-            elapsed = datetime.now(timezone.utc) - context.started_at
-            duration_ms = int(elapsed.total_seconds() * 1000)
-
-        entry = AuditEntry(
-            timestamp=datetime.now(timezone.utc),
-            correlation_id=context.correlation_id,
-            action=action,
-            actor_type=context.actor_type,
-            actor_id=context.actor_id,
-            repo=context.repo,
-            pr_number=context.pr_number,
-            issue_number=context.issue_number,
-            result=result,
-            duration_ms=duration_ms,
-            error=error,
-            details=details or {},
-            token_usage=token_usage,
-        )
-
-        self._write_entry(entry)
-        return entry
-
-    def _write_entry(self, entry: AuditEntry) -> None:
-        """Write an entry to the log file."""
-        if not self.enabled:
-            return
-
-        self._rotate_if_needed()
-
-        try:
-            log_file = self._get_log_file_path()
-            with open(log_file, "a") as f:
-                f.write(entry.to_json() + "\n")
-        except Exception as e:
-            logger.error(f"Failed to write audit log: {e}")
-
-    @contextmanager
-    def operation(
-        self,
-        action_start: AuditAction,
-        action_complete: AuditAction,
-        action_failed: AuditAction,
-        actor_type: ActorType,
-        actor_id: str | None = None,
-        repo: str | None = None,
-        pr_number: int | None = None,
-        issue_number: int | None = None,
-        metadata: dict[str, Any] | None = None,
-    ):
-        """
-        Context manager for auditing an operation.
-
-        Usage:
-            with audit.operation(
-                action_start=AuditAction.PR_REVIEW_STARTED,
-                action_complete=AuditAction.PR_REVIEW_COMPLETED,
-                action_failed=AuditAction.PR_REVIEW_FAILED,
-                actor_type=ActorType.AUTOMATION,
-                repo="owner/repo",
-                pr_number=123,
-            ) as ctx:
-                # Do work
-                ctx.metadata["findings_count"] = 5
-
-        Automatically logs start, completion, and failure with timing.
-        """
-        ctx = self.start_operation(
-            actor_type=actor_type,
-            actor_id=actor_id,
-            repo=repo,
-            pr_number=pr_number,
-            issue_number=issue_number,
-            metadata=metadata,
-        )
-
-        self.log(ctx, action_start, result="started")
-        start_time = time.monotonic()
-
-        try:
-            yield ctx
-            duration_ms = int((time.monotonic() - start_time) * 1000)
-            self.log(
-                ctx,
-                action_complete,
-                result="success",
-                details=ctx.metadata,
-                duration_ms=duration_ms,
-            )
-        except Exception as e:
-            duration_ms = int((time.monotonic() - start_time) * 1000)
-            self.log(
-                ctx,
-                action_failed,
-                result="failure",
-                error=str(e),
-                details=ctx.metadata,
-                duration_ms=duration_ms,
-            )
-            raise
-
-    def log_github_api_call(
-        self,
-        context: AuditContext,
-        endpoint: str,
-        method: str = "GET",
-        status_code: int | None = None,
-        duration_ms: int | None = None,
-        error: str | None = None,
-    ) -> None:
-        """Log a GitHub API call."""
-        action = (
-            AuditAction.GITHUB_API_CALL if not error else AuditAction.GITHUB_API_ERROR
-        )
-        self.log(
-            context,
-            action,
-            result="success" if not error else "failure",
-            error=error,
-            details={
-                "endpoint": endpoint,
-                "method": method,
-                "status_code": status_code,
-            },
-            duration_ms=duration_ms,
-        )
-
-    def log_ai_agent(
-        self,
-        context: AuditContext,
-        agent_type: str,
-        model: str,
-        input_tokens: int | None = None,
-        output_tokens: int | None = None,
-        duration_ms: int | None = None,
-        error: str | None = None,
-    ) -> None:
-        """Log an AI agent invocation."""
-        action = (
-            AuditAction.AI_AGENT_COMPLETED if not error else AuditAction.AI_AGENT_FAILED
-        )
-        self.log(
-            context,
-            action,
-            result="success" if not error else "failure",
-            error=error,
-            details={
-                "agent_type": agent_type,
-                "model": model,
-            },
-            token_usage={
-                "input_tokens": input_tokens or 0,
-                "output_tokens": output_tokens or 0,
-            },
-            duration_ms=duration_ms,
-        )
-
-    def log_permission_check(
-        self,
-        context: AuditContext,
-        allowed: bool,
-        reason: str,
-        username: str | None = None,
-        role: str | None = None,
-    ) -> None:
-        """Log a permission check result."""
-        action = (
-            AuditAction.PERMISSION_GRANTED if allowed else AuditAction.PERMISSION_DENIED
-        )
-        self.log(
-            context,
-            action,
-            result="granted" if allowed else "denied",
-            details={
-                "reason": reason,
-                "username": username,
-                "role": role,
-            },
-        )
-
-    def log_state_transition(
-        self,
-        context: AuditContext,
-        from_state: str,
-        to_state: str,
-        reason: str | None = None,
-    ) -> None:
-        """Log a state machine transition."""
-        self.log(
-            context,
-            AuditAction.STATE_TRANSITION,
-            details={
-                "from_state": from_state,
-                "to_state": to_state,
-                "reason": reason,
-            },
-        )
-
-    def log_override(
-        self,
-        context: AuditContext,
-        override_type: str,
-        original_action: str,
-        actor_id: str,
-    ) -> None:
-        """Log a user override action."""
-        self.log(
-            context,
-            AuditAction.OVERRIDE_APPLIED,
-            details={
-                "override_type": override_type,
-                "original_action": original_action,
-                "overridden_by": actor_id,
-            },
-        )
-
-    def query_logs(
-        self,
-        correlation_id: str | None = None,
-        action: AuditAction | None = None,
-        repo: str | None = None,
-        pr_number: int | None = None,
-        issue_number: int | None = None,
-        since: datetime | None = None,
-        limit: int = 100,
-    ) -> list[AuditEntry]:
-        """
-        Query audit logs with filters.
-
-        Args:
-            correlation_id: Filter by correlation ID
-            action: Filter by action type
-            repo: Filter by repository
-            pr_number: Filter by PR number
-            issue_number: Filter by issue number
-            since: Only entries after this time
-            limit: Maximum entries to return
-
-        Returns:
-            List of matching AuditEntry objects
-        """
-        if not self.enabled or not self.log_dir.exists():
-            return []
-
-        results = []
-
-        for log_file in sorted(self.log_dir.glob("audit_*.jsonl"), reverse=True):
-            try:
-                with open(log_file) as f:
-                    for line in f:
-                        if not line.strip():
-                            continue
-
-                        try:
-                            data = json.loads(line)
-                        except json.JSONDecodeError:
-                            continue
-
-                        # Apply filters
-                        if (
-                            correlation_id
-                            and data.get("correlation_id") != correlation_id
-                        ):
-                            continue
-                        if action and data.get("action") != action.value:
-                            continue
-                        if repo and data.get("repo") != repo:
-                            continue
-                        if pr_number and data.get("pr_number") != pr_number:
-                            continue
-                        if issue_number and data.get("issue_number") != issue_number:
-                            continue
-                        if since:
-                            entry_time = datetime.fromisoformat(data["timestamp"])
-                            if entry_time < since:
-                                continue
-
-                        # Reconstruct entry
-                        entry = AuditEntry(
-                            timestamp=datetime.fromisoformat(data["timestamp"]),
-                            correlation_id=data["correlation_id"],
-                            action=AuditAction(data["action"]),
-                            actor_type=ActorType(data["actor_type"]),
-                            actor_id=data.get("actor_id"),
-                            repo=data.get("repo"),
-                            pr_number=data.get("pr_number"),
-                            issue_number=data.get("issue_number"),
-                            result=data["result"],
-                            duration_ms=data.get("duration_ms"),
-                            error=data.get("error"),
-                            details=data.get("details", {}),
-                            token_usage=data.get("token_usage"),
-                        )
-                        results.append(entry)
-
-                        if len(results) >= limit:
-                            return results
-
-            except Exception as e:
-                logger.error(f"Error reading audit log {log_file}: {e}")
-
-        return results
-
-    def get_operation_history(self, correlation_id: str) -> list[AuditEntry]:
-        """Get all entries for a specific operation by correlation ID."""
-        return self.query_logs(correlation_id=correlation_id, limit=1000)
-
-    def get_statistics(
-        self,
-        repo: str | None = None,
-        since: datetime | None = None,
-    ) -> dict[str, Any]:
-        """
-        Get aggregate statistics from audit logs.
-
-        Returns:
-            Dictionary with counts by action, result, and actor type
-        """
-        entries = self.query_logs(repo=repo, since=since, limit=10000)
-
-        stats = {
-            "total_entries": len(entries),
-            "by_action": {},
-            "by_result": {},
-            "by_actor_type": {},
-            "total_duration_ms": 0,
-            "total_input_tokens": 0,
-            "total_output_tokens": 0,
-        }
-
-        for entry in entries:
-            # Count by action
-            action = entry.action.value
-            stats["by_action"][action] = stats["by_action"].get(action, 0) + 1
-
-            # Count by result
-            result = entry.result
-            stats["by_result"][result] = stats["by_result"].get(result, 0) + 1
-
-            # Count by actor type
-            actor = entry.actor_type.value
-            stats["by_actor_type"][actor] = stats["by_actor_type"].get(actor, 0) + 1
-
-            # Sum durations
-            if entry.duration_ms:
-                stats["total_duration_ms"] += entry.duration_ms
-
-            # Sum token usage
-            if entry.token_usage:
-                stats["total_input_tokens"] += entry.token_usage.get("input_tokens", 0)
-                stats["total_output_tokens"] += entry.token_usage.get(
-                    "output_tokens", 0
-                )
-
-        return stats
-
-
-# Convenience functions for quick logging
-def get_audit_logger() -> AuditLogger:
-    """Get the global audit logger instance."""
-    return AuditLogger.get_instance()
-
-
-def audit_operation(
-    action_start: AuditAction,
-    action_complete: AuditAction,
-    action_failed: AuditAction,
-    **kwargs,
-):
-    """Decorator for auditing function calls."""
-
-    def decorator(func):
-        async def async_wrapper(*args, **func_kwargs):
-            audit = get_audit_logger()
-            with audit.operation(
-                action_start=action_start,
-                action_complete=action_complete,
-                action_failed=action_failed,
-                **kwargs,
-            ) as ctx:
-                return await func(*args, audit_context=ctx, **func_kwargs)
-
-        def sync_wrapper(*args, **func_kwargs):
-            audit = get_audit_logger()
-            with audit.operation(
-                action_start=action_start,
-                action_complete=action_complete,
-                action_failed=action_failed,
-                **kwargs,
-            ) as ctx:
-                return func(*args, audit_context=ctx, **func_kwargs)
-
-        import asyncio
-
-        if asyncio.iscoroutinefunction(func):
-            return async_wrapper
-        return sync_wrapper
-
-    return decorator

apps/backend/runners/github/batch_validator.py

@@ -1,326 +0,0 @@
-"""
-Batch Validation Agent
-======================
-
-AI layer that validates issue batching using Claude SDK with extended thinking.
-Reviews whether semantically grouped issues actually belong together.
-"""
-
-from __future__ import annotations
-
-import importlib.util
-import json
-import logging
-from dataclasses import dataclass
-from pathlib import Path
-from typing import Any
-
-logger = logging.getLogger(__name__)
-
-# Check for Claude SDK availability without importing (avoids unused import warning)
-CLAUDE_SDK_AVAILABLE = importlib.util.find_spec("claude_agent_sdk") is not None
-
-# Default model and thinking configuration
-DEFAULT_MODEL = "claude-sonnet-4-20250514"
-DEFAULT_THINKING_BUDGET = 10000  # Medium thinking
-
-
-@dataclass
-class BatchValidationResult:
-    """Result of batch validation."""
-
-    batch_id: str
-    is_valid: bool
-    confidence: float  # 0.0 - 1.0
-    reasoning: str
-    suggested_splits: list[list[int]] | None  # If invalid, suggest how to split
-    common_theme: str  # Refined theme description
-
-    def to_dict(self) -> dict[str, Any]:
-        return {
-            "batch_id": self.batch_id,
-            "is_valid": self.is_valid,
-            "confidence": self.confidence,
-            "reasoning": self.reasoning,
-            "suggested_splits": self.suggested_splits,
-            "common_theme": self.common_theme,
-        }
-
-
-VALIDATION_PROMPT = """You are reviewing a batch of GitHub issues that were grouped together by semantic similarity.
-Your job is to validate whether these issues truly belong together for a SINGLE combined fix/PR.
-
-Issues should be batched together ONLY if:
-1. They describe the SAME root cause or closely related symptoms
-2. They can realistically be fixed together in ONE pull request
-3. Fixing one would naturally address the others
-4. They affect the same component/area of the codebase
-
-Issues should NOT be batched together if:
-1. They are merely topically similar but have different root causes
-2. They require separate, unrelated fixes
-3. One is a feature request and another is a bug fix
-4. They affect completely different parts of the codebase
-
-## Batch to Validate
-
-Batch ID: {batch_id}
-Primary Issue: #{primary_issue}
-Detected Themes: {themes}
-
-### Issues in this batch:
-
-{issues_formatted}
-
-## Your Task
-
-Analyze whether these issues truly belong together. Consider:
-- Do they share a common root cause?
-- Could a single PR reasonably fix all of them?
-- Are there any outliers that don't fit?
-
-Respond with a JSON object:
-```json
-{{
-  "is_valid": true/false,
-  "confidence": 0.0-1.0,
-  "reasoning": "Brief explanation of your decision",
-  "suggested_splits": null or [[issue_numbers], [issue_numbers]] if invalid,
-  "common_theme": "Refined description of what ties valid issues together"
-}}
-```
-
-Only output the JSON, no other text."""
-
-
-class BatchValidator:
-    """
-    Validates issue batches using Claude SDK with extended thinking.
-
-    Usage:
-        validator = BatchValidator(project_dir=Path("."))
-        result = await validator.validate_batch(batch)
-
-        if not result.is_valid:
-            # Split the batch according to suggestions
-            new_batches = result.suggested_splits
-    """
-
-    def __init__(
-        self,
-        project_dir: Path | None = None,
-        model: str = DEFAULT_MODEL,
-        thinking_budget: int = DEFAULT_THINKING_BUDGET,
-    ):
-        self.model = model
-        self.thinking_budget = thinking_budget
-        self.project_dir = project_dir or Path.cwd()
-
-        if not CLAUDE_SDK_AVAILABLE:
-            logger.warning(
-                "claude-agent-sdk not available. Batch validation will be skipped."
-            )
-
-    def _format_issues(self, issues: list[dict[str, Any]]) -> str:
-        """Format issues for the prompt."""
-        formatted = []
-        for issue in issues:
-            labels = ", ".join(issue.get("labels", [])) or "none"
-            body = issue.get("body", "")[:500]  # Truncate long bodies
-            if len(issue.get("body", "")) > 500:
-                body += "..."
-
-            formatted.append(f"""
-**Issue #{issue["issue_number"]}**: {issue["title"]}
-- Labels: {labels}
-- Similarity to primary: {issue.get("similarity_to_primary", 1.0):.0%}
-- Body: {body}
-""")
-        return "\n---\n".join(formatted)
-
-    async def validate_batch(
-        self,
-        batch_id: str,
-        primary_issue: int,
-        issues: list[dict[str, Any]],
-        themes: list[str],
-    ) -> BatchValidationResult:
-        """
-        Validate a batch of issues.
-
-        Args:
-            batch_id: Unique batch identifier
-            primary_issue: The primary/anchor issue number
-            issues: List of issue dicts with issue_number, title, body, labels, similarity_to_primary
-            themes: Detected common themes
-
-        Returns:
-            BatchValidationResult with validation decision
-        """
-        # Single issue batches are always valid
-        if len(issues) <= 1:
-            return BatchValidationResult(
-                batch_id=batch_id,
-                is_valid=True,
-                confidence=1.0,
-                reasoning="Single issue batch - no validation needed",
-                suggested_splits=None,
-                common_theme=themes[0] if themes else "single issue",
-            )
-
-        # Check if SDK is available
-        if not CLAUDE_SDK_AVAILABLE:
-            logger.warning("Claude SDK not available, assuming batch is valid")
-            return BatchValidationResult(
-                batch_id=batch_id,
-                is_valid=True,
-                confidence=0.5,
-                reasoning="Validation skipped - Claude SDK not available",
-                suggested_splits=None,
-                common_theme=themes[0] if themes else "",
-            )
-
-        # Format the prompt
-        prompt = VALIDATION_PROMPT.format(
-            batch_id=batch_id,
-            primary_issue=primary_issue,
-            themes=", ".join(themes) if themes else "none detected",
-            issues_formatted=self._format_issues(issues),
-        )
-
-        try:
-            # Create settings for minimal permissions (no tools needed)
-            settings = {
-                "permissions": {
-                    "defaultMode": "ignore",
-                    "allow": [],
-                },
-            }
-
-            settings_file = self.project_dir / ".batch_validator_settings.json"
-            with open(settings_file, "w") as f:
-                json.dump(settings, f)
-
-            try:
-                # Create Claude SDK client with extended thinking
-                from core.simple_client import create_simple_client
-
-                client = create_simple_client(
-                    agent_type="batch_validation",
-                    model=self.model,
-                    system_prompt="You are an expert at analyzing GitHub issues and determining if they should be grouped together for a combined fix.",
-                    cwd=self.project_dir,
-                    max_thinking_tokens=self.thinking_budget,  # Extended thinking
-                )
-
-                async with client:
-                    await client.query(prompt)
-                    result_text = await self._collect_response(client)
-
-                # Parse JSON response
-                result_json = self._parse_json_response(result_text)
-
-                return BatchValidationResult(
-                    batch_id=batch_id,
-                    is_valid=result_json.get("is_valid", True),
-                    confidence=result_json.get("confidence", 0.5),
-                    reasoning=result_json.get("reasoning", "No reasoning provided"),
-                    suggested_splits=result_json.get("suggested_splits"),
-                    common_theme=result_json.get("common_theme", ""),
-                )
-
-            finally:
-                # Cleanup settings file
-                if settings_file.exists():
-                    settings_file.unlink()
-
-        except Exception as e:
-            logger.error(f"Batch validation failed: {e}")
-            # On error, assume valid to not block the flow
-            return BatchValidationResult(
-                batch_id=batch_id,
-                is_valid=True,
-                confidence=0.5,
-                reasoning=f"Validation error (assuming valid): {str(e)}",
-                suggested_splits=None,
-                common_theme=themes[0] if themes else "",
-            )
-
-    async def _collect_response(self, client: Any) -> str:
-        """Collect text response from Claude client."""
-        response_text = ""
-
-        async for msg in client.receive_response():
-            msg_type = type(msg).__name__
-
-            if msg_type == "AssistantMessage":
-                for content in msg.content:
-                    if hasattr(content, "text"):
-                        response_text += content.text
-
-        return response_text
-
-    def _parse_json_response(self, text: str) -> dict[str, Any]:
-        """Parse JSON from the response, handling markdown code blocks."""
-        # Try to extract JSON from markdown code block
-        if "```json" in text:
-            start = text.find("```json") + 7
-            end = text.find("```", start)
-            if end > start:
-                text = text[start:end].strip()
-        elif "```" in text:
-            start = text.find("```") + 3
-            end = text.find("```", start)
-            if end > start:
-                text = text[start:end].strip()
-
-        try:
-            return json.loads(text)
-        except json.JSONDecodeError:
-            # Try to find JSON object in text
-            start = text.find("{")
-            end = text.rfind("}") + 1
-            if start >= 0 and end > start:
-                return json.loads(text[start:end])
-            raise
-
-
-async def validate_batches(
-    batches: list[dict[str, Any]],
-    project_dir: Path | None = None,
-    model: str = DEFAULT_MODEL,
-    thinking_budget: int = DEFAULT_THINKING_BUDGET,
-) -> list[BatchValidationResult]:
-    """
-    Validate multiple batches.
-
-    Args:
-        batches: List of batch dicts with batch_id, primary_issue, issues, common_themes
-        project_dir: Project directory for Claude SDK
-        model: Model to use for validation
-        thinking_budget: Token budget for extended thinking
-
-    Returns:
-        List of BatchValidationResult
-    """
-    validator = BatchValidator(
-        project_dir=project_dir,
-        model=model,
-        thinking_budget=thinking_budget,
-    )
-    results = []
-
-    for batch in batches:
-        result = await validator.validate_batch(
-            batch_id=batch["batch_id"],
-            primary_issue=batch["primary_issue"],
-            issues=batch["issues"],
-            themes=batch.get("common_themes", []),
-        )
-        results.append(result)
-        logger.info(
-            f"Batch {batch['batch_id']}: valid={result.is_valid}, "
-            f"confidence={result.confidence:.0%}, theme='{result.common_theme}'"
-        )
-
-    return results

apps/backend/runners/github/bot_detection.py

@@ -1,454 +0,0 @@
-"""
-Bot Detection for GitHub Automation
-====================================
-
-Prevents infinite loops by detecting when the bot is reviewing its own work.
-
-Key Features:
-- Identifies bot user from configured token
-- Skips PRs authored by the bot
-- Skips re-reviewing bot commits
-- Implements "cooling off" period to prevent rapid re-reviews
-- Tracks reviewed commits to avoid duplicate reviews
-
-Usage:
-    detector = BotDetector(bot_token="ghp_...")
-
-    # Check if PR should be skipped
-    should_skip, reason = detector.should_skip_pr_review(pr_data, commits)
-    if should_skip:
-        print(f"Skipping PR: {reason}")
-        return
-
-    # After successful review, mark as reviewed
-    detector.mark_reviewed(pr_number, head_sha)
-"""
-
-from __future__ import annotations
-
-import json
-import os
-import subprocess
-import sys
-from dataclasses import dataclass, field
-from datetime import datetime, timedelta
-from pathlib import Path
-
-try:
-    from .file_lock import FileLock, atomic_write
-except (ImportError, ValueError, SystemError):
-    from file_lock import FileLock, atomic_write
-
-
-@dataclass
-class BotDetectionState:
-    """State for tracking reviewed PRs and commits."""
-
-    # PR number -> set of reviewed commit SHAs
-    reviewed_commits: dict[int, list[str]] = field(default_factory=dict)
-
-    # PR number -> last review timestamp (ISO format)
-    last_review_times: dict[int, str] = field(default_factory=dict)
-
-    def to_dict(self) -> dict:
-        """Convert to dictionary for JSON serialization."""
-        return {
-            "reviewed_commits": self.reviewed_commits,
-            "last_review_times": self.last_review_times,
-        }
-
-    @classmethod
-    def from_dict(cls, data: dict) -> BotDetectionState:
-        """Load from dictionary."""
-        return cls(
-            reviewed_commits=data.get("reviewed_commits", {}),
-            last_review_times=data.get("last_review_times", {}),
-        )
-
-    def save(self, state_dir: Path) -> None:
-        """Save state to disk with file locking for concurrent safety."""
-        state_dir.mkdir(parents=True, exist_ok=True)
-        state_file = state_dir / "bot_detection_state.json"
-
-        # Use file locking to prevent concurrent write corruption
-        with FileLock(state_file, timeout=5.0, exclusive=True):
-            with atomic_write(state_file) as f:
-                json.dump(self.to_dict(), f, indent=2)
-
-    @classmethod
-    def load(cls, state_dir: Path) -> BotDetectionState:
-        """Load state from disk."""
-        state_file = state_dir / "bot_detection_state.json"
-
-        if not state_file.exists():
-            return cls()
-
-        with open(state_file) as f:
-            return cls.from_dict(json.load(f))
-
-
-class BotDetector:
-    """
-    Detects bot-authored PRs and commits to prevent infinite review loops.
-
-    Configuration via GitHubRunnerConfig:
-        - review_own_prs: bool = False (whether bot can review its own PRs)
-        - bot_token: str | None (separate bot account token)
-
-    Automatic safeguards:
-        - 1-minute cooling off period between reviews of same PR (for testing)
-        - Tracks reviewed commit SHAs to avoid duplicate reviews
-        - Identifies bot user from token to skip bot-authored content
-    """
-
-    # Cooling off period in minutes (reduced to 1 for testing large PRs)
-    COOLING_OFF_MINUTES = 1
-
-    def __init__(
-        self,
-        state_dir: Path,
-        bot_token: str | None = None,
-        review_own_prs: bool = False,
-    ):
-        """
-        Initialize bot detector.
-
-        Args:
-            state_dir: Directory for storing detection state
-            bot_token: GitHub token for bot (to identify bot user)
-            review_own_prs: Whether to allow reviewing bot's own PRs
-        """
-        self.state_dir = state_dir
-        self.bot_token = bot_token
-        self.review_own_prs = review_own_prs
-
-        # Load or initialize state
-        self.state = BotDetectionState.load(state_dir)
-
-        # Identify bot username from token
-        self.bot_username = self._get_bot_username()
-
-        print(
-            f"[BotDetector] Initialized: bot_user={self.bot_username}, review_own_prs={review_own_prs}",
-            file=sys.stderr,
-        )
-
-    def _get_bot_username(self) -> str | None:
-        """
-        Get the bot's GitHub username from the token.
-
-        Returns:
-            Bot username or None if token not provided or invalid
-        """
-        if not self.bot_token:
-            print(
-                "[BotDetector] No bot token provided, cannot identify bot user",
-                file=sys.stderr,
-            )
-            return None
-
-        try:
-            # Use gh api to get authenticated user
-            # Pass token via environment variable to avoid exposing it in process listings
-            env = os.environ.copy()
-            env["GH_TOKEN"] = self.bot_token
-            result = subprocess.run(
-                [
-                    "gh",
-                    "api",
-                    "user",
-                ],
-                capture_output=True,
-                text=True,
-                timeout=5,
-                env=env,
-            )
-
-            if result.returncode == 0:
-                user_data = json.loads(result.stdout)
-                username = user_data.get("login")
-                print(f"[BotDetector] Identified bot user: {username}")
-                return username
-            else:
-                print(f"[BotDetector] Failed to identify bot user: {result.stderr}")
-                return None
-
-        except Exception as e:
-            print(f"[BotDetector] Error identifying bot user: {e}")
-            return None
-
-    def is_bot_pr(self, pr_data: dict) -> bool:
-        """
-        Check if PR was created by the bot.
-
-        Args:
-            pr_data: PR data from GitHub API (must have 'author' field)
-
-        Returns:
-            True if PR author matches bot username
-        """
-        if not self.bot_username:
-            return False
-
-        pr_author = pr_data.get("author", {}).get("login")
-        is_bot = pr_author == self.bot_username
-
-        if is_bot:
-            print(f"[BotDetector] PR is bot-authored: {pr_author}")
-
-        return is_bot
-
-    def is_bot_commit(self, commit_data: dict) -> bool:
-        """
-        Check if commit was authored by the bot.
-
-        Args:
-            commit_data: Commit data from GitHub API (must have 'author' field)
-
-        Returns:
-            True if commit author matches bot username
-        """
-        if not self.bot_username:
-            return False
-
-        # Check both author and committer (could be different)
-        commit_author = commit_data.get("author", {}).get("login")
-        commit_committer = commit_data.get("committer", {}).get("login")
-
-        is_bot = (
-            commit_author == self.bot_username or commit_committer == self.bot_username
-        )
-
-        if is_bot:
-            print(
-                f"[BotDetector] Commit is bot-authored: {commit_author or commit_committer}"
-            )
-
-        return is_bot
-
-    def get_last_commit_sha(self, commits: list[dict]) -> str | None:
-        """
-        Get the SHA of the most recent commit.
-
-        Args:
-            commits: List of commit data from GitHub API
-
-        Returns:
-            SHA of latest commit or None if no commits
-        """
-        if not commits:
-            return None
-
-        # GitHub API returns commits in chronological order (oldest first, newest last)
-        latest = commits[-1]
-        return latest.get("oid") or latest.get("sha")
-
-    def is_within_cooling_off(self, pr_number: int) -> tuple[bool, str]:
-        """
-        Check if PR is within cooling off period.
-
-        Args:
-            pr_number: The PR number
-
-        Returns:
-            Tuple of (is_cooling_off, reason_message)
-        """
-        last_review_str = self.state.last_review_times.get(str(pr_number))
-
-        if not last_review_str:
-            return False, ""
-
-        try:
-            last_review = datetime.fromisoformat(last_review_str)
-            time_since = datetime.now() - last_review
-
-            if time_since < timedelta(minutes=self.COOLING_OFF_MINUTES):
-                minutes_left = self.COOLING_OFF_MINUTES - (
-                    time_since.total_seconds() / 60
-                )
-                reason = (
-                    f"Cooling off period active (reviewed {int(time_since.total_seconds() / 60)}m ago, "
-                    f"{int(minutes_left)}m remaining)"
-                )
-                print(f"[BotDetector] PR #{pr_number}: {reason}")
-                return True, reason
-
-        except (ValueError, TypeError) as e:
-            print(f"[BotDetector] Error parsing last review time: {e}")
-
-        return False, ""
-
-    def has_reviewed_commit(self, pr_number: int, commit_sha: str) -> bool:
-        """
-        Check if we've already reviewed this specific commit.
-
-        Args:
-            pr_number: The PR number
-            commit_sha: The commit SHA to check
-
-        Returns:
-            True if this commit was already reviewed
-        """
-        reviewed = self.state.reviewed_commits.get(str(pr_number), [])
-        return commit_sha in reviewed
-
-    def should_skip_pr_review(
-        self,
-        pr_number: int,
-        pr_data: dict,
-        commits: list[dict] | None = None,
-    ) -> tuple[bool, str]:
-        """
-        Determine if we should skip reviewing this PR.
-
-        This is the main entry point for bot detection logic.
-
-        Args:
-            pr_number: The PR number
-            pr_data: PR data from GitHub API
-            commits: Optional list of commits in the PR
-
-        Returns:
-            Tuple of (should_skip, reason)
-        """
-        # Check 1: Is this a bot-authored PR?
-        if not self.review_own_prs and self.is_bot_pr(pr_data):
-            reason = f"PR authored by bot user ({self.bot_username})"
-            print(f"[BotDetector] SKIP PR #{pr_number}: {reason}")
-            return True, reason
-
-        # Check 2: Is the latest commit by the bot?
-        # Note: GitHub API returns commits oldest-first, so commits[-1] is the latest
-        if commits and not self.review_own_prs:
-            latest_commit = commits[-1] if commits else None
-            if latest_commit and self.is_bot_commit(latest_commit):
-                reason = "Latest commit authored by bot (likely an auto-fix)"
-                print(f"[BotDetector] SKIP PR #{pr_number}: {reason}")
-                return True, reason
-
-        # Check 3: Are we in the cooling off period?
-        is_cooling, reason = self.is_within_cooling_off(pr_number)
-        if is_cooling:
-            print(f"[BotDetector] SKIP PR #{pr_number}: {reason}")
-            return True, reason
-
-        # Check 4: Have we already reviewed this exact commit?
-        head_sha = self.get_last_commit_sha(commits) if commits else None
-        if head_sha and self.has_reviewed_commit(pr_number, head_sha):
-            reason = f"Already reviewed commit {head_sha[:8]}"
-            print(f"[BotDetector] SKIP PR #{pr_number}: {reason}")
-            return True, reason
-
-        # All checks passed - safe to review
-        print(f"[BotDetector] PR #{pr_number} is safe to review")
-        return False, ""
-
-    def mark_reviewed(self, pr_number: int, commit_sha: str) -> None:
-        """
-        Mark a PR as reviewed at a specific commit.
-
-        This should be called after successfully posting a review.
-
-        Args:
-            pr_number: The PR number
-            commit_sha: The commit SHA that was reviewed
-        """
-        pr_key = str(pr_number)
-
-        # Add to reviewed commits
-        if pr_key not in self.state.reviewed_commits:
-            self.state.reviewed_commits[pr_key] = []
-
-        if commit_sha not in self.state.reviewed_commits[pr_key]:
-            self.state.reviewed_commits[pr_key].append(commit_sha)
-
-        # Update last review time
-        self.state.last_review_times[pr_key] = datetime.now().isoformat()
-
-        # Save state
-        self.state.save(self.state_dir)
-
-        print(
-            f"[BotDetector] Marked PR #{pr_number} as reviewed at {commit_sha[:8]} "
-            f"({len(self.state.reviewed_commits[pr_key])} total commits reviewed)"
-        )
-
-    def clear_pr_state(self, pr_number: int) -> None:
-        """
-        Clear tracking state for a PR (e.g., when PR is closed/merged).
-
-        Args:
-            pr_number: The PR number
-        """
-        pr_key = str(pr_number)
-
-        if pr_key in self.state.reviewed_commits:
-            del self.state.reviewed_commits[pr_key]
-
-        if pr_key in self.state.last_review_times:
-            del self.state.last_review_times[pr_key]
-
-        self.state.save(self.state_dir)
-
-        print(f"[BotDetector] Cleared state for PR #{pr_number}")
-
-    def get_stats(self) -> dict:
-        """
-        Get statistics about bot detection activity.
-
-        Returns:
-            Dictionary with stats
-        """
-        total_prs = len(self.state.reviewed_commits)
-        total_reviews = sum(
-            len(commits) for commits in self.state.reviewed_commits.values()
-        )
-
-        return {
-            "bot_username": self.bot_username,
-            "review_own_prs": self.review_own_prs,
-            "total_prs_tracked": total_prs,
-            "total_reviews_performed": total_reviews,
-            "cooling_off_minutes": self.COOLING_OFF_MINUTES,
-        }
-
-    def cleanup_stale_prs(self, max_age_days: int = 30) -> int:
-        """
-        Remove tracking state for PRs that haven't been reviewed recently.
-
-        This prevents unbounded growth of the state file by cleaning up
-        entries for PRs that are likely closed/merged.
-
-        Args:
-            max_age_days: Remove PRs not reviewed in this many days (default: 30)
-
-        Returns:
-            Number of PRs cleaned up
-        """
-        cutoff = datetime.now() - timedelta(days=max_age_days)
-        prs_to_remove: list[str] = []
-
-        for pr_key, last_review_str in self.state.last_review_times.items():
-            try:
-                last_review = datetime.fromisoformat(last_review_str)
-                if last_review < cutoff:
-                    prs_to_remove.append(pr_key)
-            except (ValueError, TypeError):
-                # Invalid timestamp - mark for removal
-                prs_to_remove.append(pr_key)
-
-        # Remove stale PRs
-        for pr_key in prs_to_remove:
-            if pr_key in self.state.reviewed_commits:
-                del self.state.reviewed_commits[pr_key]
-            if pr_key in self.state.last_review_times:
-                del self.state.last_review_times[pr_key]
-
-        if prs_to_remove:
-            self.state.save(self.state_dir)
-            print(
-                f"[BotDetector] Cleaned up {len(prs_to_remove)} stale PRs "
-                f"(older than {max_age_days} days)"
-            )
-
-        return len(prs_to_remove)

apps/backend/runners/github/bot_detection_example.py

@@ -1,154 +0,0 @@
-"""
-Bot Detection Integration Example
-==================================
-
-Demonstrates how to use the bot detection system to prevent infinite loops.
-"""
-
-from pathlib import Path
-
-from models import GitHubRunnerConfig
-from orchestrator import GitHubOrchestrator
-
-
-async def example_with_bot_detection():
-    """Example: Reviewing PRs with bot detection enabled."""
-
-    # Create config with bot detection
-    config = GitHubRunnerConfig(
-        token="ghp_user_token",
-        repo="owner/repo",
-        bot_token="ghp_bot_token",  # Bot's token for self-identification
-        pr_review_enabled=True,
-        auto_post_reviews=False,  # Manual review posting for this example
-        review_own_prs=False,  # CRITICAL: Prevent reviewing own PRs
-    )
-
-    # Initialize orchestrator (bot detector is auto-initialized)
-    orchestrator = GitHubOrchestrator(
-        project_dir=Path("/path/to/project"),
-        config=config,
-    )
-
-    print(f"Bot username: {orchestrator.bot_detector.bot_username}")
-    print(f"Review own PRs: {orchestrator.bot_detector.review_own_prs}")
-    print(
-        f"Cooling off period: {orchestrator.bot_detector.COOLING_OFF_MINUTES} minutes"
-    )
-    print()
-
-    # Scenario 1: Review a human-authored PR
-    print("=== Scenario 1: Human PR ===")
-    result = await orchestrator.review_pr(pr_number=123)
-    print(f"Result: {result.summary}")
-    print(f"Findings: {len(result.findings)}")
-    print()
-
-    # Scenario 2: Try to review immediately again (cooling off)
-    print("=== Scenario 2: Immediate re-review (should skip) ===")
-    result = await orchestrator.review_pr(pr_number=123)
-    print(f"Result: {result.summary}")
-    print()
-
-    # Scenario 3: Review bot-authored PR (should skip)
-    print("=== Scenario 3: Bot-authored PR (should skip) ===")
-    result = await orchestrator.review_pr(pr_number=456)  # Assume this is bot's PR
-    print(f"Result: {result.summary}")
-    print()
-
-    # Check statistics
-    stats = orchestrator.bot_detector.get_stats()
-    print("=== Bot Detection Statistics ===")
-    print(f"Bot username: {stats['bot_username']}")
-    print(f"Total PRs tracked: {stats['total_prs_tracked']}")
-    print(f"Total reviews: {stats['total_reviews_performed']}")
-
-
-async def example_manual_state_management():
-    """Example: Manually managing bot detection state."""
-
-    config = GitHubRunnerConfig(
-        token="ghp_user_token",
-        repo="owner/repo",
-        bot_token="ghp_bot_token",
-        review_own_prs=False,
-    )
-
-    orchestrator = GitHubOrchestrator(
-        project_dir=Path("/path/to/project"),
-        config=config,
-    )
-
-    detector = orchestrator.bot_detector
-
-    # Manually check if PR should be skipped
-    pr_data = {"author": {"login": "alice"}}
-    commits = [
-        {"author": {"login": "alice"}, "oid": "abc123"},
-        {"author": {"login": "alice"}, "oid": "def456"},
-    ]
-
-    should_skip, reason = detector.should_skip_pr_review(
-        pr_number=789,
-        pr_data=pr_data,
-        commits=commits,
-    )
-
-    if should_skip:
-        print(f"Skipping PR #789: {reason}")
-    else:
-        print("PR #789 is safe to review")
-        # Proceed with review...
-        # After review:
-        detector.mark_reviewed(789, "abc123")
-
-    # Clear state when PR is closed/merged
-    detector.clear_pr_state(789)
-
-
-def example_configuration_options():
-    """Example: Different configuration scenarios."""
-
-    # Option 1: Strict bot detection (recommended)
-    strict_config = GitHubRunnerConfig(
-        token="ghp_user_token",
-        repo="owner/repo",
-        bot_token="ghp_bot_token",
-        review_own_prs=False,  # Bot cannot review own PRs
-    )
-
-    # Option 2: Allow bot self-review (testing only)
-    permissive_config = GitHubRunnerConfig(
-        token="ghp_user_token",
-        repo="owner/repo",
-        bot_token="ghp_bot_token",
-        review_own_prs=True,  # Bot CAN review own PRs
-    )
-
-    # Option 3: No bot detection (no bot token)
-    no_detection_config = GitHubRunnerConfig(
-        token="ghp_user_token",
-        repo="owner/repo",
-        bot_token=None,  # No bot identification
-        review_own_prs=False,
-    )
-
-    print("Strict config:", strict_config.review_own_prs)
-    print("Permissive config:", permissive_config.review_own_prs)
-    print("No detection config:", no_detection_config.bot_token)
-
-
-if __name__ == "__main__":
-    print("Bot Detection Integration Examples\n")
-
-    print("\n1. Configuration Options")
-    print("=" * 50)
-    example_configuration_options()
-
-    print("\n2. With Bot Detection (requires GitHub setup)")
-    print("=" * 50)
-    print("Run: asyncio.run(example_with_bot_detection())")
-
-    print("\n3. Manual State Management")
-    print("=" * 50)
-    print("Run: asyncio.run(example_manual_state_management())")