Improve oversight change previews

This commit is contained in:
JB
2026-07-25 21:25:15 -04:00
parent 65aa6361a6
commit c5036e7bf0
5 changed files with 124 additions and 4 deletions
+11
View File
@@ -717,6 +717,17 @@ must be separately saved and audit logged before approval, and material changes
should be rejected for contributor revision. Collapse the decision controls and
correction fields to one column on narrow screens.
Proposal evidence is reviewer-facing product data, not JSON-first diagnostics.
Open review in a wide, scroll-contained confirmation surface and present live
and proposed values side by side using the visual structure and terminology of
the source module's editor. Label the two states explicitly as `CURRENT LIVE /
BEFORE` and `PROPOSED / AFTER`; for additions, replace the empty live panel with
an explicit `NEW RECORD` state. Stack comparisons on narrow screens. Raw stored
payloads remain available in a collapsed technical-evidence disclosure for
troubleshooting and audit support, but must not be the primary review surface.
Each module should add a purpose-built preview as its editor matures; until then,
use compact labeled field cards rather than an exposed JSON document.
Data-navigation links with pending proposals use a dedicated four-column layout:
module code, flexible label, square orange count cell, then navigation arrow.
Never insert a count into the ordinary three-column link without changing its