UI updates, changes sync'd to UI docs

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

@@ -59,14 +59,14 @@ This checklist does not cover:
 ## Read Acceptance Criteria
 
 ### RD-1 Source detail retrieval
-1. Given a valid Source id in source context, typically via job detail in first release
+1. Given a valid Source id in source context, typically via a document-scoped source list in first release
 2. When the user opens source detail or equivalent panel
-3. Then source metadata and preview are displayed for that source only
+3. Then source metadata and preview are displayed for that source only if the detail UI exists in a later revision
 
 ### RD-2 Transcription and revision visibility
-1. Original transcription context is visible read-only
-2. Revision state is visible
-3. If revised_text is absent, no revision yet messaging is shown
+1. Original transcription context is visible read-only when the revision UI exists
+2. Revision state is visible when the revision UI exists
+3. If revised_text is absent, no revision yet messaging is shown when the revision UI exists
 
 ### RD-3 Missing source state
 1. Given a missing source
@@ -77,29 +77,29 @@ This checklist does not cover:
 ### UP-1 Revision editing entry
 1. Given a source context
 2. When the user enters revision edit flow
-3. Then revised_text input is available
+3. Then revised_text input is available in a later revision of the UI
 
 ### UP-2 Revision validation
-1. revised_text cannot be saved as empty after trimming
-2. Warning feedback is shown for invalid empty input
+1. revised_text cannot be saved as empty after trimming when the revision UI exists
+2. Warning feedback is shown for invalid empty input when the revision UI exists
 
 ### UP-3 Successful revision save
 1. Given valid revision text
-2. When the user saves
+2. When the user saves in a later revision of the UI
 3. Then revised_text persists
 4. Then date_revised is updated
 5. Then success feedback is shown
 6. Then refreshed revision content is visible
 
 ### UP-4 Revision save failure
-1. Given backend failure during save
+1. Given backend failure during save in a later revision of the UI
 2. Then clear error feedback is shown
 3. Then the user-entered text remains available for retry where possible
 
 ## Delete Acceptance Criteria
 
 ### DL-1 Delete entry and confirmation
-1. Given a source in source context, typically via job detail in first release
+1. Given a source in source context, typically via a later source detail view
 2. When the user selects delete source
 3. Then a permanent-action confirmation dialog appears