UI updates, changes sync'd to UI docs

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

@@ -15,9 +15,9 @@ Creating a Document is a metadata-first workflow:
 1. The user opens the Document page.
 2. The user selects Create new document.
 3. The user enters descriptive metadata about the document.
-4. The user optionally links one related person.
+4. The user optionally selects one related person from the existing Person list.
 5. The system creates the Document.
-6. If a person was selected or created, the system links that Person to the Document through DocumentPerson.
+6. If a person was selected, the system links that Person to the Document through DocumentPerson with author role.
 7. The user sees a success state and lands on the new Document detail page.
 
 ## 2. User Goal
@@ -46,9 +46,9 @@ The Document detail page is the page for one specific Document after it has been
 It should show:
 1. the Document metadata
 2. related people linked to the Document
-3. a Sources section
-4. a Jobs section
-5. empty states when no sources or jobs exist yet
+3. a linked-author summary when available
+4. document-scoped navigation links for Sources and Jobs
+5. filtered views for sources and jobs linked to the current document
 
 It should later support links to filtered views for:
 1. jobs associated with the current document only
@@ -67,7 +67,8 @@ Expected UI affordance:
 Preferred first implementation:
 1. A dedicated Document create page or panel.
 2. A simple form with explicit labels.
-3. Text inputs are acceptable for first release, even where future versions may use dropdowns or richer selectors.
+3. Existing Person records should be selectable through a dropdown.
+4. Text inputs are acceptable for the remaining fields in first release.
 
 ## 5. Create Document Form
 
@@ -124,12 +125,13 @@ The Create Document flow may optionally link one related person during first rel
 
 | UI Label | Schema Area | Input Type | Required | Notes |
 |---|---|---|---|---|
-| Related person | Person -> DocumentPerson | Search/select or create inline | No | Intended to support common author-like associations without making the field mandatory |
+| Related person | Person -> DocumentPerson | Dropdown select | No | Selects an existing Person and links as author when saved |
 
 First release behavior:
 1. The user may save a Document without linking any person.
 2. If a person is linked during create, only one person is supported in first release.
-3. Additional people and recipient workflows are deferred to a future revision.
+3. The selected person is linked as author.
+4. Additional people and recipient workflows are deferred to a future revision.
 
 ### 5.6 Related Records Not Created Directly Here
 
@@ -144,7 +146,7 @@ First release behavior:
 
 The user should be able to:
 1. select an existing Person to associate with the Document
-2. create a new Person if the person does not already exist
+2. change the associated Person from the Document edit flow
 3. save the Document even if no person is linked
 
 ### 6.2 Data Model Interpretation
@@ -162,16 +164,13 @@ This means:
 ### 6.3 Related Person UI Behavior
 
 Minimum acceptable first implementation:
-1. Searchable or scrollable list of existing Person records.
-2. Option to create a new Person inline or in a small secondary flow.
-3. Clear display of the selected related person before submit.
+1. Dropdown of existing Person records.
+2. Clear display of the selected related person before submit.
+3. Ability to change or clear the selected person in the Document edit flow.
 
 If the person does not exist:
-1. User selects Create new person.
-2. User enters the minimum required Person information.
-3. System creates Person.
-4. System returns to Document create flow.
-5. System links the new Person if the user completes Document creation.
+1. The user should create the Person first from the Person page.
+2. The Document create flow only links existing Person records in first release.
 
 ## 7. Validation Rules