nx_h2_conformance.nx

nx_h2_conformance.nx -- TUTOR-BOOTSTRAP SCAFFOLD (Claude, authored under the R4-H2 HTTP/2-transport-ladder workflow), NOT credited as team self-authoring. R4-H2-006 of the sovereign HTTP/2 transport ladder (knowledge/specs/2026-06-13-http2-transport-ladder.md). The CONFORMANCE harness: it composes ALL of the lower GREEN rungs -- HPACK (R4-H2-002), the frame codec (R4-H2-003), the stream state machine (R4-H2-004) and flow control (R4-H2-005) -- into a minimal HTTP/2 CLIENT CONNECTION SEQUENCE asserted over an IN-MEMORY / loopback byte stream (NO live network, NO sockets in the gate): preface -> empty SETTINGS -> HEADERS(GET, END_STREAM|END_HEADERS) -> expect peer SETTINGS + our SETTINGS-ACK exchange + response HEADERS + DATA. The byte sequence is the allowed internet-boundary requirement (RFC 9113 / 7541 dictate the exact octets so we interoperate); the IMPLEMENTATION is pure NishiLang via nx_cc -> nxasm_x86: no gcc, no openssl, no nghttp2. FOUNDED ON (composes, does not reinvent -- anti-orphan law): - nx_h2_flow.nx (R4-H2-005, GREEN): imported EXACTLY ONCE. It transitively splices nx_h2_frame.nx -> nx_hpack.nx -> nx_str.nx -> syscalls.nx, so this ONE import inherits the whole stack: the HPACK encoders (hpack_encode_indexed / hpack_encode_lit_inc_indexed_name), the frame builders (h2_write_preface / h2_frame_write_settings_empty / h2_frame_write_settings_ack / h2_frame_write_headers / h2_frame_write_data / h2_frame_read_header / h2_check_preface), the flow-window arithmetic (h2_flow_init / h2_flow_consume / h2_flow_is_data_frame), plus sys_mmap / sys_write / sys_exit / sys_openat_append / sys_close. Importing nx_h2_frame / nx_hpack / nx_str / nx_syscalls / nx_h2_stream directly TOO would be the RC6 double-import landmine. - nx_h2_stream.nx (R4-H2-004, GREEN): imported EXACTLY ONCE for the stream state machine (h2_stream_new / h2_stream_send_headers / h2_stream_recv_headers / h2_stream_recv_data). nx_h2_stream imports nx_h2_frame, and nx_h2_flow ALSO imports nx_h2_frame -- but each shared module is included at most once by the linker (include-guarded), so importing BOTH nx_h2_flow and nx_h2_stream here pulls nx_h2_frame in once. No floating capability: HPACK founds the codec founds the stream machine founds flow control founds THIS conformance/ALPN rung -- the top of the ladder. BACK-FILL: the team RE-AUTHORS this from the DATA spec via the emitter-of-emitters (X-AUT-006c/e/f) -- this hand-authored scaffold is the sanctioned one-time bootstrap only (meter-integrity, mirror nx_frame_codec.nx:13-16 / nx_h2_frame.nx:31-34 / nx_h2_flow.nx:30-33).