This is really cool! I tried building something similar recently (with an LLM-based query parser), but you definitely executed it much better.
I immediately noticed some quirks in the parsing - for example: https://hippomaps.ch/?q=campsite+within+100+ft+of+a+mine+in+...
In that query, it should interpret "campsite" as (tourism=camp_pitch || tourism=camp_site), not camp_site alone, and "mine" as (industrial=mine || historic=mine), not minefield! (The camp_pitch vs camp_site distinction is very annoying and I wish those had better names.)