I get what you are saying, but then the definition of done is confusing. Maybe it would be better to class Phase 1 (MVP) as done as there is more to be completed in phase 2 (build in user feedback) or mark it as done when the feedback loop is implemented?
It’s the same as when payments was implemented. It was marked as done but I would have classed the implementation as a very bare MVP. So it would be good to know where on the roadmap the next iteration would be.
I think it is great you have an open roadmap. But it can also have an adverse effect in scenarios like the above. In the old world an item marked done generally meant it was unlikely to be touched again. So seeing an item as done when it is know to not be fully complete can raise the concern it will remain that way.