4 Commits

Include renames

Author	SHA1	Message	Date
clawbot	fd48065f03	Keep modules, lint cache and system packages in check builds (closes #109) ... Re-vendors REPO_POLICIES.md, script/cibuild, script/docker, script/lint and script/test from sneak/prompts next at 0653579, on sneak's ruling in sneak/prompts#130. In the lint, test and builder stages of the Dockerfile, the module download, and in builder the apk install, move above ARG CACHEBUST, so Docker keeps those layers until the base image, the install line, go.mod or go.sum changes. golangci-lint run also mounts golangci-lint's cache. Every step that lints, tests or compiles still comes after ARG CACHEBUST, and go test keeps -count=1 and -race. README and TODO.md say the same. Model: opus-5-5	2026-10-18 15:04:08 +00:00
clawbot	198cefa152	Re-vendor the canonical files from sneak/prompts at e3f79c4 (closes #95) ... Every vendored file, REPO_POLICIES.md and every model script is the copy at sneak/prompts e3f79c4, with this repository's own entries kept after the canonical content. Lint and test are Dockerfile phases that write no image; make test runs the suite under the race detector as nobody. Every build in script/ passes a new CACHEBUST value, which every stage declares first, so every RUN step runs again; the steps that compile keep Go's build cache, and both go test runs pass -count=1. Dockerfile.lint, script/verify-lint-image-pin and make test-race are gone, prettier runs on the host, and .claude/settings.json is deleted. Deviation: the set comes from e3f79c4 on next rather than dd4027b. Judgement call: the test phase mounts the cache at nobody's /tmp/.cache/go-build, owned by nobody. Model: opus-5-5	2026-10-15 18:28:54 +02:00
clawbot	99d757c31d	Re-vendor REPO_POLICIES.md from the canonical copy (closes #20) ... The vendored copy had drifted to 368 lines against the canonical 408 while still declaring `last_modified: 2026-07-06`, so nothing about the file signalled that it was stale. Agents working in this repo read the vendored copy to learn the rules, which makes a silent 40-line gap a source of real defects rather than untidiness: two have already been traced to exactly this drift, `script/fmt` having dropped the prettier Markdown pass (#19, still open) and the README having no Entrypoints section (#21, since fixed). Restored by copying the canonical file wholesale — no hand-editing, no partial merge, no local adaptation, because it is a vendored copy and its value comes from matching upstream byte for byte. What comes back: - the entire Scripts to Rule Them All section, including the POSIX sh requirement, the repo-root discovery idiom, and the division between the standard's canonical scripts and our four extensions - `bootstrap`, `setup` and `hooks` in the required Makefile target list - the `script/precommit` paragraph and how the pre-commit hook is wired through `script/install-precommit` - the README **Entrypoints** section requirement - the Dockerfile bootstrap-layer guidance and the `script/cibuild` wording in the Gitea Actions bullet Verified: `diff` against the canonical file is empty, sha256 is 117dde7f148ed3cd693b333312f6345a0a0ee84fadbbe5cca559ca6fed4a1775, and `REPO_POLICIES.md` is the only changed path. `make check` is green. No `TODO.md` entry accompanies this commit. The repo convention is to record the work in the same commit, but the issue's definition of done restricts the change to `REPO_POLICIES.md` alone; that scope discipline is what lets a docs-only change skip adversarial review.	2026-08-09 09:57:43 +00:00
sneak	2512ae797b	Add REPO_POLICIES.md from canonical source (2026-07-06)	2026-07-22 22:24:04 +07:00