Clarify restored reference device role · 5d79f9c

+6 -0

HealthProbe/Doc/04-project/Import-Optimization-Log.md

@@ -798,6 +798,12 @@ The likely bottleneck is per-row SQLite work:
   after authorization/query interaction. Preserve this report as forensic
   evidence that HealthKit access/authorization state changed, not merely that
   the Health UI displayed different data.
+- This large-database device is not the untouched original source. It is a
+  restored copy of the pre-data-loss database from a backup that still exists,
+  and it has already been used for multiple attempts to restart or force natural
+  iCloud synchronization. It can therefore be used for aggressive experiments
+  when needed, but results must be labelled as coming from a restored
+  pre-loss-reference copy rather than from the original live device state.
 
 ## Open Issues / Observations
 


	@@ -798,6 +798,12 @@ The likely bottleneck is per-row SQLite work:
798	798	after authorization/query interaction. Preserve this report as forensic
799	799	evidence that HealthKit access/authorization state changed, not merely that
800	800	the Health UI displayed different data.
	801	+- This large-database device is not the untouched original source. It is a
	802	+ restored copy of the pre-data-loss database from a backup that still exists,
	803	+ and it has already been used for multiple attempts to restart or force natural
	804	+ iCloud synchronization. It can therefore be used for aggressive experiments
	805	+ when needed, but results must be labelled as coming from a restored
	806	+ pre-loss-reference copy rather than from the original live device state.
801	807
802	808	## Open Issues / Observations
803	809