Incorrect timestamp prefix in dragon_logs output

[takenagain]

As noted by CA

To Reproduce

1. Run the application with dragon_logs enabled
2. Observe log output
3. Compare the initial timestamp prefix with the timestamp in the log message

Expected behavior

1. The timestamp prefix at the beginning of each log line should match the timestamp value in the log message. This discrepancy might result from the UTC normalisation in dragon_logs, where KDF returns the time in the current timezone.
2. Single-digit minutes should be zero-padded (e.g., 11:04:48 instead of 11:4:48)

Actual behavior

The timestamp prefix shows an incorrect time and format. For example:

• Log line starts with: 2025-10-26: 11:4:48.865T+0:01:03.904963
• But the timestamp field in the message shows: timestamp: 1761476687864, date: 2025-10-26 12:04:47.864149
• Single-digit minutes are not zero-padded (e.g., 11:4:48 instead of 11:04:48)

Packages affected

• packages/dragon_logs

Code Location
packages/dragon_logs/lib/src/logger/logger_interface.dart, lines 27-31

Example log output

2025-10-26: 11:4:48.865T+0:01:03.904963 [LOG] {message: INFO: [ACTIVATION] Protocol breakdown: {{txoProtocol: 1} – null, path: CoinsRepo, app_version: 0.9.3, mm2_version: 2.5.2-beta_a295579b8, os_language: en-NL, screen_size: , timestamp: 1761476687864, date: 2025-10-26 12:04:47.864149}}