diff --git a/README.md b/README.md
index eeeab2e..d9f18c5 100644
--- a/README.md
+++ b/README.md
@@ -558,11 +558,14 @@ bash scripts/selftest.sh --fast   # fixture-only suites, no compiler
 Both run in CI — `.gitea/workflows/ci.yaml`, one job, on pushes to `main` and
 on PRs that were non-draft when the run was created. It installs shellcheck
 and both a stable and a nightly Rust toolchain (nightly so
-`hardlink-clone-selftest.sh` can run its content-freshness scenario — which no
-nightly currently enables, so it is skipped and the step is kept only against
-the day upstream restores it) and references no credentials; the scratch
-workspaces the compiler-backed suites build use path dependencies only, so
-nothing reaches crates.io. It runs the full suite rather than `--fast`,
+`hardlink-clone-selftest.sh` can run its content-freshness scenario, which as
+of 2026-08-26 a nightly does enable — 1.100.0-nightly (787af2b8c 2026-08-25)
+resolves freshness by content given both `CARGO_UNSTABLE_CHECKSUM_FRESHNESS`
+and `CARGO_BUILD_FINGERPRINT: content`, per cargo PR #17382; the suite still
+settles that by experiment on every run and skips the scenario loudly when it
+cannot measure) and references no credentials; the scratch workspaces the
+compiler-backed suites build use path dependencies only, so nothing reaches
+crates.io. It runs the full suite rather than `--fast`,
 because the two compiler-backed suites are the ones that check this scheme
 against real Cargo instead of against a fixture. Draft (`WIP:`-titled) PRs
 skip it, and un-drafting does **not** un-skip them — the guard is evaluated