Utilizing the new utility script, call the same script from the Actions runs to ensure consistency between local and remote builds.
Note that the only one not connected right now is the Lychee step; there is a pre-existing action on Github that is used in the actions, so it is not necessarily the same call. However, we rely on the user as of now to download or install the lychee executable locally for themselves, so there are bound to be some differences there. It should provide enough consistency for now, and we can revisit it later if it becomes an issue.
Utilizing the new utility script, call the same script from the Actions runs to ensure consistency between local and remote builds.
Note that the only one not connected right now is the Lychee step; there is a pre-existing action on Github that is used in the actions, so it is not necessarily the same call. However, we rely on the user as of now to download or install the lychee executable locally for themselves, so there are bound to be some differences there. It should provide enough consistency for now, and we can revisit it later if it becomes an issue.