chore: regenerate update-journal-entry docs for in-step flow re-tags

sdk/sdk.gen.ts

@@ -2396,7 +2396,7 @@ export const signOffReconciliation = <ThrowOnError extends boolean = false>(opti
 /**
  * Update Journal Entry
  *
- * Update a draft journal entry, or re-tag any entry's flows. If line_items is provided, existing line items are replaced atomically, the new set must balance, and a line on a retired (`is_active=false`) account is refused. `line_flows` sets the cash flow row of the named lines in place, on a posted entry too, closed month included, since a flow moves no balance; the lines on the other side of the entry follow when that side carries one flow. Posted entries accept nothing else and are corrected via `create-event-block(event_type='journal_entry_reversed')`.
+ * Update a draft journal entry, or re-tag any entry's flows. If line_items is provided, existing line items are replaced atomically, the new set must balance, and a line on a retired (`is_active=false`) account is refused. `line_flows` sets the cash flow row of the named lines in place, on a posted entry too, closed month included, since a flow moves no balance; the lines on the other side of the entry that were in step with it follow. Posted entries accept nothing else and are corrected via `create-event-block(event_type='journal_entry_reversed')`.
  *
  * **Idempotency**: supply an `Idempotency-Key` header to make safe retries; replays within 24 hours return the same envelope. Reusing the key with a different body returns HTTP 409 Conflict.
  */

sdk/types.gen.ts

@@ -20619,7 +20619,7 @@ export type UpdateJournalEntryRequest = {
     /**
      * Line Flows
      *
-     * Re-tag lines in place: each named line takes its `flow_qname` (null clears it), and when every line on that side of the entry then carries one flow, the lines on the other side not named here take it too, so the cash line and the account line agree. Allowed on a posted entry, closed month included, and the only change one accepts; recorded on the entry as `flow_retags`. Not combinable with `line_items`, which replaces the lines (set `flow_qname` on them).
+     * Re-tag lines in place: each named line takes its `flow_qname` (null clears it), and when every line on that side of the entry then carries one flow, the lines on the other side not named here follow when they were in step with it — untagged, or carrying the flow the named lines carried before — so the cash line and the account line agree; a line tagged differently on purpose keeps its tag. Allowed on a posted entry, closed month included, and the only change one accepts; recorded on the entry as `flow_retags`, with what each changed line carried before. Not combinable with `line_items`, which replaces the lines (set `flow_qname` on them).
      */
     line_flows?: Array<JournalEntryLineFlow> | null;
 };