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

docs/roadmap_plan.md

@@ -137,6 +137,25 @@ Migration policy for legacy installs:
 
 ---
 
+## V5.1 — Person table structural redesign
+
+- Replace `person.full_name` with split required fields:
+  - `last_name`
+  - `given_names` (first + middle)
+- Remove `display_name` and `maiden_name` from active schema/UI.
+- Keep `family_search_id` optional and unique (not required in this version).
+- Add `person_tag` many-to-many links so People use the same Tag registry as Documents.
+- Update Archival Entities: People list columns to:
+  - Last Name
+  - First & Middle
+  - FamilySearch ID
+  - Birth Date
+  - Death Date
+  - # Documents
+- Migration/export-import behavior backfills split names from legacy `full_name` values.
+
+---
+
 ## V6.0 — Server Hosting Migration
 
 Your stated approach (Postgres in Docker, app in Docker, Cloudflare Tunnel) is
@@ -210,8 +229,11 @@ forecloses them later:
 
 ---
 
-## Open items for you
-- V5.0 unified `photos` table: needs the follow-up design discussion you
-  flagged (exact schema, how photos link to homepage vs. person context)
-  before implementation.
-- Confirm this version numbering/grouping matches your intent before work starts.
+## Current status
+- V5.0 unified photos has been implemented with:
+  - shared `photo` table (`person_id` nullable for homepage ownership),
+  - flat media storage under `UPLOAD_DIR/photos/{photo_id}{suffix}`,
+  - migration backfill from legacy Person portraits and homepage images,
+  - homepage markdown relocated to `UPLOAD_DIR/homepage.md`.
+- Version numbering/grouping is now established by implementation and can
+  proceed to V5.1 planning/execution.