nx_meal_emit.nx

nx_meal_emit.nx -- MAIN: SEED the meal stores and RENDER the page. Idempotent end to end (rule 10): every seed is a value-compare put that writes nothing when unchanged, and the render simply overwrites its artifact. Run it twice, get the same estate. IT OWNS STORES AND MARKUP, AND NOTHING ELSE. Preserving the origin page is nx_meal_capture's job, in its own organ, because the decompressor it needs drags nx_runtime/nx_tier/nx_deflate/nx_crc32 in behind it and that destabilised the seg-store seeding here -- untouched code that had been green minutes before. Splitting on the job boundary (rule 9) was the fix, not a workaround: this organ reads the finished WARC and never decodes anything. It writes the page to a FILE and stops. Publishing is a separate deliberate act through nx_site_publish -- a renderer that also deploys is a renderer you cannot safely run just to look at the output. argv[1] = output html path (default /tmp/kitchen.html) license_tier: ORIGINAL No hw writes (Rule 26).