Record large-device blood pressure reference · d7df54e

+15 -0

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

@@ -786,6 +786,18 @@ The likely bottleneck is per-row SQLite work:
   queries returned HealthKit `com.apple.healthkit` error code `5`:
   `Authorization not determined`. Treat this as a permission/device-state issue,
   not an import engine regression.
+- An earlier matching report from the same large-database device
+  (`Device: 4A8B3EE5-BA8B-44F2-A3D9-44105FFEA033`) captured a complete first
+  import on 2026-06-04 at 20:42:44: `8,421,978` records, `127/127` complete,
+  `initialImport=127`, wall clock `166m10s`, fetch `5m19s`, processing
+  `20m29s`, insert `137m31s`, finalize `1m53s`. In that report Blood Pressure
+  Diastolic and Systolic were both `authorizationStatus: granted`, both had
+  `5,120` samples, and both ranged from `2014-12-18T11:24:11Z` to
+  `2026-05-29T03:06:36Z`. This is a strong before/after reference: the same
+  device later reported `Authorization not determined` for those same types
+  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.
 
 ## Open Issues / Observations
 
@@ -864,6 +876,9 @@ Prioritize experiments in this order:
    queries, so the next app-side check is whether `Request Health Access`
    re-prompts for those types or whether iOS Health settings expose them for
    HealthProbe.
+   Compare any future attempt against the 2026-06-04 first-import reference,
+   where the same device granted HealthProbe access and imported `5,120`
+   systolic + `5,120` diastolic records through 2026-05-29.
 12. Investigate full-profile empty anchored-query cost for zero-count types.
    Compare slow empty types across reports before changing behavior; any skip or
    lower-frequency strategy must preserve the promise that full authorized


	@@ -786,6 +786,18 @@ The likely bottleneck is per-row SQLite work:
786	786	queries returned HealthKit `com.apple.healthkit` error code `5`:
787	787	`Authorization not determined`. Treat this as a permission/device-state issue,
788	788	not an import engine regression.
	789	+- An earlier matching report from the same large-database device
	790	+ (`Device: 4A8B3EE5-BA8B-44F2-A3D9-44105FFEA033`) captured a complete first
	791	+ import on 2026-06-04 at 20:42:44: `8,421,978` records, `127/127` complete,
	792	+ `initialImport=127`, wall clock `166m10s`, fetch `5m19s`, processing
	793	+ `20m29s`, insert `137m31s`, finalize `1m53s`. In that report Blood Pressure
	794	+ Diastolic and Systolic were both `authorizationStatus: granted`, both had
	795	+ `5,120` samples, and both ranged from `2014-12-18T11:24:11Z` to
	796	+ `2026-05-29T03:06:36Z`. This is a strong before/after reference: the same
	797	+ device later reported `Authorization not determined` for those same types
	798	+ after authorization/query interaction. Preserve this report as forensic
	799	+ evidence that HealthKit access/authorization state changed, not merely that
	800	+ the Health UI displayed different data.
789	801
790	802	## Open Issues / Observations
791	803
	@@ -864,6 +876,9 @@ Prioritize experiments in this order:
864	876	queries, so the next app-side check is whether `Request Health Access`
865	877	re-prompts for those types or whether iOS Health settings expose them for
866	878	HealthProbe.
	879	+ Compare any future attempt against the 2026-06-04 first-import reference,
	880	+ where the same device granted HealthProbe access and imported `5,120`
	881	+ systolic + `5,120` diastolic records through 2026-05-29.
867	882	12. Investigate full-profile empty anchored-query cost for zero-count types.
868	883	Compare slow empty types across reports before changing behavior; any skip or
869	884	lower-frequency strategy must preserve the promise that full authorized