[ryanbr]

A WHOOP 4.0 user with no synced motion asked whether entering their Apple Health steps by hand would
start NOOP counting and calibrating. It wouldn't — and the sheet is why they thought it might.

The misdirection

With no banked motion, the card still showed:

Need 1 more day where your phone also counted steps

That names phone-step days as the blocker. They aren't:

public static func estimate(motion: Double, calibration: Calibration) -> Int? {
    guard motion >= minMotionForFit, calibration.coefficient > 0 else { return nil }
    let raw = motion * calibration.coefficient

A step estimate is motion * coefficient, and a calibration point is the ratio steps / motion. Both
halves are required, so with the motion half missing neither the estimate nor the fit moves however
many days the phone counts. Setting the coefficient by hand doesn't help either — that sets the
multiplier, and the thing being multiplied is what's absent.

So the countdown pointed at the one input the user could supply, while the input they actually
needed went unmentioned in that card. The no-motion banner at the top of the same sheet explains the
real blocker, and the two were competing — the user believed the countdown.

The fix

The countdown and its explanatory line now render only when motion exists.

Deliberately no new copy. The banner already says the right thing; the fix is to stop
contradicting it rather than add a third message. The comparison card is untouched for the same
reason — "no days yet where both counted" is simply true in this state.

Net diff is two lines of code and a comment explaining why.

Scope

Not a fix for the underlying no-motion case, which on a 4.0 is a history sync that hasn't completed —
#1149 covers the harder version. This only stops the UI sending someone down a road that cannot work.

Verification

• swiftc -parse clean; doc_comment_lint and i18n_audit --ci clean; no strings added or changed.
• Not compiled and not seen. App-target Swift with no local build and no default CI job — -parse
  is syntax, not type-checking, and this changes what a card renders. The testing build's iOS leg
  compiles it; the state is reachable on any strap that hasn't synced motion.

🤖 Generated with Claude Code