[merefield]

Summary

• separate countdown formatting from the system clock
• test countdown boundaries with a fixed timestamp
• assert the mathematically correct exact values for long and short durations

Root cause

The test constructed its deadline from one time.Now() call while production
formatting used another through time.Until. Windows can return the same coarse
clock tick for both calls, leaving the deadline exactly 125 hours away
(5D 05:00), while finer-resolution runners observed a tiny elapsed interval
and produced 5D 04:59.

Impact

Countdown behavior is unchanged in production, but the cross-platform test no
longer depends on scheduler timing or clock resolution.

Validation

• go test ./...
• go test -race -cover ./...
• go vet ./...
• gofmt -l .

[Copilot]

Pull request overview

This PR makes the countdown formatting tests deterministic across platforms by separating the countdown calculation from the system clock and updating the tests to use a fixed reference timestamp, eliminating timing/clock-resolution flakiness (notably on Windows).

Changes:

• Refactors countdown to delegate to a new countdownFrom(now, at) helper for clock injection.
• Updates TestTimeFormatting to use a fixed now (time.Unix(...)) instead of time.Now().
• Tightens assertions to check exact expected formatted outputs for long and short durations.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
internal/ui/view.go	Adds countdownFrom and routes countdown through it to decouple formatting from the system clock.
internal/ui/view_test.go	Rewrites countdown tests to use a fixed timestamp and assert exact expected strings.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.