Syntax highlighting palette (five hues + comment + punctuation)

Approach

Authors the syntax token values into the same ThemeTokensConfig as WORK-200. The seven values are specified; verification work happens during the multi-language visual pass.

For the visual pass: pick representative snippets of real refrakt-relevant code:

• TypeScript: a plugin definition (heavy on imports, types, function calls)
• Python: a class with methods (different keyword/function balance)
• Markdown: a refrakt content file with frontmatter, headings, code fences
• JSON: a refrakt.config.json (mostly strings and structural punctuation)
• HTML: a snippet with attributes and tags
• Bash: a one-liner with strings and flags

Render each in both light and dark mode. Look for: any role that becomes invisible against the surface; any pair of roles that's hard to distinguish; any role that dominates visually.

If the teal-for-keywords choice looks off in practice, the SPEC-051 open question about swapping for #2c4a6e ink-blue is the agreed pivot — capture that decision in this work item's resolution rather than reopening the spec.