nx_nishios_docview.nx

nx_nishios_docview.nx -- DOC-OMNITOOL-ON-ALL-OS, rung N-DOC-1: NishiOS OPENS DOCUMENTS. Operator (2026-07-08): "i want nishi browser and os to support rendering these different docs ... the browser is becoming the workhorse of systems." The Linux browser side shipped (nx_browser + nx_doc_view fork-dispatch, gate 7/7, live PNG proof). This rung puts the same capability on NISHIOS, following the proven nx_nishios_browser idiom: boot the persisted NishiOS image on the sovereign x86 emu, and ONLY because the disk-loaded kernel reached LONG mode does the OS app layer open a DOCUMENT -- a persisted .md file read back off disk -> the ON-OS VIEWER REGISTRY (ext -> renderer id; NishiOS has no process fork yet, so renderers LINK as libs (nx_md_lib) and are invoked at ONE dispatch point; adding a format = one registry row + one lib import, the dispatch core never changes) -> md_to_html -> br_layout -> br_draw_fb -> composited into the NishiOS desktop as a "NISHI DOCS" window. Export = knowledge/status/ nishios_docview.bmp + .html = one picture of "boot NishiOS -> open report.md natively". KAT: T1 booted off the persisted image; T2 LONG mode; T3 UART banner 'NishiOS'; T4 registry routes .md AND refuses .xyz; T5 conversion real (h1/bold/link/blockquote/pre markers in the produced HTML); T6 REAL layout (ok, boxes>=15, page_h>=100); T7 heading ink pixels; T8 link-blue pixels; T9 body-text pixels; T10 BMP exact size; T11 NEG 0-sector image never reaches long mode -> viewer never fires; T12 NEG empty document collapses the box count vs the real document (content-sensitive evidence). HONEST SEAM (same as nx_nishios_browser): the emu EXECUTES the MBR loader + real->protected->long transition off the on-disk bytes; the doc pipeline then runs in NishiLang as the OS's app layer painting nx_fb. Renderers as x86-on-emu processes via nx_nxe_loader, on-OS networking, and live input remain future rungs -- named, not claimed. MEASURED (BMP palette probe, 07-09): on this author-styled page the render core paints its DEFAULT ink palette -- headings #14142b (20,20,43), body #202124 (32,33,36) -- author-CSS text colors (link-blue, pre backgrounds) are NOT yet applied; that render-core CSS-color rung is likewise named, not claimed. The pixel KATs below assert the MEASURED palette, not a wished one. NEVER-BRICK (Rule 26): FILE artifacts only; models INT 13h *reads*. expect_exit: 0 license_tier: ORIGINAL