Motivation

• Correlate POS payment lines with Glory machine transactions using a persistent UUID to reliably link payments to orders and avoid duplicate transaction records.
• Record transaction processing state and diagnostics to improve retry handling and error visibility.
• Surface new transaction metadata in the backend views and enable searching/filtering by state and payment UUID.

Description

• Added new fields to glory.transaction: state, pos_payment_uuid, attempt_count, last_error, and processed_at, and enforced uniqueness of pos_payment_uuid via an SQL constraint.
• Updated generate_glory_transaction to accept pos_payment_uuid, to deduplicate/update existing transactions when the UUID is present, increment attempt_count and set state/last_error appropriately, and to record processed_at on creation/update.
• Enhanced pos.order.create_from_ui to build a map of incoming order payloads, extract glory_payment_uuid from statement_ids, and link existing glory.transaction records to newly created pos.order records by UUID when available.
• Improved action_set_glory_on_order to attempt linking transactions by payment UUID before falling back to matching by amount/session/operation, and simplified imports (AccessError).
• Extended POS frontend: models.js now attaches glory_payment_uuid to paymentlines and preserves it in JSON import/export, and GloryPaymentScreen.js initializes glory_payment_uuid, populates it when missing, and forwards it in all RPC calls to try_write_glory_transaction.
• Updated RPC signature try_write_glory_transaction to accept pos_payment_uuid, and adapted call sites accordingly.
• Adjusted views in glory_transaction_view.xml to display state and pos_payment_uuid in forms/trees, added search filters for state, and fixed a view field naming inconsistency.

Testing

• No automated tests were executed for this change.

Codex Task