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/queue/retry_queue_item.md

@@ -1,3 +1,11 @@
+---
+method: POST
+path: /api/queue/items/:item_id/retry
+auth: jwt
+area: queue
+---
+<!-- source: internal/handlers/queue.go:220 QueueHandler.RetryQueueItem -->
+
 # Retry Queue Item
 
 Retry a failed queue item.
@@ -26,10 +34,13 @@ Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...
 
 ## Response (200 OK)
 
-```json
+```json example-response
 {
-  "message": "Queue item retry initiated",
-  "item_id": "uuid"
+  "message": "item queued for retry",
+  "item_id": "uuid",
+  "status": "pending",
+  "attempts": 0,
+  "max_attempts": 0
 }
 ```