feat(dashboard): group courses by semester with an Archive for past terms (#140)

[Jose-Gael-Cruz-Lopez]

Closes#140.

Groups enrolled classes by semester, defaults to the current term, and puts past terms behind an Archive.

The dependency was already satisfied

#140 is filed as "depends on the backend API issue", but that's stale — nothing was blocking:

• GET /api/semesters already exists and serves {id, term, year, label, start_date, end_date, sort_key}.
• GET /api/graph/{user_id}/courses already returns a term label per course; only the frontend EnrolledCourse interface hadn't declared it.

So this is frontend-only.

It also fixes a live bug

screens/Gradebook/Landing.tsx read (c as any).semester off the courses payload — but the API sends term. The lookup therefore always came back empty and fell through to the hardcoded demo constant:

constSAMPLE_SEMESTERS=["Spring 2026","Fall 2025"];

Every signed-in user was being shown those two fake semester chips instead of their own. The as any is exactly what let the field-name mismatch through the type checker. SAMPLE_SEMESTERS is now strictly the logged-out preview; a signed-in user with no terms gets their own empty state (a termsReady gate keeps that from hanging on the skeleton). Covered by tests.

New src/lib/semesters.ts — one tested source of truth

• currentTerm(semesters, today) mirrors services/academics.py::current_termexactly: the highest-sort_key term whose [start_date, end_date] contains today, falling back to the highest sort_key overall when today lands in a gap between terms. today is injectable. Dates compare as YYYY-MM-DD strings (lexicographic == chronological), and a Date is read in local time — toISOString() would shift the day either side of midnight.
• termRankFromLabel("Fall 2025") -> 20253, mirroring migration 0019's year * 10 + ordinal. Only consulted when no real sort_key is available; sort_key always wins.
• groupCoursesByTerm, courseTermLabels, partitionCurrentAndArchive.

Degradation — the rule is "never hide a course"

If /api/semesters fails or returns nothing, everything collapses to one flat ungrouped list with no Archive control and nothing hidden. Courses with an empty or unparseable term are never dropped and never archived. Future-term courses are never archived. Only a course ranking strictly below the current term is archived — showing a course in the wrong bucket is recoverable, hiding it isn't.

UI

The partition is applied to the "My courses" panel (which is also the mobile courses tab), the graph legend chips, the CoursesKey overlay, and ManageCoursesModal's list. CourseProgressRow was extracted rather than copying that markup a third time. Archived rows route to /gradebook?semester=<label>, which the gradebook landing reads and preselects — so selecting an archived class lands in that semester's gradebook, per the acceptance criteria.

The Calendar is untouched, per the explicit product decision in the issue.

Verification

Gate	Result
npm test	131 passing (baseline 88) — 15 files, +43 tests
npx tsc --noEmit	0 errors
npx eslint . --max-warnings=-1	exit 0, 36 warnings (baseline)
npm run build	exit 0, compiled successfully

One thing worth flagging because it nearly shipped broken: fixing the as any removed the only no-explicit-any in Landing.tsx, which left a stale entry in eslint-suppressions.json. ESLint exits 2 on a stale suppression even with zero errors — main exits 0, this branch did not — so the lint gate would have failed CI. Pruned in its own commit.

For the reviewer

1. Two files outside the intended scope got a one-line fixture addition each (src/lib/data.test.ts, src/components/DocumentUploadModal.test.tsx), forced by making term required on EnrolledCourse.
2. Landing reads ?semester= from window.location.search in a useState initializer rather than useSearchParams(), which would require a Suspense boundary in the route shell this component doesn't own. It never reaches the rendered tree, so there's no hydration mismatch — but adding the boundary instead is a reasonable alternative.
3. The client's current-term rule is a hand-mirror of the Python one. Test fixtures are migration 0019's four terms verbatim so drift surfaces, but there is no automated cross-language check.
4. The knowledge graph still renders nodes from all terms — only the course lists and legends are term-scoped. Filtering graph data by term is a separate product call.

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

@AndresL230, you've reached your PR review limit, so we couldn't start this review.

Next review available in:54 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Free

Run ID: 39694af7-3514-4235-b33b-03e1297e832a

📥 Commits

Reviewing files that changed from the base of the PR and between 4227689 and c1d6f9b.

📒 Files selected for processing (11)

• frontend/eslint-suppressions.json
• frontend/src/components/DocumentUploadModal.test.tsx
• frontend/src/components/ManageCoursesModal.tsx
• frontend/src/components/screens/Dashboard.test.tsx
• frontend/src/components/screens/Dashboard.tsx
• frontend/src/components/screens/Gradebook/Landing.test.tsx
• frontend/src/components/screens/Gradebook/Landing.tsx
• frontend/src/lib/api.ts
• frontend/src/lib/data.test.ts
• frontend/src/lib/semesters.test.ts
• frontend/src/lib/semesters.ts

---

Note

🎁 Summarized by CodeRabbit Free

Your organization is on the Free plan. CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please upgrade your subscription to CodeRabbit Pro by visiting https://app.coderabbit.ai/login.

_{Comment @coderabbitai help to get the list of available commands.}

[cloudflare-workers-and-pages]

Deploying with Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	frontend-staging	c1d6f9b	Commit Preview URL Branch Preview URL	Jul 22 2026, 04:25 AM

[Jose-Gael-Cruz-Lopez]

@coderabbitai review

[coderabbitai]

✅ Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[Jose-Gael-Cruz-Lopez]

Closes#140.

Groups enrolled classes by semester, defaults to the current term, and puts past terms behind an Archive.

The dependency was already satisfied

#140 is filed as "depends on the backend API issue", but that's stale — nothing was blocking:

• GET /api/semesters already exists and serves {id, term, year, label, start_date, end_date, sort_key}.
• GET /api/graph/{user_id}/courses already returns a term label per course; only the frontend EnrolledCourse interface hadn't declared it.

So this is frontend-only.

It also fixes a live bug

screens/Gradebook/Landing.tsx read (c as any).semester off the courses payload — but the API sends term. The lookup therefore always came back empty and fell through to the hardcoded demo constant:

constSAMPLE_SEMESTERS=["Spring 2026","Fall 2025"];

Every signed-in user was being shown those two fake semester chips instead of their own. The as any is exactly what let the field-name mismatch through the type checker. SAMPLE_SEMESTERS is now strictly the logged-out preview; a signed-in user with no terms gets their own empty state (a termsReady gate keeps that from hanging on the skeleton). Covered by tests.

New src/lib/semesters.ts — one tested source of truth

• currentTerm(semesters, today) mirrors services/academics.py::current_termexactly: the highest-sort_key term whose [start_date, end_date] contains today, falling back to the highest sort_key overall when today lands in a gap between terms. today is injectable. Dates compare as YYYY-MM-DD strings (lexicographic == chronological), and a Date is read in local time — toISOString() would shift the day either side of midnight.
• termRankFromLabel("Fall 2025") -> 20253, mirroring migration 0019's year * 10 + ordinal. Only consulted when no real sort_key is available; sort_key always wins.
• groupCoursesByTerm, courseTermLabels, partitionCurrentAndArchive.

Degradation — the rule is "never hide a course"

If /api/semesters fails or returns nothing, everything collapses to one flat ungrouped list with no Archive control and nothing hidden. Courses with an empty or unparseable term are never dropped and never archived. Future-term courses are never archived. Only a course ranking strictly below the current term is archived — showing a course in the wrong bucket is recoverable, hiding it isn't.

UI

The partition is applied to the "My courses" panel (which is also the mobile courses tab), the graph legend chips, the CoursesKey overlay, and ManageCoursesModal's list. CourseProgressRow was extracted rather than copying that markup a third time. Archived rows route to /gradebook?semester=<label>, which the gradebook landing reads and preselects — so selecting an archived class lands in that semester's gradebook, per the acceptance criteria.

The Calendar is untouched, per the explicit product decision in the issue.

Verification

Gate	Result
npm test	131 passing (baseline 88) — 15 files, +43 tests
npx tsc --noEmit	0 errors
npx eslint . --max-warnings=-1	exit 0, 36 warnings (baseline)
npm run build	exit 0, compiled successfully

One thing worth flagging because it nearly shipped broken: fixing the as any removed the only no-explicit-any in Landing.tsx, which left a stale entry in eslint-suppressions.json. ESLint exits 2 on a stale suppression even with zero errors — main exits 0, this branch did not — so the lint gate would have failed CI. Pruned in its own commit.

For the reviewer

1. Two files outside the intended scope got a one-line fixture addition each (src/lib/data.test.ts, src/components/DocumentUploadModal.test.tsx), forced by making term required on EnrolledCourse.
2. Landing reads ?semester= from window.location.search in a useState initializer rather than useSearchParams(), which would require a Suspense boundary in the route shell this component doesn't own. It never reaches the rendered tree, so there's no hydration mismatch — but adding the boundary instead is a reasonable alternative.
3. The client's current-term rule is a hand-mirror of the Python one. Test fixtures are migration 0019's four terms verbatim so drift surfaces, but there is no automated cross-language check.
4. The knowledge graph still renders nodes from all terms — only the course lists and legends are term-scoped. Filtering graph data by term is a separate product call.

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

@AndresL230, you've reached your PR review limit, so we couldn't start this review.

Next review available in:54 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Free

Run ID: 39694af7-3514-4235-b33b-03e1297e832a

📥 Commits

Reviewing files that changed from the base of the PR and between 4227689 and c1d6f9b.

📒 Files selected for processing (11)

• frontend/eslint-suppressions.json
• frontend/src/components/DocumentUploadModal.test.tsx
• frontend/src/components/ManageCoursesModal.tsx
• frontend/src/components/screens/Dashboard.test.tsx
• frontend/src/components/screens/Dashboard.tsx
• frontend/src/components/screens/Gradebook/Landing.test.tsx
• frontend/src/components/screens/Gradebook/Landing.tsx
• frontend/src/lib/api.ts
• frontend/src/lib/data.test.ts
• frontend/src/lib/semesters.test.ts
• frontend/src/lib/semesters.ts

---

Note

🎁 Summarized by CodeRabbit Free

Your organization is on the Free plan. CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please upgrade your subscription to CodeRabbit Pro by visiting https://app.coderabbit.ai/login.

_{Comment @coderabbitai help to get the list of available commands.}

[cloudflare-workers-and-pages]

Deploying with Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	frontend-staging	c1d6f9b	Commit Preview URL Branch Preview URL	Jul 22 2026, 04:25 AM

[Jose-Gael-Cruz-Lopez]

@coderabbitai review

[coderabbitai]

✅ Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[Jose-Gael-Cruz-Lopez]

Closes#140.

Groups enrolled classes by semester, defaults to the current term, and puts past terms behind an Archive.

The dependency was already satisfied

#140 is filed as "depends on the backend API issue", but that's stale — nothing was blocking:

• GET /api/semesters already exists and serves {id, term, year, label, start_date, end_date, sort_key}.
• GET /api/graph/{user_id}/courses already returns a term label per course; only the frontend EnrolledCourse interface hadn't declared it.

So this is frontend-only.

It also fixes a live bug

screens/Gradebook/Landing.tsx read (c as any).semester off the courses payload — but the API sends term. The lookup therefore always came back empty and fell through to the hardcoded demo constant:

constSAMPLE_SEMESTERS=["Spring 2026","Fall 2025"];

Every signed-in user was being shown those two fake semester chips instead of their own. The as any is exactly what let the field-name mismatch through the type checker. SAMPLE_SEMESTERS is now strictly the logged-out preview; a signed-in user with no terms gets their own empty state (a termsReady gate keeps that from hanging on the skeleton). Covered by tests.

New src/lib/semesters.ts — one tested source of truth

• currentTerm(semesters, today) mirrors services/academics.py::current_termexactly: the highest-sort_key term whose [start_date, end_date] contains today, falling back to the highest sort_key overall when today lands in a gap between terms. today is injectable. Dates compare as YYYY-MM-DD strings (lexicographic == chronological), and a Date is read in local time — toISOString() would shift the day either side of midnight.
• termRankFromLabel("Fall 2025") -> 20253, mirroring migration 0019's year * 10 + ordinal. Only consulted when no real sort_key is available; sort_key always wins.
• groupCoursesByTerm, courseTermLabels, partitionCurrentAndArchive.

Degradation — the rule is "never hide a course"

If /api/semesters fails or returns nothing, everything collapses to one flat ungrouped list with no Archive control and nothing hidden. Courses with an empty or unparseable term are never dropped and never archived. Future-term courses are never archived. Only a course ranking strictly below the current term is archived — showing a course in the wrong bucket is recoverable, hiding it isn't.

UI

The partition is applied to the "My courses" panel (which is also the mobile courses tab), the graph legend chips, the CoursesKey overlay, and ManageCoursesModal's list. CourseProgressRow was extracted rather than copying that markup a third time. Archived rows route to /gradebook?semester=<label>, which the gradebook landing reads and preselects — so selecting an archived class lands in that semester's gradebook, per the acceptance criteria.

The Calendar is untouched, per the explicit product decision in the issue.

Verification

Gate	Result
npm test	131 passing (baseline 88) — 15 files, +43 tests
npx tsc --noEmit	0 errors
npx eslint . --max-warnings=-1	exit 0, 36 warnings (baseline)
npm run build	exit 0, compiled successfully

One thing worth flagging because it nearly shipped broken: fixing the as any removed the only no-explicit-any in Landing.tsx, which left a stale entry in eslint-suppressions.json. ESLint exits 2 on a stale suppression even with zero errors — main exits 0, this branch did not — so the lint gate would have failed CI. Pruned in its own commit.

For the reviewer

1. Two files outside the intended scope got a one-line fixture addition each (src/lib/data.test.ts, src/components/DocumentUploadModal.test.tsx), forced by making term required on EnrolledCourse.
2. Landing reads ?semester= from window.location.search in a useState initializer rather than useSearchParams(), which would require a Suspense boundary in the route shell this component doesn't own. It never reaches the rendered tree, so there's no hydration mismatch — but adding the boundary instead is a reasonable alternative.
3. The client's current-term rule is a hand-mirror of the Python one. Test fixtures are migration 0019's four terms verbatim so drift surfaces, but there is no automated cross-language check.
4. The knowledge graph still renders nodes from all terms — only the course lists and legends are term-scoped. Filtering graph data by term is a separate product call.

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

@AndresL230, you've reached your PR review limit, so we couldn't start this review.

Next review available in:54 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Free

Run ID: 39694af7-3514-4235-b33b-03e1297e832a

📥 Commits

Reviewing files that changed from the base of the PR and between 4227689 and c1d6f9b.

📒 Files selected for processing (11)

• frontend/eslint-suppressions.json
• frontend/src/components/DocumentUploadModal.test.tsx
• frontend/src/components/ManageCoursesModal.tsx
• frontend/src/components/screens/Dashboard.test.tsx
• frontend/src/components/screens/Dashboard.tsx
• frontend/src/components/screens/Gradebook/Landing.test.tsx
• frontend/src/components/screens/Gradebook/Landing.tsx
• frontend/src/lib/api.ts
• frontend/src/lib/data.test.ts
• frontend/src/lib/semesters.test.ts
• frontend/src/lib/semesters.ts

---

Note

🎁 Summarized by CodeRabbit Free

Your organization is on the Free plan. CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please upgrade your subscription to CodeRabbit Pro by visiting https://app.coderabbit.ai/login.

_{Comment @coderabbitai help to get the list of available commands.}

[cloudflare-workers-and-pages]

Deploying with Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	frontend-staging	c1d6f9b	Commit Preview URL Branch Preview URL	Jul 22 2026, 04:25 AM

[Jose-Gael-Cruz-Lopez]

@coderabbitai review

[coderabbitai]

✅ Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[Jose-Gael-Cruz-Lopez]

Closes#140.

Groups enrolled classes by semester, defaults to the current term, and puts past terms behind an Archive.

The dependency was already satisfied

#140 is filed as "depends on the backend API issue", but that's stale — nothing was blocking:

• GET /api/semesters already exists and serves {id, term, year, label, start_date, end_date, sort_key}.
• GET /api/graph/{user_id}/courses already returns a term label per course; only the frontend EnrolledCourse interface hadn't declared it.

So this is frontend-only.

It also fixes a live bug

screens/Gradebook/Landing.tsx read (c as any).semester off the courses payload — but the API sends term. The lookup therefore always came back empty and fell through to the hardcoded demo constant:

constSAMPLE_SEMESTERS=["Spring 2026","Fall 2025"];

Every signed-in user was being shown those two fake semester chips instead of their own. The as any is exactly what let the field-name mismatch through the type checker. SAMPLE_SEMESTERS is now strictly the logged-out preview; a signed-in user with no terms gets their own empty state (a termsReady gate keeps that from hanging on the skeleton). Covered by tests.

New src/lib/semesters.ts — one tested source of truth

• currentTerm(semesters, today) mirrors services/academics.py::current_termexactly: the highest-sort_key term whose [start_date, end_date] contains today, falling back to the highest sort_key overall when today lands in a gap between terms. today is injectable. Dates compare as YYYY-MM-DD strings (lexicographic == chronological), and a Date is read in local time — toISOString() would shift the day either side of midnight.
• termRankFromLabel("Fall 2025") -> 20253, mirroring migration 0019's year * 10 + ordinal. Only consulted when no real sort_key is available; sort_key always wins.
• groupCoursesByTerm, courseTermLabels, partitionCurrentAndArchive.

Degradation — the rule is "never hide a course"

If /api/semesters fails or returns nothing, everything collapses to one flat ungrouped list with no Archive control and nothing hidden. Courses with an empty or unparseable term are never dropped and never archived. Future-term courses are never archived. Only a course ranking strictly below the current term is archived — showing a course in the wrong bucket is recoverable, hiding it isn't.

UI

The partition is applied to the "My courses" panel (which is also the mobile courses tab), the graph legend chips, the CoursesKey overlay, and ManageCoursesModal's list. CourseProgressRow was extracted rather than copying that markup a third time. Archived rows route to /gradebook?semester=<label>, which the gradebook landing reads and preselects — so selecting an archived class lands in that semester's gradebook, per the acceptance criteria.

The Calendar is untouched, per the explicit product decision in the issue.

Verification

Gate	Result
npm test	131 passing (baseline 88) — 15 files, +43 tests
npx tsc --noEmit	0 errors
npx eslint . --max-warnings=-1	exit 0, 36 warnings (baseline)
npm run build	exit 0, compiled successfully

One thing worth flagging because it nearly shipped broken: fixing the as any removed the only no-explicit-any in Landing.tsx, which left a stale entry in eslint-suppressions.json. ESLint exits 2 on a stale suppression even with zero errors — main exits 0, this branch did not — so the lint gate would have failed CI. Pruned in its own commit.

For the reviewer

1. Two files outside the intended scope got a one-line fixture addition each (src/lib/data.test.ts, src/components/DocumentUploadModal.test.tsx), forced by making term required on EnrolledCourse.
2. Landing reads ?semester= from window.location.search in a useState initializer rather than useSearchParams(), which would require a Suspense boundary in the route shell this component doesn't own. It never reaches the rendered tree, so there's no hydration mismatch — but adding the boundary instead is a reasonable alternative.
3. The client's current-term rule is a hand-mirror of the Python one. Test fixtures are migration 0019's four terms verbatim so drift surfaces, but there is no automated cross-language check.
4. The knowledge graph still renders nodes from all terms — only the course lists and legends are term-scoped. Filtering graph data by term is a separate product call.

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

@AndresL230, you've reached your PR review limit, so we couldn't start this review.

Next review available in:54 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Free

Run ID: 39694af7-3514-4235-b33b-03e1297e832a

📥 Commits

Reviewing files that changed from the base of the PR and between 4227689 and c1d6f9b.

📒 Files selected for processing (11)

• frontend/eslint-suppressions.json
• frontend/src/components/DocumentUploadModal.test.tsx
• frontend/src/components/ManageCoursesModal.tsx
• frontend/src/components/screens/Dashboard.test.tsx
• frontend/src/components/screens/Dashboard.tsx
• frontend/src/components/screens/Gradebook/Landing.test.tsx
• frontend/src/components/screens/Gradebook/Landing.tsx
• frontend/src/lib/api.ts
• frontend/src/lib/data.test.ts
• frontend/src/lib/semesters.test.ts
• frontend/src/lib/semesters.ts

---

Note

🎁 Summarized by CodeRabbit Free

Your organization is on the Free plan. CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please upgrade your subscription to CodeRabbit Pro by visiting https://app.coderabbit.ai/login.

_{Comment @coderabbitai help to get the list of available commands.}

[cloudflare-workers-and-pages]

Deploying with Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	frontend-staging	c1d6f9b	Commit Preview URL Branch Preview URL	Jul 22 2026, 04:25 AM

[Jose-Gael-Cruz-Lopez]

@coderabbitai review

[coderabbitai]

✅ Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[Jose-Gael-Cruz-Lopez]

Closes#140.

Groups enrolled classes by semester, defaults to the current term, and puts past terms behind an Archive.

The dependency was already satisfied

#140 is filed as "depends on the backend API issue", but that's stale — nothing was blocking:

• GET /api/semesters already exists and serves {id, term, year, label, start_date, end_date, sort_key}.
• GET /api/graph/{user_id}/courses already returns a term label per course; only the frontend EnrolledCourse interface hadn't declared it.

So this is frontend-only.

It also fixes a live bug

screens/Gradebook/Landing.tsx read (c as any).semester off the courses payload — but the API sends term. The lookup therefore always came back empty and fell through to the hardcoded demo constant:

constSAMPLE_SEMESTERS=["Spring 2026","Fall 2025"];

Every signed-in user was being shown those two fake semester chips instead of their own. The as any is exactly what let the field-name mismatch through the type checker. SAMPLE_SEMESTERS is now strictly the logged-out preview; a signed-in user with no terms gets their own empty state (a termsReady gate keeps that from hanging on the skeleton). Covered by tests.

New src/lib/semesters.ts — one tested source of truth

• currentTerm(semesters, today) mirrors services/academics.py::current_termexactly: the highest-sort_key term whose [start_date, end_date] contains today, falling back to the highest sort_key overall when today lands in a gap between terms. today is injectable. Dates compare as YYYY-MM-DD strings (lexicographic == chronological), and a Date is read in local time — toISOString() would shift the day either side of midnight.
• termRankFromLabel("Fall 2025") -> 20253, mirroring migration 0019's year * 10 + ordinal. Only consulted when no real sort_key is available; sort_key always wins.
• groupCoursesByTerm, courseTermLabels, partitionCurrentAndArchive.

Degradation — the rule is "never hide a course"

If /api/semesters fails or returns nothing, everything collapses to one flat ungrouped list with no Archive control and nothing hidden. Courses with an empty or unparseable term are never dropped and never archived. Future-term courses are never archived. Only a course ranking strictly below the current term is archived — showing a course in the wrong bucket is recoverable, hiding it isn't.

UI

The partition is applied to the "My courses" panel (which is also the mobile courses tab), the graph legend chips, the CoursesKey overlay, and ManageCoursesModal's list. CourseProgressRow was extracted rather than copying that markup a third time. Archived rows route to /gradebook?semester=<label>, which the gradebook landing reads and preselects — so selecting an archived class lands in that semester's gradebook, per the acceptance criteria.

The Calendar is untouched, per the explicit product decision in the issue.

Verification

Gate	Result
npm test	131 passing (baseline 88) — 15 files, +43 tests
npx tsc --noEmit	0 errors
npx eslint . --max-warnings=-1	exit 0, 36 warnings (baseline)
npm run build	exit 0, compiled successfully

One thing worth flagging because it nearly shipped broken: fixing the as any removed the only no-explicit-any in Landing.tsx, which left a stale entry in eslint-suppressions.json. ESLint exits 2 on a stale suppression even with zero errors — main exits 0, this branch did not — so the lint gate would have failed CI. Pruned in its own commit.

For the reviewer

1. Two files outside the intended scope got a one-line fixture addition each (src/lib/data.test.ts, src/components/DocumentUploadModal.test.tsx), forced by making term required on EnrolledCourse.
2. Landing reads ?semester= from window.location.search in a useState initializer rather than useSearchParams(), which would require a Suspense boundary in the route shell this component doesn't own. It never reaches the rendered tree, so there's no hydration mismatch — but adding the boundary instead is a reasonable alternative.
3. The client's current-term rule is a hand-mirror of the Python one. Test fixtures are migration 0019's four terms verbatim so drift surfaces, but there is no automated cross-language check.
4. The knowledge graph still renders nodes from all terms — only the course lists and legends are term-scoped. Filtering graph data by term is a separate product call.

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

@AndresL230, you've reached your PR review limit, so we couldn't start this review.

Next review available in:54 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Free

Run ID: 39694af7-3514-4235-b33b-03e1297e832a

📥 Commits

Reviewing files that changed from the base of the PR and between 4227689 and c1d6f9b.

📒 Files selected for processing (11)

• frontend/eslint-suppressions.json
• frontend/src/components/DocumentUploadModal.test.tsx
• frontend/src/components/ManageCoursesModal.tsx
• frontend/src/components/screens/Dashboard.test.tsx
• frontend/src/components/screens/Dashboard.tsx
• frontend/src/components/screens/Gradebook/Landing.test.tsx
• frontend/src/components/screens/Gradebook/Landing.tsx
• frontend/src/lib/api.ts
• frontend/src/lib/data.test.ts
• frontend/src/lib/semesters.test.ts
• frontend/src/lib/semesters.ts

---

Note

🎁 Summarized by CodeRabbit Free

Your organization is on the Free plan. CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please upgrade your subscription to CodeRabbit Pro by visiting https://app.coderabbit.ai/login.

_{Comment @coderabbitai help to get the list of available commands.}

[cloudflare-workers-and-pages]

Deploying with Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	frontend-staging	c1d6f9b	Commit Preview URL Branch Preview URL	Jul 22 2026, 04:25 AM

[Jose-Gael-Cruz-Lopez]

@coderabbitai review

[coderabbitai]

✅ Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[Jose-Gael-Cruz-Lopez]

Closes#140.

Groups enrolled classes by semester, defaults to the current term, and puts past terms behind an Archive.

The dependency was already satisfied

#140 is filed as "depends on the backend API issue", but that's stale — nothing was blocking:

• GET /api/semesters already exists and serves {id, term, year, label, start_date, end_date, sort_key}.
• GET /api/graph/{user_id}/courses already returns a term label per course; only the frontend EnrolledCourse interface hadn't declared it.

So this is frontend-only.

It also fixes a live bug

screens/Gradebook/Landing.tsx read (c as any).semester off the courses payload — but the API sends term. The lookup therefore always came back empty and fell through to the hardcoded demo constant:

constSAMPLE_SEMESTERS=["Spring 2026","Fall 2025"];

Every signed-in user was being shown those two fake semester chips instead of their own. The as any is exactly what let the field-name mismatch through the type checker. SAMPLE_SEMESTERS is now strictly the logged-out preview; a signed-in user with no terms gets their own empty state (a termsReady gate keeps that from hanging on the skeleton). Covered by tests.

New src/lib/semesters.ts — one tested source of truth

• currentTerm(semesters, today) mirrors services/academics.py::current_termexactly: the highest-sort_key term whose [start_date, end_date] contains today, falling back to the highest sort_key overall when today lands in a gap between terms. today is injectable. Dates compare as YYYY-MM-DD strings (lexicographic == chronological), and a Date is read in local time — toISOString() would shift the day either side of midnight.
• termRankFromLabel("Fall 2025") -> 20253, mirroring migration 0019's year * 10 + ordinal. Only consulted when no real sort_key is available; sort_key always wins.
• groupCoursesByTerm, courseTermLabels, partitionCurrentAndArchive.

Degradation — the rule is "never hide a course"

If /api/semesters fails or returns nothing, everything collapses to one flat ungrouped list with no Archive control and nothing hidden. Courses with an empty or unparseable term are never dropped and never archived. Future-term courses are never archived. Only a course ranking strictly below the current term is archived — showing a course in the wrong bucket is recoverable, hiding it isn't.

UI

The partition is applied to the "My courses" panel (which is also the mobile courses tab), the graph legend chips, the CoursesKey overlay, and ManageCoursesModal's list. CourseProgressRow was extracted rather than copying that markup a third time. Archived rows route to /gradebook?semester=<label>, which the gradebook landing reads and preselects — so selecting an archived class lands in that semester's gradebook, per the acceptance criteria.

The Calendar is untouched, per the explicit product decision in the issue.

Verification

Gate	Result
npm test	131 passing (baseline 88) — 15 files, +43 tests
npx tsc --noEmit	0 errors
npx eslint . --max-warnings=-1	exit 0, 36 warnings (baseline)
npm run build	exit 0, compiled successfully

One thing worth flagging because it nearly shipped broken: fixing the as any removed the only no-explicit-any in Landing.tsx, which left a stale entry in eslint-suppressions.json. ESLint exits 2 on a stale suppression even with zero errors — main exits 0, this branch did not — so the lint gate would have failed CI. Pruned in its own commit.

For the reviewer

1. Two files outside the intended scope got a one-line fixture addition each (src/lib/data.test.ts, src/components/DocumentUploadModal.test.tsx), forced by making term required on EnrolledCourse.
2. Landing reads ?semester= from window.location.search in a useState initializer rather than useSearchParams(), which would require a Suspense boundary in the route shell this component doesn't own. It never reaches the rendered tree, so there's no hydration mismatch — but adding the boundary instead is a reasonable alternative.
3. The client's current-term rule is a hand-mirror of the Python one. Test fixtures are migration 0019's four terms verbatim so drift surfaces, but there is no automated cross-language check.
4. The knowledge graph still renders nodes from all terms — only the course lists and legends are term-scoped. Filtering graph data by term is a separate product call.

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

@AndresL230, you've reached your PR review limit, so we couldn't start this review.

Next review available in:54 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Free

Run ID: 39694af7-3514-4235-b33b-03e1297e832a

📥 Commits

Reviewing files that changed from the base of the PR and between 4227689 and c1d6f9b.

📒 Files selected for processing (11)

• frontend/eslint-suppressions.json
• frontend/src/components/DocumentUploadModal.test.tsx
• frontend/src/components/ManageCoursesModal.tsx
• frontend/src/components/screens/Dashboard.test.tsx
• frontend/src/components/screens/Dashboard.tsx
• frontend/src/components/screens/Gradebook/Landing.test.tsx
• frontend/src/components/screens/Gradebook/Landing.tsx
• frontend/src/lib/api.ts
• frontend/src/lib/data.test.ts
• frontend/src/lib/semesters.test.ts
• frontend/src/lib/semesters.ts

---

Note

🎁 Summarized by CodeRabbit Free

Your organization is on the Free plan. CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please upgrade your subscription to CodeRabbit Pro by visiting https://app.coderabbit.ai/login.

_{Comment @coderabbitai help to get the list of available commands.}

[cloudflare-workers-and-pages]

Deploying with Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	frontend-staging	c1d6f9b	Commit Preview URL Branch Preview URL	Jul 22 2026, 04:25 AM

[Jose-Gael-Cruz-Lopez]

@coderabbitai review

[coderabbitai]

✅ Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[Jose-Gael-Cruz-Lopez]

Closes#140.

Groups enrolled classes by semester, defaults to the current term, and puts past terms behind an Archive.

The dependency was already satisfied

#140 is filed as "depends on the backend API issue", but that's stale — nothing was blocking:

• GET /api/semesters already exists and serves {id, term, year, label, start_date, end_date, sort_key}.
• GET /api/graph/{user_id}/courses already returns a term label per course; only the frontend EnrolledCourse interface hadn't declared it.

So this is frontend-only.

It also fixes a live bug

screens/Gradebook/Landing.tsx read (c as any).semester off the courses payload — but the API sends term. The lookup therefore always came back empty and fell through to the hardcoded demo constant:

constSAMPLE_SEMESTERS=["Spring 2026","Fall 2025"];

Every signed-in user was being shown those two fake semester chips instead of their own. The as any is exactly what let the field-name mismatch through the type checker. SAMPLE_SEMESTERS is now strictly the logged-out preview; a signed-in user with no terms gets their own empty state (a termsReady gate keeps that from hanging on the skeleton). Covered by tests.

New src/lib/semesters.ts — one tested source of truth

• currentTerm(semesters, today) mirrors services/academics.py::current_termexactly: the highest-sort_key term whose [start_date, end_date] contains today, falling back to the highest sort_key overall when today lands in a gap between terms. today is injectable. Dates compare as YYYY-MM-DD strings (lexicographic == chronological), and a Date is read in local time — toISOString() would shift the day either side of midnight.
• termRankFromLabel("Fall 2025") -> 20253, mirroring migration 0019's year * 10 + ordinal. Only consulted when no real sort_key is available; sort_key always wins.
• groupCoursesByTerm, courseTermLabels, partitionCurrentAndArchive.

Degradation — the rule is "never hide a course"

If /api/semesters fails or returns nothing, everything collapses to one flat ungrouped list with no Archive control and nothing hidden. Courses with an empty or unparseable term are never dropped and never archived. Future-term courses are never archived. Only a course ranking strictly below the current term is archived — showing a course in the wrong bucket is recoverable, hiding it isn't.

UI

The partition is applied to the "My courses" panel (which is also the mobile courses tab), the graph legend chips, the CoursesKey overlay, and ManageCoursesModal's list. CourseProgressRow was extracted rather than copying that markup a third time. Archived rows route to /gradebook?semester=<label>, which the gradebook landing reads and preselects — so selecting an archived class lands in that semester's gradebook, per the acceptance criteria.

The Calendar is untouched, per the explicit product decision in the issue.

Verification

Gate	Result
npm test	131 passing (baseline 88) — 15 files, +43 tests
npx tsc --noEmit	0 errors
npx eslint . --max-warnings=-1	exit 0, 36 warnings (baseline)
npm run build	exit 0, compiled successfully

One thing worth flagging because it nearly shipped broken: fixing the as any removed the only no-explicit-any in Landing.tsx, which left a stale entry in eslint-suppressions.json. ESLint exits 2 on a stale suppression even with zero errors — main exits 0, this branch did not — so the lint gate would have failed CI. Pruned in its own commit.

For the reviewer

1. Two files outside the intended scope got a one-line fixture addition each (src/lib/data.test.ts, src/components/DocumentUploadModal.test.tsx), forced by making term required on EnrolledCourse.
2. Landing reads ?semester= from window.location.search in a useState initializer rather than useSearchParams(), which would require a Suspense boundary in the route shell this component doesn't own. It never reaches the rendered tree, so there's no hydration mismatch — but adding the boundary instead is a reasonable alternative.
3. The client's current-term rule is a hand-mirror of the Python one. Test fixtures are migration 0019's four terms verbatim so drift surfaces, but there is no automated cross-language check.
4. The knowledge graph still renders nodes from all terms — only the course lists and legends are term-scoped. Filtering graph data by term is a separate product call.

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

@AndresL230, you've reached your PR review limit, so we couldn't start this review.

Next review available in:54 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Free

Run ID: 39694af7-3514-4235-b33b-03e1297e832a

📥 Commits

Reviewing files that changed from the base of the PR and between 4227689 and c1d6f9b.

📒 Files selected for processing (11)

• frontend/eslint-suppressions.json
• frontend/src/components/DocumentUploadModal.test.tsx
• frontend/src/components/ManageCoursesModal.tsx
• frontend/src/components/screens/Dashboard.test.tsx
• frontend/src/components/screens/Dashboard.tsx
• frontend/src/components/screens/Gradebook/Landing.test.tsx
• frontend/src/components/screens/Gradebook/Landing.tsx
• frontend/src/lib/api.ts
• frontend/src/lib/data.test.ts
• frontend/src/lib/semesters.test.ts
• frontend/src/lib/semesters.ts

---

Note

🎁 Summarized by CodeRabbit Free

Your organization is on the Free plan. CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please upgrade your subscription to CodeRabbit Pro by visiting https://app.coderabbit.ai/login.

_{Comment @coderabbitai help to get the list of available commands.}

[cloudflare-workers-and-pages]

Deploying with Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	frontend-staging	c1d6f9b	Commit Preview URL Branch Preview URL	Jul 22 2026, 04:25 AM

[Jose-Gael-Cruz-Lopez]

@coderabbitai review

[coderabbitai]

✅ Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[Jose-Gael-Cruz-Lopez]

Closes#140.

Groups enrolled classes by semester, defaults to the current term, and puts past terms behind an Archive.

The dependency was already satisfied

#140 is filed as "depends on the backend API issue", but that's stale — nothing was blocking:

• GET /api/semesters already exists and serves {id, term, year, label, start_date, end_date, sort_key}.
• GET /api/graph/{user_id}/courses already returns a term label per course; only the frontend EnrolledCourse interface hadn't declared it.

So this is frontend-only.

It also fixes a live bug

screens/Gradebook/Landing.tsx read (c as any).semester off the courses payload — but the API sends term. The lookup therefore always came back empty and fell through to the hardcoded demo constant:

constSAMPLE_SEMESTERS=["Spring 2026","Fall 2025"];

Every signed-in user was being shown those two fake semester chips instead of their own. The as any is exactly what let the field-name mismatch through the type checker. SAMPLE_SEMESTERS is now strictly the logged-out preview; a signed-in user with no terms gets their own empty state (a termsReady gate keeps that from hanging on the skeleton). Covered by tests.

New src/lib/semesters.ts — one tested source of truth

• currentTerm(semesters, today) mirrors services/academics.py::current_termexactly: the highest-sort_key term whose [start_date, end_date] contains today, falling back to the highest sort_key overall when today lands in a gap between terms. today is injectable. Dates compare as YYYY-MM-DD strings (lexicographic == chronological), and a Date is read in local time — toISOString() would shift the day either side of midnight.
• termRankFromLabel("Fall 2025") -> 20253, mirroring migration 0019's year * 10 + ordinal. Only consulted when no real sort_key is available; sort_key always wins.
• groupCoursesByTerm, courseTermLabels, partitionCurrentAndArchive.

Degradation — the rule is "never hide a course"

If /api/semesters fails or returns nothing, everything collapses to one flat ungrouped list with no Archive control and nothing hidden. Courses with an empty or unparseable term are never dropped and never archived. Future-term courses are never archived. Only a course ranking strictly below the current term is archived — showing a course in the wrong bucket is recoverable, hiding it isn't.

UI

The partition is applied to the "My courses" panel (which is also the mobile courses tab), the graph legend chips, the CoursesKey overlay, and ManageCoursesModal's list. CourseProgressRow was extracted rather than copying that markup a third time. Archived rows route to /gradebook?semester=<label>, which the gradebook landing reads and preselects — so selecting an archived class lands in that semester's gradebook, per the acceptance criteria.

The Calendar is untouched, per the explicit product decision in the issue.

Verification

Gate	Result
npm test	131 passing (baseline 88) — 15 files, +43 tests
npx tsc --noEmit	0 errors
npx eslint . --max-warnings=-1	exit 0, 36 warnings (baseline)
npm run build	exit 0, compiled successfully

One thing worth flagging because it nearly shipped broken: fixing the as any removed the only no-explicit-any in Landing.tsx, which left a stale entry in eslint-suppressions.json. ESLint exits 2 on a stale suppression even with zero errors — main exits 0, this branch did not — so the lint gate would have failed CI. Pruned in its own commit.

For the reviewer

1. Two files outside the intended scope got a one-line fixture addition each (src/lib/data.test.ts, src/components/DocumentUploadModal.test.tsx), forced by making term required on EnrolledCourse.
2. Landing reads ?semester= from window.location.search in a useState initializer rather than useSearchParams(), which would require a Suspense boundary in the route shell this component doesn't own. It never reaches the rendered tree, so there's no hydration mismatch — but adding the boundary instead is a reasonable alternative.
3. The client's current-term rule is a hand-mirror of the Python one. Test fixtures are migration 0019's four terms verbatim so drift surfaces, but there is no automated cross-language check.
4. The knowledge graph still renders nodes from all terms — only the course lists and legends are term-scoped. Filtering graph data by term is a separate product call.

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

@AndresL230, you've reached your PR review limit, so we couldn't start this review.

Next review available in:54 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Free

Run ID: 39694af7-3514-4235-b33b-03e1297e832a

📥 Commits

Reviewing files that changed from the base of the PR and between 4227689 and c1d6f9b.

📒 Files selected for processing (11)

• frontend/eslint-suppressions.json
• frontend/src/components/DocumentUploadModal.test.tsx
• frontend/src/components/ManageCoursesModal.tsx
• frontend/src/components/screens/Dashboard.test.tsx
• frontend/src/components/screens/Dashboard.tsx
• frontend/src/components/screens/Gradebook/Landing.test.tsx
• frontend/src/components/screens/Gradebook/Landing.tsx
• frontend/src/lib/api.ts
• frontend/src/lib/data.test.ts
• frontend/src/lib/semesters.test.ts
• frontend/src/lib/semesters.ts

---

Note

🎁 Summarized by CodeRabbit Free

Your organization is on the Free plan. CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please upgrade your subscription to CodeRabbit Pro by visiting https://app.coderabbit.ai/login.

_{Comment @coderabbitai help to get the list of available commands.}

[cloudflare-workers-and-pages]

Deploying with Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	frontend-staging	c1d6f9b	Commit Preview URL Branch Preview URL	Jul 22 2026, 04:25 AM

[Jose-Gael-Cruz-Lopez]

@coderabbitai review

[coderabbitai]

✅ Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.