fix(recently-deleted): keep previous-criteria rows inert while the new list loads

[waleedlatif1]

Summary

• Recently Deleted keeps the previous tab/search/sort rows on screen while the new criteria load (no flicker), but they could still be restored and could drive infinite scroll
• While those rows are placeholder data, disable Restore and stop the load-more sentinel, so a stale hasNextPage can't fetch a "next page" against the new criteria
• Matches how other settings surfaces treat isPlaceholderData as not-yet-current data

Type of Change

• Bug fix

Testing

• biome on the changed file; type-check, lint, and audits in CI
• No component test added: the change is a disabled/enabled condition the repo's testing rules ask not to restate

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing (new tests pass the test-audit authoring gate)
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated
docs	Skipped		Oct 13, 2026 5:55am UTC

[cubic-dev-ai]

No issues found across 1 file

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

<sub>Heads up: you’ve reached your flex budget. Increase your flex budget or wait for usage to reset.

Turn on auto-fix | Re-trigger cubic</sub>

[greptile-apps]

Confidence Score: 5/5

[Medium impact] This PR appears safe to merge; both guards block actions on placeholder rows and allow them again when current data arrives.

Summary

Keeps previous tab, search, and sort results visible while the new Recently Deleted list loads.

• Recently Deleted waits for current rows before restore or load-more.

_{Reviews (1) · Last reviewed commit: "fix(recently-deleted): keep previous-cri..." · Reviewed by Greptile}