refactor(topstepx): migrate to extensions & enhance cli integration

- **Migration**: Moved TopstepX Python client to  and SignalR Bridge to .
- **Refactor**: Updated all tests to be standalone, removing server dependencies. Verified 20/20 pass.
- **CLI**: Added  command group for managing credentials, environment, and Hub URLs.
- **Configuration**: Standardized environment variables (, , ) with production defaults.
- **Documentation**: Added  guide and  files for Agent support.

Author: quantDIY

docs/TOPSTEPX_INTEGRATION.md

@@ -0,0 +1,100 @@
+# TopstepX Integration Guide
+
+## Overview
+The **TopstepX Integration** enables QuanuX to interact with the TopstepX platform for trading, account management, and real-time market data. It is architected as a set of decoupled [QuanuX Extensions](EXTENSIONS.md):
+
+1.  **TopstepX Interface (`quanux-topstepx`)**: A Python-based REST client for account retrieval, order execution, and history.
+2.  **SignalR Bridge (`quanux-bridge-signalr`)**: A polyglot (Node.js/Python) bridge that maintains a persistent WebSocket connection to TopstepX's SignalR hubs for real-time market data and user events.
+
+## Architecture
+
+```mermaid
+graph TD
+    User[User / QuanuX Agent] -->|CLI / Events| TopstepX[TopstepX Extension]
+    User -->|Market Data| SignalR[SignalR Bridge]
+    
+    TopstepX -->|REST API| TS_API[api.topstepx.com]
+    SignalR -->|WebSockets| TS_Hubs[rtc.topstepx.com]
+    
+    subgraph "Extensions Layer"
+        TopstepX
+        SignalR
+    end
+    
+    subgraph "External"
+        TS_API
+        TS_Hubs
+    end
+```
+
+## Configuration
+
+### Credentials
+All sensitive credentials are stored securely in the system keyring via `quanuxctl`. They are **never** stored in plain text configuration files.
+
+| Key | Description |
+| :--- | :--- |
+| `QUANUX_TOPSTEP__USERNAME` | TopstepX Username |
+| `QUANUX_TOPSTEP__PASSWORD` | TopstepX Password |
+| `QUANUX_TOPSTEP__API_KEY` | TopstepX API Key |
+
+### Endpoints (Defaults)
+The extensions are pre-configured for the production environment but can be overridden via `quanuxctl`.
+
+| Key | Default Value | Description |
+| :--- | :--- | :--- |
+| `QUANUX_TOPSTEP__BASE_API_URL` | `https://api.topstepx.com` | REST API Base URL |
+| `QUANUX_SIGNALR_USER_HUB` | `https://rtc.topstepx.com/hubs/user` | Real-time User Events |
+| `QUANUX_SIGNALR_MARKET_HUB` | `https://rtc.topstepx.com/hubs/market` | Real-time Market Data |
+
+## Usage
+
+### CLI Management (`quanuxctl`)
+Manage the integration directly from the command line:
+
+```bash
+# Set Credentials
+quanuxctl topstepx user "myuser"
+quanuxctl topstepx password "mypass"
+quanuxctl topstepx apikey "mykey"
+
+# Verify Environment
+quanuxctl topstepx env
+
+# Install Dependencies
+quanuxctl topstepx install
+```
+
+### SignalR Bridge
+The bridge runs as a separate process managed by QuanuX. It connects to the configured hubs and broadcasts events to the local QuanuX message bus.
+
+**Status Check:**
+```bash
+quanuxctl bridge status
+```
+
+**Manual Start (Debug):**
+```bash
+quanuxctl bridge run
+```
+
+## Developer Usage
+
+### Python Extension (`extensions/python/topstepx`)
+The extension exposes a standard interface for interactions. The source code is located in `extensions/python/topstepx/src`.
+
+**Key Modules:**
+*   `auth.py`: Handles authentication and token management.
+*   `orders.py`: Order placement and management.
+*   `positions.py`: Position tracking.
+*   `history.py`: Historical bar retrieval.
+
+### SignalR Bridge (`extensions/python/signalr_bridge`)
+The bridge uses a Node.js worker (default) or Flask app to handle the proprietary SignalR protocol.
+
+**Custom Hub Configuration:**
+If you need to connect to a different environment (e.g., simulation):
+```bash
+quanuxctl topstepx user-hub "https://sim-rtc.topstepx.com/hubs/user"
+quanuxctl topstepx market-hub "https://sim-rtc.topstepx.com/hubs/market"
+```

extensions/python/signalr_bridge/SKILL.md

@@ -0,0 +1,55 @@
+---
+name: signalr-bridge
+description: Instructions for operating and configuring the SignalR Bridge for TopstepX.
+---
+
+# SignalR Bridge Skill
+
+The **SignalR Bridge** (`quanux-bridge-signalr`) is a specialized extension that maintains persistent WebSocket connections to TopstepX's SignalR Hubs. It bridges the gap between the proprietary SignalR protocol and QuanuX's internal messaging.
+
+## Location
+- **Path**: `extensions/python/signalr_bridge`
+- **Config**: `extensions/python/signalr_bridge/extension.yaml`
+- **Node Runtime**: `extensions/python/signalr_bridge/src/node` (Preferred)
+- **Flask Runtime**: `extensions/python/signalr_bridge/src/flask` (Legacy/Fallback)
+
+## Architecture
+The bridge runs as a standalone process (supervised by QuanuX).
+- **Upstream**: Connects to `rtc.topstepx.com` (User/Market Hubs).
+- **Downstream**: Exposes a wrapper WebSocket (or HTTP callbacks) to QuanuX components.
+
+## Configuration (TopstepX Specific)
+This bridge is pre-configured for TopstepX logic but is technically generic.
+
+**Key Environment Variables (Managed via `quanuxctl topstepx env`):**
+- `QUANUX_SIGNALR_USER_HUB`: URL for the User Hub (Login, Orders, Fills). 
+  - Default: `https://rtc.topstepx.com/hubs/user`
+- `QUANUX_SIGNALR_MARKET_HUB`: URL for the Market Hub (Quotes, Level 2).
+  - Default: `https://rtc.topstepx.com/hubs/market`
+
+## Operation
+
+### Starting the Bridge
+The bridge is usually started automatically by `quanuxctl bridge` or the main server.
+To verify functionality manually:
+```bash
+# In extensions/python/signalr_bridge
+python src/supervisor.py
+```
+
+### Health Check
+The Node runtime exposes a health endpoint:
+```bash
+curl http://localhost:8077/health
+```
+Response should include `"status": "ok"` and `"hubUrl"`.
+
+### Debugging Connection Issues
+1.  **Check URLs**: Ensure `QUANUX_SIGNALR_USER_HUB` is set correctly.
+2.  **Check Token**: The bridge relies on `SIGNALR_ACCESS_TOKEN` which is usually refreshed and injected by the main `quanux-topstepx` auth flow. If authentication fails, the bridge cannot connect.
+3.  **Logs**: Check `~/.quanux/logs/quanux-bridge-signalr.log`.
+
+## Development
+- **Node.js**: `src/node/index.mjs`. Uses `@microsoft/signalr` client. 
+  - To install deps: `npm install` in `src/node`.
+- **Modifying Events**: If new TopstepX events need to be tracked, update the `on(...)` listeners in `index.mjs`.

server/bridges/signalr/manifest.yaml …ons/python/signalr_bridge/extension.yamlserver/bridges/signalr/manifest.yaml renamed to extensions/python/signalr_bridge/extension.yaml server/bridges/signalr/manifest.yaml renamed to extensions/python/signalr_bridge/extension.yaml

@@ -2,6 +2,7 @@ name: quanux-bridge-signalr
 version: v0.0.1
 owner: platform
 description: "Real-time SignalR bridge for QuanuX (scaffold). Choose Flask or Node runtime."
+command: "python src/supervisor.py"
 
 default_runtime: flask
 alternatives:
@@ -12,6 +13,8 @@ config:
     QUANUX_BRIDGE_PORT: 8077
     QUANUX_LOG_LEVEL: INFO
     QUANUX_BRIDGE_CORS: "*"
+    QUANUX_SIGNALR_USER_HUB: "https://rtc.topstepx.com/hubs/user"
+    QUANUX_SIGNALR_MARKET_HUB: "https://rtc.topstepx.com/hubs/market"
 
 endpoints:
   flask:
@@ -20,15 +23,17 @@ endpoints:
 
 runtimes:
   flask:
-    entry: "python3 server/bridges/signalr/flask/app.py"
+    entry: "python src/flask/app.py"
   node:
-    entry: "node server/bridges/signalr/node/index.mjs"
+    entry: "node src/node/index.mjs"
 
 process_model:
   node_worker:
-    entry: "server/bridges/signalr/node/index.mjs"
+    entry: "src/node/index.mjs"
     env:
       SIGNALR_HUB_URL: "${SIGNALR_HUB_URL}"
+      SIGNALR_USER_HUB: "${QUANUX_SIGNALR_USER_HUB}"
+      SIGNALR_MARKET_HUB: "${QUANUX_SIGNALR_MARKET_HUB}"
       SIGNALR_ACCESS_TOKEN: "${SIGNALR_ACCESS_TOKEN}"
       SIGNALR_PROTOCOL: "json"
 
@@ -42,6 +47,10 @@ security:
   secrets:
     - key: "SIGNALR_ACCESS_TOKEN"
       provider: "quanux.secrets"
+    - key: "QUANUX_SIGNALR_USER_HUB"
+      provider: "quanux.secrets"
+    - key: "QUANUX_SIGNALR_MARKET_HUB"
+      provider: "quanux.secrets"
 
 health:
   checks: