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/collections/scenarios/Test Collection Rules.yml

@@ -8,60 +8,11 @@ http:
   auth: inherit
   body:
     type: json
-    jsonBody: "{\n    \"rules\": [\n      {\n        \"field\": \"genre\",\n     \
-      \   \"operator\": \"equals\",\n        \"value\": \"Science Fiction\""
+    data: "{\n    \"rules\": [\n      {\n        \"field\": \"genre\",\n        \"operator\": \"equals\",\n        \"value\": \"Science Fiction\""
   headers:
   - key: Content-Type
     value: application/json
   - key: Authorization
     value: Bearer {{authToken
-
-docs: |-
-  ## Test Collection Rules
-  
-    Tests collection rules against the library to see which books match, without creating a collection. Useful for previewing what books would be included in a collection with specific rules.
-  
-    **Method:** POST
-  
-    **Endpoint:** /api/collections/test-rules
-  
-    **Authentication:** Bearer token
-  
-    **Request Body:**
-    - `rules` (array): Array of rule objects to test
-      - `field` (string): Field to test (genre, author, copyright_year, tags, etc.)
-      - `operator` (string): Comparison operator
-        - `equals`: Exact match
-        - `contains`: Contains substring (for text fields)
-        - `greater_than`: Greater than (for numeric fields)
-        - `less_than`: Less than (for numeric fields)
-        - `not_equals`: Not equal to
-        - `starts_with`: Starts with
-        - `ends_with`: Ends with
-        - `is_empty`: Field is empty or null
-        - `is_not_empty`: Field is not empty and not null
-      - `value` (string): Value to compare against (not required for is_empty/is_not_empty)
-  
-    **Response:**
-    - `matches` (array): Array of matching books
-      - `id` (string): Book UUID
-      - `title` (string): Book title
-      - `author` (string): Book author
-      - `genre` (string): Book genre
-      - Additional book metadata
-    - `total` (number): Total number of matching books
-  
-    **Status Codes:**
-    - 200: Success - returns matching books
-    - 400: Invalid request (empty rules array, invalid field/operator)
-    - 401: Unauthorized
-    - 500: Internal server error
-  
-    **Example Request:**
-    ```json
-    {
-      "rules": [
-        {
-          "field": "genre",
-          "operator": "equals",
-          "value": "Science Fiction"
+docs: "## Test Collection Rules\n\n  Tests collection rules against the library to see which books match, without creating a collection. Useful for previewing what books would be included in a collection with specific rules.\n\n  **Method:** POST\n\n  **Endpoint:** /api/collections/test-rules\n\n  **Authentication:** Bearer token\n\n  **Request Body:**\n  - `rules` (array): Array of rule objects to test\n    - `field` (string): Field to test (genre, author, copyright_year, tags, etc.)\n    - `operator` (string): Comparison operator\n      - `equals`: Exact match\n      - `contains`: Contains substring (for text fields)\n      - `greater_than`: Greater than (for numeric fields)\n      - `less_than`: Less than (for numeric fields)\n      - `not_equals`: Not equal to\n      - `starts_with`: Starts with\n      - `ends_with`: Ends with\n      - `is_empty`: Field is empty or null\n      - `is_not_empty`: Field is not empty and not null\n    - `value` (string): Value to compare against (not required\
+  \ for is_empty/is_not_empty)\n\n  **Response:**\n  - `matches` (array): Array of matching books\n    - `id` (string): Book UUID\n    - `title` (string): Book title\n    - `author` (string): Book author\n    - `genre` (string): Book genre\n    - Additional book metadata\n  - `total` (number): Total number of matching books\n\n  **Status Codes:**\n  - 200: Success - returns matching books\n  - 400: Invalid request (empty rules array, invalid field/operator)\n  - 401: Unauthorized\n  - 500: Internal server error\n\n  **Example Request:**\n  ```json\n  {\n    \"rules\": [\n      {\n        \"field\": \"genre\",\n        \"operator\": \"equals\",\n        \"value\": \"Science Fiction\""