Feat/trade panel dex

.git-blame-ignore-revs

@@ -0,0 +1,6 @@
+# Revisions listed here are skipped by `git blame`.
+# Enable locally with:
+#   git config blame.ignoreRevsFile .git-blame-ignore-revs
+#
+# (style) mechanical format sweep: isort then black over the Python tree (READ-133)
+3fa941fa3e49fb647b94916b92d11e481e7b7fdd

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -1,40 +1,70 @@
 name: Bug Report
-description: Create a bug report to help us improve
-title: "Bug Report"
-labels: bug
+description: Something in Condor does not work the way it should
+title: "[Bug] "
+labels: [bug]
 body:
- - type: markdown
-   attributes:
-     value: |
-       ## **Before Submitting:**
-
-       * Please edit the "Bug Report" to the title of the bug or issue
-       * Please make sure to look on our GitHub issues to avoid duplicate tickets
-       * You can add additional `Labels` to support this ticket (connectors, strategies, etc)
-       * If this is something to do with installation and how to's we would recommend to visit our [Hummingbot docs](https://hummingbot.org/docs/) and [Discord server](https://discord.gg/hummingbot)
- - type: textarea
-   id: what-happened
-   attributes:
-     label: Describe the bug
-     description: A clear and concise description of the bug or issue. Please make sure to add screenshots and error message to help us investigate
-     placeholder: Tell us what happened?
-   validations:
-     required: true
- - type: textarea
-   id: reproduce
-   attributes:
-     label: Steps to reproduce
-     description: A concise description of the steps to reproduce the buggy behavior
-     value: |
-       1. 
-       2. 
-       3. 
-   validations:
-     required: true
- - type: textarea
-   id: attachment
-   attributes:
-     label: Attach required files
-     description: Please attach your config file and log file located on the "../gateway/logs/" folder. It would be really helpful to triage the issue. 
-   validations:
-     required: false
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to report this.
+
+        **Before you file:** search the [open issues](https://github.com/hummingbot/condor/issues?q=is%3Aissue) first — a duplicate splits the discussion in two.
+
+        **Never paste secrets.** API keys, wallet private keys, seed phrases, your `.env` or an unredacted `config.yml` do not belong in a public issue. If the dashboard filled in the "Environment" box below, read it before you submit.
+
+  - type: dropdown
+    id: area
+    attributes:
+      label: Area
+      description: Where in Condor did this happen? (The dashboard preselects this for you.)
+      options:
+        - Agents & chat
+        - Portfolio
+        - Bots & controllers
+        - Trading & executors
+        - Routines & reports
+        - Settings & connections
+        - Dashboard (other)
+        - Telegram bot
+        - Gateway / DEX
+        - Not sure
+    validations:
+      required: true
+
+  - type: textarea
+    id: what-happened
+    attributes:
+      label: What happened
+      description: What you expected, and what you got instead. Screenshots help.
+      placeholder: The portfolio chart stays blank after I switch servers, but the balances table updates.
+    validations:
+      required: true
+
+  - type: textarea
+    id: reproduce
+    attributes:
+      label: Steps to reproduce
+      description: The shortest path from a fresh session to the bug.
+      value: |
+        1. 
+        2. 
+        3. 
+    validations:
+      required: true
+
+  - type: textarea
+    id: attachment
+    attributes:
+      label: Environment
+      description: |
+        Condor version, page, browser and recent errors. The dashboard's "Report an issue" button (🐛, top right) fills this in automatically; otherwise paste the output of `git rev-parse --short HEAD` and how you run Condor (source, Docker).
+    validations:
+      required: false
+
+  - type: textarea
+    id: logs
+    attributes:
+      label: Logs
+      description: Relevant lines from the bot log or the browser console. Redact keys, hosts and wallet addresses first.
+    validations:
+      required: false

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -1,35 +1,58 @@
-name: Feature request
-description: Suggest an idea that will improve the Hummingbot codebase
-title: "Feature Request"
-labels: enhancement
+name: Feature Request
+description: Suggest something Condor should be able to do
+title: "[Feature] "
+labels: [enhancement]
 body:
- - type: markdown
-   attributes:
-     value: |
-       ## **Before Submitting:**
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for the idea.
 
-       * Please edit the "Feature Request" to the title of the feature
-       * Please make sure to look on our GitHub issues to avoid duplicate tickets
-       * You can add additional `Labels` to support this ticket (connectors, strategies, etc)
-       * If this is something to do with installation and how to's we would recommend to visit our [Discord server](https://discord.gg/hummingbot) and [Hummingbot docs](https://hummingbot.org/docs/)
- - type: textarea
-   id: feature-suggestion
-   attributes:
-     label: Feature Suggestion
-     description: A clear and concise description of the feature request. If you have looked at the code and know exactly what code changes are needed then please consider submitting a pull request instead.
-     placeholder: How you want to achieve the desired behavior
-   validations:
-     required: true
- - type: textarea
-   id: feature-impact
-   attributes:
-     label: Impact
-     description: A succinct description of why you want the desired behavior specified above.
-     placeholder: The desired behavior will allow me to..
-   validations:
-     required: true
- - type: textarea
-   id: feature-additional-context
-   attributes:
-     label: Additional context
-     description: Add any other context or screenshots about the feature request here (optional)
+        **Before you file:** search the [open issues](https://github.com/hummingbot/condor/issues?q=is%3Aissue) — someone may already be arguing for it, and a second voice on one thread carries further than a second thread.
+
+        If you already know what the change looks like in code, a pull request is welcome instead.
+
+  - type: dropdown
+    id: area
+    attributes:
+      label: Area
+      description: Which part of Condor would this touch? (The dashboard preselects this for you.)
+      options:
+        - Agents & chat
+        - Portfolio
+        - Bots & controllers
+        - Trading & executors
+        - Routines & reports
+        - Settings & connections
+        - Dashboard (other)
+        - Telegram bot
+        - Gateway / DEX
+        - Not sure
+    validations:
+      required: true
+
+  - type: textarea
+    id: feature-suggestion
+    attributes:
+      label: What should it do
+      description: Describe the behavior you want, not the implementation.
+      placeholder: Let me filter the executors table by connector, the way the bots table already filters by status.
+    validations:
+      required: true
+
+  - type: textarea
+    id: feature-impact
+    attributes:
+      label: Why it matters
+      description: What this would let you do that you cannot do today, and how often you hit it.
+      placeholder: With 40 executors open I scroll past everything to find the two on Hyperliquid.
+    validations:
+      required: true
+
+  - type: textarea
+    id: feature-additional-context
+    attributes:
+      label: Additional context
+      description: Mockups, links, the workaround you use today, or the version you are on.
+    validations:
+      required: false

.github/workflows/ci.yml

@@ -0,0 +1,103 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
+
+jobs:
+  backend-lint:
+    name: Backend Lint
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: astral-sh/setup-uv@v4
+        with:
+          version: "latest"
+
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+
+      - name: Install dependencies
+        run: uv sync --dev
+
+      - name: Check formatting with black
+        run: uv run black --check .
+
+      - name: Check import sorting with isort
+        run: uv run isort --check .
+
+  backend-import-check:
+    name: Backend Import Check
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: astral-sh/setup-uv@v4
+        with:
+          version: "latest"
+
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+
+      - name: Install dependencies
+        run: uv sync
+
+      - name: Verify main modules import without errors
+        run: |
+          uv run python -c "
+          import config_manager
+          import handlers
+          import utils
+          print('All core modules imported successfully')
+          "
+
+  backend-tests:
+    name: Backend Tests
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: astral-sh/setup-uv@v4
+        with:
+          version: "latest"
+
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+
+      - name: Install dependencies
+        run: uv sync --dev
+
+      - name: Run tests
+        run: uv run pytest --tb=short -q
+
+  frontend-build:
+    name: Frontend Build & Lint
+    runs-on: ubuntu-latest
+    defaults:
+      run:
+        working-directory: frontend
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-node@v4
+        with:
+          node-version: "20"
+          cache: "npm"
+          cache-dependency-path: frontend/package-lock.json
+
+      - name: Install dependencies
+        run: npm ci
+
+      # Gates on *new* errors against eslint-baseline.json rather than on the
+      # 76 that predate this workflow -- see frontend/scripts/lint-baseline.mjs.
+      - name: Lint
+        run: npm run lint:ci
+
+      - name: Build
+        run: npm run build