nx_search_handler_flow.nx

nx_search_handler_flow.nx -- HUB primitive; site-agnostic search HTTP handler flow. Operator cardinal 2026-05-27: "make sure you make the onsite and offsite search reusable and not just tied to the wiki but with capabilities to be used on other sites". COMPOSES (HUB / runtime-level primitives only -- ZERO site imports): hub/nx_search_query_parser (query string -> NxSearchQuery) hub/nx_search_render_html (HTML render with per-site theme) nx_search_onsite_engine (NxSearchResults) nx_search_inverted (NxInvIndex) COMPOSED BY: wiki/nx_wiki_search_wiring (next commit) (future) obd-config search wiring (future) sprinkler-config search wiring (future) Nishi-hosted third-party site search per charter §3.5 V4 SEPARATION OF CONCERNS (per operator cardinal): This module owns the FLOW: parse -> execute -> render -> HTTP wrap. The SITE owns: 1. Building the index (when content changes) 2. The doc-store callback: given rowid, return title/url/body 3. The theme literals (per-site CSS class prefixes) 4. The HTTP route prefix matching ("/wiki/search" vs "/obd/search") The site never re-implements query parsing, AND-intersection, snippet extraction, or HTML emission -- those are HUB primitives. HOW SITES INTEGRATE (~50-line per-site wiring): 1. Allocate one NxSearchFlow at startup (large buffers reused) 2. Define site doc-store walker: given results.rowids[], fill the inputs.title_ptrs/url_ptrs/body_ptrs arrays 3. Build NxSearchRenderTheme with site CSS class prefixes 4. On HTTP request: extract query string, call nx_search_flow_run(flow, query_str, q_n, walker_fn, theme, resp_buf, resp_cap, resp_n) V1 SCOPE per NISHI_SEARCH_CHARTER.md §6: - End-to-end onsite query -> HTML response bytes - Site doc-store integration via pre-resolved inputs - QoS elapsed_us observable