Yes, it is clearly a bug or an oversight.
It never being true is clearly not something that should be happening when there the variable has an optionable value.
On top of that, there is no ambiguity when comparing an optionable variable to true like such since you aren’t fetching its value. It’s not like true could be confused for option{true}.
Let’s hope a dev will show up here. I’ve come across a fair amount of inconsistent things while using Verse and fixing issues such as this one would be a first step to making writing code in Verse a much more enjoyable experience for me (and others) who are used to some things that don’t work in Verse working in other more popular languages.