Revert "feat(ui): update rule builder logic" (#268)

Author: prajjwalkumar17

README.md

@@ -75,7 +75,7 @@ docker compose --profile dashboard-postgres-ghcr up -d
 Open:
 
 - API: `http://localhost:8080`
-- Dashboard: `http://localhost:8081/decision-engine/`
+- Dashboard: `http://localhost:8081/dashboard/`
 - Docs: `http://localhost:8081/introduction`
 - API reference: `http://localhost:8081/api-overview`
 
@@ -115,11 +115,6 @@ For the full local dev environment (API + dashboard on port 5173 + docs), run:
 
 This brings up Postgres, Redis, ClickHouse, and Kafka via Docker Compose, runs migrations, and starts the API server and dashboard locally. See [Local Setup Guide](docs/local-setup.md) for full details and options like `ONECLICK_KEEP_INFRA=1`.
 
-Source-run dashboard routes are mounted at root, for example `http://localhost:5173/routing/rules`.
-Hosted builds can be mounted under a configured prefix such as `/decision-engine/`.
-Local dev API calls use `/decision-engine-api/*`, which Vite proxies to `http://localhost:8080`.
-Override the build prefix with `VITE_DASHBOARD_BASE_PATH=/your-prefix/ npm run build` from `website/`, and override the API base with `VITE_API_BASE_PATH=https://your-host/your-api-prefix`.
-
 ### Verify
 
 ```bash
@@ -161,6 +156,21 @@ Decision Engine fits into an existing payment stack without replacing your orche
 
 ---
 
+## Roadmap
+
+| Status | Feature | Description |
+|:------:|---------|-------------|
+| ✅ | Rule-based routing | Merchant-defined priority rules via Euclid |
+| ✅ | Dynamic ordering | Success-rate based gateway selection |
+| ✅ | Downtime detection | Automatic health monitoring |
+| ✅ | Multi-database | MySQL & PostgreSQL support |
+| ✅ | Dashboard | Visual rule management and decision audit UI |
+| ✅ | Team management | Invite members to merchant accounts |
+| 🔄 | Enhanced routing models | Better success rate prediction |
+| 📋 | Multi-tenant analytics | Per-tenant routing insights |
+| 📋 | GraphQL API | Alternative query interface |
+
+---
 
 ## Contributing
 

docker-compose.yaml

@@ -162,7 +162,7 @@ services:
       - "8081:80"
     volumes:
       - ./nginx/nginx.conf:/etc/nginx/nginx.conf:ro
-      - ./website/dist:/usr/share/nginx/html/decision-engine:ro
+      - ./website/dist:/usr/share/nginx/html/dashboard:ro
     depends_on:
       mintlify-docs:
         condition: service_healthy

docs/analytics.mdx

@@ -69,8 +69,8 @@ RULE_EVALUATIONS=40 bash scripts/generate-routing-traffic.sh
 CONNECTORS_CSV=stripe,adyen,checkout,paypal bash scripts/generate-routing-traffic.sh
 ```
 
-After the script finishes, sign in as `merchant_space` and open `/decision-engine/analytics` or
-`/decision-engine/audit`. Analytics reads will resolve the merchant from your authenticated session.
+After the script finishes, sign in as `merchant_space` and open `/dashboard/analytics` or
+`/dashboard/audit`. Analytics reads will resolve the merchant from your authenticated session.
 
 ## ClickHouse Setup
 

docs/api-overview.md

@@ -75,6 +75,7 @@ If the dashboard is hosted under a prefix such as `/decision-engine/`, the docs
 | Public | `GET /health`, `GET /health/ready`, `GET /health/diagnostics`, `POST /auth/signup`, `POST /auth/login` | None |
 | Admin bootstrap | `POST /merchant-account/create` | Admin secret configured for the deployment |
 | Protected | Routing, decision, score update, rule config, API key, merchant read/delete, analytics, audit, config, and authenticated auth routes | `Authorization: Bearer <jwt_token>` or `x-api-key: <api_key>` |
+| Sandbox | Same routes through `https://sandbox.hyperswitch.io` | Same auth rules plus `x-feature: decision-engine` |
 
 ## Common flows
 

docs/api-reference.md

@@ -19,6 +19,7 @@ If you need rule examples such as AND, OR, nested AND+OR, `volume_split_priority
 | Public | `GET /health`, `GET /health/ready`, `GET /health/diagnostics`, `POST /auth/signup`, `POST /auth/login` | None |
 | Admin bootstrap | `POST /merchant-account/create` | Admin secret |
 | Protected | All routing, decision, score update, rule config, API key, merchant read/delete, analytics, audit, config, and authenticated auth routes | `Authorization: Bearer <jwt_token>` or `x-api-key: <api_key>` |
+| Sandbox | Any Decision Engine route served through `https://sandbox.hyperswitch.io` | Same auth rules plus `x-feature: decision-engine` |
 
 ## Endpoint Families
 
@@ -93,4 +94,4 @@ If you need rule examples such as AND, OR, nested AND+OR, `volume_split_priority
 
 ## Curl Examples
 
-For local and deployment smoke-test examples, use [API Examples](./api-refs/api-ref.mdx).
+For local and sandbox smoke-test examples, use [API Examples](./api-refs/api-ref.mdx).

docs/api-reference/endpoint/activateRoutingRule.mdx

@@ -12,13 +12,16 @@ Marks a created routing algorithm as active for the merchant/creator scope.
 
 ## Authentication
 
-Protected. Send either `Authorization: Bearer <jwt_token>` or `x-api-key: <api_key>`.
+Protected. Send either `Authorization: Bearer <jwt_token>` or `x-api-key: <api_key>`. In sandbox, also send `x-feature: decision-engine`.
 
 For local development, start with:
 
 ```bash
 export BASE_URL=http://localhost:8080
 export AUTH_HEADER="Authorization: Bearer <jwt_token>"
+# Sandbox only:
+# export BASE_URL=https://sandbox.hyperswitch.io
+# export FEATURE_HEADER="x-feature: decision-engine"
 ```
 
 ## Request

docs/api-reference/endpoint/analyticsDecisions.mdx

@@ -12,13 +12,16 @@ Returns decision volume time series and routing approach totals for the selected
 
 ## Authentication
 
-Protected. Send either `Authorization: Bearer <jwt_token>` or `x-api-key: <api_key>`.
+Protected. Send either `Authorization: Bearer <jwt_token>` or `x-api-key: <api_key>`. In sandbox, also send `x-feature: decision-engine`.
 
 For local development, start with:
 
 ```bash
 export BASE_URL=http://localhost:8080
 export AUTH_HEADER="Authorization: Bearer <jwt_token>"
+# Sandbox only:
+# export BASE_URL=https://sandbox.hyperswitch.io
+# export FEATURE_HEADER="x-feature: decision-engine"
 ```
 
 ## Request

docs/api-reference/endpoint/analyticsGatewayScores.mdx

@@ -12,13 +12,16 @@ Returns connector success-rate score snapshots and time series for auth-rate bas
 
 ## Authentication
 
-Protected. Send either `Authorization: Bearer <jwt_token>` or `x-api-key: <api_key>`.
+Protected. Send either `Authorization: Bearer <jwt_token>` or `x-api-key: <api_key>`. In sandbox, also send `x-feature: decision-engine`.
 
 For local development, start with:
 
 ```bash
 export BASE_URL=http://localhost:8080
 export AUTH_HEADER="Authorization: Bearer <jwt_token>"
+# Sandbox only:
+# export BASE_URL=https://sandbox.hyperswitch.io
+# export FEATURE_HEADER="x-feature: decision-engine"
 ```
 
 ## Request

docs/api-reference/endpoint/analyticsLogSummaries.mdx

@@ -12,13 +12,16 @@ Returns error aggregates and recent failed event samples for the selected mercha
 
 ## Authentication
 
-Protected. Send either `Authorization: Bearer <jwt_token>` or `x-api-key: <api_key>`.
+Protected. Send either `Authorization: Bearer <jwt_token>` or `x-api-key: <api_key>`. In sandbox, also send `x-feature: decision-engine`.
 
 For local development, start with:
 
 ```bash
 export BASE_URL=http://localhost:8080
 export AUTH_HEADER="Authorization: Bearer <jwt_token>"
+# Sandbox only:
+# export BASE_URL=https://sandbox.hyperswitch.io
+# export FEATURE_HEADER="x-feature: decision-engine"
 ```
 
 ## Request

docs/api-reference/endpoint/analyticsOverview.mdx

@@ -12,13 +12,16 @@ Returns summary metrics for the dashboard overview: request volume, gateway shar
 
 ## Authentication
 
-Protected. Send either `Authorization: Bearer <jwt_token>` or `x-api-key: <api_key>`.
+Protected. Send either `Authorization: Bearer <jwt_token>` or `x-api-key: <api_key>`. In sandbox, also send `x-feature: decision-engine`.
 
 For local development, start with:
 
 ```bash
 export BASE_URL=http://localhost:8080
 export AUTH_HEADER="Authorization: Bearer <jwt_token>"
+# Sandbox only:
+# export BASE_URL=https://sandbox.hyperswitch.io
+# export FEATURE_HEADER="x-feature: decision-engine"
 ```
 
 ## Request