This appears to only be a problem for file protected under a SeaBee policy, not seabee itself.
Reproduce with the following sample policy:
name: sample-policy
version: 1
scope:
files:
- /home/test_file
config:
file_write_access: block
and the command sudo sed -i 's/^/Test!/' /home/test_file
No SeaBee logs will be printed and the file is modified.
The underlying cause is currently unclear