[BUG] Self-hosted steel-browser-api fails with "Failed to generate a consistent fingerprint after 10 attempts"

**Describe the bug** Self-hosted Steel containers fail to start due to fingerprint generation errors. The browser never launches and the container becomes unhealthy. This happens with both `steel-browser` and `steel-browser-api` images.

Live View WebSocket URL omits active session ID

# Live View WebSocket URL omits active session ID

Self-hosted `/v1/sessions` does not implement the SDK session timeout field

The Steel SDKs expose a session timeout when creating a browser session. For example, the Node SDK uses:

[BUG] Failed to launch the browser process in Docker due to dbus connection failure

Issue tracker is **ONLY** used for reporting bugs. New features should be discussed in our [Discord server](https://discord.gg/steel-dev).

feat: overhaul the ui and live view streaming

## Summary

feat(docker): run API image under tini init

Closes #378

[FEATURE] Add per-session network usage metrics

**Is your feature request related to a problem? Please describe.**

WebGL renderer is always SwiftShader, with no session option to change it

## Summary

[BUG] Logs tab renders blank: UI does JSON.parse(f.text) but records carry the payload nested under the record type

## Describe the bug

[BUG] Caller-supplied userDataDir is ignored — every session with a custom profile path shares one directory

### Describe the bug

DevTools inspector redirect broken with USE_SSL=true (ws= param keeps wss:// scheme)

Self-hosted steel-browser behind a TLS-terminating proxy, with DOMAIN=<public-host> and USE_SSL=true.

recordCanvas: true never captures canvas frames on pages that create their context before document_idle

## Summary

Session viewer UI has no route/URL param wiring — always shows sessions[0], not the requested session

## What happened

[BUG] Live session details serialize browserVersion as "[object Object]"

### What I was trying to do

[BUG] Proxy byte counters remain zero after routed session traffic

### What I was trying to do

[BUG] Requested dimensions leave browser-visible screen at 800x600

### What I was trying to do

[BUG] Releasing or rapidly relaunching a session can terminate the API with TargetCloseError

### What I was trying to do

fix(cdp): eliminate dedicated worker network capture race

## Summary

feat: update chrome browser support for 146 + resolve extension installtion

## Description

feat: log browser interactions

## Description

[FEATURE] Support more than one chrome process per container

**Is your feature request related to a problem? Please describe.** I'm frustrated that the product is so close to what I need but missing one simple thing: **All sessions are connected to the same browser when running in a docker container!**

Cluster support and request routing to correct node (session affinity)

Support for clustering?