diff --git a/docs/working/plans/2026-07-04-frontend-entry-edit.md b/docs/working/plans/2026-07-04-frontend-entry-edit.md
index 821b0b2..f895261 100644
--- a/docs/working/plans/2026-07-04-frontend-entry-edit.md
+++ b/docs/working/plans/2026-07-04-frontend-entry-edit.md
@@ -9,7 +9,7 @@ date: 2026-07-04
 
 # Front-End Journal Entry Edit - Plan
 
-**Status:** 🔄 In progress — M1 (U1–U6) complete & verified (V1–V7) on the 2.0.4 container; `entry.md`→`entry.en.md` migration done (edits leave no orphan). `origin/main` (Grav 2.0.4 prod-deploy work) integrated into `feat/journal-post-form` in both repos and re-verified; **held on the branch for review — not merged to main / not deployed** (per owner decision). M2 (U7–U8, editable photos) **deferred**: confirmed blocked by the Form 9.1.10 filepond regression (photo uploads don't persist to disk); land it with the form-to-page/image-upload rework.
+**Status:** 🔄 In progress — M1 (U1–U6) complete & verified (V1–V7). M2 **partially delivered** (2026-07-05): **U7 (load existing photos into FilePond) + remove + reorder** are implemented and verified end-to-end on the :8091 container — V9 (photos load, cover-ordered) and V10 (remove a photo, reorder so a different image is the cover; on-disk `photo-1..N` renumber) both pass; reconcile helpers also covered by a reflection unit test (4 cases). One real bug found & fixed en route: `onFormProcessed` fires once per `process:` action (4×), so photo reconciliation is now latched to run **once** (a 2nd pass deleted the just-renamed `photo-N` files). Changes are in `cache-on-save.php` (edit-aware reconcile) + `post-form.js` (U7 load, D1 disable-sweep excludes the FilePond field). **R9 (add NEW photos on edit) is DEFERRED to the form-to-page/image-upload rework** — not by choice: a new upload on edit runs add-page-by-form's edit-mode file merge, which fatals on Grav 2.0 (`(array)$page->header()` yields mangled protected-property keys, so `$original_frontmatter['photos']` is never set → `array_merge(null,…)` TypeError). add-page-by-form is a **stock GPM-managed, git-ignored** plugin (Alt B: no fork), so this can't be patched here; the add affordance is suppressed in edit mode (`allowBrowse/allowDrop` off) so remove/reorder ship cleanly without exposing the fatal. (The earlier Form 9.1.10 filepond "regression" was a separate, already-disproven test artifact — commit `06d9629`.) **Held on the branch for review — not merged / not deployed.**
 
 ## Goal Capsule