27e6765a43
RULES.md gains "The machine you build on": check memory, load and running builds first, cap Cargo jobs and test threads, run at low priority, one heavy job at a time, stop when the person says the machine is slow, and clean up scratch targets. Locally only the test targets a change touches run; the full suite runs on GitHub before a release. AGENTS.md, CONTRIBUTING.md and the PR checklist say the same. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
829 B
829 B
What and why
How I tested it
AI assistance
Screenshots
Checklist
- Tests first; new code is covered, error paths included
cargo fmt --all,cargo clippy --all-targetsand the affectedcargo test --testtargets pass- Follows RULES.md (no overflow, data safety, one undo step per tool call)
- Docs, tool descriptions and
PROGRESS.mdupdated where needed - Conventional commit messages
- I read and understand every line of this change (AI-assisted or not)