Bridge v0.15.0

Bridge opens on a real loading screen, a verse aligned across verses can earn its tick, the engine's database work is several times faster, and the Tamil Language QA pack reaches 1.3.0 with the native reviewer's wording.

Highlights

A startup screen instead of a blank window (#233). The window opens on the Bridge name, the version and what the engine is actually doing, stage by stage: starting the process, loading Python, loading the engine modules, starting the engine, ready. If the engine cannot start, or does not answer within 30 seconds, you see a plain error with Retry, Show details (the engine's log) and Copy diagnostics, which puts the version, the paths Bridge used, the startup stages and the log on the clipboard for a bug report.

The verse ✓ for cross-verse alignment (#228). A verse whose words are aligned through a cross-verse link could never show the tick, because translationCore itself cannot mark it complete. The verse list now has a fifth alignment state, "complete (cross-verse)": every remaining word is accounted for by a link or a reasoned null decision, the ✓ shows, and the chapter tallies count it. Export is unchanged.

Faster everywhere the engine touches its databases (#113). The engine used to open and close a fresh SQLite connection for every operation. It now keeps one per thread and reuses it within a request. The semantic pipeline's profiled test went from 95 seconds to 10; the packaged Language QA stages roughly halved; the whole engine test suite runs in two thirds of the time. Durability is NORMAL under WAL: every committed change survives an application crash.

Tamil Language QA pack 1.2.0 and 1.3.0 (#234, #235). The pack now carries a changelog and every change to it bumps the version. 1.3.0 takes the native reviewer's corrections to every Tamil string on screen, exported for review as one list with the English alongside (#235), and stops offering an ஒற்று verdict after கூட, சொந்த and கள்ள.

The Language QA panel stays usable at 1366×768 (#177, #178). Close, Pause/Resume and the Findings / Re-check / False positives switch are pinned under the tab bar instead of scrolling away, and the "checks / does not check" coverage list sits behind an ⓘ.

Also in this release

• The editor gets a panel rail on the right: Review, Language QA and Reference open as resizable columns that close by dragging (#236, UI part).
• A checks.status poll that times out while the sidecar is busy now waits instead of failing the check (#210).
• Cross-verse alignment re-tested: offline corpus suggestions come from the project's own completed alignments (#208); the AI path re-tested against a real provider (#188).
• The dead TA_DOUBLE_SPACE check was resolved by the USFM parser work (#191).
• Decisions recorded: full user management and the team hub are version-1 scope, the dashboard is a browser app inside the hub (#226); the engine always stamps the acting user itself and a request can no longer name one (#183).

Before upgrading

Bridge is pre-release and projects are re-imported, not migrated. Nothing in this release changes the project folder layout or the database schemas.