Repository navigation
feat: expose optional stored client identity (java, #192) - #5
Open
KonstantinSerebryakov wants to merge 1 commit into
Open
KonstantinSerebryakov wants to merge 1 commit into
KonstantinSerebryakov wants to merge 1 commit into
Conversation
KonstantinSerebryakov
marked this pull request as ready for review
October 6, 2026 00:25
This branch has not been deployed
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.
Expose optional typed client_identity from both History and webhook normalization. Preserve server subject scope, classification revision, evidence and unknown raw fields; absent/malformed optional attribution stays absent. Keep existing risk normalization unchanged and clarify that legacy search_bot is a UA signal.
Tests cover shared saved-decision fixtures, both surfaces, optional absence, future values and score independence. 351 tests, Maven verify and coverage gates passed.
Task #192, following the updated analyst handoff and user decisions: separate claimed and verified attributes, calculate in ingest, preserve admitted decisions/evidence on retry, keep Analytics non-band OR semantics and one full snapshots facts dataset.
No scoring exemption or reinterpretation of a verified provider as a verified agent/mode. Feature flags default off. Runtime enablement requires real provider captures, schema/all-writer barrier, retained physical read-pin/completeness gate, and full-sized traffic/storage measurements. These remain explicit acceptance gaps; local synthetic evidence does not close them. This coordinated PR is draft pending those gates.