Restore interview settings when retrying

[yuuka5555]

Summary

Try Again previously restored only the selected problem, requiring candidates to choose the interview settings again.

This change restores the previous attempt's:

• Interview duration
• Coding-only or coding + behavioral loop
• Editor or whiteboard mode

It also remembers lobby settings across reloads, preserves current duration limits, and explains when a saved duration must be adjusted. Older attempts without saved settings use the existing defaults.

Closes #207

Validation

• Manually confirmed that Try Again restores the attempt's problem and settings.
• Affected test suites: 194 passed, no failures.
• Rust library tests in a clean checkout with Unix line endings: 720 passed, 8 ignored.
• Controlled browser comparison: the unchanged baseline had 981 passing tests and 5 failures; this branch had 993 passing tests and the same 5 failures.
• Prettier, ESLint, Rust formatting, and Clippy passed.

The full local Windows verification gate did not pass. Investigation traced the remaining failures to Windows paths, line endings, and existing test-harness issues. No new failures appeared in the browser comparison. Some optional checks were skipped because their tools were unavailable.

---

Summary by cubic

Try Again now restores the previous attempt's interview settings (duration, loop, and mode) so candidates don't have to re-choose them. Lobby settings are remembered across reloads, and saved durations are adjusted when they exceed the current cap. Closes #207. Browser test editor setup now waits for delayed problem initialization before clearing the starter buffer.

Details

• Saves interviewMode in history entries alongside duration and loop, and restores settings from account or device history.
• Ignores Try Again, loop, and duration clicks while an interview start is pending, and falls back to defaults for older attempts without saved settings.
• Uses the server limit and explains it when no offered duration fits the cap; only explicit duration choices are saved.
• Invalid or blocked preference storage still leaves the lobby usable.
• Adds delayed-response coverage for the editor initialization race.

Validation

• 224 combined browser tests pass (including new coverage for retry settings, preference persistence, pending starts, duration limits, editor initialization, and invalid storage); Rust library tests pass (720 passed, 8 ignored).

^{Written for commit ed5b88b. Summary will update on new commits.}

[ColtenOuO]

Please include a commit body to make it easier to track for future collaboration.

[yuuka5555]

@ColtenOuO Thanks for the feedback. I added explanatory bodies to both commits and pushed the updated history. Could you review the updated commit messages?

[ColtenOuO]

The code changes look good to me, but could you squash the commits into one (since the second commit just fixes an issue introduced by the first)?

Please also update the commit title or body accordingly after squashing.

[yuuka5555]

@ColtenOuO Thanks for reviewing. I squashed the two commits into one, updated the commit message to describe the complete change, and pushed the updated history.

[jserv]

Rebase latest main branch and resolve conflicts.

[yuuka5555]

Rebased onto the latest main and resolved the conflict while preserving the editor-options behavior. All 203 affected tests pass.

[jserv]

Resolve regressions raised by CI.

[yuuka5555]

@jserv Could you rerun the failed check job? It timed out while clearing the editor during setup for “a loaded grammar replaces cached fallback ranges without an edit.”

I reran the complete editor-pipeline suite locally: all 17 tests passed. This PR does not modify the editor implementation or that test. I don’t have permission to rerun the upstream workflow.

[jserv]

I reran the complete editor-pipeline suite locally: all 17 tests passed. This PR does not modify the editor implementation or that test. I don’t have permission to rerun the upstream workflow.

Do more analysis and refinements.

[yuuka5555]

I reproduced an initialization race by holding the problem response. The textarea is already enabled in the initial HTML, so the old helper could clear it before initialization later inserted starter code.

Updated the helper to wait until editor initialization completes and added a delayed-response regression test. The test fails with the old readiness check and passes with the refinement. All 221 combined tests pass locally, along with ESLint and Prettier.

[ColtenOuO]

Dismiss approval

There's no need to include 'All 224 combined tests pass' in the commit body.

Please focus the commit message on the changes themselves -- why they were made and what was changed.

[yuuka5555]

Updated the commit body to focus on the changes and their rationale, and removed the test-result statement.

[ColtenOuO]

Thanks, LGTM.

[jserv]

Thank @yuuka5555 for contributing!