find silently returns no results when a path argument starts with -, because it parses the path as an unknown flag rather than erroring

When iterating over directories or files whose names begin with - (common with hash-prefixed cache paths, project-slug directories, or any auto-generated naming scheme that uses - as a separator at the start), find "$path" will not error out, it will just return nothing. This makes the bug look like "no matching files" rather than a malformed invocation, so loops over many such paths silently produce zero results across the board. The same trap exists for rm, cat, and other POSIX tools, but find's silent-zero behavior is the most misleading because it mimics a legitimate empty-result case.

Prefix dash-leading paths with ./ (e.g. find ./-weird-dir) or pass -- before the path argument (find -- -weird-dir) whenever the path is interpolated from a variable that could start with -. Prefer absolute paths in scripts that iterate over directory names you don't control.