chore: Update specific proxy features to reference editor UI options

Author: sparkison

docs/proxy/failover.md

@@ -141,6 +141,40 @@ When [Sticky Sessions](./sticky-sessions.md) are enabled, the proxy locks to a s
 3. If the original URL also fails, trigger failover to the next failover URL
 4. The sticky session locks to the new provider's backend
 
+## Advanced Failover (M3U Editor)
+
+The M3U Editor adds a higher-level **failover resolver** on top of the proxy's built-in URL cycling. When enabled, the proxy calls back to the editor to determine which playlist to use next, taking into account playlist stream limits and health state.
+
+Configure this under **Settings → Preferences → Proxy** in the editor.
+
+### Failover Resolver
+
+| Setting | Description |
+|---------|-------------|
+| **Enable advanced failover logic** | Proxy calls the editor to resolve the next failover source based on playlist capacity |
+| **Resolver URL** | The URL the proxy uses to reach the editor (e.g. `http://m3u-editor:36400`). Must be reachable from the proxy container |
+
+When enabled, the proxy sends a request to the editor's resolver endpoint during failover, and the editor returns the best available backup source — respecting stream limits, marked-invalid playlists, and provider health.
+
+### Fail Conditions
+
+| Setting | Description |
+|---------|-------------|
+| **Enable playlist fail conditions** | Mark playlists as temporarily unavailable when specific HTTP errors are returned by the provider |
+| **HTTP status codes** | Codes that trigger an invalid state (e.g. `403`, `404`, `502`, `503`) |
+| **Invalid timeout (minutes)** | How long a playlist stays invalid before being retried. Default: 5 minutes |
+| **Clear failed playlists** | Immediately un-marks all playlists currently flagged as invalid |
+
+This is particularly useful when providers return `403` or `503` errors under load — the editor will temporarily route traffic away from that source without requiring a manual fix.
+
+### Stream Limit Handling
+
+| Setting | Description |
+|---------|-------------|
+| **Stop oldest stream when limit reached** | When a playlist's stream limit is hit, automatically stops the oldest active stream to free capacity for the new request. Enables instant channel switching on single-connection providers |
+
+---
+
 ## Before vs After Failover
 
 ### Without failover

docs/proxy/sticky-sessions.md

@@ -34,17 +34,19 @@ Player: stream jumped, must reload
 
 With sticky sessions enabled, after the first redirect the proxy locks to that backend for all subsequent requests, ensuring monotonic sequence progression.
 
-## Configuration
+## Enabling Sticky Sessions
 
-### Global setting
+There are three ways to enable sticky sessions, from most specific to most broad:
 
-```bash
-USE_STICKY_SESSION=true
-```
+### Per-Playlist (M3U Editor UI)
 
-Default is `false`.
+Open a playlist in the editor and go to the **Proxy Settings** section. Toggle **Enable Sticky Session Handler** on.
 
-### Per-stream override
+This applies to all channels from that playlist. It is the recommended approach — you can target only the providers that need it without affecting others.
+
+### Per-Stream (Proxy API)
+
+When calling the proxy API directly, pass `use_sticky_session: true` on the stream creation request:
 
 ```bash
 curl -X POST "http://localhost:8085/streams" \
@@ -56,7 +58,15 @@ curl -X POST "http://localhost:8085/streams" \
   }'
 ```
 
-Per-stream settings override the global configuration.
+### Globally (Environment Variable)
+
+Enable for all streams:
+
+```bash
+USE_STICKY_SESSION=true
+```
+
+Default is `false`. Per-stream and per-playlist settings override the global configuration.
 
 ## When to Enable
 

docs/proxy/strict-live-ts.md

@@ -54,16 +54,23 @@ Monitors upstream data flow. If no data arrives for more than 2 seconds (configu
 
 HEAD requests for live TS streams return immediately without hitting the upstream provider. This avoids redundant connections that can interfere with live stream state.
 
-## Quick Start
+## Enabling Strict Live TS
 
-### Enable globally (all live TS streams)
+There are three ways to enable this feature, from most specific to most broad:
 
-```bash
-# .env or docker-compose environment
-STRICT_LIVE_TS=true
-```
+### Per-Playlist (M3U Editor UI)
+
+Open a playlist in the editor and go to the **Proxy Settings** section. Toggle **Enable Strict Live TS Handling** on.
+
+This applies to all channels from that playlist. It is the recommended approach for most users — you can target specific providers without affecting others.
+
+:::note
+The **Enable Strict Live TS Handling** option is only relevant when the playlist is **not** using a transcoding profile. If a stream profile is assigned to the playlist, transcoding takes over and strict TS handling is bypassed.
+:::
+
+### Per-Stream (Proxy API)
 
-### Enable per stream (via API)
+When calling the proxy API directly, pass `strict_live_ts: true` on the stream creation request:
 
 ```bash
 curl -X POST "http://localhost:8085/streams" \
@@ -76,7 +83,16 @@ curl -X POST "http://localhost:8085/streams" \
   }'
 ```
 
-Per-stream configuration overrides the global setting for that stream.
+### Globally (Environment Variable)
+
+Enable for all live TS streams across every playlist:
+
+```bash
+# .env or docker-compose environment
+STRICT_LIVE_TS=true
+```
+
+Per-stream and per-playlist settings override the global setting for that specific stream.
 
 ## Configuration