Per-request visibility into challenge pass/fail events

Hi,

Today: challenges only expose aggregates — issued and passed. Per-request detail exists for attacks and custom rule matches, but not for challenge events.

Problem: we can't investigate why a specific legitimate client keeps failing; we can't detect a successful bypass, because a bot that reliably solves the challenge just looks like a healthy pass rate; and we can't isolate automation clusters to reuse in our own rules.

Request: a per-request challenge event log with the same inspection capabilities as attacks and rule matches, including

timestamp, IP, ASN, geo
JA4
User-Agent and full request headers, URL, method
time to solve and number of attempts
session or cookie ID, to link the event to the client's later requests
the automation signals behind the decision (no JS execution, headless indicators)

Benefit: we can investigate false positives and user complaints, detect bypass, enrich our rules from JA4 clusters, and measure human pass rate against bot pass rate instead of one blended number