• Create PR with unit tests
• Post copyable unit tests in a comment

Reviewing files that changed from the base of the PR and between 8144c7f and aaadb42.

• src/display/plugins/ShotHistoryPlugin.cpp (3 hunks)
• src/display/plugins/ShotHistoryPlugin.h (1 hunks)

• GitHub Check: deploy
• GitHub Check: test

src/display/plugins/ShotHistoryPlugin.h (1)

81-81: maxRecordedWeight field fits cleanly into existing per‑shot state

The new maxRecordedWeight member is well named, uses the same type as other weight fields, and is safely default‑initialized. Together with the reset in startRecording(), this should behave correctly per shot without leaking state between shots.

src/display/plugins/ShotHistoryPlugin.cpp (3)

143-146: Max-weight tracking logic correctly captures peak shot weight

Updating maxRecordedWeight whenever currentBluetoothWeight exceeds it ensures you retain the highest observed value across both brew and extended-recording phases. Because the field is per-instance and only written here, this is a simple and robust way to derive a peak weight for the shot.

---

221-222: finalWeight now correctly derived from the tracked maximum

Using maxRecordedWeight to derive header.finalWeight aligns the stored volume with the peak weight seen during the shot, rather than a potentially transient final reading. Existing consumers that rely on header.finalWeight (history list, index entries, rebuild logic) will automatically get the improved semantics without further changes.

---

288-290: Per-shot reset of maxRecordedWeight prevents cross-shot contamination

Resetting maxRecordedWeight in startRecording() complements the default initializer and guarantees each new shot’s final volume is computed purely from that shot’s samples, even if the plugin instance is reused across multiple shots.