Syntax highlighting issue: read(__E5) is not colored correctly in wp-editor

[datasc31]

Description:
In the WarpParse editor platform, syntax highlighting does not correctly apply color to read(__E5).

While other similar expressions such as read(__E1) / read(__E2) / read(__E3) / read(__E4) are highlighted correctly, read(__E5) is rendered with incorrect or missing color styling.

This leads to inconsistent syntax highlighting and may confuse users when editing OML rules.

Environment:

• Platform: wp-editor (web)
• Editor version: wp-editor 1.10.0
• Engine version: warp-engine 1.14.0
• Browser: (fill if needed)

Reproduction Steps:

1. Open wp-editor.

2. Use or paste the following OML snippet:

   EventId = read(__target) | get(id);
   EventTemplate = read(__target) | get(tpl);

   __target = match read(Content){
   starts_with('jk2_init() Found child') => read(__E1);
   starts_with('workerEnv.init() ok') => read(__E2);
   starts_with('mod_jk child workerEnv in error state') => read(__E3);
   contains('Directory index forbidden by rule:') => read(__E4);
   starts_with('jk2_init() Can''t find child') => read(__E5);
   };

3. Observe syntax highlighting in the editor.

Expected Behavior:

• read(__E5) should have the same syntax coloring as other read(__Ex) expressions.

Actual Behavior:

• read(__E5) is displayed with incorrect or missing syntax highlighting.

Impact:

• Causes visual inconsistency in rule editing.
• May reduce readability and user confidence in rule correctness.

Notes:

• Parsing and execution logic appear to work correctly.
• The issue seems limited to editor syntax highlighting.

Attachments:

• Screenshot showing incorrect highlighting.