Answer
This has been confirmed as a genuine bug specifically affecting date-arithmetic expressions built on Context Substitution Values inside a Lobby datasource's WHERE clause — check whether your current release already includes the fix (addressed starting around the 25R1 early-access track) before spending more time adjusting the expression syntax itself, since the same value used without arithmetic, or the equivalent computed via a database function call, works around the underlying issue in the meantime.