matchSaturation inconsistencies between light/dark modes when using harmonizeWithPrimary

[nxoim]

The primary color is different in light and dark modes, which causes the harmonized tone to be a little different. I am unsure whether that is actually a feature, but it can cause unintentional inconsistencies. This can be fixed by getting a static tone from the color scheme (for example, the primary 50 tone) but google's tonal palette tools are internal to the m3 library, but this can be done on android using colorResource(android.R.color.system_accent1_500) (assuming its the theme's base color) OR when using material kolor's color scheme

[nxoim]

Just realized google has further advanced the idea of fixed accent colors, however I do not see them in the material3 library and it's unclear whether they are going to be added at all. If they do - fixed primary should be used for harmonization