Describe the bug
I'm trying to implement shift function as described here: https://docs.helgoboss.org/realearn/further-concepts/mapping.html#conditional-activation
And my setup is following: I want to have undo/redo based on shift button.
So, shift button set parameter1, and it goes to "undo history". But it start to spam "undo history".
So, when I do Undo (one or several steps) and want to do Redo (Shift + Button) -> shift button starts to spam Undo history, and obviously truncates undo history, so I can't do Redo.

To Reproduce
Steps to reproduce the behavior:

1. Open "Undo history"
2. Map first button to Modify parameter1
3. Map second button to condition "parameter1" = off to Reaper action undo
4. Map third button to condition "parameter1" = On to Reaper action redo
5. Do so actions in DAW
6. Do several undo steps
7. Press first button, check that undo history truncated on last undoed step and other actions are not available anymore.

Expected behavior
Option to exclude internal ReaLearn parameters from history or any other solution that would not tamper history.

Screenshots

Desktop (please complete the following information):

• OS: Linux
• Version Mint 22.1
• Reaper 7.43

Additional context
Add any other context about the problem here.

===
I'm not very familiar with ReaScript, but possibly this could help
Lua example:

reaper.Undo_BeginBlock()
m = reaper.GetMasterTrack(0)
reaper.TrackFX_GetByName(m, "ReaEQ", 1)
reaper.Undo_EndBlock("Add ReaEQ FX to the master track", -1)