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/Register Web Device.yml

@@ -2,48 +2,62 @@ info:
   name: Register Web Device
   type: http
   seq: 3
-
 http:
   method: POST
   url: '{{base_url}}/api/devices/register'
   auth: none
   headers:
-    - key: Content-Type
-      value: application/json
+  - key: Content-Type
+    value: application/json
   body:
     type: json
-    json:
-      device_name: Chrome Browser
-      device_type: web
-      device_identifier: web-client-abc123
+    data: "{\n  \"device_name\": \"Chrome Browser\",\n  \"device_type\": \"web\",\n  \"device_identifier\": \"web-client-abc123\"\n}"
+docs: '## Register Web Device
 
-docs: |-
-  ## Register Web Device
 
   Registers a web browser client for reading progress sync.
 
+
   **Method:** POST
 
+
   **Endpoint:** /api/devices/register
 
+
   **Authentication:** None (public endpoint)
 
+
   **Request Body:**
+
   - `device_name` (string): Browser identification (e.g., "Chrome Browser")
+
   - `device_type` (string): Must be `web`
+
   - `device_identifier` (string): Unique browser/client identifier
 
+
   **Response:**
+
   - `registration_id` (string): UUID for tracking
+
   - `status` (string): `pending` or `auto-approved`
+
   - `message` (string): Status message
 
+
   **Status Codes:**
+
   - 201: Registration successful
+
   - 400: Invalid request
 
+
   **Web Device Notes:**
+
   - Web devices use localStorage for device identification
+
   - May be auto-approved without admin intervention
+
   - Used for browser-based reading progress tracking
-  - Supports manual progress updates, highlights, and notes
+
+  - Supports manual progress updates, highlights, and notes'