Preserve maintenance timeout behavior and prepare SILO 20261026

Signed-off-by: Feng Ruohang <rh@vonng.com>

CONTRIBUTING.md

@@ -53,15 +53,19 @@ Before opening a pull request:
 - Explain any preserved `MINIO_*`, `minio_*`, `x-minio-*`, `/minio/*`,
   `.minio.sys`, ARN, module/import-path, or serialized compatibility name.
 
-The maintenance branch retains the existing read-quorum and healing policy.
-Deferred strict-read and cross-pool recovery tests are preserved behind the
-`consistency_strict` build tag. Run them explicitly with
-`go test -tags kqueue,dev,consistency_strict ./cmd`; known failures must be
-reported separately, not described as fixed or included in a passing result.
-They cover late commits after lease loss, stale metadata reads, and stricter
-read refusal. The normal suite covers the retained write/undo/cleanup fixes
-and continued readability after a failed partial overwrite. This scope does
-not provide distributed fencing or repair previously inconsistent objects.
+The maintenance branch retains existing storage timeouts, cancellation,
+object locking, read-quorum and healing behavior. The normal suite checks local
+and RPC timeout/cancellation, remote rollback options, and readability after a
+failed partial overwrite. A timeout does not prove that a disk worker stopped
+or that a write did not commit.
+
+Stronger mutation lifetime, rollback ownership, generation ordering, strict-read
+and cross-pool recovery diagnostics are preserved behind `consistency_strict`.
+Compile them with `go test -tags kqueue,dev,consistency_strict ./cmd -run '^$'`
+and run individual scenarios explicitly. They describe guarantees outside the
+maintenance contract and may fail; report their results separately from the
+normal suite. They must not be used to claim distributed fencing or repair of
+previously inconsistent objects.
 
 ### Commit changes