Contact Request or Pay actions are clipped on compact screens #1666

Observed behavior

The Contact Detail Request or Pay sheet hides its Pay and Request actions below the visible area on a 320 × 640 dp Android display, even at default text size.

Reported by the exact-head device review of #1564, tested at c1f1c0a784a04107617eccef5fdc698b9dc08789 on Android 16. Compact-screen recording. The reviewer completed Pay → Amount and Request → request amount on a normal-height display; no payment or request was submitted.

Reproduction

1. Use a 320 × 640 dp display at 100% font scale, with an existing linked contact eligible for payments/requests.
2. Open the contact and tap Pay to open Request or Pay.
3. Check whether both footer actions can be seen and reached without changing the display configuration.

Expected: both actions remain reachable on compact screens and with enlarged text. Preserve loading, cancellation and duplicate-payment protection.

Source investigation and scope

ContactDetailScreen.kt renders RequestOrPaySheet as a non-scrolling column at SheetSize.MEDIUM, with a fixed 256 dp illustration before the headline, description and action row. SheetHeight.kt limits that sheet to the available height after toolbar/inset reservations. This leaves insufficient room for all fixed content on compact screens.

The screen, its ViewModel and sheet-height implementation have identical blobs in the tested PR, its base 22a5cb561, and current master d5526d409. This is inherited behavior, outside #1564's contact-picker changes. Source was independently checked; this issue's native reproduction evidence is the linked reviewer run, not a new local device run.

iOS has a similar fixed 256-point illustration in RequestOrPayView (CreatePaymentRequestView.swift); check its compact/enlarged-text behavior too. An iOS overflow is not yet confirmed.

Keep this separate from #1617's activity-recreation/cancelled-payment state and #1419's preparation latency. The device review's several-second Pay delay does not establish a layout-related latency cause.