jab diff:/commit: --color showed no change highlighting — only flat +/-
fg lines, with word-merged text garbled — while be shows a word-level
background wash. The 2-bit diff side in each tok32 (eq/in/rm) was ignored by
the renderer jab used. Fix: port bro's two-pass side→bg renderer into
view/bro.js (the ONE JS impl) and route both jab colour edges through it;
retire the duplicate C HUNKu8sFeedColor diff branch and the hd.color() use.
jab commit:?<sha> --color vs be commit:?<sha> --color — jab fg
+/- with merged-text garble; be a red/green word-level bg wash.--plain was already byte-identical (LineBased).bro/BRO.c bro_cell_ansi (be, correct), C
HUNKu8sFeedColor diff branch (fg, used by jab via hd.color), JS
view/bro.js cellSGR (pager, diff side EQ-only), JS hd.color (dump).diff:/commit: --color byte-matches be --color (bro) for the
diff: view (single-file + hermetic whole-tree).bro/BRO.c), ONE JS impl (view/bro.js).hd.color).--color oracle flipped graf → be (bro).--color body byte-matches be); bro/BRO.c calls the
libdog copies (no dup). Built jab/be/graf/bro; 472/472 C tests, 20/20 JS.diff:?<range> over the journal store still diverges (jab emits
the test submodule recursion in a different order) — PRE-EXISTING diff.js
issue, reproduces in --plain too; out of scope here. Own ticket TBD.+/- branch) and JS-2
(hd.color for diff hunks) retired.e5cf0fdd, beagle b14b895d, dog 1be9e26c, jab 842b342.