fix(bruno): convert drifted body keys to body.data — CLI scenario runs now carry bodies

Follow-up to the sweep route audit, correcting its diagnosis: the CLI
DOES read .yml bodies — via OpenCollection's `body.data` string form
(the NewDevDBSetup script always worked because it used it). The
failing scenario POSTs used `body.json` (structured) / `body.jsonBody`
(string) — keys the CLI silently ignores, sending Content-Length: 0
with form-urlencoded content-type, so every server bind failed.

- 81 bodies converted to data-form (json maps serialized; jsonBody
  strings kept verbatim, {{vars}} intact).
- 6 pre-existing TRUNCATED payloads repaired: the original generator
  cut bodies at the first {{var}} (every SHA-256-identified scenario
  plus Sync Progress/Sync Bookmarks shipped mid-JSON and 400'd from
  day one). Rewritten whole, faithful to each file's documented
  purpose; book_sha256/book_uuid added to the environment.
- environments: opds_base_url correction from the sweep retained.

Verified live against the rebuilt dev container: the full koreader
scenario tree runs green through `bru run` — 14/14 (202s across
immediate/checkpoint/SHA-256 progress, 200s bookmarks, highlights,
notes; SHA-256 book identification exercised against a real
file_sha256).

bruno/devices/scenarios/Create Device File Alias.yml

@@ -8,48 +8,12 @@ http:
   auth: inherit
   body:
     type: json
-    jsonBody: "{\n    \"file_path\": \"/mnt/sd/books/my-book.kepub.epub\",\n    \"\
-      media_item_id\": \"{{media_item_id"
+    data: "{\n    \"file_path\": \"/mnt/sd/books/my-book.kepub.epub\",\n    \"media_item_id\": \"{{media_item_id"
   headers:
   - key: Content-Type
     value: application/json
 runtime:
   scripts:
   - type: tests
-    code: "test_create_device_file_alias_success(status, headers, body) {\n    if\
-      \ (status !== 201 && status !== 200) {\n      throw new Error(\"Expected status\
-      \ 201 or 200, got \" + status);"
-
-docs: |-
-  ## Create Device File Alias
-  
-    Creates a new file alias for a device. File aliases map device-specific file paths to media items.
-  
-    **Method:** POST
-  
-    **Endpoint:** /api/devices/:id/file-aliases
-  
-    **Authentication:** Required (Bearer token)
-  
-    **Path Parameters:**
-    - `id` (string, required): Device UUID
-  
-    **Request Body:**
-    - `file_path` (string, required): Device-specific file path
-    - `media_item_id` (string, required): Media item UUID to link to
-  
-    **Response:** Created file alias object
-    - `id` (string): Alias UUID
-    - `device_id` (string): Device UUID
-    - `file_path` (string): Device-specific file path
-    - `media_item_id` (string): Associated media item UUID
-    - `created_at` (string): Creation timestamp
-    - `updated_at` (string): Last update timestamp
-  
-    **Status Codes:**
-    - 201: Created
-    - 200: Success
-    - 400: Invalid request body
-    - 401: Unauthorized
-    - 404: Device not found
-    - 500: Internal server error
+    code: "test_create_device_file_alias_success(status, headers, body) {\n    if (status !== 201 && status !== 200) {\n      throw new Error(\"Expected status 201 or 200, got \" + status);"
+docs: "## Create Device File Alias\n\n  Creates a new file alias for a device. File aliases map device-specific file paths to media items.\n\n  **Method:** POST\n\n  **Endpoint:** /api/devices/:id/file-aliases\n\n  **Authentication:** Required (Bearer token)\n\n  **Path Parameters:**\n  - `id` (string, required): Device UUID\n\n  **Request Body:**\n  - `file_path` (string, required): Device-specific file path\n  - `media_item_id` (string, required): Media item UUID to link to\n\n  **Response:** Created file alias object\n  - `id` (string): Alias UUID\n  - `device_id` (string): Device UUID\n  - `file_path` (string): Device-specific file path\n  - `media_item_id` (string): Associated media item UUID\n  - `created_at` (string): Creation timestamp\n  - `updated_at` (string): Last update timestamp\n\n  **Status Codes:**\n  - 201: Created\n  - 200: Success\n  - 400: Invalid request body\n  - 401: Unauthorized\n  - 404: Device not found\n  - 500: Internal server error"