Describe leaving a panorama frame out, and its white clouds

panorama.md still had a frame that did not fit end the job, and FR-MRG-5
still said the merge stops; since 621a6b83 the frame is named on its
row and unticked, and the rest are solved again from the pairs already
matched. §15 records the split of align into match_pairs and solve and
why re-aligning a subset from scratch moved every RANSAC seed, and the
rule e98b1def gave a blown sample, which §8's "nothing about being a
RAW is lost" now mentions. The manual says where the boxes are and
what an unplaceable frame does to Merge.

docs/dev/requirements.md

@@ -1979,6 +1979,11 @@ The same rule as `spot-removal.md`'s and D17's: a tool that quietly alters or om
 photograph is the failure this application must not have, and here the omission would be an
 entire frame.
 
+*Amended 2026-09-27:* the job no longer stops. The frame is named on its row, with why, and the
+merge cannot be confirmed until the photographer unticks it; the rest are then solved again from
+the pairs already measured (panorama.md §15). The omission is the photographer's, made in view,
+which is what this clause asks — never a silent drop.
+
 **FR-MRG-6 — Provenance.** *(general to any merge)* The composite's sidecar carries
 `derived_from`: the content hashes of its sources in order, and the merge parameters. The history
 records the merge as the first entry, and export metadata declares the composite as one. Sources