[UtkuDenizAltiok]

What

The Charge breakdown's skin-temperature row ("What shaped it") printed the engine's Celsius deviation to everyone, even when Settings asks for Fahrenheit. The English text also had no degree sign. It happened on both platforms:

• Apple shows the engine's valueText verbatim, which is Celsius-only by contract: +0.4 C vs baseline.
• Android formats the typed value with a Celsius-only string: %1$s C vs baseline.

Now the row reads +0.4 °C vs baseline, or +0.8 °F vs baseline for a Fahrenheit reader. Apple's separate relative row (+0.3 °C vs your normal) follows the same rule.

How

• The engine text is unchanged. It stays pinned byte-for-byte across Swift and Kotlin. Only the display layer changes, formatting the row from the night's raw deviation.

• The conversion is for a difference: ×9/5 with no +32 offset, applied to the unrounded value. For example, 0.44 °C is 0.792 °F, so the row shows +0.8, not the +0.7 a rounded +0.4 would give.

• Rounding is explicit and shared: once, half away from zero. This is the display rule RecoveryScorer.displayRounded already applies to breathing. While testing this I found two formatter differences at round-off points:

  • Foundation's locale formatter rounds a tie the other way from Java's. 0.25 printed +0.2 on Apple and +0.3 on Android.
  • Foundation prints -+0.0 for a negative zero, and the old hand-built sign on Apple's relative row printed +-0.0.

  Anything that rounds to zero now prints +0.0 on both platforms, as Kotlin's displayRounded already did.

• Apple: ChargeBreakdownFormat.skinTempDeviationFigure and displayDriver. ChargeBreakdownSection reads the temperature preference the way other temperature read-outs do, so all three hosts are covered (Today's Charge sheet, Intelligence, Coupled).

• Android: chargeDriverTempDeviation in TodayScreen.kt and a new today_driver_value_temp_deviation_fahrenheit string in every locale. The Italian Celsius string also gets its missing degree sign.

Verification

• Oracle, as AGENTS.md asks: the Swift twin was compiled standalone over 21 inputs per unit (ties, both zeroes, signs, small values). Its stdout is pasted verbatim as the expected values in ChargeDriverTempDeviationTest. The same ties are pinned in ChargeBreakdownFormatTests.
• StrandTests on macOS: 2306 tests, 0 failures. NOOPiOS simulator build passes.
• Android (fork CI, android.yml on this head): run 42167206054 green at 2d482919 (Build debug APK and Run unit tests both success)
• i18n_audit.py --ci upstream/main exit 0; doc_comment_lint.py clean; Tools 338 OK; parity acceptance OK.

🤖 Generated with Claude Code