[Feature]: Implement Pagination for Structured Verification Result Reporting

[rishabh0510rishabh]

Description

Issue #36 introduces Structured Verification Result Reporting. As the system processes more "seeds", the database or storage layer will accumulate a massive amount of verification reports. Fetching all reports in a single API call will eventually cause high memory consumption and slow response times.

Suggested Fix

1. Update the API endpoint responsible for fetching verification results to accept page and limit (or cursor) query parameters.
2. Update the underlying database query to utilize LIMIT and OFFSET.
3. Ensure the API response includes pagination metadata (e.g., total_items, total_pages, current_page, next_page_url) alongside the structured results.

[abdullahxyz85]

Hi @rishabh0510rishabh I would like to work on this issue, please assign this issue to me under gssoc label: gssoc:approved and level!

[pranadarao55555-prog]

Hi, I am a GSSoC '26 contributor. I have a strong foundation in Python and Data Structures, and I would love to work on this issue. Please assign it to me!

[rishabh0510rishabh]

Sure @pranadarao55555-prog go ahead with this one too...if need any help you can reach mentors and me too

[rishabh0510rishabh]

any update @pranadarao55555-prog ?

[samalbishnupriya06-stack]

Subject: Follow-up: Status of Issue #58

Hi @rishabh0510rishabh

I hope you’re having a good week.

I noticed that issue #58 has been open for some time without an active assignment. Given the current project timeline, I would like to take ownership of this task to help move it forward.

Could you please assign this to me, or let me know if there is anything I need to do to get started on it?

/assign

[rishabh0510rishabh]

sure assigned @samalbishnupriya06-stack

[Saksham-Joshi856]

Hi @rishabh0510rishabh,

I reviewed this issue and understand that as the number of processed seeds grows, returning all verification reports in a single API response can lead to increased memory usage, slower response times, and reduced scalability.

I'd like to work on this by:

• Adding pagination support through query parameters such as page and limit (or a cursor-based approach if preferred).
• Updating the database query to use LIMIT and OFFSET for efficient data retrieval.
• Extending the API response to include pagination metadata such as total_items, total_pages, current_page, and navigation information for subsequent pages.
• Ensuring backward compatibility and maintaining the existing structured verification result format.

Could you please assign this issue to me? I'd be happy to contribute this enhancement.