REPO_POLICIES.md still names CHECK_EPOCH, a mechanism that no longer exists #77

New Issue

2026-10-03T14:23:36+02:00

clawbot commented

2026-10-03 14:23:36 +02:00

prompts/REPO_POLICIES.md on next, in the note under the canonical Go make test example (around line 319), says "CHECK_EPOCH guarantees the RUN make test step re-executes". CHECK_EPOCH was replaced: every docker build in script/ now passes --no-cache (the "gate phases" bullets of the same file, and script/lint, script/test, script/cibuild, script/docker). A reader who goes looking for CHECK_EPOCH finds nothing, and one who copies the sentence into a repo brings back a dead mechanism.

Fix

Rewrite that note so it is true of the current files. Work out, rather than assume, where Go's test-result cache can still replay a pass: a --no-cache build starts every layer empty, so inside the scripted Docker builds there may be nothing to replay, while a native make test on a developer's machine or in the pre-commit hook still can. Keep the point that -count=1 is what defeats Go's own cache, say plainly where that matters, and drop anything about baked-in GOCACHE layers that no longer holds. Drop the reference to issue 26 if the sentence no longer needs it. Then check that no canonical document still names CHECK_EPOCH (git grep -n CHECK_EPOCH).

Definition of done

git grep -n CHECK_EPOCH on the branch is empty.
The note explains why -count=1 is needed, in plain words, says only what the current files do, and agrees with the "gate phases" bullets.
make check passes.

Model: opus-5-5

`prompts/REPO_POLICIES.md` on `next`, in the note under the canonical Go `make test` example (around line 319), says "`CHECK_EPOCH` guarantees the `RUN make test` _step_ re-executes". `CHECK_EPOCH` was replaced: every `docker build` in `script/` now passes `--no-cache` (the "gate phases" bullets of the same file, and `script/lint`, `script/test`, `script/cibuild`, `script/docker`). A reader who goes looking for `CHECK_EPOCH` finds nothing, and one who copies the sentence into a repo brings back a dead mechanism. ## Fix Rewrite that note so it is true of the current files. Work out, rather than assume, where Go's test-result cache can still replay a pass: a `--no-cache` build starts every layer empty, so inside the scripted Docker builds there may be nothing to replay, while a native `make test` on a developer's machine or in the pre-commit hook still can. Keep the point that `-count=1` is what defeats Go's own cache, say plainly where that matters, and drop anything about baked-in `GOCACHE` layers that no longer holds. Drop the reference to issue 26 if the sentence no longer needs it. Then check that no canonical document still names `CHECK_EPOCH` (`git grep -n CHECK_EPOCH`). ## Definition of done - `git grep -n CHECK_EPOCH` on the branch is empty. - The note explains why `-count=1` is needed, in plain words, says only what the current files do, and agrees with the "gate phases" bullets. - `make check` passes. Model: opus-5-5

clawbot referenced this issue from a commit

2026-10-04 05:20:04 +02:00

Rewrite the -count=1 note to match the current files (closes #77)

clawbot referenced a pull request that will close this issue

2026-10-04 05:21:36 +02:00

Rewrite the -count=1 note to match the current files (closes #77) #87

clawbot commented

2026-10-04 05:21:44 +02:00

Done in #87. The note now says Go's test result cache can replay a pass on a developer's machine, where the Makefile target runs, and has nothing to replay in the test phase of the Dockerfile. One point in the brief did not hold: the pre-commit hook builds the test phase in Docker and does not run go test on the host, so the note does not mention it.

Model: opus-5-5

Done in https://git.eeqj.de/sneak/prompts/pulls/87. The note now says Go's test result cache can replay a pass on a developer's machine, where the Makefile target runs, and has nothing to replay in the `test` phase of the `Dockerfile`. One point in the brief did not hold: the pre-commit hook builds the `test` phase in Docker and does not run `go test` on the host, so the note does not mention it. Model: opus-5-5

clawbot referenced this issue from a commit

2026-10-04 06:50:05 +02:00

Rewrite the -count=1 note to match the current files (closes #77)

clawbot referenced this issue from a commit

2026-10-04 07:05:46 +02:00

Rewrite the -count=1 note to match the current files (closes #77)

clawbot closed this issue

2026-10-04 07:31:49 +02:00

clawbot referenced this issue from a commit

2026-10-04 07:31:50 +02:00

Rewrite the -count=1 note to match the current files (closes #77)

Sign in to join this conversation.