UI slog grinds on

docs/ui/entities/job/acceptance-criteria.md

@@ -81,7 +81,7 @@ This checklist does not cover:
 ### RD-4 Detail execution context visibility
 1. provider, model, and prompt_name are displayed when known
 2. status lifecycle value is visible
-3. source-level transcription and revision context remains deferred in the current UI
+3. source-level transcription and revision context is available through Source detail navigation from Job detail
 
 ### RD-5 Missing and invalid id states
 1. Given an invalid job id format
@@ -94,16 +94,17 @@ This checklist does not cover:
 ### UP-1 Revision edit entry
 1. Given a job detail page
 2. When the user opens the page
-3. Then document-scoped navigation links are available
+3. Then navigation links to job-scoped Sources are available
+4. Then source rows can open Source detail revision workflow
 
 ### UP-2 Revision validation
-1. source revision editing remains deferred in the current UI
+1. revision save blocks empty trimmed text and shows warning feedback
 
 ### UP-3 Successful revision save
-1. deferred until the source revision UI is restored
+1. Source detail save persists revised text and shows success feedback
 
 ### UP-4 Revision save failure
-1. deferred until the source revision UI is restored
+1. Source detail save failure shows clear error feedback with retry path
 
 ### UP-5 Job lifecycle state update visibility
 1. status changes from queued to processing to terminal states are reflected in UI
@@ -113,19 +114,28 @@ This checklist does not cover:
 ## Delete Acceptance Criteria
 
 ### DL-1 Delete entry and confirmation
-1. job deletion is deferred in the current UI
+1. Given a job detail context
+2. When the user opens job delete page
+3. Then a permanent-action confirmation is shown for non-processing jobs
 
 ### DL-2 Dependency guardrails
-1. deferred until a job delete flow is reintroduced
+1. Delete is blocked while job status is processing
+2. Related JobSource links are removed as part of allowed delete flow
 
 ### DL-3 Blocked delete behavior
-1. deferred until a job delete flow is reintroduced
+1. When blocked, the UI shows clear processing-state guidance
+2. The user is offered navigation back to job or jobs list
 
 ### DL-4 Successful delete
-1. deferred until a job delete flow is reintroduced
+1. Given an allowed delete
+2. When the user confirms delete
+3. Then the job is removed and success feedback is shown
+4. Then the user is returned to Jobs list
 
 ### DL-5 Delete failure
-1. deferred until a job delete flow is reintroduced
+1. Given backend failure during delete
+2. Then clear error feedback is shown
+3. Then the user remains in delete context with retry path
 
 ## Cross-Criteria Quality Gates