It's so the priorities appear at the beginning and are aligned nicely, like so:
If you have a way to have it render this way even if the priority is at the end of task, do let me know, and I'd be happy to consider switching to it.
I don't currently have a solution that'd let me switch to putting the priority attribute at the end, so this is very cool!
I can’t think of a clear use case for that, and I’m also not confident it would be supported by SB syntax now or in the future, so my answer would be no.
More broadly, though, in a system like SilverBuller where user code and libraries are such a central part of the experience, it’s easy for the ecosystem to drift into a state where individual libraries unintentionally account for only a subset of valid user syntax. Over time, this can create friction: users often need multiple libraries to accomplish what they want, only to discover edge cases, incompatibilities with base syntax, conflicts with other libraries, or assumptions about fixed attribute names, as a few examples. The result can be a fragmented, frustrating experience where limitations are learned only through trial and error.
I want to be clear that I’m not pointing to your libraries as an example of this. Quite the opposite. Your work demonstrates how far AI-assisted development can enable genuinely useful features and be amazingly helpful in short order! That said, the recent issue brought this broader ecosystem concern to mind, and I wanted to share the thought with the wider SB community.