v2026.09.18 — Safer TMX workflows and clearer work controls

Added

• More reliable TMX import and export. Translation memories use a qualified streaming path for large files, with standard inline tags and their surrounding text preserved through import and export.
• Language-pair checks before import. TilBridge now checks the beginning of a TMX file before upload when it can determine that the file does not match the selected memory. A mismatch is reported with the detected and expected language pairs instead of becoming a misleading empty success.
• Clearer workflow control. Start workflow actions, queued work and held runs now explain what is waiting, which job or step is involved, and what action can unblock it. Human stages can also carry a default performer, and the jobs queue exposes clearer Open, Completed and Cancelled views.
• New list filters and scopes. Projects and jobs can be narrowed to My or All, jobs can be separated by status and current performer, and workflow views keep the relevant language-pair and work context visible while you manage a project.

Improved

• More useful editor and provider feedback. Refused confirmations and blocked steps report actionable reasons. Missing machine-translation credentials are identified as provider-availability problems, and malformed provider output is handled without exposing invalid data to the editor or chat tools.
• More informative translation-memory activity. Import cards show the latest relevant run, language-pair misses are visible, and dates follow the user’s locale. Import and export progress, recovery and cancellation behavior are more explicit.

Fixed

• Large untagged TMX imports no longer repeat a full staged-data scan during merge. This removes a major source of avoidable delay for large files.
• Cancelling a busy import no longer waits indefinitely behind the merge. If the merge already holds the database lock, TilBridge returns a clear “too late to cancel” response instead.
• Term-entry dialogs keep all actions visible in narrow or translated layouts.
• Work and review edge cases now recover cleanly. This includes stale language-pair filters, final review validation after concurrent edits, and clearer handling when a workflow step cannot run.