Repository navigation
feat(webhooks): define final risk and HRE contract - #12
Merged
Merged
Conversation
This was referenced Oct 5, 2026
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.
Contract
2026-10-06exports the identification risk score only, all 19 implemented risk events (including zero-weight flags), three completed on-demand HRE results and distinct device/fp21 hardware identities. AI bots/browser are documented as planned and are not fabricated in payloads. Multiaccount remains a separate periodic pipeline; no all-time entity risk reads are added.Add conditional current-version required fields while retaining legacy bodies and open response values. Document stable logical event IDs, bounded retries, raw-body signatures and the distinct scan/event clocks. Bundled YAML/JSON and JSON Schema exports are regenerated. Five actual Core-marshaled fixtures independently validate the contract, including anonymous, no-history, banned and incomplete cases.
Validation: strict Redocly lint, 64 tests and deterministic bundle check. Legacy example exceptions remain scoped to the existing two missing flags. No package publication.
Related changes: core, portal, node, go, python, php, docs.
Merge/release order: OpenAPI and SDK compatibility, then Portal/docs, then Core emission. Merging Core/Portal development PRs invokes their normal development deployment workflows; this task does not merge them.