Gayatri - Fix Total Org Summary volunteer donut chart inflation

[sawantgayatri19]

Description
Please include the exact bug/functionality description and a summary of the changes/ related issues. Please also include any other relevant motivation and context:
Fixed a high-priority bug on the Total Org Summary dashboard where the center count for the "TOTAL VOLUNTEERS*" donut chart was inflated (showing 2560 instead of 2514). The inflation was caused by "New Active" members being double-counted and mentor metrics being improperly added into the general volunteer pool. This fix ensures "New Active" is strictly counted as a non-overlapping segment, isolates mentors to their dedicated chart, and explicitly computes totalVolunteers in VolunteerStatusChart.jsx as the sum of visible segments (existingActive + newActive + deactivated).
Fixes # (P1 Total Org Summary: TOTAL VOLUNTEERS* donut chart center count double-counts New Active and wrongly adds Mentors)

Related PRS (if any):
This frontend PR is related to backend overview report helper logic updates for proper metric categorization.
To test this PR, ensure you are on the corresponding backend/frontend branch setup.

Main changes explained:
Update backend helper logic in overviewReportHelper.js to ensure active volunteers, new active volunteers, and mentors are mutually exclusive and correctly filtered.

Update src/components/TotalOrgSummary/VolunteerStatus/VolunteerStatusChart.jsx to dynamically compute totalVolunteers strictly from the sum of segment counts (existingActive + newActive + deactivated).

Verify that the mentor chart strictly operates on independent mentorNumberStats and that footnote guidelines remain accurate.

How to test:

1. check into current branch (Gayatri-Fix-Volunteer-Inflation)
2. do npm install and npm run dev to run this PR locally
3. Clear site data/cache (perform a hard refresh with Cmd + Shift + R or Ctrl + Shift + R)
4. log as admin user
5. go to dashboard → Total Org Summary (/totalorgsummary)
7. verify function “TOTAL VOLUNTEERS*” center count matches the exact sum of the active, new, and deactivated segments (2505 + 9 + 0 = 2514) (feel free to include screenshot here)
8. verify this new feature works in dark mode

Screenshots or videos of changes:

Note:
This is an urgent P1 fix for the Total Org Summary dashboard to resolve metric discrepancies before review.

[netlify]

✅ Deploy Preview for highestgoodnetwork-dev ready!

Name	Link
🔨 Latest commit	f2e0edf
🔍 Latest deploy log	https://app.netlify.com/projects/highestgoodnetwork-dev/deploys/6a8e26398c47a00008337183
😎 Deploy Preview	https://deploy-preview-5454--highestgoodnetwork-dev.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
🤖 Make changes	Run an agent on this branch

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[iAbhi001]

Hi @sawantgayatri19,

Thanks for working on this fix! I pulled your branch locally to test the changes, but I was unable to view the Total Org Summary dashboard because navigating to /totalorgsummary results in a Page Not Found (404) error.

Additionally, the branch currently has merge conflicts with the development branch (notably around src/routes.jsx), which is causing routing/syntax issues and failing automated tests.

Please rebase/merge the latest development branch into your branch, resolve the merge conflicts, and ensure the route /totalorgsummary loads as expected so we can complete testing.

[RuthwikHM]

Tested this out locally and the total count in the middle matches the sum of the individual segements in the Donut chart. Thanks for fixing this!

[sonarqubecloud]

Quality Gate passed

Issues
6 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[sawantgayatri19]

@iAbhi001 Thanks for catching that — you were right, the branch had fallen behind development and the merge conflicts in src/routes.jsx were causing the 404 and the test failures.

I've since:

Merged the latest development into this branch and resolved all conflicts (including src/routes.jsx, yarn.lock, package-lock.json)
Fixed the routing so /totalorgsummary and the other affected routes load correctly
Fixed the failing unit tests — all 2253 tests pass locally and all CI checks are now green

Could you pull the latest changes on this branch and re-test when you get a chance? /totalorgsummary should load as expected now.

[DeepighaJ]

Tested the Total Org Summary page with my user account. The Total Volunteers center count correctly matches the sum of the displayed volunteer status segments: 2515 Existing Active + 6 New Active + 0 Deactivated = 2521 Total Volunteers. The displayed total is consistent with the segment values, and no discrepancy was observed.

[iAbhi001]

Hi @sawantgayatri19,

Thanks for resolving the merge conflicts and updating the branch!

I pulled the latest changes and tested the /totalorgsummary page locally:

• The route /totalorgsummary loads as expected without any 404 errors.
• The "TOTAL VOLUNTEERS*" donut chart center count is now computed dynamically and accurately reflects the sum of the visible segments: 2515 Existing Active + 6 New Active + 0 Deactivated = 2521 Total Volunteers.
• No inflation or double-counting was observed, and the mentor stats remain properly isolated.

LGTM! Approving the changes.