docs: retire the whole-project review plan, correct its CHANGELOG traces

Every item in docs/PROJECT_REVIEW_PLAN.md is now either landed or moved to
ROADMAP.md, so the working document retires the way TEST_REVIEW_PLAN.md did.
Nothing else referenced it.

Two 1.0.2 Internal entries were out of step with what shipped: the timing
diagnostic is written as notify-timing.tsv (kept out of CleanupLogs and off
the UI thread), not notify-timing.log, and the removal of the two per-run
no-op jobs.json rewrites - along with the run-start rollback and the start
error RunDue used to surface - was not recorded at all.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

docs/CHANGELOG.md

@@ -77,9 +77,17 @@ the app icon (experimental).**
 
 **Internal:**
 
-- App-side failure-notification timing is appended to `logs/notify-timing.log`
-  for diagnosing toast delay (OS latency excluded). `scripts/measure-windows-toast.ps1`
-  measures the PowerShell baseline on Windows.
+- App-side failure-notification timing is appended to `logs/notify-timing.tsv`
+  for diagnosing toast delay (OS latency excluded). The `.tsv` extension keeps
+  the diagnostic file out of `CleanupLogs`, which manages only `.log` files, so
+  it is neither deleted by age nor counted against **Max log files**. The append
+  runs off the UI thread. `scripts/measure-windows-toast.ps1` measures the
+  PowerShell baseline on Windows.
+- `jobs.json` is no longer rewritten twice per run. Starting and finishing a run
+  touch only `JobRuntime`, which is never persisted, so both saves re-serialised
+  identical bytes; `SetGlobalPause` did the same alongside its real `SaveConfig`.
+  Removing them also removes the run-start rollback path and the save failure it
+  reported, so `RunDue` no longer has a start error to surface at all.
 - File I/O no longer happens while `Service.mu` is held — that is the lock the
   UI thread takes on every job and runtime read, so a JSON write, the
   post-run log cleanup, or the startup log scan used to make a UI refresh wait