git support reports incorrect values when lfs is used.

On an lfs-enabled proprietary repo:
$ git status
On branch feature/https-proxy
Your branch is up to date with 'origin/feature/https-proxy'.

nothing to commit, working tree clean
$ brz status
 M [REDACTED].avi
 M [REDACTED].avi
 M [REDACTED].avi
(and so on, 689 lines or so)

The files all appear to be binary files that match our LFS .gitattributes lines. For at least one file, it's clear that it's diffing the file contents against an LFS file pointer. Breezy should not report an incorrect status. Until / unless it supports LFS, it should detect that it cannot support this format correctly and error out.

These issues probably apply to other filter types.