// ZPWR-HOOKS-EDITOR — ENGINEERING REPORT

>_EXECUTIVE SUMMARY

zpwr-hooks-editor is the shared stryke Hooks code editor of the MenkeTechnologies app stack — one JavaScript source of truth for a Monaco editor wired with monaco-vim, monaco-emacs and a thin stryke-LSP adapter. It was extracted from the Audio-Haxor frontend so the editor is no longer duplicated across apps; the source lives in src/ and each consuming app bundles it with its own monaco-* dependencies.

The bundle is produced with esbuild (IIFE, ES2020, minified) and exposes a single window.HooksEditor facade. Language intelligence — completion, hover, diagnostics, definitions, references, rename, signature help, document symbols, code actions, semantic tokens — comes from the stryke language server (stryke --lsp) over a caller-supplied transport, mapped onto Monaco's provider/marker APIs by a thin LSP JSON-RPC client.

Two Monarch grammars ship in the one bundle, picked per editor with create({ language }): stryke (the default, Perl tokens plus the full language server) and latex (grammar, structural snippets, document-driven \ref/\cite completion and a sectioning outline, with no language server). An app that edits LaTeX — zlatex's equation pane — reuses this editor instead of forking a second one, so the theme, the vim/emacs keymaps and the Monaco instance stay shared.

Counts derived from the repo: src/*.mjs = 3 files / 1091 lines; with scripts/build-hooks-editor.mjs = 4 files / 1179 lines; register…Provider(LANG_ID call sites = 13 (plus 3 LATEX_ID providers, 16 registrations in all); monaco.languages.setMonarchTokensProvider call sites = 2; window.HooksEditor methods = 5; consumers Audio-Haxor + traderview + ztranslator + zpwr-daw = 4; devDependencies in package.json = 4.

~ARCHITECTURE

One editor source, built per consumer. The entry registers the stryke and latex languages, the cyberpunk theme, the vim/emacs keymaps and the LSP↔Monaco provider mappings; the bundler runs inside each app to resolve its own Monaco deps and emit vendored IIFE artifacts.

&LSP PROVIDER SURFACE

The entry registers 13 Monaco language providers against the stryke language id, each mapping a stryke-LSP method onto Monaco's provider API (LSP positions/ranges are 0-based, Monaco 1-based; kinds and severities are translated). Diagnostics arrive as server notifications and are applied as Monaco model markers. The latex id carries 3 further providers of its own (two completion, one document symbol) that are computed locally from the model and never touch the server.

/BUNDLER & RESOLVE FIXES

scripts/build-hooks-editor.mjs emits two bundles — hooks-editor.bundle.js (+ .css) and hooks-editor.worker.js — and carries esbuild resolve overrides to avoid AMD define() builds that throw in the WebView and silently degrade the editor to a textarea. monaco-vim is forced to its ESM build (dist/index.mjs) because the browser condition's UMD bundle ships an embedded CodeMirror vim keymap with a bare define(). Bare monaco-editor imports are pinned to esm/vs/editor/edcore.main.js (the same lean ESM instance the entry uses) instead of the AMD min build monaco-emacs' require() would pull. Deep monaco-editor/esm/* subpaths without a file extension get .js appended and resolve to the package dir directly. The build defaults its output to <cwd>/frontend/lib and honors HOOKS_EDITOR_OUT.

$CI GATES

This is a non-Rust (frontend / JS) Tier-6 submodule, so it is exempt from the meta repo's cargo gates (fmt / clippy / doc / cargo test). The umbrella MenkeTechnologiesMeta repo enforces the documentation and brand gates on docs/:

#PROJECT METADATA