Yay ;).
Did you have to type your devel-su password or your ssh password? The former should only be needed when pushing the patch to the device for testing. The latter is needed for every SSH connection, but there are ways to make the system remember the password (see here).
Well, it’s always just guessing. The only thing that changes with experience is that you get better at guessing :). That’s not a big problem though, because Patchmanager doesn’t actually change any files (it just “simulates” changes) so it’s hard(er) to accidentally break your system.
For the internals of the system? No, sadly not. If Jolla were to release everything under a Free Software license then people could step up and document things… Or did I misunderstand your question?
sailfish-patch always uses the current working directory. You can either put the script into a folder in your $PATH (like this), or you can run it using its full path (like /home/myname/Downloads/sailfish-patch), or you can copy/link the script as you did.
This sounds like a problem with Patchmanager. Maybe ask here?
But you don’t need that anyway. Just add this to your CONFIG file and sailfish-patch restarts it for you during development:
TestCommands:
- systemctl --user restart lipstick
Users also don’t have to use Patchmanager, they can use the “Utilities” settings page and select “restart homescreen” there.
Exactly, but you will need accounts on OpenRepos and for the Web catalog. The -Po command runs a wizard that guides you through publishing on OpenRepos, -Pm does the same for Patchmanager’s web catalog (the “m” stands for “manager”…).
Awesome, thank you so much 
!