The signed-in physician, and the tick of the onboarding cadence clock.

Welcome package v2 §5: sessions_seen increments on the /auth/me that follows a login — not in /auth/login, because the portal also reaches this endpoint on a cold boot from a token still in storage, and a physician who closes the tab on Monday and opens it on Tuesday has started a session without signing in again.

Idempotent per LOGIN, keyed on the token's jti: a reload, a second tab and the parallel calls one page paint makes all carry the same token and count once, while a genuine new sign-in mints a new one and counts. Without that key the clock would run at the speed of page loads and every physician would be past the re-entry page before they had seen it twice.

Best-effort by construction. This endpoint is how the portal learns who it is talking to, and a counter that cannot write is not a reason to fail that.