Make Global Functions Non-Optional [AARD-1986]

[rutmanz]

Task

AARD-1986

Very small task to improve the typing on the Global_* functions

Symptom

Currently the Global_DoWhatever functions are typed as potentially undefined and require optional chaining (Global_DoWhatever?.(...)) whenever they're called. This is ugly and somewhat unintuitive because these functions are, in practice, always defined when they'd be called

Solution

I provided a default () => {} implementation so that they're always callable and don't include undefined in their type signature

Verification

Type checking handles most of it, and I ran synthesis and checked that toasts still worked (they did)

---

Before merging, ensure the following criteria are met:

• All acceptance criteria outlined in the ticket are met.
• Necessary test cases have been added and updated.
• A feature toggle or safe disable path has been added (if applicable).
• User-facing polish:
  • Ask: "Is this ready-looking?"
• Cross-linking between Jira and GitHub:
  • PR links to the relevant Jira issue.
  • Jira ticket has a comment referencing this PR.

[azaleacolburn]

lgtm

[BrandonPacewic]

Love stuff like this, nice clear win for the codebase.