v5.0 Introduce centralized homepage & portrait photo management

docs/ui/pages/people.md

@@ -2,7 +2,7 @@
 
 ## Purpose
 
-People manages reusable historical-person records. A Person may appear in many Documents under different relationship roles and may optionally carry a portrait and FamilySearch identifier.
+People manages reusable historical-person records. A Person may appear in many Documents under different relationship roles and may optionally carry one or more photos plus a FamilySearch identifier.
 
 ## Routes
 
@@ -38,7 +38,6 @@ Optional:
 - Exact and approximate birth/death dates.
 - Birth/death places.
 - Biography.
-- Portrait path or uploaded portrait.
 - FamilySearch ID.
 
 Rules:
@@ -46,7 +45,7 @@ Rules:
 - Missing Full name blocks save with a warning.
 - Exact date inputs are native browser date inputs.
 - FamilySearch IDs are normalized and validated by `PeopleService`.
-- Portrait uploads are stored under the configured upload root in a Person-specific directory and update Portrait path.
+- Photos are managed on Person Detail (not in create/edit form fields).
 - Metadata JSON remains hidden.
 - Save success returns to Person Detail.
 
@@ -54,7 +53,8 @@ Rules:
 
 - The header provides **New Document**, **Edit Person**, and **Delete**.
 - **New Document** opens Document creation with this Person requested for author preselection.
-- The portrait viewer resolves supported relative upload paths and absolute HTTP/data URLs.
+- Person Detail includes a photo gallery card with multi-file upload, per-photo description edits, set-primary, and delete.
+- Primary photo is shown first and labeled as the primary portrait.
 - Biographical Record shows names, compact birth/death dates, and places.
 - Birth and death place values are clickable links to Google Maps when present.
 - FamilySearch ID is shown as a metadata value and is clickable to the FamilySearch person details route when present.
@@ -67,6 +67,7 @@ Rules:
 ## Delete Behavior
 
 - The page warns when linked Document relationships exist.
+- Delete is blocked when related Photos exist.
 - Confirmed deletion removes the Person and its relationship links; it does not delete Documents.
 - Success returns to the People list.
 - Missing or already-deleted records return to a safe list state.
@@ -76,7 +77,7 @@ Rules:
 - List fields, alignment, date fallback, search, sorting, and navigation match this contract.
 - Full name is enforced on create and edit.
 - FamilySearch ID validation and link generation use the fixed supported identifier format.
-- Portrait upload and rendering remain constrained to supported media paths.
+- Photo upload and rendering remain constrained to supported media paths.
 - New Document carries the Person context.
 - Linked Documents show the correct role and target.
 - Delete wording distinguishes removal of relationship links from deletion of Documents.