Add idle refresh prompt for creator list after inactivity threshold

[Chucks1093]

Summary
Users who leave the creator list open for an extended period may be viewing stale data without realising it. A subtle prompt that appears after an inactivity threshold and offers to refresh the list keeps data fresh without forcing unwanted reloads.

Scope

• add an idle detection helper that tracks time since the last creator list refresh
• show a subtle prompt after the defined threshold offering to refresh
• dismiss the prompt automatically if the user interacts with the page

Acceptance Criteria

• the refresh prompt appears after the defined inactivity threshold
• activating the prompt triggers a creator list refresh
• the prompt dismisses automatically on user interaction without refreshing

Contributor coordination: if you pick this up, reach out in Telegram for updates or clarification: https://t.me/accesslayerorg

[Chidubemkingsley]

@Chidubemkingsley has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

https://www.drips.network/wave/stellar/issues/ea7f02d6-9e17-436f-8cf9-2c792052f2c5/apply/success

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Chidubemkingsley to this issue.

[GreatShinro]

@GreatShinro has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

Hi, can I work on this please?

ℹ️ Repo Maintainers: To accept this application, review their application or assign @GreatShinro to this issue.

[Nuel-ship-it]

@Nuel-ship-it has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

I’m interested in handling this issue. I’ve built and tested web3 applications across contracts, backend services, and frontend flows.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Nuel-ship-it to this issue.

[michaelvic123]

@michaelvic123 has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

pleae assign this to me

ℹ️ Repo Maintainers: To accept this application, review their application or assign @michaelvic123 to this issue.

[drips-wave]

Congratulations, @Chidubemkingsley! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 2, 2026.

🧑‍💻 @Chidubemkingsley: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[drips-wave]

This issue has been completed by @Chidubemkingsley as part of the Stellar Wave Program's 5th Wave 🥳

😎 @Chidubemkingsley: You earned 150 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.