Bank Journal Render

Render the edited bank journal export to a file — and auto-post it to the GL.

⚠️ This docstring used to say "(CompanyMember). Stateless." and that was false (corrected ZCT-257, 2026-08-31). The body below calls autopost_normalized_entries — "the GL is now the system of record; the file render below is an export of the GL". So this writes the customer's books, and the word "Stateless" was load-bearing in the wrong direction: it is exactly the sentence that got this route classified as a POST-shaped read and permanently waived from the role sweep, until review caught it. Accountant/owner, like its /post sibling.

The submitted entry_ids ARE the source selection identity. They are re-resolved (no accountant call); if any is no longer exportable (e.g. journal-linked since preview) or the resolved set differs from the submitted set → 409 drift. The edited document is run through the fixed render pipeline + validation (→ 422 on a broken/unbalanced/cross-FY/out-of-chart document) → format renderer → file bytes.

ZENO-236: a movement or document the ledger already holds — including one an earlier render posted — is refused with 409 conflict.selectionChangedSincePreview rather than rendered into a second file (a second bexio import). The file is built BEFORE the post, so a render failure posts nothing and the request can simply be retried.