InterviewHub’s practice workspace has moved from ambiguous red signals and an empty “Raw output” panel to a visible diagnostic path: named failures, concrete details, Python tracebacks, and coach-ready context.
The earlier interview-workspace work is represented in the current main history.
The newest change is present in the working tree and passes its focused tests, lint, whitespace checks, and production build—but it is not part of the frozen HEAD commit.
Design, narrative, and general code checks now attach a concrete sentence to every missing signal. A missing empty-input example, for instance, explains what pattern was not detected and explicitly notes when the signal may not apply.
The result type now carries an optional traceback. The worker records it for failed assertions, unexpected runtime exceptions, and setup failures. A shared formatter turns failed tests into a numbered console transcript.
stderr; without copying the traceback into the result, the raw console was technically accurate but practically unhelpful.When code is attached, the coach’s diagnostic summary prioritizes runtime errors and stderr, then the formatted reference-test transcript, then ordinary output. This gives the coach a concrete failure to reason about without presenting reference tests as comprehensive grading.
The question library can be collapsed from its own header, restored from a thin visible rail, and remembered across reloads. The coach’s Read aloud control and browser speech-synthesis path have been removed.
The first production build attempt surfaced an existing configuration rule: the auth cookie secret must be at least 32 characters. Re-running with a local placeholder satisfied that build-time guard without changing repository credentials.
git diff --checkPassing every attached test still does not guarantee every edge case. The product copy retains that distinction.
A missing readiness signal means a pattern was not visible in the draft. It is preparation guidance, not definitive correctness.
Console output is capped at 100,000 characters so a runaway program cannot make the workspace unresponsive.
traceback?: string to each Python test result and formats only failed tests into a numbered transcript containing name, detail, and traceback.traceback module and stores format_exc() for failed assertions, unexpected exceptions, and setup failures.Read aloud, speechSynthesis, and SpeechSynthesisUtterance in the InterviewHub source.