Configuration file doesn't change font colors on Quartz 5 installation

Describe the bug Following the steps to do an upgrade of my digital garden I've run into a bug where no matter what values I set for the theme colors, it will always default to a white font color and ignore the settings in the quartz.config.yaml file.

To Reproduce Steps to reproduce the behavior:

1. Follow the steps listed for Migrating from v4 to v5 in the documentation
2. When prompted for template select obsidian
3. Finish installing and updating dependencies
4. Build and serve using npx quartz build --serve
5. Open a browser to the localhost address
6. Font color will not match the settings specified in the quartz.config.yaml file

Expected behavior All of the CSS values specified in the quartz.config.yaml file should be reflected on the site.

Screenshots and Source Here is an image of my existing site running Quartz 4 (neoncrypt.garden):

Here is the same content with the same font colors added in quartz.config.yaml, but the font color remains incorrect:

1. providing a simple reproduction
   • There are some interesting behaviors with this bug when disabling community plugins, the details are below in the comments
2. linking to your Quartz repository where the problem can be observed
   • Will add a link momentarily, gotta clean up all those juicy commented out lines of nonsense I've scribbled in places
   • Repository Link

Desktop (please complete the following information):

• Quartz Version: v5
• node Version: v24.18.0
• npm version: 11.16.0
• OS: Windows 11
• Browser: Occurring in both Firefox & Chrome, even in incognito modes

Additional context Typescript isn't exactly a familiar language for me, so forgive the following observations if they end up being irrelevant:

• componentResource.ts has a lot of CSS processing, but its hard for me to follow how its creating these style sheets. I'm wondering if maybe a preset for obsidian projects is overriding the custom CSS in the quartz.config.yaml when the build process happens.
• The function joinStyles in theme.ts seems to our understanding to join all of the CSS together based on how its placed into the string[], but does the order of the strings in the array matter? If it does then it could be worthwhile to examine the usage of joinStyles in componentResource.ts to see if that arrangement is causing this issue