Repository navigation
Fix native Hermes live delta accumulation - #275
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hermes live replies were replacing the accumulated body with the latest fragment. The Bridge sends incremental
chat.delta.message.content, while the native mapper treated every chat delta as a complete snapshot. Map only Hermes fragments to.deltaand keep snapshot identity absent; OpenClaw cumulative snapshots, full finals and SDK text modes retain their existing behavior.Six pure package tests (eight parameterized cases) cover the actual producer-shaped synthetic envelopes, whitespace and Unicode bytes, Direct/Relay mapping, tool boundaries, full/final-only snapshots and source-metadata isolation. Only Hermes raw fragments bypass the cumulative silent-prefix filter, so
NO+RMALremainsNORMAL; full-final, OpenClaw, SDK and subagent filtering stays unchanged. One actual app regression feedsSessionEvents.mapdirectly intoNativeLiveMessagesto verify a single segment's intermediate accumulated body, stable render UUID and corrected whole final replacement. Multi-segment aggregate-final reconciliation remains unchanged and is explicitly not claimed. App report minimum is 315, including a 314-case rejection.Validation:
git diff --checkpassed.653895db: the new package file passed all six methods/eight cases; the actual new mapper-to-consumer app case passed 1/1. The dual-architecture development build compiled all 315 app methods. No full local app suite ran.