From 29c4b57db9a34e0f815d93cac6a2cae543778a93 Mon Sep 17 00:00:00 2001 From: kboz Date: Fri, 24 Apr 2026 01:11:23 +0200 Subject: build(core): adopt fork and remove experimental rust backend - Added a 2026 copyright statement under the original creator's in `license.md` to properly establish new fork logic. - Updated `readme.md` to explicitly state this repository is a maintained fork. - Eliminated the `rust_backend/` directory, Actix codebase, and its associated launch configurations. - Purged all references specifying a Python/Rust/React tri-split from `AGENTS.md` and the frontend `.instructions.md` configuration. Co-authored-by: Copilot --- AGENTS.md | 11 +++-------- 1 file changed, 3 insertions(+), 8 deletions(-) (limited to 'AGENTS.md') diff --git a/AGENTS.md b/AGENTS.md index e01bd4e..0ba3b7e 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -2,9 +2,8 @@ ## Start Here -- See [readme.md](readme.md) for product context and the Python/React/Rust split. +- See [readme.md](readme.md) for product context and the Python/React split. - Treat the Python backend as the active application backend. The React frontend is hardcoded to `http://localhost:8000`. -- Treat `rust_backend/` as an experimental rewrite. It runs separately on `127.0.0.1:8080` and is not a drop-in replacement for the Python backend. ## Run and Validate @@ -12,8 +11,6 @@ - Frontend tests: `cd frontend && npm test -- --watchAll=false` - Frontend build: `cd frontend && npm run build` - Python backend: `cd backend/src && python -m uvicorn main:app --reload --port 8000` -- Rust backend: `cd rust_backend && cargo run` -- Rust tests: `cd rust_backend && cargo test` - The Python backend has no checked-in dependency manifest. Before running it, confirm the local environment already has the required packages plus the EVE auth/cache files and CSV map data under `backend/data/`. ## Architecture @@ -22,12 +19,10 @@ - `backend/src/esi/` owns ESI auth, character location, waypoint updates, and other live API side effects. - `backend/src/graph.py`, `loader.py`, `market.py`, `arbitrage.py`, `pathfinder.py`, and `route.py` form the route-planning and market-analysis pipeline. - `frontend/src/` uses small function components. `usePolling.js` and `useSSE.js` own long-lived network subscriptions; display components render the returned payloads. -- `rust_backend/src/main.rs` is a thin Actix entrypoint. `manager.rs` owns shared state and polling, `eve_service.rs` wraps `eve_api.rs`, and `pathfinding/` plus `market/` stay modular. ## Repo-Specific Conventions -- Preserve the current port split unless the task is explicitly a migration: frontend `:3000`, Python backend `:8000`, Rust backend `:8080`. +- Preserve the current port split: frontend `:3000`, Python backend `:8000`. - Keep external API calls and UI side effects out of the route-planning and market-analysis modules. - Prefer typed models, named thresholds/constants, and small transformations over ad hoc inline logic in backend algorithms. -- When changing the Rust backend, do not assume Python endpoint parity. Add routes, SSE or polling support, and CORS explicitly before wiring the frontend to it. -- Be cautious about local-only runtime dependencies: Python expects ESI auth/cache state plus CSV map data under `backend/data/`; Rust expects OAuth env vars and `token.json`. \ No newline at end of file +- Be cautious about local-only runtime dependencies: Python expects ESI auth/cache state plus CSV map data under `backend/data/`. \ No newline at end of file -- cgit v1.3