Add LeetCode problem reference to completed interview reports

[kuanlin1227]

Motivation

The interview flow intentionally presents each problem as a scenario rather than exposing its original LeetCode identity during the session.

However, after completing an interview, users may want to revisit the original LeetCode problem for further practice, comparison, or review. Currently, this requires manually searching for the corresponding problem.

Providing the original LeetCode problem name and link after the interview would make post-interview review more convenient without affecting the interview experience itself.

Proposal

The LeetCode reference should only be shown after the interview has been completed.

When the user opens the report for a completed interview, the original LeetCode problem should be displayed directly below the report title.

For example:

Interview Report

Original problem: Two Sum

Two Sum should be a clickable link that opens the corresponding LeetCode problem page.

The expected user flow is:

1. Complete an interview.
2. Open the generated report, either immediately after the interview or later through Past attempts.
3. See the original LeetCode problem name directly below the report title.
4. Click the problem name to open the corresponding LeetCode page for further review or practice.

The original problem name and link should not be shown during the active interview. This preserves the scenario-based interview flow introduced in PR [#38](#38), while still giving users an easy way to find the original problem once the interview is over.

[jserv]

@kuanlin1227 Most of the first half is already in the lobby. Past attempts lists every saved report, PR #26 made that history visible, PR #121 collapses an opened report again, and PR #138 deletes a single attempt. Open PR #108 then adds topic and practice status filters over that same list, which is the browsing problem described here.

So what is genuinely new in this issue is the LeetCode name and link under the problem title. Please narrow it to that and take the history browsing to PR #108, so the same list is not redesigned twice.

One thing to settle before proposing the link: PR #38 deliberately poses each problem as a scenario rather than as its LeetCode original, so naming the original next to the title changes what the candidate reads during the interview. Say where the link would go and why it does not hand the candidate a searchable answer mid-session; after the interview, on the report or the attempt card, is an easier case to make than on the problem tab.

[jserv]

Correction to the comment above: the interview page already names the LeetCode problem under the scenario (web/render.js:175, from PR #38), so naming the original does not change what the candidate reads mid-session. What is new here is only the link. #201 asks for the opposite, hiding that line during the interview, so the two are being settled as one decision there. The history browsing still belongs with PR #108.

[kuanlin1227]

Thanks for pointing this out. I agree that the history browsing part overlaps with the existing Past attempts work and PR #108, so I'll narrow this issue to the LeetCode problem name and link.

For the link placement, I agree that it should not be visible during an active interview. Since PR #38 intentionally presents problems as scenarios to avoid exposing the original LeetCode problem, showing the original name or link on the problem tab could make the answer searchable during the session.

I think a better place would be after the interview, for example in the generated report and/or the corresponding Past attempts card. The candidate could then use the original LeetCode link for review and further practice without affecting the interview itself.

I'll update the issue accordingly and leave the history browsing/filtering behavior to PR #108.