[turnipdabeets]

Summary

Follow-up to #143. That PR gave client SDKs one property order with no exceptions (SDK-set, then registered, then caller, then before_send), and named the replay debug properties among the keys that move under it. But session-replay-debug-properties still says SDK-computed $recording_status and $sdk_debug_* values win over a registered or caller property and that the debug map is merged last, so the two specs disagree. The PostHog review bot flagged the conflict on PostHog/posthog-ios#938.

Changes

• Session, queue, hold-reason, trigger, and mode keys: the debug keys follow capture's Caller-supplied event properties take precedence. A registered property overrides the SDK-computed value, a caller property overrides both, before_send can change any of them, and the override applies to that event only.
• "Debug values win over same-named caller or registered properties" is replaced by three scenarios: a registered override, a caller override, and the next event carrying the SDK-computed value again.
• The posthog-ios references drop the 3.x merge that let the debug map win, and its covering test, and cite the 4.0 test instead.

openspec validate --specs --strict passes (67/67). No acceptance feature covers these keys.

Impact

• posthog-ios: conforms in 4.0 (feat!: send events through capture v1 and add captureAi posthog-ios#938).
• posthog-js (browser), posthog-android, @posthog/core: no work beyond what fix(capture): one property precedence for client SDKs #143 already lists for them (setting the replay debug properties before super and caller properties).
• Server SDKs: not applicable.

🤖 Generated with Claude Code

[dustinbyrne]

This aligns replay-debug property precedence with capture’s existing contract, with synchronized archived requirements and scenarios for registered, caller, and event-local overrides. No actionable findings.

AI-assisted review.