SPA: render audit detailsJson as a readable per-key table instead of a raw tooltip #745

Follow-up named in #722's own mockup comment and recorded as unowned in that slice's design; filed late — #722 closed without it, caught by the owner.

What

web/src/routes/AuditPage.tsx:409 renders the audit payload as the row's raw title attribute:

<tr key={e.id} title={e.detailsJson ?? undefined}>

So a payload arrives as a single unformatted JSON blob in a hover tooltip — unselectable, unwrappable, unfilterable, and identical in all three locales because none of its keys are translated.

Why it matters now

#722 (merged, 97c866f) made these payloads worth reading. A SalesOrder.AddItem row now carries salesOrderItemId, productId, quantity, unitPriceMinorUnits, listUnitPriceMinorUnits, listPriceBasis, currencyCode and currencyMinorUnit; SalesOrder.UpdateItem adds a before/after pair. That is the data an investigator needs for the incident that opened #719 — and today the only way to read it in-app is to hover a row and squint at raw JSON.

The mockup on #722 (docs/images/discount-mockups/AuditRow.png) draws the intended readable table. #722's comment explicitly scoped it out: "today the SPA shows detailsJson as a raw JSON tooltip with no per-key renderer, so the readable table in the mockup needs a small follow-up."

Scope

• Render detailsJson as a per-key table or definition list in the audit row's expanded state, not a title tooltip.
• Money values need their denomination applied — the payload carries currencyCode and currencyMinorUnit precisely so a renderer does not have to guess.
• Key names are currently English identifiers. Rendering them as labels makes them user-visible strings, which pulls in web/src/i18n and catalog parity for en/es/tl — that is the bulk of the work, and it is why Sales: record list/old/new price in the order-line audit payload #722 did not do it.
• AuditPage.test.tsx already fixtures detailsJson: '{"count":5}', so there is a seam to build on.

Not in scope

The payload's shape. #722 fixed it and it is covered by mutation rows; a renderer reads it and does not change it.