What one profile action event reads of a visit: the visit's own fields (the
target, the chain, the session id) plus the process's ranking token. The
token is required and is not the visit's: it is the run's
tray_session_id without its dashes, one value for every event of the
process — so no builder can mint one per event or derive it from the visit.
targetUsername is not read by an action event, so it stays out.
What one profile action event reads of a visit: the visit's own fields (the target, the chain, the session id) plus the process's ranking token. The token is required and is not the visit's: it is the run's
tray_session_idwithout its dashes, one value for every event of the process — so no builder can mint one per event or derive it from the visit.targetUsernameis not read by an action event, so it stays out.