Thanks for the follow-up.
This question evolved out of this discussion:
As the OP there noted: “Thank you. I am aware of that. If I could do this with Apple Script I wouldn’t be using KM.”
A more nuanced response is that demonstrating the apparent bug in Applescript helped to isolate it to a DT3 issue rather than an issue with KM or some other non-DT3 problem.
In the larger picture, I think for many of us KM hits just the right sweet spot in terms of benefit from time invested. I spend a lot of time on the knowledge domain for which I use DT3. Applescript is a wonderful tool and I have used it when it is the only option; but it tends to take time and research to apply it to a new project. On the other hand, with KM the concepts generalize both elsewhere in DT3 and to other apps. I can go from idea to solution with KM very rapidly; Applescript usually takes a lot more time to figure out so to do an Applescript project just for me I may invest more time than the completed project would save me.
As I have mentioned before, I do think it would be immensely helpful to have a curated set of Applescript solutions on this Forum rather than randomly in the Discourse archives. Even better would be an entire book of examples of Applescript for Devonthink. For now, KM is just right as a tool to quickly make me more productive so I can focus more on my primary knowledge domain.