red 62 red 63

[afostr]

No description provided.

[linear]

RED-63 Fix issues with isNodeOutOfRoationBounds

ISSUE SUMMARY:

The naming of this function is leading to confusion in its usage. It sounds like this would return true if a node was rotating in/out, but it actually returns false in this case. We need to refactor this to use a clearer name and update existing references that may be using the negated expected value.

---

ISSUE REPRO STEPS:

<HINT: Add steps to list as-needed. If interaction is complex, add screenshots or a Slack screen-capture video (just drag and drop)>

1. <<TODO: Replace with repro step Bump the npm_and_yarn group across 1 directory with 5 updates #1>>
2. <<TODO: Replace with repro step BLUE-2: fix: receipt generation in case of challenge #2>>
3. Observe <<TODO: Describe unintended behavior.>>

---

EXPECTED RESULT:

<<TODO: Replace this with your expected results.>>

---

MERGE REQUESTS:

<HINT: If your fix requires changes in multiple repos, add the following info per-repository.>

<<TODO: Enter Repository Name>>

Pull Request Link: <TODO: Insert PR-Link>

GPT Review Link: <<TODO: Insert GPT-Review-Link>>

Jenkins Test Link: <<TODO: Insert Jenkins Test Job Link>>

---

ADDITIONAL INSTRUCTIONS:

<HINT: Add any additional instructions needed for the assignee. If you have specific requirements for how the task should be implemented or fixed, enter them or link them here.>

<<TODO: Insert additional instructions for assignee.>>