Many times players like to use this command
execute as @a[scores=\{Trigger=.. -2147483647}] at @s run say 1
execute as @a[scores=\{Trigger=1..}] at @s run say 1
execute as @a[scores=\{Trigger=.. -2147483647}] if entity @s run scoreboard player enable @s Trigger
execute as @a[scores=\{Trigger=1..2147483647}] if entity @s run scoreboard players enable @s Trigger
Not resident
scoreboard player enable @a Trigger
Because it doesn't require conditions, many commands trigger sometimes, and you don't want players to use the Trigger command when they don't need to

And "/trigger add 0" and "/trigger set 0" obviously shouldn't exist, which increases the uncertainty of the command and sometimes allows the player to exploit the instructions with little to no solution to the instructions

It is also recommended to add a command to disable the scoreboard players enable trigger, which is much better than deleting the scoreboard directly

What I expected to happen was...:
Trigger add 0 and trigger set 0 are no longer viable