feat: Enhance dashboard metrics and summary statistics

- Added new summary fields: variance, 5th percentile, 95th percentile, VaR (95%), and expected shortfall (95%) to the dashboard.
- Updated the display logic for summary metrics to handle non-finite values gracefully.
- Modified the chart rendering to include additional percentile points and tail risk metrics in tooltips.

test: Introduce unit tests for consumption, costs, and other modules

- Created a comprehensive test suite for consumption, costs, equipment, maintenance, production, reporting, and simulation modules.
- Implemented fixtures for database setup and teardown using an in-memory SQLite database for isolated testing.
- Added tests for creating, listing, and validating various entities, ensuring proper error handling and response validation.

refactor: Consolidate parameter tests and remove deprecated files

- Merged parameter-related tests into a new test file for better organization and clarity.
- Removed the old parameter test file that was no longer in use.
- Improved test coverage for parameter creation, listing, and validation scenarios.

fix: Ensure proper validation and error handling in API endpoints

- Added validation to reject negative amounts in consumption and production records.
- Implemented checks to prevent duplicate scenario creation and ensure proper error messages are returned.
- Enhanced reporting endpoint tests to validate input formats and expected outputs.

README.md

@@ -71,20 +71,21 @@ uvicorn main:app --reload
 - **API base URL**: `http://localhost:8000/api`
 - **Key routes**:
   - `POST /api/scenarios/` create scenarios
-  - `POST /api/parameters/` manage process parameters
+  - `POST /api/parameters/` manage process parameters; payload supports optional `distribution_id` or inline `distribution_type`/`distribution_parameters` fields for simulation metadata
   - `POST /api/costs/capex` and `POST /api/costs/opex` capture project costs
   - `POST /api/consumption/` add consumption entries
   - `POST /api/production/` register production output
   - `POST /api/equipment/` create equipment records
   - `POST /api/maintenance/` log maintenance events
-  - `POST /api/reporting/summary` aggregate simulation results
+  - `POST /api/reporting/summary` aggregate simulation results, returning count, mean/median, min/max, standard deviation, variance, percentile bands (5/10/90/95), value-at-risk (95%) and expected shortfall (95%)
 
 ### Dashboard Preview
 
-1. Start the FastAPI server and navigate to `/dashboard` (served by `templates/Dashboard.html`).
+1. Start the FastAPI server and navigate to `/ui/dashboard` (ensure `routes/ui.py` exposes this template or add a router that serves `templates/Dashboard.html`).
 2. Use the "Load Sample Data" button to populate the JSON textarea with demo results.
-3. Select "Refresh Dashboard" to view calculated statistics and a distribution chart sourced from `/api/reporting/summary`.
-4. Paste your own simulation outputs (array of objects containing a numeric `result` property) to visualize custom runs.
+3. Select "Refresh Dashboard" to post the dataset to `/api/reporting/summary` and render the returned statistics and distribution chart.
+4. Paste your own simulation outputs (array of objects containing a numeric `result` property) to visualize custom runs; the endpoint expects the same schema used by the reporting service.
+5. If the summary endpoint is unavailable, the dashboard displays an inline error—refresh once the API is reachable.
 
 ## Testing
 
@@ -96,6 +97,13 @@ To execute the unit test suite:
 pytest
 ```
 
+### Coverage Snapshot (2025-10-20)
+
+- `pytest --cov=. --cov-report=term-missing` reports **95%** overall coverage across the project.
+- Lower coverage hotspots to target next: `services/simulation.py` (79%), `middleware/validation.py` (78%), `routes/ui.py` (82%), and several API routers around lines 12-22 that create database sessions only.
+- Deprecation cleanup migrated routes to Pydantic v2 patterns (`model_config = ConfigDict(...)`, `model_dump()`) and updated SQLAlchemy's `declarative_base`; reran `pytest` to confirm the suite passes without warnings.
+- Coverage for route-heavy modules is primarily limited by error paths (e.g., bad request branches) that still need explicit tests.
+
 ## Database Objects
 
 The database is composed of several tables that store different types of information.