StudyHub 3.0.0

• Audio tasks describe the work they actually do. Imports, subtitle files, transcript review, live-class saves and live corrections have their own details in Jobs. Request messages, timeline legends and file stages follow the task; live correction does not show an unrelated Files tab. Opening the study map while an audio task is running no longer crashes the page.
• A stopped local program keeps its slot until it has actually exited. Cancelling an install or conversion no longer frees its resources after an arbitrary ten-second wait while the program may still be running. A failed stop remains pending, so a second operation cannot silently overlap it.
• Navigation remains reachable when the interface is enlarged. Settings stays inside the sidebar's scroll area; the current-page highlight returns after starting a practice session.
• Adding questions to a deck used by a learning workflow no longer fails at publication. The active workflow keeps its original selected questions. Audio processed by the host records an unknown aggregate model instead of an unused Gemini setting.
• Failed personalized batches remain visible. A resting daily record no longer makes failed work look successful; the console names failed batches and includes the day in the failure filter.
• An upgrade can be repeated after rolling back. Once the new version starts, it clears its completed restart marker so returning to 2.7.1 does not block another upgrade from Settings.
• A narrow window no longer shifts the first screen. A "opening the study workspace…" bar for the live-class view, which stays mounted out of sight so recording survives page changes, was drawn above every page while its code loaded, then vanished and moved the page up 46 px. A view kept out of sight now shows nothing while it loads. It appeared only on a busy machine.
• A task board or notebook list edit is no longer lost to a passing Windows file lock. Saving the board or the notebook registry replaced its file once and failed if a scanner held it for a moment; it now retries the same completed file as the study library already did.
• The unified job runtime covers audio, question generation, translations, notes, study workflows and local tools. It shares task status, cancellation, model usage and recovery contracts. All 23 migration and enhancement switches remain off by default; existing explicit opt-ins keep working. The release acceptance record lists the checks and limitations. Existing task files remain compatible with 2.7.1, and the previous execution paths remain available for rollback.

Verified

• CI green on the merge commit d18a501c (ubuntu and windows verify, full suite).
• A real package round trip 2.7.1 → 3.0.0 → 2.7.1 → 3.0.0 on a pre-release candidate (not this final package) passed in segments with the public update dialog and DSH's native plugin installer; the first rollback command timed out after 600 s and the retry in the same profile passed, so it is not an uninterrupted four-round pass. See docs/plans/unified-job-runtime/s6-12-package-roundtrip.md.
• Four rollback drills against the real 2.7.1 code (audio, generation, model tasks, non-model tasks) pass.
• Real-model samples through DSH commandcode: 25 samples, 20 completed, 5 failed earlier; the five re-runs after the fixes completed. Completion does not mean every answer is right.

Not verified, or not fixed

• The final 3.0.0 package has not been through that install / rollback / upgrade round trip. The candidate predates the daily-summary UI change, the changelog link change and the two intermittent-defect fixes of this release.
• No clean full local npm run verify is recorded. An earlier full local run failed twice on the two intermittent defects fixed in this release; a later one under heavy load timed out on three browser tests that each pass when run alone (CI is the full-suite gate).
• The experience channel has not run this for a day, and the policy's real-library, real-model checklist (a question run and top-up, a multi-file audio import with a restart, a scanned book page, the Jobs console at narrow and wide windows) was not completed.
• Known and still open: a 3-card personalised batch can return incomplete JSON from the model; a single-card batch succeeds and is not proof the three-card case is solved.
• Real transcription, Marker/MinerU installation and cloud conversion, and a whole day of real use are unverified.
• All 23 migration switches are off, so by default this release behaves like 2.7.1 plus the fixes above; turning a switch on is opt-in.