if (foo == true) { // checking foo is true (rocketship emoji)
    20 lines of code;
  } else {
    the same 20 lines of code with one boolean changed in the middle;
  }

Description:

(markdown header) Summary (nerd emoji):

This PR fixes a non-existent issue by adding an *if statement** that checks if a variable is true. This has the following benefits:

  - Improves performance (rocketship emoji)
  - Increases code maintainability (rising bar chart emoji)
  - Helps prevent future bugs (detective emoji)

(markdown header) Conclusion:

This PR does not just improve performance, it fundamentally reshapes how we approach performance considerations. This is not just design --- it's architecture. Simple, succinct, yet powerful.

The clearly LLM PRs I receive are formatted similarly to:

    ## Summary
    ...

    ## Problem
    ...

    ## Solution
    ...

    ## Verification
    ...

They're too methodical, and duplicate code when they're longer than a single line fix. I've never received a pull request formatted like that from a human.