Also some apps export Shortcut actions that can run in-app code: for example my Lunar app has an action that can help fixing arrangement when monitors flip around [1]
It's much easier to implement a struct for a Shortcut, than exporting AppleScript sdef files or creating IPC command-line tools, so a lot of apps take this route for code that needs access to the memory of the running app.
Being able to adjust my monitor brightness during the pandemic actively changed my quality of life for the better (I was in a small SF apartment).
That was also my pain point with Lunar, working on a small balcony in a small apartment where the light from the window was constantly changing and the monitor always being way too bright or way too dim.
I broke one of those LG monitor joystick OSD buttons before I got to building Lunar.
With Hammerspoon, you get Lua and direct macOS APIs, so you can push much further if you don't mind writing more glue code. If you care about serious Mac automation, you'll probably mix them and curse each one for a different reason.
Apple bought Workflow from DeskConnect (they may have bough the entire company).
I do. I completely left all of the automation options. I just use Swift and the private macOS APIs. Though, I will admit that there are still some things that Shortcuts can do that I have not found a to hack around in Swift. The difference is likely due to App Intents, which is big lame.