[Aursen]

Summary

 .github/workflows/ci.yml
-  Install Solana CLI v4.1.2   (+ no-op `export PATH="$GITHUB_PATH:$PATH"`)
+  Install Agave CLI v4.3.2
 Cargo.toml
-  agave-* / solana-{builtins,fee,program-runtime,svm-*,...} = "4.3.0"
+  agave-* / solana-{builtins,fee,program-runtime,svm-*,...} = "4.3.2"
 justfile (bench)
-  cargo build-sbf --tools-version v1.53
+  cargo build-sbf              # default platform-tools v1.57, same as CI
 README.md
-  Solana CLI >= 1.18.8 required
+  Agave CLI v4.3.2, the version used in CI

Cargo.lock already resolved these crates to 4.3.2; this aligns the manifest requirements and the toolchain.

Evidence

• Before: CI built test programs with Solana CLI v4.1.2 while runtime crates were on 4.3.x; bench pinned the older platform-tools v1.53.
  After (local, Agave v4.3.2): cargo build-sbf in test_programs builds cleanly; cargo test 166 passed / 0 failed; cargo clippy --all-targets -D warnings clean; cargo metadata --locked OK.

Merge Danger

Door: two-way

Patch-level version bumps plus CI/doc tweaks; revert is trivial.

Blast Radius: small

Downstream users get a 4.3.2 minimum for the Agave crates instead of 4.3.0.