fix(ops): stop the distance dry run promising work it will refuse

Low, review 2. An account with one out-of-range candidate is refused
whole, rows and audit row included, but the dry run counted its rows into
"N row(s) would be repaired" — so the number an operator read before
--apply was larger than the number --apply could ever produce. The refused
accounts are now counted and reported separately, and the per-account line
says its rows are not in the total.

The refusal itself told the operator to check the Health app "before
forcing anything". There is no --force and never was. It now names the
only route that exists: re-run with the matching --unit if the archive
really was in another one.

src/lib/measurements/repair-apple-health-distance.ts

@@ -259,8 +259,9 @@ function outOfRangeRefusal(plan: AccountRepairPlan, factor: number): string {
     `leave the plausible range after x${factor}, so these rows are not the ` +
     "1000x class — the account was most likely re-imported on the fixed " +
     "build, or its archive was never in the affected unit. Nothing written. " +
-    "Check the dry run's worked examples against the account's Health app " +
-    "before forcing anything."
+    "There is no override: check the dry run's worked examples against the " +
+    "account's Health app, and if the archive really was in another unit, " +
+    "re-run with the matching --unit."
   );
 }