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/Get Analytics Tests.yml

@@ -2,95 +2,16 @@ info:
   name: Get Analytics Tests
   type: http
   seq: 7
-
 http:
   method: POST
   url: '{{base_url}}/api/sync/kobo/{{kobo_device_token}}/v1/analytics/gettests'
   auth: inherit
   headers:
-    - key: Content-Type
-      value: application/json
+  - key: Content-Type
+    value: application/json
   body:
     type: json
-    json:
-      platform: android
-      firmware_version: 4.30.19023
-
-docs: |-
-  ## Get Kobo Analytics Tests
-
-  Retrieves A/B testing configuration and feature flags for Kobo device.
-
-  **Method:** POST
-
-  **Endpoint:** /api/sync/kobo/v1/analytics/gettests
-
-  **Authentication:** Bearer token
-
-  **Request Body:**
-  - `platform` (string): Device platform
-    - `android`: Kobo Android app
-    - `kobo`: Native Kobo firmware
-  - `firmware_version` (string): Firmware version (e.g., "4.30.19023")
-  - `device_model` (string, optional): Device model identifier
-  - `locale` (string, optional): Device locale (e.g., "en_US")
-
-  **Response:**
-  - `tests` (array): Active A/B tests
-    - `test_name` (string): Test identifier
-    - `variant` (string): Assigned variant (A, B, C, etc.)
-    - `enabled` (boolean): Whether test is active
-    - `parameters` (object): Test-specific parameters
-  - `features` (object): Feature flags
-    - `feature_name` (boolean/string): Feature state
-  - `configuration` (object): Device configuration
-    - `sync_interval_minutes` (integer): Recommended sync frequency
-    - `batch_size` (integer): Max items per batch sync
-    - `timeout_seconds` (integer): Request timeout
-  - `version` (string): Configuration version
-
-  **Status Codes:**
-  - 200: Success
-  - 401: Unauthorized
-  - 400: Invalid request parameters
-
-  **Analytics Testing Purpose:**
-  - Kobo uses A/B testing for UX features
-  - Feature flags for gradual rollout
-  - Performance monitoring configuration
-  - Sync behavior optimization
-  - Device-specific tuning
-
-  **Common Tests:**
-  - Sync frequency optimization
-  - UI/UX variations
-  - Network usage patterns
-  - Battery life improvements
-  - Feature set variations by model
-
-  **Feature Flags:**
-  - New sync features
-  - Beta functionality
-  - Platform-specific capabilities
-  - Experimental features
-
-  **Configuration Parameters:**
-  - Optimal sync intervals for device
-  - Batch size limits based on device capabilities
-  - Timeout values for network conditions
-  - Retry logic configuration
-  - Cache policy settings
-
-  **Usage:**
-  - Called during device initialization
-  - Refreshed daily or weekly
-  - Cached on device
-  - Affects sync behavior
-  - Can be overridden by server
-
-  **Use Cases:**
-  - Device initialization
-  - Feature rollout testing
-  - Performance optimization
-  - UX experiment participation
-  - Configuration management
+    data: "{\n  \"platform\": \"android\",\n  \"firmware_version\": \"4.30.19023\"\n}"
+docs: "## Get Kobo Analytics Tests\n\nRetrieves A/B testing configuration and feature flags for Kobo device.\n\n**Method:** POST\n\n**Endpoint:** /api/sync/kobo/v1/analytics/gettests\n\n**Authentication:** Bearer token\n\n**Request Body:**\n- `platform` (string): Device platform\n  - `android`: Kobo Android app\n  - `kobo`: Native Kobo firmware\n- `firmware_version` (string): Firmware version (e.g., \"4.30.19023\")\n- `device_model` (string, optional): Device model identifier\n- `locale` (string, optional): Device locale (e.g., \"en_US\")\n\n**Response:**\n- `tests` (array): Active A/B tests\n  - `test_name` (string): Test identifier\n  - `variant` (string): Assigned variant (A, B, C, etc.)\n  - `enabled` (boolean): Whether test is active\n  - `parameters` (object): Test-specific parameters\n- `features` (object): Feature flags\n  - `feature_name` (boolean/string): Feature state\n- `configuration` (object): Device configuration\n  - `sync_interval_minutes` (integer): Recommended sync frequency\n\
+  \  - `batch_size` (integer): Max items per batch sync\n  - `timeout_seconds` (integer): Request timeout\n- `version` (string): Configuration version\n\n**Status Codes:**\n- 200: Success\n- 401: Unauthorized\n- 400: Invalid request parameters\n\n**Analytics Testing Purpose:**\n- Kobo uses A/B testing for UX features\n- Feature flags for gradual rollout\n- Performance monitoring configuration\n- Sync behavior optimization\n- Device-specific tuning\n\n**Common Tests:**\n- Sync frequency optimization\n- UI/UX variations\n- Network usage patterns\n- Battery life improvements\n- Feature set variations by model\n\n**Feature Flags:**\n- New sync features\n- Beta functionality\n- Platform-specific capabilities\n- Experimental features\n\n**Configuration Parameters:**\n- Optimal sync intervals for device\n- Batch size limits based on device capabilities\n- Timeout values for network conditions\n- Retry logic configuration\n- Cache policy settings\n\n**Usage:**\n- Called during device initialization\n\
+  - Refreshed daily or weekly\n- Cached on device\n- Affects sync behavior\n- Can be overridden by server\n\n**Use Cases:**\n- Device initialization\n- Feature rollout testing\n- Performance optimization\n- UX experiment participation\n- Configuration management"