Exactly 11 students breaks pagination (inside school building)

[Pragya79645]

Pagination behaves incorrectly when the student count is exactly 11.

[Sampurnasit]

Building: [ School House ] Difficulty (your estimate): [Medium]

What is broken?
Pagination collapses to 2 pages instead of 3 when there are exactly 11 student records.

Steps to reproduce

1. Go to the School House and open Student Records.
2. Ensure there are exactly 11 students visible (this is the default state).
3. Observe the footer showing "Page 2 / 2" even though there are more records that should be on a 3rd page (with a page size of 5).
4. Note that the "Next" button is disabled on page 2, preventing access to the remaining record.

Expected behavior
With 11 records and a page size of 5, the application should calculate 3 total pages (5 + 5 + 1) and allow navigation to the 3rd page.

Actual behavior
An intentional logic bug in useStudentRecordsChallenge.js was subtracting 1 from the total page count whenever the record count was exactly 11, causing the last page to be unreachable.

Environment
Browser: Chrome / Firefox (Latest) Screen size: Desktop (1440px) Mode: Dark (Debug Quest Mode)

[Soyam27]

Please provide Solution/Approach.

[Sampurnasit]

Fix: Corrected pagination calculation for exactly 11 student records
Closes #23

Bug found
When the total count of student records was exactly 11, the pagination system would incorrectly display "Page X / 2" instead of "Page X / 3". Visible symptom: With a page size of 5, the first 10 students were visible across two pages, but the 11th student was unreachable because the "Next" button became disabled on page 2.

Root cause
An intentional edge-case bug was hardcoded into the totalPages memoized value.

File: src/components/school-house/hooks/useStudentRecordsChallenge.js
Line: ~83-85
Logic: The code explicitly checked if (filtered.length === 11) and, if true, returned computed - 1. This forced the total page count to drop from 3 to 2, effectively "swallowing" the final page of data.

Fix applied
I refactored the totalPages calculation to remove the biased logic:

useStudentRecordsChallenge.js: Removed the if (filtered.length === 11) condition.

Logic Update: The function now strictly returns Math.max(1, Math.ceil(filtered.length / pageSize)). This ensures that any remainder (like the 11th student) correctly triggers the creation of an additional page.

Cleanup: While fixing this, I also cleaned up stale search query and class filter logic in the same hook to ensure the pagination remains accurate during active filtering.

Testing done
[x] Reproduced the bug before applying fix (verified 11 records = 2 pages) , Confirmed fix resolves the issue (verified 11 records = 3 pages) , Verified no existing features are broken , Tested on: Chrome / Windows 11

After resolving:

[Soyam27]

Assigned.