2fcb3e6ced
All checks were successful
check / check (push) Successful in 14s
`docker build -fDockerfile.lint .` is a plain `-f` naming a literal file — the flag parser reads the attached value for any shorthand — but the resolver's `[=\s]+` required a separator, so the invocation fell through to the default `Dockerfile` edge. Mutating the `check` recipe to that spelling left the suite 52/52 green while `-f Dockerfile.lint` was caught. The header already promised this form was followed: it claimed the file named by `-f` is resolved wherever the flag sits, and disclosed only a bundled short cluster (`-qf <file>`) as unfollowed. Overclaiming is the defect, so the resolver is taught the form rather than the claim narrowed. The attached form is allowed only for the short flag, keeping `--force-rm` out of it; `--file` still requires `=` or whitespace. The `-qf` cluster limitation is untouched and still pinned.
48 KiB
48 KiB