Repository navigation
Add Ripple content history and bounded rollout - #26
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.
Ripple’s footer opens /ripple/updates with actual content additions, separate operating checks, and conditional rollout target dates. The public mount exposes measured operations while all collection, assessment and research writers remain on the existing owner-private backend. Main VersionCompass navigation stays unlinked.
The backend adds durable queue/session/event/usage records, a persistent 150-request daily collection cap, bounded retries and five admitted 12-minute research sessions per day. No discovery source or vulnerability conclusion is added, and no paid integration is introduced.
Validation: 25 Ripple production-workflow tests using SQLite with the actual migration, TypeScript, private build; 162 VersionCompass tests, four ordered generation gates and Worker build. Browser rendering/native export are not claimed. The comparison report and export implementation are unchanged; affected Ripple live reads/writers and guard checks are recorded separately in the rollout audit.