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/kobo/scenarios/Sync Single Bookmark.yml

@@ -2,91 +2,18 @@ info:
   name: Sync Single Bookmark
   type: http
   seq: 5
-
 http:
   method: POST
   url: '{{base_url}}/api/sync/kobo/{{kobo_device_token}}/bookmark'
   auth: inherit
   headers:
-    - key: Content-Type
-      value: application/json
-    - key: x-kobo-device
-      value: '{"DeviceId":"{{kobo_device_id}}","Model":"Kobo Clara"}'
+  - key: Content-Type
+    value: application/json
+  - key: x-kobo-device
+    value: '{"DeviceId":"{{kobo_device_id}}","Model":"Kobo Clara"}'
   body:
     type: json
-    json:
-      ContentId: book-uuid
-      BookmarkText: Bookmarked passage
-      BookmarkType: annotation
-      BookmarkTitle: Chapter 3
-
-docs: |-
-  ## Sync Single Bookmark
-
-  Synchronizes an individual bookmark/highlight from Kobo device.
-
-  **Method:** POST
-
-  **Endpoint:** /api/sync/kobo/bookmark
-
-  **Authentication:** Bearer token
-
-  **Headers:**
-  - `Authorization`: Bearer {{kobo_device_token}}
-  - `x-kobo-device`: Device information JSON
-
-  **Request Body:**
-  - `ContentId` (string): Book UUID
-  - `BookmarkText` (string): Highlighted text or bookmark description
-  - `BookmarkType` (string): Type of bookmark
-    - `annotation`: Highlighted text passage
-    - `note`: Personal note
-    - `bookmark`: Location marker
-  - `BookmarkTitle` (string): Reference title (e.g., chapter name)
-  - `ChapterID` (string, optional): Chapter identifier
-  - `DateCreated` (string, optional): ISO 8601 timestamp
-  - `highlight_color` (string, optional): Color name (yellow, green, blue, pink, orange)
-
-  **Response:**
-  - `id` (string): Server bookmark ID
-  - `ContentId` (string): Associated book UUID
-  - `status` (string): `created`, `updated`, `skipped` (duplicate)
-  - `timestamp` (string): Server timestamp
-  - `url` (string): API URL to retrieve bookmark
-
-  **Status Codes:**
-  - 201: Bookmark created
-  - 200: Bookmark updated (duplicate found)
-  - 409: Duplicate bookmark (unchanged)
-  - 401: Unauthorized
-  - 400: Invalid bookmark data
-
-  **Single Bookmark Sync vs Batch:**
-  - **Single bookmark endpoint:** Real-time, immediate sync
-  - **Batch markup endpoint:** Deferred, periodic sync
-  - Use single when user explicitly creates highlight
-  - Use batch for periodic background sync
-
-  **Kobo Trigger:**
-  - User highlights text → immediate single sync
-  - User adds note → immediate single sync
-  - Device goes online → batch sync of all changes
-
-  **Duplicate Detection:**
-  - Same ContentId + similar BookmarkText + same location
-  - Updates existing if text modified
-  - Skips if identical bookmark exists
-  - Preserves creation date of original
-
-  **Use Cases:**
-  - Real-time highlight sync
-  - Instant note backup
-  - Immediate annotation sharing
-  - Quick single annotation update
-  - Testing annotation sync
-
-  **Notes:**
-  - Much faster than full markup sync
-  - Lower bandwidth usage
-  - Ideal for intermittent connectivity
-  - Can be called multiple times safely
+    data: "{\n  \"ContentId\": \"book-uuid\",\n  \"BookmarkText\": \"Bookmarked passage\",\n  \"BookmarkType\": \"annotation\",\n  \"BookmarkTitle\": \"Chapter 3\"\n}"
+docs: "## Sync Single Bookmark\n\nSynchronizes an individual bookmark/highlight from Kobo device.\n\n**Method:** POST\n\n**Endpoint:** /api/sync/kobo/bookmark\n\n**Authentication:** Bearer token\n\n**Headers:**\n- `Authorization`: Bearer {{kobo_device_token}}\n- `x-kobo-device`: Device information JSON\n\n**Request Body:**\n- `ContentId` (string): Book UUID\n- `BookmarkText` (string): Highlighted text or bookmark description\n- `BookmarkType` (string): Type of bookmark\n  - `annotation`: Highlighted text passage\n  - `note`: Personal note\n  - `bookmark`: Location marker\n- `BookmarkTitle` (string): Reference title (e.g., chapter name)\n- `ChapterID` (string, optional): Chapter identifier\n- `DateCreated` (string, optional): ISO 8601 timestamp\n- `highlight_color` (string, optional): Color name (yellow, green, blue, pink, orange)\n\n**Response:**\n- `id` (string): Server bookmark ID\n- `ContentId` (string): Associated book UUID\n- `status` (string): `created`, `updated`, `skipped` (duplicate)\n\
+  - `timestamp` (string): Server timestamp\n- `url` (string): API URL to retrieve bookmark\n\n**Status Codes:**\n- 201: Bookmark created\n- 200: Bookmark updated (duplicate found)\n- 409: Duplicate bookmark (unchanged)\n- 401: Unauthorized\n- 400: Invalid bookmark data\n\n**Single Bookmark Sync vs Batch:**\n- **Single bookmark endpoint:** Real-time, immediate sync\n- **Batch markup endpoint:** Deferred, periodic sync\n- Use single when user explicitly creates highlight\n- Use batch for periodic background sync\n\n**Kobo Trigger:**\n- User highlights text → immediate single sync\n- User adds note → immediate single sync\n- Device goes online → batch sync of all changes\n\n**Duplicate Detection:**\n- Same ContentId + similar BookmarkText + same location\n- Updates existing if text modified\n- Skips if identical bookmark exists\n- Preserves creation date of original\n\n**Use Cases:**\n- Real-time highlight sync\n- Instant note backup\n- Immediate annotation sharing\n- Quick single annotation\
+  \ update\n- Testing annotation sync\n\n**Notes:**\n- Much faster than full markup sync\n- Lower bandwidth usage\n- Ideal for intermittent connectivity\n- Can be called multiple times safely"