Bridge v0.16.0

Bridge 0.16.0 is the responsiveness release on 0.15.0: the four slow calls that held the engine's single request thread now run as background jobs or on a worker, and the app starts measuring its own click-to-paint times. Nothing on disk changes shape: the three databases stay at their current schema versions (semantic v16, workbench v7, workspace v2) and no project file is written by anything new.

Import is a cancellable background job (#231)

Importing a file, a folder or a Paratext project shows a progress banner at once (phase, book x of y, chapter for the first book, percent) with a working Cancel, and Project Home stays usable while it runs. Cancel leaves nothing on disk. Two defects fixed on the way: a collection import used to move each book into place as soon as it was written, so a failure on book 40 left 39 behind (every book is now staged and the set is moved at the end), and the project registry had no lock.

"Align automatically" on a window no longer freezes the app (#242)

The cross-verse page's two provider calls run on a worker. Status polls, verse reads and navigation keep answering meanwhile (on 0.14.0 this was 275 s of "Language QA: unavailable"), the job reports which pass is in flight, and a cancel writes nothing. The modal's own pass text from that state is #243.

Opening a book returns before the semantic runtime is built (#112)

project.open comes back once the translationCore project is loaded, registered and recovered; the passage-semantic runtime (0.3 to 1 s of a cold open) is built on a worker, and anything that needs it, an edit, an alignment write, a semantic analysis, waits for it rather than racing it.

Click-to-paint timing and the responsiveness table (#232)

Every Tier A and B action of requirement 1 is timed from the click to the paint and written to the diagnostics log. Engine diagnostics gained a Responsiveness section with this session's p95 table, "Copy table" and "Measure 20× each"; scripts/perf_table.py prints the same table from the log. NFR-PERF-001 in the SRS now states the three tiers.

Responsiveness table: not yet measured on the reference configuration (Intel Core i3 8th gen, 8 GB, 512 GB HDD, 15-inch 1366x768). The table is added to these notes when the first measurement is taken on that class of machine; until then the expectation from the development machine's traces is in #232.

Also in this release (Benz)

Language QA: spacing.extra offers its fix and the human-review round 3 labels (#230), section-heading rules (#244), footnote text without \ft (#245), note callers (#246).

Known

• word.select is the one Tier A action without a timing mark yet (its selection lives in the verse editor).
• Under a parallel test run on a loaded machine two pre-existing tests are flaky; see #247 and BUILD_LOG 2026-10-14. They do not affect the installed app.