feat(paywalls): add web_view message value types (PWENG-98)

[alexrepty]

Checklist

• If applicable, unit tests
• If applicable, create follow-up issues for purchases-ios and hybrids

Motivation

The web_view bidirectional-messaging bridge needs a JSON-compatible value type to represent message payloads in a type-safe, public-API-friendly way.

Part of PWENG-98.

Description

• Adds the public PaywallWebViewValue sealed type (String / Number / Boolean / Object / Array / Null) plus JSON conversion helpers.
• Pure data type — no message envelope, parser, or bridge yet.
• Tested by PaywallWebViewValueTest.

iOS parity: mirrors purchases-ios (web-view-bridge-wiring).
Stack (merge bottom-up): schema → rendering → CSP → value types → message model → variables provider → JS bridge → wiring.

---

Note

Low Risk
Additive public API and internal helpers only; no changes to purchase, auth, or existing paywall runtime behavior.

Overview
Introduces PaywallWebViewValue, a new public JSON-shaped type for Paywalls V2 web_view message payloads, ahead of the JS bridge stack (PWENG-98).

The type is an abstract class with nested variants (String, Number, Boolean, Object, Array, Null)—same pattern as CustomVariableValue for stable public API. api.txt documents the new surface.

Internal helpers add fromJson (with a nesting depth cap and rejection of non-JSON types) and outbound serialization via toJsonRepresentation / toJsonObject (whole numbers emitted as integers). No message envelope, parser, or WebView wiring in this PR—data layer only.

PaywallWebViewValueTest covers primitives, nested structures, depth limits, and round-trip JSON.

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

[alexrepty]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• Add paywall-tester web_view sample #3724
• feat(paywalls): wire web_view messaging into the paywall (PWENG-98) #3653
• feat(paywalls): add web_view JavaScript bridge (PWENG-98) #3655
• feat(paywalls): add web_view SDK variables provider (PWENG-98) #3663
• feat(paywalls): add web_view message model and parsing (PWENG-98) #3654
• feat(paywalls): add web_view message value types (PWENG-98) #3662 👈 (View in Graphite)
• feat(paywalls): isolate web_view content with a fixed CSP (PWENG-98) #3652
• feat(paywalls): render web_view component (PWENG-98) #3651
• feat(paywalls): add web_view component schema (PWENG-98) #3650
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[emerge-tools]

📸 Snapshot Test

593 unchanged

Name	Added	Removed	Modified	Renamed	Unchanged	Errored	Approval
TestPurchasesUIAndroidCompatibility Paparazzi com.revenuecat.testpurchasesuiandroidcompatibility.paparazzi	0	0	0	0	258	0	N/A
TestPurchasesUIAndroidCompatibility com.revenuecat.testpurchasesuiandroidcompatibility	0	0	0	0	335	0	N/A

---

🛸 Powered by Emerge Tools

[cursor]

Cursor Bugbot has reviewed your changes 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 7aceb78. Configure here.}

[cursor]

Number.equals/hashCode contract violation with IEEE 754 doubles

Low Severity

Number.equals uses IEEE 754 == (value == other.value) while hashCode delegates to Double.hashCode() which uses doubleToLongBits. This breaks the equals/hashCode contract: Number(0.0) and Number(-0.0) are equal but produce different hash codes, and Number(NaN) violates reflexivity (not equal to itself). Using value.toBits() == other.value.toBits() in equals would make both methods consistent.

 

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