V6.1 UI refinements, add Maintenance jobs to Settings

docs/roadmap_plan.md

@@ -27,25 +27,24 @@ Detailed plan: [`v6_0_hosting_migration_plan.md`](v6_0_hosting_migration_plan.md
 
 ## V6.1 - Testing and Refinement
 
-[*Potential app refinements:*
-* Create a **single “Maintenance Jobs” UI** backed by your existing async worker pattern, not direct shell execution from the page.
-  1. Add a `maintenance_run` table (`id`, `job_type`, `status`, `started_at`, `finished_at`, `triggered_by`, `summary`, `log_path`, `error_detail`).
-  2. In the UI, add two buttons: **Run Backup** and **Run Storage Reconciliation**; clicking creates a run row and enqueues worker execution.
-  3. Worker executes the existing scripts/commands, captures stdout/stderr to a timestamped log file, updates run status/summary.
-  4. UI shows a run history grid with live status, duration, summary, and “View Log”/“Download Log”.
-  5. Add optional schedule controls (daily/weekly) that create queued runs through the same path so manual and scheduled runs behave identically.
+Objective: improve navigation and operational workflows after user feedback.
 
-* Consider a difference Sources for Document page
-  * Presenting the list of Document sources is not very useful.
-  * Consider presenting a thumbnail gallery instead. I think this would make it easier to select the single source file the user is looking for.
-  * This idea may be useful in other areas as well.
-
-* People detail page -> LINKED DOCUMENTS:
-  * How to handle long list of identically named documents (e.g., "Hig postcard to Zenna")? The table shown is not useful, but there isn't enough real estate in the column to add something like the document date, I don't think.
-
-* Start reviewing what the UI looks like on a smart phone. How do those cards arrange themselves on a phone?
-
-]
+### Scope
+1. Make Document Detail the primary source-page workspace:
+   - Use Source-style pan/zoom + previous/next page controls.
+   - Move editable revision controls into Document Detail.
+   - Move archival/system metadata to dedicated Document Info route.
+2. Simplify top navigation:
+   - Remove top-level Tags and Sources entries.
+   - Retire the Tags page and the global Source Asset Records entry flow.
+3. Improve list/detail clarity:
+   - Add Document transcription status to Archival Documents list.
+   - Add Document Date in People Detail -> Linked Documents table.
+4. Add worker-backed Settings maintenance runs:
+   - Add `maintenance_run` persistence (`id`, `job_type`, `status`, `started_at`, `finished_at`, `triggered_by`, `summary`, `log_path`, `error_detail`).
+   - Add Run Backup and Run Storage Reconciliation actions that enqueue runs and execute in the worker.
+   - Add run history with status, duration, summary, and log view/download.
+   - Defer daily/weekly scheduling controls to V6.2.
 
 ## V6.2 - Reporting Features