docs: regenerate HTML/WASM docs after adding 13_config module

docs_v1.0/doc_wasm/modules/02_health.md

@@ -128,8 +128,48 @@ curl "$API/health/detailed" | jq '{status, services, resources: {cpu: .resources
 | `pipeline.scripts_integrity` | object | SHA256 checksum verification results |
 | `schema.ok` | boolean | All required migrations applied |
 | `identities.synced` | boolean | Identity file count matches DB count |
+| `config` | object | Runtime toggle states (cache, auto-pipeline, watcher) |
 | `integrations.tmdb` | object | TMDB API key config and reachability |
 
+### `GET /health/consistency`
+
+**Auth**: Required
+**Scope**: system-level
+
+Scans the database for data consistency issues. Reports anomalies without modifying any data.
+
+#### Example
+
+```bash
+curl -s "$API/health/consistency" -H "X-API-Key: $KEY" | jq '.checks[] | {check, severity, count}'
+```
+
+#### Response (200)
+
+```json
+{
+  "status": "degraded",
+  "checked_at": "2026-05-18T17:30:00Z",
+  "checks": [
+    {
+      "check": "stale_processing",
+      "severity": "warn",
+      "count": 3,
+      "files": [
+        {"file_name": "video.mp4", "file_uuid": "abc123...", "status": "processing", "detail": "job_id is null"}
+      ]
+    }
+  ]
+}
+```
+
+| Check | Description | Severity |
+|-------|-------------|---------|
+| `stale_processing` | Status=processing but job_id is null | `warn` |
+| `orphaned_processing` | Status=processing but no active monitor_job | `warn` |
+| `processing_job_done` | Status=processing but job already completed | `warn` |
+| `unregistered_with_uuid` | Status=unregistered but row still in DB (migration residue) | `info` |
+
 #### Health status rules
 
 | Condition | status |

docs_v1.0/doc_wasm/modules/03_register.md

@@ -11,7 +11,8 @@
 
 Register a video file for processing. Returns the file's metadata and UUID.
 
-**New in v0.1.2**: Registration now **automatically triggers the processing pipeline** — no need to call `POST /api/v1/file/:file_uuid/process` separately. The system will:
+Registration can **automatically trigger the processing pipeline** if the
+[auto-pipeline toggle](/api/v1/config/auto-pipeline) is enabled (disabled by default). The system will:
 1. Register the file and run ffprobe
 2. Auto-run offline TMDb probe (reads local identity files, no API calls)
 3. Create a monitor job for the worker

docs_v1.0/doc_wasm/modules/10_pipeline.md

@@ -105,6 +105,14 @@ curl "http://localhost:3003/api/v1/stats/ingestion-status/bd80fec9c42afb0307eb28
 
 See [13_config.md](13_config.md) for runtime configuration endpoints:
 
+| Endpoint | Description |
+|----------|-------------|
+| `POST /api/v1/config/cache` | Toggle Redis cache |
+| `POST /api/v1/config/auto-pipeline` | Toggle auto-pipeline on register |
+| `POST /api/v1/config/watcher-auto-register` | Toggle watcher auto-register |
+
+### Unmounted Routes
+
 The following routes are defined in source code but are **NOT** currently mounted in the router:
 
 | Endpoint | Source file |