feat: add severity filter support in findings dashboard

[swathiyara9-ai]

Linked issue

Closes #39

What this PR does

Adds severity-based filtering to the Findings dashboard. Users can filter findings by Critical, High, Medium, and Low severity levels. The findings table updates dynamically based on selected filters, and filter selections are preserved using URL search parameters for improved navigation and triage workflows.

Type of change

• Bug fix
• New feature
• ML model / training pipeline
• Refactor (no behaviour change)
• Documentation
• Tests only

ML tier (if applicable)

• Tier 1 — Triage
• Tier 2 — Predictive
• Tier 3 — Autonomous
• Not ML-related

Stack affected

• Backend
• Frontend
• Both

---

Changes

Backend

• None

Frontend

• Added Critical, High, Medium, and Low severity filter options.
• Implemented dynamic filtering of findings based on selected severities.
• Preserved filter state using URL search parameters.
• Improved findings triage workflow and user experience.

New dependencies

• None

Database / schema changes

• None

---

Testing

How did you test this?

Tested locally by running the frontend application and verifying individual and multiple severity filter selections. Confirmed that findings update dynamically based on selected filters and that filter state persists during navigation and page refresh. Also verified that URL search parameters correctly preserve selected severity filters.

Checklist

• Tested locally end-to-end (upload ZIP or GitHub URL → scan → findings returned correctly)
• New ML model falls back gracefully when model file is absent
• No new "console.error" or unhandled Python exceptions introduced
• Added or updated tests where applicable
• "requirements.txt" / "package.json" updated if new dependencies added
• New model files (".pkl", ".pt", etc.) are gitignored, not committed

---

Anything reviewers should focus on

Please review the severity filtering logic, URL state persistence implementation, and interaction between severity filters and findings table updates in "frontend/src/app/pages/findings.tsx".

Screenshots (if UI changed)

• Added severity filter chips (Critical, High, Medium, Low) to the Findings dashboard.
• Verified dynamic filtering of findings based on selected severity levels.
• Screenshot attached in the PR showing the filter functionality in action.

[github-actions]

⚠️ Automated Check: This PR does not strictly follow the required template. Please ensure you have not deleted any checkboxes or mandatory headings, and that you have written explanations under What this PR does and How did you test this?.

[ionfwsrijan]

@swathiyara9-ai Please fix failing checks

[swathiyara9-ai]

Hi! @ionfwsrijan I noticed that a PR implementing Issue #39 has already been merged after I opened my PR. My branch now shows conflicts with the updated "main" branch. Since the issue appears to be resolved, please let me know if any further changes are needed from my side. Thank you for your review.

[ionfwsrijan]

@swathiyara9-ai Fix merge conflicts and PR description.