feat(backend): Performance Improvements and ToolStack maturation

### OmniRoute Version

*

### Installation Method

npm (global)

### Operating System

Windows

### OS Version

*

### Node.js Version

*

### Provider(s) Involved

*

### Model(s) Involved

*

### Client Tool

*

### Description

Unbearable Frontend load times and bloat, similar issues for backend

Request a rewrite \ migr to a lighter solu or more optimized production builds on same frameworks.

Routing layer itself can be noted to similarly be unsuited for our loadscales of ~500-1k Req per Minute with ~ 100-200 active concurrent agent sessions acr two host devices.

Willing to do my own audit and ADR proposals.

### Steps to Reproduce

Use the system via UI or API

### Expected Behavior

Near instant page load and interaction times, near "at cost" routing times.

### Actual Behavior

On slight system load 5s to 2 minute long load or interaction times. API responses times +5s to +45s average depending on load.

### Test Impact

Needs a new e2e test

### Error Logs / Output

```shell

```

### Screenshots

_No response_

### Additional Context

_No response_

### Validation Plan

_No response_

No files, failing tests, or code entry points are identified. Start by reproducing the slow UI and API behavior under load, then review the proposed audit and ADRs; completion would require an agreed optimization approach and a new end-to-end test validating near-instant interactions and improved routing/API response times.

Written by the indexing model from the issue text.