docs: record control versus DryRun project deltas

Plant3D2026/P_Rec_Annot/docs/ortho-viewport-membership.md

@@ -24,9 +24,13 @@ model drawing. No geometry-only result is upgraded to `Resolved`.
 with stable reason codes. `Resolved` membership can progress only through the
 existing annotation rules; this DryRun slice never writes an annotation.
 
-## Runtime evidence still required
+## Paired DryRun evidence
 
-The API contract and build/test coverage are complete, but the exact counts of
-resolved and outside-view objects require the next Launcher Next DryRun on the
-local Ortho fixture. The runtime report must record the command-pair PlanIds,
-summary equality, DBMOD, and automatic rollback.
+The paired local DryRun resolved five of seven source rows through the exact
+view query and classified the remaining two as `ObjectOutsideView`. Each of
+the three supported commands produced an identical PlanId on its repeated
+invocation. Both Launcher sessions reached `RolledBack`.
+
+The paired command-window DBMOD output was not retained. It is intentionally
+reported as `NOT RECORDED`; project-file SHA-256 inventories nevertheless had
+zero delta for both CONTROL and DRYRUN copies.