fix(runner): retain unlabeled prefixes and complete tool JSON

Retain the published message identity when a provider begins labeling deltas. Preserve the original full-prefix oracle, separate subsequent message boundaries, and keep unknown JSON result fields inspectable. Record native, server and browser proof and the pending release gates.

Co-Authored-By: Paperclip <noreply@paperclip.ing>

packages/paperclip-runner/docs/hermes.md

@@ -108,7 +108,10 @@ extend the task's execution deadline.
 - Assistant message identity v2 includes the provider message and provider turn.
   A final snapshot replaces only its own deltas, retaining preceding commentary
   and steered messages. Providers without message IDs retain the original
-  identity; existing PRP v1 events replay unchanged. This is an identity change
+  identity. If a provider first supplies an ID after an unlabelled prefix,
+  that prefix and the continuation retain one item identity and one final
+  snapshot. A later distinct native message gets its own item. Existing PRP v1
+  events replay unchanged. This is an identity change
   within the current event contract, not a new wire field or transcript rewrite.
 - Native questions publish a 65,536-character limit for text and custom
   answers. The form, canonical response validation and bridge count UTF-16