5 Commits

This Branch

This Branch

All Branches

Author	SHA1	Message	Date
user	48db9b438a	test(lint-once): read docker image/builder build as builds too ... `docker image build` and `docker builder build` are management-command spellings of the same build, take the same -f, and were emitting no edge at all — the same shape as the buildx miss.	2026-09-04 12:08:54 +00:00
user	81150f433c	test(lint-once): disclose the build shapes read, correct the run: | claim ... Header now states which docker invocation shapes are recognised as builds (bare, buildx, and either through global flags) and which are not (compose), and that the RUN keyword is read case-insensitively with any whitespace separator. The workflow comment claimed a `run: |` block fails the count; it does not — the count is unmoved by it and the pinned resolved list is what turns it red.	2026-09-04 12:06:44 +00:00
user	f67a1c4d92	test(lint-once): match RUN case-insensitively, follow buildx builds ... WIP round 9: items 1-3. Verification matrix still to re-run.	2026-09-04 12:04:24 +00:00
user	ffc817522e	test(lint-once): pin the two-build and later-flag shapes ... The false green: script/lint chaining a second docker build after the lint image ran prettier twice and counted once. The misresolution: a bare docker build followed by cp -f resolved to the cp's file. Pin both, and each separator that bounds an invocation.	2026-09-04 11:51:17 +00:00
user	88a5fcaa87	lint-once: bound the docker file flag to its own invocation ... edgesOf used a single test/exec for docker build, so a line with two builds produced one edge and the file flag was searched across the whole line. Follow every occurrence with matchAll and slice each one to the next shell separator before looking for its flag. Also correct the README's claim that script/fmt-check is the one formatting path left on the host.	2026-09-04 11:49:38 +00:00