feat(rokt): add MPRokt clearSession passthrough

[nickolas-dimitrakas]

Summary

Adds clearSession to MPRokt, forwarding to the Rokt kit so a host app can end the current Rokt session and have the next selectPlacements call start a new one.

Why

This is for self-service terminals — kiosks, counter tablets, shared point-of-sale hardware — where a queue of unrelated customers uses a single device.

The Rokt SDK carries session identity in a token it persists and replays on every request, and its gateway continues the existing session for as long as a live token is presented. On a device that is busy, that token never lapses, so consecutive customers were all recorded against one session. There was no way for a host app to say "this transaction is over, the next person is someone else."

The companion Rokt SDK change adds a public clearSession() that does the work; this passthrough exposes it to apps integrating through mParticle. The Rokt kit will also call it automatically on MPID change, so most integrations will not need this method — it is the manual escape hatch.

Implementation notes

Follows the existing close pattern: no parameters, forwarded via forwardSDKCall: with MPMessageTypeEvent, and no MPKitProtocol change needed since the selector resolves at runtime (setSessionId: forwards the same way today).

One deliberate difference from close: this dispatches on [MParticle messageQueue] rather than the main queue, to match selectPlacements. Both forwards ultimately hop to main inside attemptToLogEventToKit, so dispatching from two different queues would leave their relative order down to which queue drains first. A caller doing clearSession immediately followed by selectPlacements would then sometimes send the departing session's credentials. Sharing the serial message queue makes that ordering deterministic.

Compatibility

Purely additive — no existing behaviour changes. Kits that do not implement clearSession simply do not receive the forward.

Testing

The method is a forwarding shim with no branching logic. I have not run the full mParticle test suite locally; CI coverage on this PR is the check that matters.

Verification status

The underlying SDK behaviour this forwards to (ROKT/rokt-sdk-ios#298) has been verified end to end on simulators against the production gateway: a before/after matrix on two devices confirmed that consecutive "customers" separated by Rokt.clearSession() receive distinct session ids, that placements with no reset keep sharing one session (no premature severing), and that sessions still survive a full app kill and relaunch. Details in that PR's description.

This PR's own forwarding path was not part of that E2E — it exercised Rokt.clearSession() directly, which is the same single funnel this code calls. Kit-level unit coverage for the trigger conditions is a known follow-up.

🤖 Generated with Claude Code

[cursor]

PR Summary

Low Risk
Additive public API and kit forward with no protocol or existing-behavior changes. Kits that do not implement clearSession simply ignore the selector.

Overview
Adds clearSession on MPRokt so a host app can drop the current Rokt session (kiosks / shared POS) and have the next selectPlacements start a new one.

The method logs ROKT_CLEAR_SESSION then fire-and-forgets forwardSDKCall:@selector(clearSession) on [MParticle messageQueue] (same serial queue as selectPlacements, unlike close on main) so a clear immediately followed by a placement cannot race and reuse the departing session token. No MPKitProtocol change; unimplemented kits skip the forward.

Tests cover the diagnostic and the kit forward, plus a drainMessageQueue helper so the async block cannot hit torn-down OCMocks.

^{Reviewed by Cursor Bugbot for commit 6884be2. Bugbot is set up for automated code reviews on this repo. Configure here.}

[github-actions]

📦 SDK Size Impact Report

Measures how much the SDK adds to an app's size (with-SDK minus without-SDK).

Metric	Target Branch	This PR	Change
App Bundle Impact	1.79 MB	1.79 MB	+N/A
Executable Impact	848 bytes	848 bytes	+N/A
XCFramework Size	6.49 MB	6.49 MB	+N/A

➡️ SDK size impact change is minimal.

Raw measurements

Target branch (main):

{"baseline_app_size_kb":84,"baseline_executable_size_bytes":75464,"with_sdk_app_size_kb":1920,"with_sdk_executable_size_bytes":76312,"sdk_impact_kb":1836,"sdk_executable_impact_bytes":848,"xcframework_size_kb":6648}

This PR:

{"baseline_app_size_kb":84,"baseline_executable_size_bytes":75464,"with_sdk_app_size_kb":1920,"with_sdk_executable_size_bytes":76312,"sdk_impact_kb":1836,"sdk_executable_impact_bytes":848,"xcframework_size_kb":6648}

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit e01ca56. Configure here.}