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/Initiate Device Registration.yml

@@ -8,32 +8,5 @@ http:
   auth: none
   body:
     type: json
-    jsonBody: "{\n    \"device_name\": \"My Kindle Paperwhite\",\n    \"device_type\"\
-      : \"koreader\",\n    \"device_identifier\": \"kindle-pw5-hardware-id-12345\""
-
-docs: |-
-  ## Initiate Device Registration
-  
-    Initiates a new device registration request that requires admin approval.
-  
-    **Method:** POST
-  
-    **Endpoint:** /api/devices/register
-  
-    **Authentication:** None (open endpoint)
-  
-    **Request Body:**
-    - `device_name` (string, required): Human-readable device name (max 100 chars)
-    - `device_type` (string, required): Device type (kobo, koreader, kindle, etc.)
-    - `device_identifier` (string, required): Unique hardware ID (max 200 chars)
-  
-    **Response:**
-    - `registration_id` (string): Unique registration request ID
-    - `status` (string): Initial status (pending)
-    - `expires_at` (string): Expiration timestamp (usually 24 hours)
-    - `message` (string): Informational message
-  
-    **Status Codes:**
-    - 201: Registration initiated
-    - 400: Invalid request
-    - 409: Device already registered
+    data: "{\n    \"device_name\": \"My Kindle Paperwhite\",\n    \"device_type\": \"koreader\",\n    \"device_identifier\": \"kindle-pw5-hardware-id-12345\""
+docs: "## Initiate Device Registration\n\n  Initiates a new device registration request that requires admin approval.\n\n  **Method:** POST\n\n  **Endpoint:** /api/devices/register\n\n  **Authentication:** None (open endpoint)\n\n  **Request Body:**\n  - `device_name` (string, required): Human-readable device name (max 100 chars)\n  - `device_type` (string, required): Device type (kobo, koreader, kindle, etc.)\n  - `device_identifier` (string, required): Unique hardware ID (max 200 chars)\n\n  **Response:**\n  - `registration_id` (string): Unique registration request ID\n  - `status` (string): Initial status (pending)\n  - `expires_at` (string): Expiration timestamp (usually 24 hours)\n  - `message` (string): Informational message\n\n  **Status Codes:**\n  - 201: Registration initiated\n  - 400: Invalid request\n  - 409: Device already registered"