Repository navigation
chore: adopt ORES config contracts for Flutter client - #9
Merged
Merged
Conversation
ORESoftware
marked this pull request as ready for review
September 12, 2026 06:24
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.
Adds client-only middleware propagation, a client-local LRU config, and a Shared Auth Flutter compatibility manifest. The pre-existing
.ores-rl.tomlis preserved semantically (observe-only/advisory fixed-window policy) and augmented with the exact TJSV + flags-2-env policy notes rather than being overwritten.No server Redis/HMAC references are exposed to the Flutter rate-limit projection. GATE: Shared Auth #49 still needs executable exact-head TJSV admission; keep draft/unmerged until that passes.