Conversation
Every entry in `events.json` now has an `event_id` that remains stable across saves and content edits. Scripts can reference stored entries without relying on array positions, and tool-call payload IDs retain their separate meaning. Legacy entries receive IDs on load and persist them on the next save. For duplicate IDs, the first occurrence is preserved and later ones get new IDs. JP warns for each replacement and retains duplicated values as load-scoped ambiguity for future reference consumers. Projection preserves the IDs of retained entries. Synthetic summary entries receive ephemeral IDs with no corresponding entry in `events.json`. The CLI help and architecture docs explain this boundary and the manual-edit repair rules. Implements: RFD 097 Signed-off-by: Jean Mertz <git@jeanmertz.com>
Signed-off-by: Jean Mertz <git@jeanmertz.com>
Signed-off-by: Jean Mertz <git@jeanmertz.com>
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
1 participant
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.
Every entry in
events.jsonnow has anevent_idthat remains stable across saves and content edits. Scripts can reference stored entries without relying on array positions, and tool-call payload IDs retain their separate meaning.Legacy entries receive IDs on load and persist them on the next save. For duplicate IDs, the first occurrence is preserved and later ones get new IDs. JP warns for each replacement and retains duplicated values as load-scoped ambiguity for future reference consumers.
Projection preserves the IDs of retained entries. Synthetic summary entries receive ephemeral IDs with no corresponding entry in
events.json. The CLI help and architecture docs explain this boundary and the manual-edit repair rules.Implements: RFD 097