Connect Settings v2 to the existing runtime state - #58
Closed
IMONsergey wants to merge 1 commit into
Closed
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
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.
Superseded before merge by the stricter Settings history-retention contract prepared after this adapter was opened. The first adapter proved the projection shape, but the product contract is changing from
historyEnabled + free-form limit labelto typedOff / Last 1 / Last 5 / Last 10, and explicit destructive clear must clear both recent history and durable Library so the agent cannot immediately reindex deleted data. Rebuild the runtime adapter after that contract lands. Branch retained as implementation reference; no production behavior was changed.