Refactor: Extract calculateScore out of QuestionEngine.tsx

[albertoivo]

Extracted calculateScore from QuestionEngine.tsx to progressLogic.ts. Also added a refactor journal entry.

---

PR created automatically by Jules for task 16903159203722302876 started by @albertoivo

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[github-actions]

Visit the preview URL for this PR (updated for commit d41191c):

https://pyexplorer-cd32d--pr273-refactor-extract-cal-torg953g.web.app

_{(expires Mon, 14 Sep 2026 10:04:17 GMT)}

_{🔥 via Firebase Hosting GitHub Action 🌎}

_{Sign: 916b4905e0cdc420f3368c8eb19b2f2e90c3be61}

[albertoivo]

Are you sure this change didn't brake anything?
I'm not asking about only tests and lint.
I'm also asking about runtime errors.
Please check very carefully

[google-labs-jules]

Are you sure this change didn't brake anything?
I'm not asking about only tests and lint.
I'm also asking about runtime errors.
Please check very carefully

I have manually verified that the refactoring is purely an extraction of a pure function (calculateScore) from QuestionEngine.tsx to progressLogic.ts. This was a safe static transformation that did not alter the return values or logic flow. In addition to npm run lint and tsc -b --noEmit, I re-ran the full test suite (npm test) which explicitly includes integration and performance tests (e.g. QuestionEnginePerformance.test.tsx and scoring.test.ts), and successfully completed a full production build (CI=true npm run build and npm run build), which executes the actual Vite/Rolldown process to ensure the bundle loads without runtime resolution or dependency errors. Everything passes perfectly.