v0.32.8

docs/MEMORY_STRESS.md

@@ -28,20 +28,15 @@ with real-runtime measurements rather than assuming either explanation.
 ## Source/synthetic verification
 
 ```sh
-python3 tools/checks/memory_contracts.py
-python3 tools/checks/high_traffic_memory_model.py --http-requests 10000
 ./dev.sh check
 ./dev.sh test
+# Perform separate real-runtime load and RSS measurements on staging.
 ```
 
-The offline test replays 300,000 distinct PURGE identities over six periods.
-It verifies the old cumulative model retains 50k/100k/150k/200k/250k/300k
-metadata keys whereas the revised epoch-based model holds one key after each
-operation. This is a **cardinality model**, not a Rust heap measurement. It also
-sends 10,000 HTTP GETs across 24 concurrent persistent connections and 1,000
-paths to a **Python test peer** to validate the load driver (the default quick
-`./dev.sh test` run sends 2,000 of those requests). The Rust regression
-for 512 distinct purges is executed only if `cargo test` runs successfully.
+The old Python cardinality model and protocol-peer load driver were removed
+with `tools/checks/`. They were synthetic tests, not proof of RustProxy memory
+bounds. `./dev.sh test` now runs only the Rust suite; runtime memory behavior
+must still be verified by sustained staging traffic and RSS tracking.
 
 ## Real RustProxy staging traffic and RSS