highlight: bring pseudocode onto the measured palette

highlight.py was still carrying VS Code Dark+ (#c586c0 keywords, #4ec9b0 types,
#dcdcaa identifiers) — an entirely different colour system from the listing,
which moved to a measured palette in d1cfab2. Reading a function in split view
meant reading two unrelated themes side by side, with the same thing coloured
differently in each pane.

Same palette in both panes now, so one hue means one thing everywhere: a string
is #9ece6a and a symbol #7aa2f7 whether you're in disassembly or pseudocode.

Contrast against the app background #12161c, signal 7:1+ and structure 3-4:1:

  keyword (control) #e8ecf2 15.3   operator/body   #c3cad3 11.0
  string            #9ece6a  9.9   number          #d8a657  8.2
  type/builtin      #93aee0  8.1   name            #7aa2f7  7.2
  comment           #7c8b9e  5.2   punctuation     #626c7a  3.4

Control keywords take the brightest NEUTRAL rather than a hue, mirroring the
mnemonic column: they're the skeleton you scan for, and a hue there would claim a
meaning the rest of the palette already assigns. Punctuation drops from grey70 to
3.4:1 — it was competing with the code it delimits.

Suite 192/0.

0 files changed, 0 insertions, 0 deletions