docs(nwsync): purge the edge after a repair, or verify answers per PoP

emit --verify repairs the storage zone; verify reads the pull zone in front of it, on purpose, because the edge is what a player gets. A repair is the first thing that ever makes a content-addressed key serve different bytes, so between the two a warm PoP still answers with the old blob and a cold one with the new — and verify's verdict settles nothing until the zone is purged. The purge stays out of emit: it is one call for the whole zone after a repair, against a CDN credential emit deliberately does not hold. The procedure itself lives in sow-platform's NWSync runbook. Closes #89. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-08-01 00:52:00 +02:00
parent 7cc53aeb68
commit 53cd6a79fb
2 changed files with 14 additions and 0 deletions
@@ -67,6 +67,8 @@ check on a published blob upstream of a player's client.
 --verify makes emit hash what it would otherwise skip. emit normally treats a
 blob's presence as proof of its contents, so without this an object written
 truncated, or written by an emitter since found broken, is skipped forever.
+--verify repairs the storage zone, while verify reads the edge in front of it,
+so purge the pull zone after a repair or verify answers differently per PoP.

 --out DIR writes to a local repository tree instead of uploading, which is the
 conformance path against upstream nwn_nwsync_write. Without it, the zone comes