fix(kanban): reset code element background inside board

[liuguangyong93]

Problem

The Nous DS globals.css applies a global rule:

*::selection,
code {
  background: var(--selection-bg, var(--midground));
  @apply text-background;
}

This paints an opaque cream/yellow fill on every <code> element. The kanban dashboard drawer uses <code> tags to render:

• Event payloads (.hermes-kanban-event-payload)
• Run metadata (.hermes-kanban-run-meta)
• Worker log panes (.hermes-kanban-pre)

As a result, these sections display solid colored blocks that completely obscure the text content underneath.

Before

Event payloads and run history sections show opaque yellow/cream rectangles covering all text — completely unreadable:

After

Text is clearly visible with proper contrast against the dark background:

(Screenshots omitted from this PR — the fix is straightforward to verify locally.)

Fix

Add a scoped reset at the top of the kanban plugin stylesheet:

.hermes-kanban code {
  background: transparent;
  color: inherit;
}

This ensures <code> elements inside the kanban board inherit their parent's color and stay transparent, without affecting the DS selection/code styling elsewhere.

Testing

• Opened the kanban dashboard drawer on a task with events and run history
• Verified event payload text, run-meta, and worker log are all readable
• Confirmed no visual regression on other dashboard pages

[alt-glitch]

Duplicate of #20461 — same CSS fix (kanban <code> element background reset from Nous DS globals.css). #20461 is further ahead in review.

[teknium1]

Merged via PR #20687 (rebase-merge, commit 17687911). Your commit is on main with authorship preserved. Thanks — the diagnosis was exactly right: the Nous DS bare `code` rule was winning on specificity against every per-selector patch attempt. The scoped `.hermes-kanban code` override is the minimal root-cause fix, and it cascades to event-payload, run-meta, and markdown code in one rule.

#20687

[teknium1]

Your commit was cherry-picked to main via PR #20687 (commit 17687911) with your authorship preserved in git log. Closing this PR since the change is now on main — GitHub didn't auto-close it because the cherry-pick SHA differs from your branch commit, but git log main --author=liuguangyong shows your commit landed cleanly.

Thanks again for the root-cause diagnosis.