[Due for payment 2026-06-12] perf: feed stable report projection to transaction list to avoid read-state re-renders

[mountiny]

Problem

getStableReportSelector/reportStable already produce a stable report projection in MoneyRequestReportActionsList by omitting read-state heartbeat fields (lastReadTime, lastVisibleActionCreated, lastMessageText, etc.). The full report object was still passed to MoneyRequestReportTransactionList, so every last* field mutation (e.g. marking a report as read, receiving a message) re-rendered the entire transaction-list subtree even though nothing inside it reads those fields.

Solution

Pass reportStable (typed as StableReport) to MoneyRequestReportTransactionList instead of the full report. StableReport is structurally assignable to Report because the omitted fields are optional, so downstream row components and utility calls need no changes. The existing !!reportStable guard preserves conditional rendering. Read-state churn no longer triggers transaction-list re-renders; behavior stays the same. export type {StableReport} is added to src/selectors/Report.ts for import from the selector module.

PR

#92485

Issue Owner

Current Issue Owner: @aimane-chnaif

[melvin-bot]

Reviewing label has been removed, please complete the "BugZero Checklist".

[melvin-bot]

The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.99-9 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• perf: feed stable report projection to transaction list to avoid read-state re-renders #92485

If no regressions arise, payment will be issued on 2026-06-12. 🎊

For reference, here are some details about the assignees on this issue:

• @TMisiukiewicz does not require payment (Contractor)
• @aimane-chnaif requires payment (Needs manual offer from BZ)