Follow-up from the review of #96 (which fixes #89 for script/cibuild only).
script/cibuild now passes CHECK_EPOCH so the three check-running Dockerfile stages (lint, mdfmt, builder) re-execute on every run. script/docker and the docker target in Makefile:81 still invoke a plain docker build with no CHECK_EPOCH, so a developer running make docker can still be handed a green that came out of the BuildKit cache rather than a fresh make check.
This was deliberately out of scope for #96 — the text of #89 names script/cibuild specifically in its title, every DoD bullet and every implementation bullet. Filing separately rather than widening that PR.
Definition of done
script/docker and Makefile:81 either pass a fresh CHECK_EPOCH the same way script/cibuild does, or there is a documented reason they should not.
Demonstrated with a negative control: break formatting, run make docker on an otherwise unchanged tree, and show it fails.
No linter or linter configuration changes.
Follow-up from the review of https://git.eeqj.de/sneak/mfer/pulls/96 (which fixes https://git.eeqj.de/sneak/mfer/issues/89 for `script/cibuild` only).
`script/cibuild` now passes `CHECK_EPOCH` so the three check-running Dockerfile stages (lint, mdfmt, builder) re-execute on every run. `script/docker` and the `docker` target in `Makefile:81` still invoke a plain `docker build` with no `CHECK_EPOCH`, so a developer running `make docker` can still be handed a green that came out of the BuildKit cache rather than a fresh `make check`.
This was deliberately out of scope for https://git.eeqj.de/sneak/mfer/pulls/96 — the text of https://git.eeqj.de/sneak/mfer/issues/89 names `script/cibuild` specifically in its title, every DoD bullet and every implementation bullet. Filing separately rather than widening that PR.
## Definition of done
- `script/docker` and `Makefile:81` either pass a fresh `CHECK_EPOCH` the same way `script/cibuild` does, or there is a documented reason they should not.
- Demonstrated with a negative control: break formatting, run `make docker` on an otherwise unchanged tree, and show it fails.
- No linter or linter configuration changes.
Closed at sneak's instruction, 2026-09-05: this was opened by an agent running on another machine outside the managed fleet, under superseded rules. Reopen if the content is wanted.
Model: fable-5-1
Closed at sneak's instruction, 2026-09-05: this was opened by an agent running on another machine outside the managed fleet, under superseded rules. Reopen if the content is wanted.
Model: fable-5-1
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Follow-up from the review of #96 (which fixes #89 for
script/cibuildonly).script/cibuildnow passesCHECK_EPOCHso the three check-running Dockerfile stages (lint, mdfmt, builder) re-execute on every run.script/dockerand thedockertarget inMakefile:81still invoke a plaindocker buildwith noCHECK_EPOCH, so a developer runningmake dockercan still be handed a green that came out of the BuildKit cache rather than a freshmake check.This was deliberately out of scope for #96 — the text of #89 names
script/cibuildspecifically in its title, every DoD bullet and every implementation bullet. Filing separately rather than widening that PR.Definition of done
script/dockerandMakefile:81either pass a freshCHECK_EPOCHthe same wayscript/cibuilddoes, or there is a documented reason they should not.make dockeron an otherwise unchanged tree, and show it fails.clawbot referenced this issue2026-09-04 03:37:39 +02:00
Closed at sneak's instruction, 2026-09-05: this was opened by an agent running on another machine outside the managed fleet, under superseded rules. Reopen if the content is wanted.
Model: fable-5-1