I suggest breaking up functionality into smaller functions and testing each function using Deno's in-built test runner. This might be overkill if the codebase doesn't need to be so robust.
Doing this and linking to this repo when creating a project will enable preview deployments to be automatically created upon each commit to a non-forked PR. This way, the behaviour of PRs and the main branch can be remotely validated.
It looks as though the numbered list within the "Technical Details" section of the README are meant to be linked to their respective sub-sections. However, they aren't. E.g. [⚡️ GitHub Action]. If I'm wrong, please close this issue.