docs: record source-model DataLinks runtime evidence

Plant3D2026/P_Rec_Annot/docs/ortho-runtime-results.md

@@ -10,13 +10,19 @@ viewport. In `DryRun`, `PHP_REC_ANNOT` ran twice, `PXP-AAV` ran twice, and
 `PlantProject.Name` was available for this fixture and rendered as
 `PRecAnnotTestProject`.
 
-The Ortho sheet did not expose direct Piping rows through
-`DataLinksManager.SelectAcPpRowIds`; that API threw `DLException: NotFound`.
-The adapter now converts this to an empty read-only result. Consequently the
-run read zero source Plant objects and produced an empty plan. Mapping the
-Ortho sheet to source-model objects remains the blocker for non-empty
-AnnotationPlan validation.
+The active Ortho sheet does not expose direct Piping rows and must not be used
+as a DataLinks source. Metadata inspection and a sanitized runtime probe
+confirmed `IDwgViewDef.DwgQuery.ModelFiles[].ModelFileName` as the source-model
+reference. The adapter resolves that reference through
+`PipingProject.GetPnPDrawingFiles()` and reads
+`DataLinksManager.SelectAcPpRowIds(PnPProjectDrawing.Id)`.
+
+On the latest real DryRun, one source drawing was resolved and seven source
+Plant objects were read. `PHP_REC_ANNOT` reported seven skipped operations,
+zero writes, zero conflicts, and zero errors. This verifies source-model
+DataLinks access; it does not yet verify exact source-object-to-viewport
+membership or repeated-plan determinism.
 
 The test fixture SHA baseline changed for `Piping.dcf` before the first DryRun
-command. This run therefore does not prove DCF invariance, although no plugin
-write operation was performed and DBMOD remained unchanged.
+command. This run therefore does not prove DCF invariance. A paired control
+fixture versus DryRun fixture comparison remains required.