REPO_POLICIES.md is a stale copy: it mandates a 30s test timeout the org policy replaced with 90s #196
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Milestoned 1.0.0. Docs-only, but it actively misleads and it will cause churn against work landing right now.
REPO_POLICIES.mddeclares in its front matter that it is synced from https://git.eeqj.de/sneak/prompts. The local copy is stale —last_modified: 2026-07-06against upstream's2026-08-07— and has drifted in three substantive places, all of them upstream being newer:make testmust complete in under 20 seconds. Add a 30-second timeout in the Makefile." Upstream (commita868689, prompts PR #42, "Raise org-widemake testcap to 60s, backstop timeout to 90s") says the hard cap is 60 s, the target is 20 s, a suite between 20 and 60 s is still green but its overage must be filed as an improvement bug, and the Makefile backstop is 90 s — deliberately above the hard cap so it catches a hung test rather than a merely slow one.-timeout 30sin both the plain and verbose-rerun invocations, against upstream's-timeout 90s.go installline.Nothing else differs; the whole delta is 30 diff lines.
Why this is worth fixing before the tag rather than after
It has already caused a concrete error. Working #194 I read this file, concluded the org policy mandated 30 s, and was about to open a speculative PR against
sneak/promptsproposing a change that had already been made — nearly spending someone's review attention on a question that was closed a fortnight ago.It will also cause churn in the other direction: #195 raises this repo's test timeout, and a future compliance pass reading this stale file would revert it to 30 s and reintroduce the defect 194 exists to fix. That PR carries a note in
script/testguarding against exactly that, which stops being necessary once this file is correct.Definition of done
REPO_POLICIES.mdmatches upstreamprompts/REPO_POLICIES.md— take upstream wholesale rather than merging hunk by hunk, since this file is a synced copy and not a place for local edits.script/test. Report what you found either way.Implementation requirements
next, PR based onnext, single commit, title ending(closes #N).REPO_POLICIES.md, no adversarial review is needed. If you find yourself changing code orscript/, stop — that is a different unit.TODO.md(see #112).make fmtand include the result; never commit unformatted markdown. Gate onmake check.