Hazard review

• scenarioreviewedmalformed_inputboundaryedge_caseinput_domain

  PR omacom/omarchy#13968 review (2026-10-01). stripJsonc is one string-aware scanner: string contents are copied verbatim, a // comment outside a string is dropped up to but not including its line break, a comma is dropped only when the next character that is neither whitespace nor part of a // comment is } or ], and any other JS \s character outside a string is passed on as a space (a line feed stays a line feed). Worst case: the stripper mangles authored content into different JSON, so the file parses to silently wrong entries (a comma or // inside a string eaten, as the upstream regexes did - #13250), or a correct file is rejected (an inline tail - #13493; a trailing comma before a commented-out entry - the #13512 regression; a byte order mark or Unicode space - the regression in the PR's first commit ff77cd02, fixed by its second commit b2dae8db). The controls are the decomposed rules SW-REQ-260927-66FW, SW-REQ-260928-C8W1 and SW-REQ-261001-BNZG with their witnesses, the preservation tests (incl. the shipped extension template with its examples uncommented) and the seeded differential test against an independent reference model in test/node/menumodel-replay.test.mjs. Block comments stay unsupported (KI-MENU-JSONC-STRIP-GAPS). boundary: end of input inside a comment or a string ends the pass without error; a file that strips to whitespace yields []; a comma at end of input is kept. edge_case: an escaped quote or an escaped backslash inside a string, a whole-line comment with an unbalanced quote, CRLF line endings, and a comment between two tokens (the line break keeps them apart). Catalog 1.11.0 re-review: input_domain applied, input_domain is on its obligation checklist: LF, CRLF, comment indentation with any JS whitespace, any character inside strings and huge files are accepted. With this PR any JS whitespace character between tokens is read as a space (SW-REQ-261001-BNZG), which fixes KI-MENU-JSONC-UNICODE-WHITESPACE. A CR-only file with a whole-line comment still empties the menu (KI-MENU-JSONC-CR-LINE-ENDINGS); this PR does not change it. concurrency_scale not applicable, a pure function of its arguments, recomputed on each load or keystroke: no state across calls, no process, timer or lock.

• propertyrevieweddeterminism

  The strip is a single left-to-right pass with two states (in a string, outside), so one input yields one output every time. The same authored file parses to the same entries on every load, including the file watcher's reloads.

• structuralnot applicable

  Character-classified string concatenation in a bounded single pass; no memory management, pointer math, or numeric surface, and no encoding transform - bytes pass through verbatim outside the two strip rules.

• domainnot applicable

  The parser consumes the two fixed local menu JSONC paths (same-user, no egress sink in the traced files), and the parse-failure recovery policy (empty list, defaults preserved) is owned by the failure-arm siblings (3T3F/66FW), so no domain class binds to the strip contract reviewed here.