[FE-122] admin/audit-logs table has no pagination or virtualization

[mftee]

Overview

frontend/app/[locale]/(protected)/admin/audit-logs/page.tsx (backing FE-63) renders access-log entries via the shared table.tsx, but on a production dataset (access logs grow unboundedly per BE-91) an unpaginated table will render every row into the DOM at once.

Tasks

• Add pagination controls wired to the backend's paginated access-logs endpoint
• Add a test asserting only one page of rows renders at a time

Acceptance Criteria

• The audit-logs table renders a bounded page size regardless of total record count

Notes for Contributors

Comment below to be assigned.

[marvelousjeremiah24]

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

I would like to work on this issue

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

[Nathanpvd]

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

Hello Maintainer, I’ve gone over the requirements and believe I can provide a solid implementation that meets the acceptance criteria. I’d appreciate being assigned this issue.

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

[0xElyte]

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

I'd love to resolve this issue fast

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

[lovesmilesmall-hue]

@lovesmilesmall-hue has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

I will add pagination controls to the admin audit-logs table wired to the backend paginated endpoint, and add a test asserting only one page of rows renders at a time. My approach is to connect the table to the paginated API and verify the bounded page size regardless of total record count.

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

[drips-wave]

Congratulations, @lovesmilesmall-hue! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

🧑‍💻 @lovesmilesmall-hue: 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 🌊

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox!

@lovesmilesmall-hue's PR #1241 was approved and merged by @mftee.

🏆 @lovesmilesmall-hue: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (697 total points). Track your full progress on GrantFox.

👏 Great work, @lovesmilesmall-hue! Keep contributing to CodeGirlsInc.

[drips-wave]

This issue has been completed by @lovesmilesmall-hue as part of the Stellar Wave Program's 8th Wave 🥳

😎 @lovesmilesmall-hue: You earned 200 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.