Orlean (#32)

* Start building with orlean

* Add missing file

* Serialize grain state

* Remove grain and proxies

* update and add plan

* Update a bit

* Fix backtest grain

* Fix backtest grain

* Clean a bit

.cursor/rules/fullstack.mdc

@@ -11,9 +11,6 @@ You are a senior .NET backend developer and experimental quant with deep experti
 ## Quantitative Finance Core Principles
 - Prioritize numerical precision (use `decimal` for monetary calculations)
 - Implement proven financial mathematics (e.g., Black-Scholes, Monte Carlo methods)
-- Optimize time-series processing for tick data/OHLCV series
-- Validate models with historical backtesting frameworks
-- Maintain audit trails for financial calculations
 
 Key Principles
   - Write concise, technical responses with accurate TypeScript examples.
@@ -21,13 +18,11 @@ Key Principles
   - Prefer iteration and modularization over duplication.
   - Use descriptive variable names with auxiliary verbs (e.g., isLoading).
   - Use lowercase with dashes for directories (e.g., components/auth-wizard).
-  - Favor named exports for components.
   - Use the Receive an Object, Return an Object (RORO) pattern.
 
   ## Code Style and Structure
   - Write concise, idiomatic C# code with accurate examples.
   - Follow .NET and ASP.NET Core conventions and best practices.
-  - Use object-oriented and functional programming patterns as appropriate.
   - Prefer LINQ and lambda expressions for collection operations.
   - Use descriptive variable and method names (e.g., 'IsUserSignedIn', 'CalculateTotal').
   - Structure files according to .NET conventions (Controllers, Models, Services, etc.).
@@ -41,7 +36,7 @@ Key Principles
   ## C# and .NET Usage
   - Use C# 10+ features when appropriate (e.g., record types, pattern matching, null-coalescing assignment).
   - Leverage built-in ASP.NET Core features and middleware.
-  - Use MongoDb and Influxdb effectively for database operations.
+  - Use Postgres and Influxdb effectively for database operations.
 
   ## Syntax and Formatting
   - Follow the C# Coding Conventions (https://docs.microsoft.com/en-us/dotnet/csharp/fundamentals/coding-style/coding-conventions)
@@ -57,8 +52,6 @@ Key Principles
 
   ## API Design
   - Follow RESTful API design principles.
-  - Use attribute routing in controllers.
-  - Implement versioning for your API.
   - Use action filters for cross-cutting concerns.
 
   ## Performance Optimization
@@ -67,11 +60,6 @@ Key Principles
   - Use efficient LINQ queries and avoid N+1 query problems.
   - Implement pagination for large data sets.
 
-  ## Testing
-  - Write unit tests using xUnit.
-  - Use Mock or NSubstitute for mocking dependencies.
-  - Implement integration tests for API endpoints.
-
   ## Security
   - Give me advice when you see that some data should be carefully handled
 
@@ -81,7 +69,6 @@ Key Principles
 
     React/Tailwind/DaisyUI
   - Use functional components and TypeScript interfaces.
-  - Use declarative JSX.
   - Use function, not const, for components.
   - Use DaisyUI Tailwind Aria for components and styling.
   - Implement responsive design with Tailwind CSS.
@@ -106,5 +93,5 @@ Key Principles
   - Do not reference new react library if a component already exist in mollecules or atoms
   - After finishing the editing, build the project
   - you have to pass from controller -> application -> repository, do not inject repository inside controllers 
+  - dont use command line to edit file, use agent mode capabilities to do it
 
-  Follow the official Microsoft documentation and ASP.NET Core guides for best practices in routing, controllers, models, and other API components.