Clarify large-device retry context · dca653d

+17 -11

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

@@ -760,14 +760,19 @@ The likely bottleneck is per-row SQLite work:
   Existing optional fields remain for old rows and compatibility, but new
   SQLite-backed captures should report no compact archive finalize cost.
 - A 2026-06-06 screenshot from the large-database device showed a fast partial
-  full-profile result: `127` metrics, `8,411,713` records fetched, `11.2s`
+  retry after first import: `127` metrics, `8,411,713` records fetched, `11.2s`
   duration, and `2` failed metrics (`Blood Pressure Diastolic` and
-  `Blood Pressure Systolic`). The attached copied diagnostic text did not match
-  that screenshot; it was the older `1.0(1)-1780689890-92064` repeated-capture
-  report with `2,625,217` records and `5.8s` duration. Do not use that pasted
-  text as evidence for the large-device partial run or for commit `0d61338`.
-  A matching Diagnostics text copy is still needed before drawing performance
-  conclusions from the large-device partial run.
+  `Blood Pressure Systolic`). The device's Health database is known to be in a
+  frozen / non-syncing iCloud state from roughly one year earlier, except those
+  two blood-pressure values appear to still sync for unknown reasons. Treat the
+  two failed blood-pressure metrics as device/data-state evidence, not as an
+  import-performance regression, unless a matching diagnostic report proves a
+  HealthProbe error. The attached copied diagnostic text did not match that
+  screenshot; it was the older `1.0(1)-1780689890-92064` repeated-capture report
+  with `2,625,217` records and `5.8s` duration. Do not use that pasted text as
+  evidence for the large-device partial run or for commit `0d61338`. A matching
+  Diagnostics text copy is still needed before drawing performance conclusions
+  from the large-device partial run.
 
 ## Open Issues / Observations
 
@@ -840,10 +845,11 @@ Prioritize experiments in this order:
    post-import responsiveness. Expected success: record archive finalize is
    zero/negligible, details still load from SQLite, and first-import memory /
    post-save behavior does not regress.
-11. Capture the matching Diagnostics text for the large-database partial run
-   that showed `8,411,713` records in `11.2s`. Confirm the build identity,
-   `CaptureModes`, failed Blood Pressure API call status/details, and whether
-   the run was a repeated delta, partial resumed import, or clean first import.
+11. Capture the matching Diagnostics text for the large-database retry after
+   first import that showed `8,411,713` records in `11.2s`. Confirm the build
+   identity, `CaptureModes`, and failed Blood Pressure API call status/details.
+   Interpret Blood Pressure failures in the context of this device's known
+   frozen / partially syncing Health database state.
 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


	@@ -760,14 +760,19 @@ The likely bottleneck is per-row SQLite work:
760	760	Existing optional fields remain for old rows and compatibility, but new
761	761	SQLite-backed captures should report no compact archive finalize cost.
762	762	- A 2026-06-06 screenshot from the large-database device showed a fast partial
763		- full-profile result: `127` metrics, `8,411,713` records fetched, `11.2s`
	763	+ retry after first import: `127` metrics, `8,411,713` records fetched, `11.2s`
764	764	duration, and `2` failed metrics (`Blood Pressure Diastolic` and
765		- `Blood Pressure Systolic`). The attached copied diagnostic text did not match
766		- that screenshot; it was the older `1.0(1)-1780689890-92064` repeated-capture
767		- report with `2,625,217` records and `5.8s` duration. Do not use that pasted
768		- text as evidence for the large-device partial run or for commit `0d61338`.
769		- A matching Diagnostics text copy is still needed before drawing performance
770		- conclusions from the large-device partial run.
	765	+ `Blood Pressure Systolic`). The device's Health database is known to be in a
	766	+ frozen / non-syncing iCloud state from roughly one year earlier, except those
	767	+ two blood-pressure values appear to still sync for unknown reasons. Treat the
	768	+ two failed blood-pressure metrics as device/data-state evidence, not as an
	769	+ import-performance regression, unless a matching diagnostic report proves a
	770	+ HealthProbe error. The attached copied diagnostic text did not match that
	771	+ screenshot; it was the older `1.0(1)-1780689890-92064` repeated-capture report
	772	+ with `2,625,217` records and `5.8s` duration. Do not use that pasted text as
	773	+ evidence for the large-device partial run or for commit `0d61338`. A matching
	774	+ Diagnostics text copy is still needed before drawing performance conclusions
	775	+ from the large-device partial run.
771	776
772	777	## Open Issues / Observations
773	778
	@@ -840,10 +845,11 @@ Prioritize experiments in this order:
840	845	post-import responsiveness. Expected success: record archive finalize is
841	846	zero/negligible, details still load from SQLite, and first-import memory /
842	847	post-save behavior does not regress.
843		-11. Capture the matching Diagnostics text for the large-database partial run
844		- that showed `8,411,713` records in `11.2s`. Confirm the build identity,
845		- `CaptureModes`, failed Blood Pressure API call status/details, and whether
846		- the run was a repeated delta, partial resumed import, or clean first import.
	848	+11. Capture the matching Diagnostics text for the large-database retry after
	849	+ first import that showed `8,411,713` records in `11.2s`. Confirm the build
	850	+ identity, `CaptureModes`, and failed Blood Pressure API call status/details.
	851	+ Interpret Blood Pressure failures in the context of this device's known
	852	+ frozen / partially syncing Health database state.
847	853	12. Investigate full-profile empty anchored-query cost for zero-count types.
848	854	Compare slow empty types across reports before changing behavior; any skip or
849	855	lower-frequency strategy must preserve the promise that full authorized