While I kind of see where you’re coming from, and also don’t disagree that sometimes what starts as a single note grows into a project or what you thought would be an entire project could actually just be wrapped up as a single note, I think it should be relatively rare (especially the latter). The problem with adding features to make this very easy is by providing extra menu items etc is twofold.
First, it causes bloat, extra menu items, extra buttons, larger contextual menu items etc. To prevent feature creep/bloat we have to put some bar up for how often it’s likely to be used to warrant the extra complexity it adds to the app. I don’t think this one makes it in that respect.
Second however, if we were to add such features we (as you already suggest) would make the distinction between projects and notes smaller and less well defined, which would lead to confusion for others, and especially new users, as to what we intend to be a note and what would be better of as a project. In fact, the Talk section of the community has already a number of topics discussing what the best setup would be for when to use categories, when to use projects, and when to use notes. And how much goes into a single note as well. The boundaries are already pretty loose, which is great because of the flexibility Agenda offers to build your own perfect system, but it does pose a bit of learning curve/trial-and-error for new users. We don’t want this to become even less clear by diminishing the boundaries even further. Hope this gives a bit more insights into our thoughts.