Review Workbench

The review workbench filter controls SHALL display a reset-all-filters button when any filter deviates from its default value. The button SHALL be hidden when all filters are at their default settings.

The reset-all-filters button SHALL reset all filters to their default state when clicked and SHALL clear any persisted filter preferences.

Citation links in the report pane SHALL navigate to and highlight the referenced paragraph in the contract pane. If the target paragraph is not found, the system SHALL handle the case gracefully.

When a user edits the recommended response in the review workbench, the updated text SHALL be persisted to the backend and restored after page refresh.

Incoming review row updates SHALL be merged with existing rows according to a shared contract, not replaced wholesale. User-applied statuses such as ignored or applied SHALL be preserved unless explicitly overridden.

Row status transitions SHALL follow an explicit state machine and reject invalid regressions. Applied status SHALL be terminal unless explicitly undone. Ignored status SHALL persist until explicitly reopened.

The backend SHALL persist row status updates and include status in all review row payloads. Status changes SHALL be durably stored and reflected in all subsequent data retrievals.

The Ignore action in the review workbench SHALL remain enabled and clickable regardless of whether document edits are currently being applied. The UI SHALL update immediately using optimistic updates and roll back on API failure.

The frontend SHALL maintain SSE connections for all reviews with processing or pending status, regardless of which review is active in the workbench. Switching the active review SHALL NOT disconnect processing streams for other reviews.

The "(edited)" badge in recommendation cells SHALL only appear when the user has actually modified the text content. Opening and closing the editor without changes SHALL NOT trigger the badge.

Apply edit operations SHALL persist genealogy steps regardless of the execution path used. Both precomputed and dynamically generated genealogy SHALL be durably stored.

The review workbench report table SHALL consolidate compliance and analysis into one column and recommended response and suggested edits into one column for a streamlined layout.

The report table SHALL collapse analysis details by default and provide both per-row and global controls for expanding analysis details. The user's default preference SHALL be persisted.

The system SHALL provide batch apply actions that dispatch progress events during batch edit operations for cross-view status tracking. Progress events SHALL include start, per-edit progress, and completion notifications. Ignored rows SHALL be excluded from the pending count.