Hazard review

• scenarioreviewedmalformed_inputboundaryedge_case

  Worst case: the stripper mangles authored content into different JSON - a URL or text containing // inside a string value gets tail-truncated as a comment, or a comma inside a string is eaten, so the file parses to silently wrong entries rather than failing loudly; the single-pass string-aware scanner (string contents copied verbatim, comments and pre-brace commas dropped only outside strings) is the control and is exactly the malformed_input handling this parser declares. boundary: EOF mid-comment and EOF mid-string terminate the pass without buffering errors, a file that strips to whitespace yields [], and a comma whose next non-whitespace character is } or ] is the exact drop condition. edge_case: escaped quotes and backslash escapes inside strings survive verbatim, inline comment tails wherever the opener sits are the fixed C8W1 sibling's subject, and the top-level array shape is the BMFE sibling's guard - both are pointer notes here, not re-reviewed.

• propertyrevieweddeterminism

  The strip is a single left-to-right state-machine pass with two states (in-string, outside), so one input yields one output every time - the same authored file parses to the same entries on every load, including across 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.