Mikhail ChusavitinandClaude Sonnet 5
7aa276320b
`ipmitool fru edit` frequently exits non-zero after a field resize (shrinking/growing a string shifts every later offset in the FRU record) even though the write itself landed correctly on the BMC - the failure is in ipmitool's own post-write re-parse, not the write. bee was treating that exit code as authoritative and marking the task failed even when the field was actually written. runIPMIFRUWriteTask now re-reads the FRU on a non-zero exit and compares the target field's actual value before deciding the task failed, logging which path it took either way. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>