V5.1 UI refinements

docs/ui/pages/documents.md

@@ -50,6 +50,7 @@ Optional:
 Rules:
 
 - Exact date must parse as `YYYY-MM-DD`; browser presentation may follow locale.
+- The exact-date input is labeled **Document date**.
 - Existing people appear with disambiguating labels.
 - Tag assignment supports selecting existing tags and adding new labels inline.
 - **Create new person** opens Person creation.
@@ -68,7 +69,7 @@ Rules:
 
 - The heading shows name, type, and internal ID.
 - The first Source, when present, appears in the dark-room viewer.
-- Archival Metadata shows authors, Document Type, tags, compact Document date, location, and archive identifier. Notes appear in a separate archival-notes block within the same card.
+- Archival Metadata shows authors, Document Type, tags, Document date (`MM-DD-YYYY` for exact dates), location, and archive identifier. Notes appear in a separate archival-notes block within the same card.
 - System Logistics shows created and updated timestamps.
 - Related People are grouped by role and link to Person Detail.
 - **Sources & Pipeline Jobs** shows counts and actions for filtered Sources, Document Jobs, and adding a Job.

docs/ui/pages/people.md

@@ -20,8 +20,8 @@ People manages reusable historical-person records. A Person may appear in many D
 - The title is **Archival Entities: People**.
 - **Create new person** opens the create route.
 - The table defaults to Last Name order and supports search and column sorting.
-- Columns are Last Name, First & Middle, FamilySearch ID, Birth Date, Death Date, and # Documents.
-- Last Name and First & Middle are left-aligned; FamilySearch ID, date columns, and # Documents are centered.
+- Columns are Last Name, First & Middle, Tags, FamilySearch ID, Birth Date, Death Date, and # Documents.
+- Name and Tags are left-aligned; FamilySearch ID, date columns, and # Documents are centered.
 - # Documents reflects how many linked Documents each Person is connected to.
 - Birth and death values independently prefer exact date, then approximate date, then `Unknown`.
 - Selecting a row opens Person Detail.

docs/ui/pages/sources.md

@@ -22,6 +22,7 @@ The list accepts optional `document_id` and `job_id` query parameters. Document
 - Rows are ordered by page number and then upload name.
 - Columns are Document Name, Page Number, Upload Title, Status, and Error Detail.
 - Document Name, Upload Title, and Error Detail are left-aligned; Status is centered.
+- Status labels are presented in uppercase for consistency with Jobs.
 - Stored Filename is intentionally absent from the list.
 - Selecting a row opens Source Detail.
 - No records displays `No source asset records found in repository.`
@@ -39,7 +40,7 @@ The list accepts optional `document_id` and `job_id` query parameters. Document
   - Wide+narrow landscape images switch to a stacked left layout (image above Editable Revision) with metadata on the right.
 - Editable Revision is seeded from an existing revision or the preferred machine transcription.
 - Source Metadata shows upload name, stored filename, page number, Document Name, Document ID, and stored path. Source ID appears in the page-header subtitle.
-- SourceJob Metadata shows latest status, Job ID, execution time, provider, model, prompt, and failure detail.
+- SourceJob Metadata shows latest status (uppercase display), Job ID, execution time, provider, model, prompt, and failure detail.
 - Revision Logistics shows revised state, last-revised time, and upload time.
 - Candidate Machine Transcriptions appears below the image/revision area, remains compact until expanded, then compares it with the preferred
   machine result and requires confirmation before **Use this transcription**.