nx_publish_verify.nx

nx_publish_verify.nx -- THE LAST STEP OF THE PUBLISHING LOOP: is the page the PUBLIC URL serves the page the emitter just wrote? (operator 2026-09-02: "beach wasnt receiving the updates for review and still isnt ... the pipeline needs to be fully mature"). WHY THE LOOP WAS OPEN: nx_craft_emit's [5/5] SHIPPED step reads the FILE back and verifies its marker -- it proves the write landed on disk and nothing about what a visitor receives through the edge (cache, a stale docroot, a route pointing at an older tree, an injected banner). nx_page_verify proves the served page's assets fetch and decode and says nothing about WHICH build it is. Neither answers the reviewer's question "am I looking at the build you just shipped?", so the reviewer answered it by eye and was wrong for a day. WHAT THIS DOES, composing the estate's own instruments and never a third-party client: reads the emitted file's build stamp (`REVIEW STAGE b<epoch>` in the <title>, written by nx_game_page_emit), fetches the PUBLIC URL through the sovereign TLS client (forks nx_https_get with the our-domain connect override so the request crosses the real edge), reads the served stamp, and prints ONE verdict line a human or a seat can act on: SERVED-CURRENT the edge serves the stamp the file carries (exit 0) SERVED-STALE the edge serves an OLDER (or different) stamp (exit 1) -- both stamps and the byte delta printed NO-MARKER the file or the served page carries no stamp (exit 4) UNREACHABLE the fetch failed; nothing is claimed about the page (exit 3) plus the REVIEW URL with every see-it lever on (?review=1&cast=1&hud=1) so the reviewer is never left to guess a query string. The served body may legitimately exceed the file (the edge injects its notice bytes); the delta is PRINTED, never hidden. nx_publish_verify <world> [base-url] (default base https://nishifamily.com/world/ ; file sites/nishifamily/world/<world>.html) license_tier: ORIGINAL No hw writes (Rule 26).