docs(theme): record stale candidate cache correction

This commit is contained in:
Joseph Doherty
2026-11-13 17:34:22 -05:00
parent f698f97889
commit 37cf0ff444
3 changed files with 20 additions and 0 deletions
@@ -42,3 +42,14 @@ No fleet-wide consumer acceptance, application deployment, G2 extraction decisio
or G3 completion is claimed. Every consumer adopts this exact common patch and
performs its chapter checks. Human screen-reader listening and additional browser
engines are separately recorded runtime limits, not fabricated passes.
## Default-cache correction
A later consumer's exact HTTP CSS check detected the first unpublished candidate
in the default NuGet1.0.1 cache. Root had created it during initial local canaries.
Final accepted runtime/tests used isolated final-package caches and independent
published-feed restore, so their bytes are unaffected. Root removed only the
recognized superseded hash and refilled from the official feed; both new default
package hash and source metadata match the delivered artifact. See
`default-cache-correction.json`. Consumers still establish exact restored hashes;
assembly version alone cannot distinguish unpublished candidates of one version.