Never scan an operand inside a .zfs directory (closes #142) #145

Merged
clawbot merged 1 commits from issue-142-zfs-operands into next 2026-10-26 15:15:39 +01:00
1 Commits
Author SHA1 Message Date
sneak e231538bc0 Never scan an operand inside a .zfs directory (closes #142)
check / check (push) Waiting to run
An operand inside a directory named .zfs was walked, because the
operand check looked only at the operand's own name. The check now
also looks at every directory above the operand, both as given and
with its symlinks resolved. Such an operand gets a warning, counts as
skipped and is not walked, whether given alone or under another
operand. The check runs before overlapping operands are pruned, so an
operand under another one still gets its warning.

The test for an operand named .zfs now writes its record beneath .zfs
straight into the database, since no scan stores one there any more.

Judgement call: a path component named .zfs counts whatever it is, a
symlink included.

Model: opus-5-5
2026-10-26 13:55:05 +00:00