bug: eza punctuation color is nearly illegible in Storm

[ZeroKnight]

Did you check docs and existing issues?

• I have read all the tokyonight.nvim docs
• I have updated the plugin to the latest version before submitting this issue
• I have searched the existing issues of tokyonight.nvim
• I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)

N/A

Operating system/version

openSUSE Tumbleweed

Describe the bug

The color chosen for the Eza punctuation group in the Storm variant is currently set to #292e42 as shown:

tokyonight.nvim/extras/eza/tokyonight_storm.yml

Line 91 in 545d72c

punctuation: { foreground: "#292e42" }

For reference, this is the current bg_highlight color from the lua definition:

tokyonight.nvim/lua/tokyonight/colors/storm.lua

Lines 3 to 6 in 545d72c

	bg = "#24283b",
	bg_dark = "#1f2335",
	bg_dark1 = "#1b1e2d",
	bg_highlight = "#292e42",

I'm also using the Storm theme for Kitty, which is using the main background (#24283b) color:

tokyonight.nvim/extras/kitty/tokyonight_storm.conf

Line 9 in 545d72c

background #24283b

At least on my monitor, the above bg_highlight (and by extension, eza's punctuation) color on the bg color is almost completely illegible, to the point where it seems dubious to call it a "highlight". For example, consider the -> pointing to the symlink target or the - after the permission mask in the following eza output (aliased as ll):

---

Would it be possible to update punctuation to something lighter? say the current comment or dark3 color? Here's what they look like:

Steps To Reproduce

1. Use tokyonight_storm Kitty theme
2. Use tokyonight_storm Eza theme
3. eza -l some directory with a symbolic link

Expected Behavior

I should be able to clearly see the eza punctuation characters, like in the latter screenshot.

Repro

vim.env.LAZY_STDPATH = ".repro"
load(vim.fn.system("curl -s https://raw.githubusercontent.com/folke/lazy.nvim/main/bootstrap.lua"))()

require("lazy.minit").repro({
  spec = {
    -- add any other plugins here
  },
})