[Tech-debt] `quizStore` has no persistence — quiz state is lost on page refresh

[RUKAYAT-CODER]

Overview

src/app/store/quizStore.ts uses Zustand without a persist middleware. A user mid-quiz who refreshes the page loses all their answers, timing data, and current question index. This forces users to restart quizzes from scratch and creates a frustrating experience especially on poor network connections where refreshes are common.

Specifications

Features:

• Active quiz state is persisted to sessionStorage so a page refresh resumes the quiz
• Completed quiz results are persisted to localStorage for review

Tasks:

• Add Zustand persist middleware to quizStore using sessionStorage as the storage engine
• Persist: currentQuiz, currentQuestionIndex, answers, startTime, reviewMode
• On endQuiz, move completed quiz data to a separate localStorage key for history
• Add a test that simulates store rehydration and asserts the quiz resumes correctly

Impacted Files:

• src/app/store/quizStore.ts

Acceptance Criteria

• Refreshing the browser during a quiz restores the current question and all answers
• Completed quiz results are accessible after the quiz session ends
• Quiz state is cleared from sessionStorage after a quiz is submitted

[heymide]

@heymide has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

I've reviewed the task and have a clear implementation plan. Looking forward to contributing with a quality PR.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @heymide to this issue.

[jotel-dev]

@jotel-dev has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Pls Assign me

ℹ️ Repo Maintainers: To accept this application, review their application or assign @jotel-dev to this issue.

[deslawson]

@deslawson has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Id love to work on this

ℹ️ Repo Maintainers: To accept this application, review their application or assign @deslawson to this issue.

[meem08]

@meem08 has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

I would like to work on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @meem08 to this issue.

[drips-wave]

Congratulations, @deslawson! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @deslawson: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊