V5.1 Modify Person table: split full name into first & last, added tags support

docs/ui/pages/people.md

@@ -19,9 +19,9 @@ 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 Full Name order and supports search and column sorting.
-- Columns are Full Name, FamilySearch ID, Birth Date, Death Date, and # Documents.
-- Full Name is left-aligned; FamilySearch ID, date columns, and # Documents are centered.
+- 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.
 - # 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.
@@ -31,35 +31,36 @@ People manages reusable historical-person records. A Person may appear in many D
 
 Required:
 
-- Full name.
+- Last name.
+- First & middle names.
 
 Optional:
 
-- Display name and maiden name.
 - Exact and approximate birth/death dates.
 - Birth/death places.
 - Biography.
 - FamilySearch ID.
+- Tags.
 
 Rules:
 
-- Missing Full name blocks save with a warning.
+- Missing last name or first/middle names blocks save with a warning.
 - Exact date inputs are native browser date inputs.
 - FamilySearch IDs are normalized and validated by `PeopleService`.
-- Photos are managed on Person Detail (not in create/edit form fields).
+- Tags use the shared Tag registry and support inline add/select behavior.
+- Photos are managed from Person Detail via `/people/{person_id}/photos` (not in create/edit form fields).
 - Metadata JSON remains hidden.
 - Save success returns to Person Detail.
 
 ## Detail Behavior
 
-- The header provides **New Document**, **Edit Person**, and **Delete**.
+- The header provides **New Document**, **Edit Person**, **Edit Photo(s)**, and **Delete**.
 - **New Document** opens Document creation with this Person requested for author preselection.
 - Person Detail shows a single-photo viewer with **Previous/Next** navigation; the page-level **Edit Photo(s)** header action opens photo management.
 - Photo management (upload, description edit, set-primary, delete) is intentionally moved to `/people/{person_id}/photos`.
-- Biographical Record shows names, compact birth/death dates, and places.
+- Biographical Record shows split names, computed full name, tags, 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.
-- Maiden Name is only shown in Biographical Record when a value exists.
 - Biography has an explicit empty value.
 - Linked Documents render as a table with **Document Name**, **Role**, and **Number of Pages**; selecting a row opens Document Detail.
 - No links shows both an empty state and guidance to link from a Document workflow.
@@ -83,7 +84,7 @@ Rules:
 ## Acceptance Checklist
 
 - List fields, alignment, date fallback, search, sorting, and navigation match this contract.
-- Full name is enforced on create and edit.
+- Last name and first/middle names are enforced on create and edit.
 - FamilySearch ID validation and link generation use the fixed supported identifier format.
 - Photo upload and rendering remain constrained to supported media paths.
 - New Document carries the Person context.