azcomputerguru/claudetools
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

sync: auto-sync from GURU-5070 at 2026-05-31 16:35:50

Browse Source 
Author: Mike Swanson
Machine: GURU-5070
Timestamp: 2026-05-31 16:35:50
This commit is contained in:
Mike Swanson
2026-05-31 16:35:55 -07:00
parent 85509a71dc
commit d17e9be135
2 changed files with 97 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
.claude/memory/reference_guru5070_rust_toolchain.md
View File

@@ -24,3 +24,11 @@ built/linted/tested locally — **no more build-host (172.16.3.30) round-trips j
**How to apply:** when a Coding Agent works on GuruConnect Rust, have it self-verify with the local toolchain
(set PROTOC, run the four gates, iterate to green) and commit CI-green code — don't delegate fmt/clippy to the
build host. See [[project_guruconnect_v2_direction]].
**CI fmt gate — don't omit it from agent briefs (incident 2026-05-31):** the CI `Build Server (Linux)` job runs
`cargo fmt --check` as a hard gate FIRST (before build/test). SPEC-004 Task 2 + Task 4 (commits ffca7f0, 4e80573)
went red on Linux CI even though the Coding Agents reported "clippy clean, tests pass" — because the briefs listed
only `cargo check` + `clippy` + `test` and NOT `cargo fmt --check`, so rustfmt drift slipped through (compactly-
written new test code). Fixed with a `cargo fmt` follow-up commit (cef1928). **Every Coding-Agent brief that
touches GuruConnect Rust MUST list `cargo fmt --check` (server: `cd server && cargo fmt --check`) as a required
gate alongside clippy/test** — a clippy-clean, test-green change can still fail CI on formatting.