UI updates, changes sync'd to UI docs

docs/ui/entities/source/user-journey.md

@@ -15,7 +15,7 @@ Managing Source records is page-first:
 1. The user starts from a transcription job flow.
 2. The user adds one or more source files.
 3. The system creates Source records linked to the Document and linked to the Job through JobSource.
-4. The user reviews original transcription output and can maintain revised text.
+4. The user reviews source lists by document and can navigate to the owning Document or Job.
 
 ## 2. User Goal
 
@@ -34,15 +34,11 @@ The user wants to:
 A Source list surface should support:
 1. listing source pages for a selected Document
 2. sorting by page_number
-3. opening a source detail or revision view
+3. opening the owning Document or Job context
 
 ### 3.2 Source Detail Surface
 
-A Source detail surface should show:
-1. file preview (image or PDF)
-2. source metadata
-3. original transcription context
-4. revision editor and revision state
+Source detail and revision surfaces are deferred in the current UI.
 
 ## 4. Entry Points
 
@@ -51,7 +47,7 @@ Primary entry points:
 2. from Job detail, open source preview and revision editor
 
 Current implementation note:
-1. source interaction currently occurs in upload and job-detail flows
+1. source interaction currently occurs in job-create and document-scoped source list flows
 
 ## 5. Create Source Flow
 
@@ -106,7 +102,7 @@ After successful source create:
 1. Source is linked to the Document
 2. Source appears in page order derived from alphabetical upload filename ordering
 3. Source is linked to the Job through JobSource at create time
-4. The user can open preview and revision workflow
+4. The user can open the owning Document or Job context
 
 ### 5.8 Source Creation Invariant
 
@@ -119,40 +115,35 @@ For first release:
 
 ### 6.1 User Intent
 
-The user wants to view each page file and understand file identity, processing context, and revision status.
+The user wants to view each page file and understand file identity and processing context.
 
 ### 6.2 Read Surface Expectations
 
 The UI should show:
-1. file preview for the current Source
+1. source lists grouped by Document
 2. upload_name as the original user-provided filename
 3. filename as the stored system filename
-4. file_path information, with the option to keep it internal or partially hidden for safety
-5. page_number and ordering context
-6. whether revised_text exists
-7. original transcription output context
+4. page_number and ordering context
+5. the owning Document and Job navigation context
 
 ### 6.3 Read Empty and Missing States
 
 If source is missing:
 1. Show clear not found or no source available messaging
 
-If source has no revision:
-1. Show empty-state guidance and create-revision action
-
 If source metadata is partially unavailable:
-1. Show fallback labels and keep preview and revision actions available where possible
+1. Show fallback labels and keep navigation available where possible
 
 ## 7. Update Source Journey
 
 ### 7.1 User Intent
 
-The user primarily updates page-level revision text while preserving raw machine output.
+The user primarily tracks page-level source records while preserving raw machine output in the service layer.
 
 ### 7.2 Intended Editable Fields
 
 Editable in first release:
-1. revised_text
+1. revised_text in a later revision, not in the current simplified UI
 
 Read-only in first release:
 1. upload_name
@@ -166,11 +157,11 @@ Read-only in first release:
 ### 7.3 Revision Save Behavior
 
 On save:
-1. validate revision text is non-empty
-2. persist revised_text
-3. set date_revised
-4. show success feedback
-5. keep user in current source context
+1. validate revision text is non-empty when the revision UI exists in a later release
+2. persist revised_text when the revision UI exists
+3. set date_revised when the revision UI exists
+4. show success feedback when the revision UI exists
+5. keep user in current source context when the revision UI exists
 
 ### 7.4 Revision Failure Behavior
 
@@ -196,13 +187,13 @@ Delete is blocked when:
 ### 8.3 Delete UX
 
 When blocked:
-1. explain dependency constraints
-2. Show cleanup guidance
+1. explain dependency constraints in a future delete flow
+2. show cleanup guidance in a future delete flow
 
 When allowed:
-1. confirm permanent removal
-2. remove source
-3. return to source list with success state
+1. confirm permanent removal in a future delete flow
+2. remove source in a future delete flow
+3. return to source list with success state in a future delete flow
 
 ## 9. Relationship to Other Workflows