API Request Logging Fix & Log Detail Improvements

Bug Fixes

• API request logging restored — request logs stopped recording after the Row Level Security deployment on 7 February. The logger’s database context was silently discarded because it used a transaction-scoped setting outside of a transaction. Logging now works correctly for all API key authenticated requests, with a proper transaction wrapper ensuring the security context is applied.
• DLA transaction form layout — the “Record Transaction” form on the director detail page no longer displaces the section heading on narrow viewports. The form now renders as a full-width block below the header row.

Improvements

• Log detail panel formatting — the Response Body section in the API request log detail panel now displays large responses as formatted, readable JSON with a truncation notice showing original size, instead of displaying raw internal metadata. Binary responses (PDFs, file downloads) show a clean content type and size indicator.