Refactor ProveScreen to ProofRequestCard layout and preserve scroll position

[transphorm]

Motivation

• Align the ProveScreen UI with the DocumentSelectorForProvingScreen design while preserving all existing proving logic and analytics.
• Preserve the user's scroll position when navigating from the document selector to the proving screen so users do not need to re-scroll.
• Remove duplicated disclosure formatting by extracting a shared disclosure utility used by both screens.
• Replace the BottomActionBar approve layout with the existing hold-to-verify control while keeping the proving state machine intact.

Description

• Added app/src/utils/disclosureUtils.ts with getDisclosureItems and migrated both screens to consume it to avoid duplication.
• Added app/src/components/proof-request/BottomVerifyBar.tsx which wraps HeldPrimaryButtonProveScreen and exported it from the proof-request index.
• Extended ProofRequestCard to accept scroll control props (onScroll, scrollViewRef, onContentSizeChange, onLayout, initialScrollOffset) and wired them to the internal ScrollView to support restoring scroll position.
• Updated navigation types to accept an optional scrollOffset for the Prove route and changed DocumentSelectorForProvingScreen to track scroll offset and pass it when navigating; refactored ProveScreen to use ProofRequestCard, DisclosureItem, ConnectedWalletBadge, WalletAddressModal, and BottomVerifyBar while preserving all existing effects, proving store logic, and analytics calls.

Testing

• No automated tests were run in this environment.
• Before creating a PR run yarn nice and yarn types to validate formatting and types locally.
• Run unit tests with yarn test and build with yarn build as part of pre-PR/CI validation.
• For mobile UI verification run platform builds or emulators using yarn ios or yarn android as appropriate.

---

Codex Task

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

🗂️ Base branches to auto review (3)

• main
• dev
• staging

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.