docs(conflicts,queue): Beam WO5 batch — 13 endpoints backfilled, registry pinned

Beam added frontmatter + provenance + labeled examples to the 7 conflict and
6 queue docs, fixing real field drift on the way (resolve response keys,
bulk result shape, dismiss-all deleted count, queue stats counts).

Claude registry verification found TWO Beam catches of Claude's own draft:
- queue routes use :device_id / :item_id params (registry first draft said :id)
- resolve_conflict DOES take a body (ConflictResolutionRequest) — registry
  first draft said nil
Both fixed; gate then surfaced one real Beam defect: example-request used a
nonexistent "resolution" field in resolve + bulk-resolve (real contract:
winner=<source|manual> with required manual_data for manual; strategy=
most_recent|highest_progress|manual). Fixed in the docs.

Pinned by type: ConflictListResponse, ConflictDetailResponse,
ConflictResolveResponse, BulkResolveRequest/Response, QueueStatsResponse,
ConflictResolutionRequest. dismiss-all deleted is an int count.

docs/developer/api/conflicts/bulk_resolve_conflicts.md

@@ -1,3 +1,11 @@
+---
+method: POST
+path: /api/conflicts/bulk-resolve
+auth: jwt
+area: conflicts
+---
+<!-- source: internal/handlers/conflicts.go:594 ConflictHandler.BulkResolveConflicts -->
+
 # Bulk Resolve Conflicts
 
 Resolve multiple conflicts at once using a specified strategy.
@@ -15,23 +23,24 @@ Resolve multiple conflicts at once using a specified strategy.
 
 ### Example Request
 
-```json
+```json example-request
 {
   "conflict_ids": [
     "550e8400-e29b-41d4-a716-446655440000",
     "660e8400-e29b-41d4-a716-446655440001"
   ],
-  "resolution": "highest_progress"
+  "strategy": "highest_progress"
 }
 ```
 
 ## Response (200 OK)
 
-```json
+```json example-response
 {
-  "message": "Conflicts resolved successfully",
-  "resolved_count": 2,
-  "failed_count": 0
+  "results": [],
+  "total": 2,
+  "success": 2,
+  "failed": 0
 }
 ```