sneak, chat, 16 November about 22:35 UTC: "the cache busting isn't policy and shouldn't go into prompts. it is a one off task to fix. dont permanently memorialize our one time errors in context, just fix them."
Work
prompts/REPO_POLICIES.md on next: remove every sentence about Docker's build cache for check builds, including the "Check builds use Docker's normal cache" rule that #178 added. The policy says nothing about caching at all; the canonical scripts simply build without --no-cache or CACHEBUST, as they already do.
The rule that a new or changed check is proven by planting a defect: keep it only if it predates cache busting (check git log -S); if it was added as part of the cache-busting machinery, remove it too.
Change nothing else.
Definition of done
No sentence in prompts/ mentions build caching, --no-cache for docker build, or CACHEBUST. apk add --no-cache lines are unrelated and stay.
make check passes.
Model: opus-5-5
sneak, chat, 16 November about 22:35 UTC: "the cache busting isn't policy and shouldn't go into prompts. it is a one off task to fix. dont permanently memorialize our one time errors in context, just fix them."
## Work
- `prompts/REPO_POLICIES.md` on `next`: remove every sentence about Docker's build cache for check builds, including the "Check builds use Docker's normal cache" rule that https://git.eeqj.de/sneak/prompts/pulls/178 added. The policy says nothing about caching at all; the canonical scripts simply build without `--no-cache` or `CACHEBUST`, as they already do.
- The rule that a new or changed check is proven by planting a defect: keep it only if it predates cache busting (check `git log -S`); if it was added as part of the cache-busting machinery, remove it too.
- Change nothing else.
## Definition of done
- No sentence in `prompts/` mentions build caching, `--no-cache` for `docker build`, or `CACHEBUST`. `apk add --no-cache` lines are unrelated and stay.
- `make check` passes.
Model: opus-5-5
Built: #180 (branch issue-179-remove-build-cache-text, base next). It removes the normal-cache rule with its prune and planted-defect sentences, two cache sentences elsewhere in REPO_POLICIES.md, the README's cache paragraph and the checklist item on CACHEBUST. The planted-defect rule post-dates cache busting, so it went too.
Judgement call: Go's build cache mounts, the kept module and package layers and -count=1 stay, as separate owner rulings, not cache busting.
Model: opus-5-5
Built: https://git.eeqj.de/sneak/prompts/pulls/180 (branch `issue-179-remove-build-cache-text`, base `next`). It removes the normal-cache rule with its prune and planted-defect sentences, two cache sentences elsewhere in `REPO_POLICIES.md`, the README's cache paragraph and the checklist item on `CACHEBUST`. The planted-defect rule post-dates cache busting, so it went too.
Judgement call: Go's build cache mounts, the kept module and package layers and `-count=1` stay, as separate owner rulings, not cache busting.
Model: opus-5-5
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.
sneak, chat, 16 November about 22:35 UTC: "the cache busting isn't policy and shouldn't go into prompts. it is a one off task to fix. dont permanently memorialize our one time errors in context, just fix them."
Work
prompts/REPO_POLICIES.mdonnext: remove every sentence about Docker's build cache for check builds, including the "Check builds use Docker's normal cache" rule that #178 added. The policy says nothing about caching at all; the canonical scripts simply build without--no-cacheorCACHEBUST, as they already do.git log -S); if it was added as part of the cache-busting machinery, remove it too.Definition of done
prompts/mentions build caching,--no-cachefordocker build, orCACHEBUST.apk add --no-cachelines are unrelated and stay.make checkpasses.Model: opus-5-5
Built: #180 (branch
issue-179-remove-build-cache-text, basenext). It removes the normal-cache rule with its prune and planted-defect sentences, two cache sentences elsewhere inREPO_POLICIES.md, the README's cache paragraph and the checklist item onCACHEBUST. The planted-defect rule post-dates cache busting, so it went too.Judgement call: Go's build cache mounts, the kept module and package layers and
-count=1stay, as separate owner rulings, not cache busting.Model: opus-5-5