CORRECTIONS
This is a publishing and release-data correction log, not a service-availability or security-incident history. Each entry separates the observed defect, the correction and the proof boundary.
Observed. Two role-specific machine-readable route files declared version 1.3.5 as both the current and previous version. Seventy-three non-null previous objects repeated current-release artifacts. Two routes had no predecessor.
Corrected. The two files were regenerated so previous_version is 1.3.4, exactly 73 non-null predecessor objects match the corresponding 1.3.4 catalog record, exactly two remain null, and no predecessor object equals its current 1.3.5 object.
Verified. Final public readback parsed both files and confirmed the route and lineage invariants.
Boundary. This correction establishes machine-readable release lineage. It does not prove device compatibility or installation suitability.
Observed. A hosting editor save appended one final line-feed byte to an exact JSON candidate. The rendered text appeared equivalent, but the public bytes and SHA-256 did not match the accepted candidate.
Corrected. A separate one-byte correction restored the accepted 233,622-byte object and SHA-256 6a4f6297b307d13822d56eca72836742dec3b8b518e22daf4749edf8249cc962.
Verified. Public byte comparison and checksum readback matched the accepted candidate.
Boundary. Visual equality is not byte identity. This event justifies exact comparison after every editor-mediated save.
Observed. The site generator rendered video README files as README.html, while the first page condition matched only directory-form routes. As a result, VideoObject was absent on three live detail pages.
Corrected. The condition and regression tests were updated in a separate correction. Final live readback found VideoObject, thumbnailUrl, uploadDate, duration and the exact public content URL on all three pages.
Verified. Final public detail-page readback passed 3/3.
Boundary. Structured metadata availability does not prove that a search engine indexed or selected the video.
Observed. A deleted external knowledge-graph identifier remained in a bounded 23-file target set. A fresh baseline found 56 literal occurrences.
Corrected. Only the dead identity assertions and visible references in that target set were removed. Canonical and hreflang values were preserved; unrelated routes, binaries, assets, sitemaps and verification files were excluded from the write.
Verified. Final public readback passed 23/23 target files with zero remaining literals in the bounded set.
Boundary. Corrected owned bytes do not prove search-engine recrawl, cache replacement or downstream entity-graph repair.
Future entries must include a date, exact affected surface, observed state, accepted correction, verification method and explicit limitation. An unverified anecdote is not added as an incident.
Published 2026-08-27 ยท Updated 2026-08-27
VNISH GLOBAL publishes role-based evidence without personal identities. Verify current facts against the linked owned source, release record, DOI or archive snapshot.