linux – Darktable 3.4 module order does not match that of pixelpipe

Darktable 3.4 manual states here:

Note: The order in which processing modules are executed exactly matches the order in which the modules appear in darktable’s user interface.

I deleted the ~/.config/darktable folder, restarted darktable, clicked “3.0” in “Module order”, and the order of the modules in the pixelpipe (history stack) and the UI are completely different, no mater which workflow is used. Clicking in the ‘i’ icon for resetting parameters made no difference.

Check here:

enter image description here

Am I doing something wrong, or this is a bug?