Command blocks fail to recognize their power state changed for 3 ticks

The bug

When any command block receives power, three ticks pass before it finally runs its command. When a repeating command block loses power, it continues to run commands for three ticks!

How to reproduce

1. Place a repeating command block: /setblock ~ ~1 ~ air
2. Place a chain command block following it: /say running
3. Place a redstone block on top
   → After a three ticks delay, "running" is printed three times.

Correct behavior: "running" should print once on the exact subsequent tick after the redstone block is placed.