Maybe if Magit contained the following form?

;;;###autoload
(autoload #'project-switch-project "magit")

i.e. autoloading an autoload :)

I have to correct you: their example is more about making sure Magit will be loaded so it configures project-switch-commands, before they call project-switch-project. And don’t “solve” it by just loading Magit on init. I suppose naively it could be solved with

 (autoload #'project-switch-project "magit")

and I’m not sure what’s the equivalent use-package expression. You have to be careful not to lose the usual guarantees of use-package wrt. graceful degradation (we don’t want an error “unknown file magit” – which is the whole point of use-package, otherwise you may as well just write the above form).

For what it’s worth, I collaborate with 1 other person, and for me it’d be sufficient if you simply alerted the user that someone else is currently editing the notes, locking them until the other user is done. What’s a much bigger problem is if someone edits the notes offline tries to sync them later!

I do collaborate on org notes with a partner! I agree with you that true simultaneous editing is unnecessary, but it’d be nice if the app flagged that someone else is currently editing the notes and locked them until the other person is done.