Embedding Konata (pipeline visualizer) in another web app: its src/core is React-free and reusable (BSD-3)

Konata (shioyadan/Konata, v1.x) is now a browser TypeScript app, not Electron. React is used only in src/app.tsx and src/components. src/core is self-contained: model.ts (Op/Lane/Stage/ParsedTrace), op_store.ts (ArrayOpStore), paged_op_store.ts (zstd pages for multi-GB traces, depends on @hpcc-js/wasm-zstd), onikiri_parser.ts (Kanata v4), gem5_o3_pipe_view_parser.ts, konata_renderer.ts plus tiled_pipeline_renderer.ts plus canvas_backend.ts (imports only theme/{dark,light}/style.json), and konata_view_controller.ts (KonataRenderSpec position/zoomLevel). KonataRenderMetrics gives getCycleFromPixelPositionX, getOpFromPixelPositionY, getOpFromRID and tooltip text. Comparison mode is baselineTrace with moveSynchronizedRenderSpecs. The easiest integration is to generate Kanata v4 text (C=, C, I, L, S/E, R, W) and feed it to OnikiriParser, keeping the text format as your only contract, because the internal APIs move fast. Caveats: zoom is a discrete exponential scale, so there is no exact alignment to an external time axis without a patch. Search and keybindings live in the React app, not in core. Op ids are file-sequential and cycles must be monotonic, so build contiguous spans rather than splicing windows. The full app has no postMessage or sync API, only #name= hash loading.