test(pro): what happens to Pro-gated state when Pro is revoked, and the CTA handling it needed - #160

Merged

Bilb merged 21 commits into

mainfrom

feat/pro-pins-over-limit-after-lapse

Aug 28, 2026

Commits on Aug 27, 2026

Add a spec for pins held over the limit once Pro is revoked
mpretty-cyro
authored
3eea753
Assert pins held over the limit survive Pro being revoked
mpretty-cyro
authored
c5c961f
Assert the home screen carries a Pro badge for a subscriber
mpretty-cyro
authored
07dfeba
Address the Android home badge by its qualified view id
mpretty-cyro
authored
ae78f49
Add the desktop halves of the revocation pin and avatar specs
mpretty-cyro
authored
a9097cb
State the gate as a property, not as a thing that was measured
mpretty-cyro
authored
3b02aab
Say why one pin past the limit is enough
mpretty-cyro
authored
5c3df00
Sort the new ids and locator into place
mpretty-cyro
authored
8167360
Assert the pinned conversation limit holds across a relaunch
mpretty-cyro
authored
5dfdf6a
test(pro): fold the relaunch case into the standard pin-limit spec
mpretty-cyro
authored
5a5e72c
refactor(pro): share the CTA dismissal helper across the mobile specs
mpretty-cyro
authored
511c5f4
refactor: give dismissCTA a mechanism instead of a boolean
mpretty-cyro
authored
7d36792
refactor: settle the conversation list inside pin and unpin
mpretty-cyro
committed
49775e2

Commits on Aug 28, 2026