nx_build_site.nx

nx_build_site.nx -- bits-up site builder. Replaces nishi-pages/build/build.py (530 LOC Python) with NishiLang substrate. Per user *"no python nothing but nishi from bits up"*. Pipeline: 1. Read content/site.yaml -> NxYamlDoc site vars (lifted to site.*) 2. Read theme templates: layout.html, index.html, post.html, page.html 3. For each .md in content/posts/: nx_build_doc round-trip emit a post-summary HTML block (for the homepage posts list) write dist/posts/<slug>.html 4. For each .md in content/pages/: nx_build_doc round-trip with PAGE template write dist/pages/<slug>.html 5. Build the homepage: substitute site.* + posts_html (concatenated summaries) wrap with layout.html write dist/index.html What this v1 does NOT do (queued): - Dynamic directory walking (uses a hardcoded list of slugs) - dist/404.html generation - style.css copy to dist/assets/ - server/pages.nx route emit These are easy follow-ups that compose with what's here. Memory budget (one rendering pass): ~64K per .md scratch ~32K per template ~256K total site arena nx_safety_envelope: intended_use: sovereign substrate builder for nishi-pages sil_target: SIL2 evidence: bench/nx_build_site_smoke.nx renders a fixture tree end-to-end and asserts output bytes verdict: NOT_YET_EVALUATED -- pending smoke