What is the bug or the crash?

Hello,

I have encountered a problem with how QGIS handles boolean fields in shapefiles (SHP) when upgrading from version 3.34.4 to 3.34.14.

Problem Description

QGIS 3.34.4 Behavior:

In version 3.34.4, boolean fields in my SHP layer were interpreted as text.
I was able to configure the field such that the "checked" state corresponded to "T" and the "unchecked" state to "F".
I built my layer's display rules based on these "T" or "F" values, which worked as expected.

QGIS 3.34.14 Behavior:

In version 3.34.14, QGIS now correctly recognizes boolean fields, but I no longer have the option to force the "checked" state to "T" or the "unchecked" state to "F".
As a result, my existing display rules based on "T" and "F" no longer work.

Question
Is there a way to configure the boolean field in QGIS 3.34.14 so that:

The "checked" state equals "T", and
The "unchecked" state equals "F"?
If not, is this change in behavior between the two versions intentional, or could it be a regression?

Steps to reproduce the issue

Create a shapefile (SHP) with a boolean field.
In QGIS 3.34.4, configure the field to map "T" for "checked" and "F" for "unchecked".
Define display rules based on these values.
Open the same SHP in QGIS 3.34.14 and try to replicate the same configuration.

I would expect the ability to customize the boolean field mapping (e.g., "checked" = "T", "unchecked" = "F") in QGIS 3.34.14, as it was possible in 3.34.4.

Versions

QGIS Version: 3.34.4 and 3.34.14

Supported QGIS version

• I'm running a supported QGIS version according to the roadmap.

New profile

• I tried with a new QGIS profile

Additional context

No response