Docs-only: REPO_POLICIES.md and nothing else. No code, config, scripts, CI or build files touched, so no adversarial review per repo policy.
Taken wholesale from sneak/prompts at a8686891ba61db895ec1d0dd71111c07950f3a62 ("Raise org-wide make test cap to 60s, backstop timeout to 90s", prompts PR #42). This file's front matter declares it a synced copy, so it is not a place for local edits or hunk-by-hunk merging.
What was stale
last_modified was 2026-07-06 against upstream's 2026-08-07. Three substantive hunks, all upstream being newer:
Test duration. Was "make test must complete in under 20 seconds. Add a 30-second timeout in the Makefile." Now: 60 s hard cap, 20 s target, a suite between the two still green but its overage filed as an improvement bug, and a 90 s Makefile backstop deliberately above the hard cap so it catches a hung test rather than a merely slow one.
The Makefile example in the same section, -timeout 30s to -timeout 90s in both the plain and verbose-rerun invocations.
The golangci-lint section, extended upstream with the canonical version (v2.12.2, 2026-05-06) and its commit-pinned go install line.
Whole delta is 14 insertions, 6 deletions.
Dependency check
The definition of done asked what in this repo depended on the stale text. One thing:script/test:9, go test -v -race -timeout 30s ./... — the figure the old text mandated. That line is #195's to change and is deliberately not touched here; the two units are disjoint by file. Nothing else in Makefile or script/ references the timeout, the 30 s figure, or the 20 s target.
Worth stating plainly, since it is the reason this was filed: this repo is currently in breach of the policy this file now carries.make test measures 62.9-68.4 s in recent cache-defeated builds against the 60 s hard cap. That is pre-existing, is not created by this sync, and is being sized separately — the sync makes the breach visible rather than causing it.
Gate
make bootstrap, then make fmt (no reflow beyond the copy), then make check — exit 0, lint in Docker 0 issues. in 46.90 s. No containers left running, no image tagged, no prune of any kind.
Closes https://git.eeqj.de/sneak/webhooker/issues/196.
Docs-only: `REPO_POLICIES.md` and nothing else. No code, config, scripts, CI or build files touched, so no adversarial review per repo policy.
Taken **wholesale** from `sneak/prompts` at `a8686891ba61db895ec1d0dd71111c07950f3a62` ("Raise org-wide `make test` cap to 60s, backstop timeout to 90s", prompts PR #42). This file's front matter declares it a synced copy, so it is not a place for local edits or hunk-by-hunk merging.
## What was stale
`last_modified` was `2026-07-06` against upstream's `2026-08-07`. Three substantive hunks, all upstream being newer:
- **Test duration.** Was "`make test` must complete in under 20 seconds. Add a 30-second timeout in the Makefile." Now: 60 s hard cap, 20 s target, a suite between the two still green but its overage filed as an improvement bug, and a **90 s** Makefile backstop deliberately above the hard cap so it catches a hung test rather than a merely slow one.
- **The Makefile example** in the same section, `-timeout 30s` to `-timeout 90s` in both the plain and verbose-rerun invocations.
- **The golangci-lint section**, extended upstream with the canonical version (v2.12.2, 2026-05-06) and its commit-pinned `go install` line.
Whole delta is 14 insertions, 6 deletions.
## Dependency check
The definition of done asked what in this repo depended on the stale text. **One thing:** `script/test:9`, `go test -v -race -timeout 30s ./...` — the figure the old text mandated. That line is https://git.eeqj.de/sneak/webhooker/pulls/195's to change and is deliberately not touched here; the two units are disjoint by file. Nothing else in `Makefile` or `script/` references the timeout, the 30 s figure, or the 20 s target.
Worth stating plainly, since it is the reason this was filed: **this repo is currently in breach of the policy this file now carries.** `make test` measures 62.9-68.4 s in recent cache-defeated builds against the 60 s hard cap. That is pre-existing, is not created by this sync, and is being sized separately — the sync makes the breach visible rather than causing it.
## Gate
`make bootstrap`, then `make fmt` (no reflow beyond the copy), then `make check` — **exit 0**, lint in Docker `0 issues.` in 46.90 s. No containers left running, no image tagged, no prune of any kind.
The local copy was stale at last_modified 2026-07-06 and still mandated
a 20s test target with a 30s Makefile timeout. Upstream a868689 replaced
that with a 60s hard cap and a 90s backstop, and also added the
canonical golangci-lint version to the lint section.
Taken wholesale from sneak/prompts a868689; this file is a synced copy,
not a place for local edits.
clawbot
merged commit a55b6f4e55 into next2026-08-18 09:33:29 +02:00
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.
Closes #196.
Docs-only:
REPO_POLICIES.mdand nothing else. No code, config, scripts, CI or build files touched, so no adversarial review per repo policy.Taken wholesale from
sneak/promptsata8686891ba61db895ec1d0dd71111c07950f3a62("Raise org-widemake testcap to 60s, backstop timeout to 90s", prompts PR #42). This file's front matter declares it a synced copy, so it is not a place for local edits or hunk-by-hunk merging.What was stale
last_modifiedwas2026-07-06against upstream's2026-08-07. Three substantive hunks, all upstream being newer:make testmust complete in under 20 seconds. Add a 30-second timeout in the Makefile." Now: 60 s hard cap, 20 s target, a suite between the two still green but its overage filed as an improvement bug, and a 90 s Makefile backstop deliberately above the hard cap so it catches a hung test rather than a merely slow one.-timeout 30sto-timeout 90sin both the plain and verbose-rerun invocations.go installline.Whole delta is 14 insertions, 6 deletions.
Dependency check
The definition of done asked what in this repo depended on the stale text. One thing:
script/test:9,go test -v -race -timeout 30s ./...— the figure the old text mandated. That line is #195's to change and is deliberately not touched here; the two units are disjoint by file. Nothing else inMakefileorscript/references the timeout, the 30 s figure, or the 20 s target.Worth stating plainly, since it is the reason this was filed: this repo is currently in breach of the policy this file now carries.
make testmeasures 62.9-68.4 s in recent cache-defeated builds against the 60 s hard cap. That is pre-existing, is not created by this sync, and is being sized separately — the sync makes the breach visible rather than causing it.Gate
make bootstrap, thenmake fmt(no reflow beyond the copy), thenmake check— exit 0, lint in Docker0 issues.in 46.90 s. No containers left running, no image tagged, no prune of any kind.