What happened

All three duration formatters check ms < 1000 before rounding, so inputs in [999.5, 1000) fall into the milliseconds branch and render as the out-of-scheme string "1000ms" instead of "1s".

Code:

• formatDurationPrecise:

  openclaw/src/infra/format-time/format-duration.ts

  Lines 36 to 38 in 4287d26

  	if (ms < 1000) {
  	return `${Math.max(0, Math.round(ms))}ms`;
  	}

• formatDurationCompact:

  openclaw/src/infra/format-time/format-duration.ts

  Lines 58 to 60 in 4287d26

  	if (ms < 1000) {
  	return `${Math.round(ms)}ms`;
  	}

• formatDurationHuman:

  openclaw/src/infra/format-time/format-duration.ts

  Lines 88 to 90 in 4287d26

  	if (ms < 1000) {
  	return `${Math.round(ms)}ms`;
  	}

Repro

formatDurationPrecise(999.6); // "1000ms" — expected "1s"
formatDurationCompact(999.6); // "1000ms" — expected "1s"
formatDurationHuman(999.6);   // "1000ms" — expected "1s"

Note the same file already guards the analogous rollover for token counts in formatTokenShort ("Rounding can reach 1000 … fall through to the million branch"), see src/shared/subagents-format.ts#L17-L24 — the duration helpers miss the same edge.

Expected

"1s" for any input that rounds to 1000ms (round first, or branch on the rounded value).

Impact

Cosmetic but user-visible: fractional millisecond timings (provider latency, tool timing) can display as 1000ms.

Environment

Current main (4287d26).

Found via source review (AI-assisted).