Skip to content

fix: enforce exact question count per category (CT-74)#44

Merged
RBanner merged 1 commit into
mainfrom
fix/CT-74-question-count
Jul 16, 2026
Merged

fix: enforce exact question count per category (CT-74)#44
RBanner merged 1 commit into
mainfrom
fix/CT-74-question-count

Conversation

@ThanasisSoftwareDeveloper

Copy link
Copy Markdown
Contributor

Summary

Describe what this PR changes and why.


Type of Change

  • Feature
  • Bug fix
  • Refactor
  • Documentation
  • Test
  • Chore

Changes


Testing

  • npm run lint
  • npm test
  • npm run build
  • Manual browser check, if UI or workflow changed

If any check was skipped, explain why:

N/A

Screenshots or Recording

Add screenshots or a short recording for UI changes.

N/A

DashFetch Workflow Impact

Check any flow touched by this PR:

  • Job description paste/upload
  • File parsing
  • Job summary extraction
  • Interview question generation
  • Mock interview practice
  • Session storage/navigation
  • API routes
  • Supabase schema or data access
  • Groq prompt or AI response normalization
  • No user-facing workflow changed

Deployment Notes

  • No deployment notes
  • Environment variables changed
  • Supabase schema changed
  • Next.js config or route behavior changed
  • Dependencies changed

Details:

N/A

Linked Issues

Closes #


Reviewer Notes

Mention tradeoffs, follow-up work, or areas where you want focused review.

N/A

@RBanner RBanner left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed and Approved.

@RBanner
RBanner merged commit 4293ef6 into main Jul 16, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants